Security engines reporting a detection: 6. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
The domain trezor.support was observed hosting a page titled "Trezor Hardware Wallet (Official) | Bitcoin & Crypto Security," a clear indication of brand impersonation targeting the Trezor hardware wallet. Registration was handled by Name.com, Inc., and the domain resolves to the IP address 172.66.137.111, which belongs to AS13335 Cloudflare, Inc. in the United States. The domain’s authoritative name servers are ns4lrt.name.com, ns1dnx.name.com, ns3bgq.name.com, and ns2fgv.name.com, all of which are typical of Name.com’s DNS infrastructure. No SSL certificate is present, meaning HTTPS connections are not established for the site.
VirusTotal analysis shows that three of ninety‑five scanning engines flagged the domain, and it appears on two security blocklists. Additional reputation services have marked the site as malicious: PhishDestroy and Enkrypt have blocked it, while Gridinsoft assigns a trust score of zero out of one hundred. The site’s current status is offline, indicating that the malicious content has been taken down or the hosting has been terminated.
Despite the takedown, the observed infrastructure—Cloudflare‑backed IP, Name.com registration, and lack of TLS—provides a reproducible pattern for future impersonation attempts. Defenders should continue to monitor the domain for re‑registration, enforce blocking of the IP address and associated name servers, and add trezor.support to threat intel feeds. Organizations using Trezor products should alert users to verify URLs and avoid entering credentials on sites lacking proper TLS certificates, especially those presenting the exact brand name in the page title without official endorsement.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='trezor.support', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 29, 2025
DOM Analysisanalyzed Mar 11, 2026score 10/1002 brand signals
Submitted URLhttp://trezor.support/
Favicon Hash
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:25:11 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-15 22:18:13 UTCcurrent episode first observed: 2026-10-01 16:16:25 UTCobserved RIP window: 2026-09-15 22:18:13 UTC → 2026-10-01 16:16:25 UTC · 377.97hmidpoint estimate ≈ 2026-09-23 19:17:19 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-11 22:18:03 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-10 22:50:51 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-03-10 02:12:18 UTC
VirusTotal scanner detections updated from 3 to 5. Added scanner alerts: CyRadar, SOCRadar.
17 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
trezor.support detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Feb 21, 2026
Time to First Unavailability
4798 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
3 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · trezor.support
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches8
Same favicon hash or the same page title as this host.
(SE)
