VirusTotal
11 / 89
“Suspected Phishing | Cloudflare”
The domain access-trazorbrz.pages.dev returned an HTTP 403 status during an HTTP check on 2026-10-01. Separately, the domain was first observed on 2026-08-09, and it appears in the PhishDestroy internal listing.
An HTTP check on 2026-10-01 recorded status 403 for access-trazorbrz.pages.dev. The domain was first observed on 2026-08-09. VirusTotal, checked on 2026-09-13, reported 11 detections across 89 scanners. An SSL scan on 2026-09-13 recorded the issuer as Google Trust Services / WE1. The PhishDestroy internal listing records the domain as listed.
The HTTP 403 record describes only the response returned on the date checked, not the domain's content or present availability. The VirusTotal and PhishDestroy entries reflect separate evaluations made under their own criteria and timing. Because the first observation and the HTTP check fall on different dates, the chronology shows only that the domain was recorded before the later check, not that its behavior changed.
For access-trazorbrz.pages.dev, preserve the HTTP response record, the VirusTotal result, and the PhishDestroy listing as separate items. Compare those source records against one another rather than merging them into a single conclusion. Retain the first-observation and SSL scan records for later reference, and re-check the domain's HTTP response before acting on any single record.
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.
Location describes the IP network.
ee8106ab5d007ec2fc08336f089d42790d70d654d0749b281fd8511b41e7a2ecSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
7 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.
142 stored lookalike domains
Showing 100 of 142
1 community report
CategoryIMPERSONATION
Brand abuse: impersonation, fake affiliation, 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