VirusTotal
6 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Trezor @Wallet* | us”
Assessment based on the stored source evidence below. Review sources →
No stored capture is available for this domain.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
6 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
DBL_ABUSED_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
The domain treeeziorrrrwleeett.gitbook.io returned HTTP status 403 in a check dated 2026-10-01. Separately, the PhishDestroy internal listing records this domain, and its earliest observation is dated 2026-09-16.
A VirusTotal scan on 2026-09-23 reported 6 detections across 89 scanners for treeeziorrrrwleeett.gitbook.io. The SSL scan on 2026-09-21 identified the issuer as Google Trust Services / WE1. The HTTP check on 2026-10-01 recorded a 403 response, and the PhishDestroy internal listing marks the domain as listed.
The HTTP response, VirusTotal scan, SSL scan and PhishDestroy listing each describe a different measurement of treeeziorrrrwleeett.gitbook.io. Because the dates span from 2026-09-16 to 2026-10-01, a reader can compare the records chronologically without treating any single source as a verdict. The 403 response describes only the recorded request, not all content on the domain.
Preserve the VirusTotal scan record and the PhishDestroy internal listing for treeeziorrrrwleeett.gitbook.io as separate source artifacts. Compare the HTTP check record with the PhishDestroy listing when reviewing the domain, and retain the SSL scan record for traceability. Review each source record individually before drawing further conclusions about treeeziorrrrwleeett.gitbook.io.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Provider response during scan: cloudflare_phishing_interstitial
Edge-IP reputation is not attributed to this domain.
hugh.ns.cloudflare.comLocation describes the IP network.
f3e0d20bcdcb0f6afa89f62c0f4ef0ea0ddd7a7445d5cc7ae8b2e212568ea348gitbook.ioSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
74 stored lookalike domains
1 community report
CategoryIMPERSONATION
Brand abuse: impersonation, impersonating Trezor
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
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