VirusTotal
8 / 89
“Suspected Phishing | Cloudflare”
On 2026-10-01, access-trezz-io-en-hrd.pages.dev returned an HTTP 403 status during a recorded check. The same date's blocklist check placed the domain in the PhishDestroy catalogue, which is the only listing recorded in this evidence set.
The first observation of access-trezz-io-en-hrd.pages.dev was recorded on 2026-08-09. An SSL scan on 2026-09-13 showed a certificate issued by Google Trust Services / WE1. VirusTotal, checked on 2026-09-13, reported 8 detections across 89 scanners. The IP address 188.114.97.9 was associated with CloudFlare, Inc. and located in CA.
The PhishDestroy listing and the HTTP 403 response both carry a 2026-10-01 date, while the SSL scan and VirusTotal results are dated 2026-09-13. Because these sources observed the domain on different dates, a reader can compare what each service recorded at its own point in time. The 2026-08-09 first observation predates all of them, so it marks the earliest recorded point rather than a current state.
Retain the dated records for access-trezz-io-en-hrd.pages.dev, including the HTTP status, catalogue listing, SSL scan and VirusTotal result, so later checks can be compared against them. When reviewing access-trezz-io-en-hrd.pages.dev, avoid submitting passwords, payment details or other sensitive information. Compare any subsequent observation with these stored dates and values to see what has changed.
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.
a7ffbdcfe9663441b3bb674855229274250c4b928dcc060796a3f4f6b2ca4985Saved 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, 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