Cloudflare Radar
Suspicious
Open report“trezorinspect.io”
Suspicious
Open report0 / 92 engine detections
Open reportno community references
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has flagged trezorinspect.io as a suspicious domain based on internal monitoring. The domain was first observed by PhishDestroy on 2026-10-20. No page title was recorded, and the site was examined by VirusTotal and Google Safe Browsing on 2026-10-20.
Suspicious domains may be used to host phishing pages, lure users into credential entry, or distribute malicious content, but the current listing does not confirm any particular activity. Without a recorded page title or observed behavior, the exact mechanism cannot be determined.
VirusTotal scan on 2026-10-20 (analysis date 2026-10-18) returned 0 detections out of 92 engines. Google Safe Browsing check on 2026-10-20 reported the domain as not flagged. External blocklists MetaMask and SEAL listed the domain, with a total of 2 external listings as of 2026-10-20. PhishDestroy’s internal blocklist includes the domain as of 2026-10-20, and OTX reported zero pulses on the same date.
The recorded IP address for trezorinspect.io is 104.21.31.167. No additional registration or hosting details are available beyond this address.
Users who have not entered credentials or granted wallet permissions can consider the site benign but should remain vigilant for unsolicited requests. If any credentials or sensitive information were submitted, change those credentials immediately and monitor associated accounts for unusual activity. Defenders should add trezorinspect.io to blocklists or monitoring rules and review access logs for any connections to the recorded IP.
Last checked
Edge-IP reputation is not attributed to this domain.
ezra.ns.cloudflare.commx2.netim.netpriority 10mx1.netim.netpriority 10Location describes the IP network.
04b5a5ae30f42cf0d33f132f8b13addf8fc525f63bab98616493dd81e8e775efSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of trezorinspect.io · checked Oct 20, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://trezorinspect.io/https://trezorinspect.io/Content-Type: text/html; charset=UTF-8Server: cloudflareX-Powered-By: PHP/8.5.4Cache-Control: no-store, no-cache, must-revalidateCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400no-store, no-cache, must-revalidateDYNAMICa4d84bb7bd3fd700-IADkeep-alivegziptext/html; charset=UTF-8Tue, 20 Oct 2026 13:16:13 GMTtrezorinspect.io{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=%2FupguSODiUX%2FQdmsX1mGr2sCdR3p9PCuoEiwGM7Yx0znzyMFfb%2FENeYseAsB3SC49FNhu0QeffPgw2L9JsZAC%2FI6Ea5ZAOl4k%2FyLGSPH2l2D%2F6DwGwb%2BkSwM8qq6yxT9FcloudflarecfCacheStatus;desc="DYNAMIC"chunkedaccept-encodingPHP/8.5.4Values retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
No threat flag
View source0/92 engine detections
View sourcetrezorinspect.io
View source74 stored lookalike domains
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
trezorinspect.io
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
trezorinspect.io)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.