VirusTotal
14 / 89
trezou-iostre-us.netlify.app returned an HTTP 404 status on 2026-10-03, documenting that the requested page was not found at that time. Google Safe Browsing flagged the domain for social engineering on 2026-09-17, which is a notable security-related observation.
Google Safe Browsing flagged trezou-iostre-us.netlify.app for social engineering on 2026-09-17. VirusTotal recorded 14 detections out of 89 scanners on 2026-09-17. The domain was internally listed by PhishDestroy as of 2026-10-05. PageSpeed measured a performance score of 100 on 2026-09-15. The SSL certificate was issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1 and scanned on 2026-09-15.
The Google Safe Browsing and VirusTotal records provide distinct security-related observations, while the HTTP 404 status documents a specific response on a separate date. The internal PhishDestroy listing and performance measurement add further context to the domain's recorded activity. These dated records allow for comparison of technical and security observations without implying any broader conclusions.
Further review of trezou-iostre-us.netlify.app should reference Google Safe Browsing and VirusTotal records for security context. Preserve the internal PhishDestroy listing and HTTP response for ongoing comparison. Retain all dated source records to support future monitoring or investigation of the domain.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
NetlifyScanner note: http_other: raw=http_404; http=404; via=http_proxy; server=Netlify
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478netlify.appSaved 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 trezou-iostre-us.netlify.app · checked Sep 15, 2026
11 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.
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