VirusTotal
6 / 89 engine detections
Apri il rapporto“Trezor Hardware Wallet (Official) | Bitcoin & Crypto Security”
trezor.support — Contenuto non disponibile. Simulazione del marchio: Trezor; Tipo di truffa: Crypto Scam. Riepilogo delle prove: VirusTotal 6/89 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, LevelBlue); Spamhaus DBL_PHISH; 1 external blocklist match (Enkrypt); PhishDestroy score 85/100. Registrar: Name.com.
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
6 / 89 engine detections
Apri il rapportoDBL_PHISH
no community references
Apri il rapportoprovider verdict: clean
Apri il rapportoNo threat flag
Apri il rapportoNo malicious flag
Apri il rapportoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
Last checked
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.
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.
La reputazione Edge-IP non è attribuita a questo dominio.
ns2fgv.name.comLocation describes the IP network.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
trezor.support
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Sconosciuto→dns_inactive
dns_nxdomain
Non disponibile→Raggiungibile
Raggiungibile→Non disponibile
3→5
audit_replace→https://radar.cloudflare.com/scan/16eeabf2-d936-4430-bef3-6c32fc0a03ce
6/89 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcetrezor.support
View source74 domini simili memorizzati
1 segnalazione della comunità
CategoriaPHISHING
Automated report created via SEAL 911
Segnalato da 1 membro della comunità; prima osservazione il 29/08/2025
“Automated report created via SEAL 911”
Listed domains receive at least one abuse report; this entry has no retained notification history.
Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.
Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
trezor.support)Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analisi delle minacce utilizzando blocklist archiviate, WHOIS, DNS e prove di scansione pubblica
Scansiona oraSegnala i domini sospetti al nostro database delle minacce — proteggi la comunità
SegnalaSegnalazioni recenti di phishing e modifiche osservate della disponibilità
MonitoraControlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.