VirusTotal
4 / 89
The domain crypto-i7t.netlify.app returned HTTP status 404 on 2026-10-01, per the recorded HTTP check. A PageSpeed observation on 2026-09-08 recorded a performance score of 100 for the same hostname.
The VirusTotal scan on 2026-09-16 recorded 4 detections across 89 scanners. External blocklists MetaMask and SEAL were noted as of 2026-10-01. The SSL certificate, scanned on 2026-09-08, was issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1. The domain was first observed on 2026-09-08.
The VirusTotal and HTTP observations carry different dates, so their results describe separate moments rather than one continuous state. The MetaMask and SEAL entries and the SSL observation are recorded alongside the PageSpeed result, but these sources do not share a common collection date. Comparing them requires treating each dated record as a snapshot rather than a current condition.
Reviewers should retain the dated records for crypto-i7t.netlify.app, including the HTTP 404 and VirusTotal results, as a baseline for later comparison. Any subsequent checks should be logged with their own dates so changes can be measured against the 2026-09-08 and 2026-10-01 observations. During review, avoid submitting sensitive information to the domain until its status is independently verified.
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 crypto-i7t.netlify.app · checked Sep 8, 2026
35.157.26.135. 13 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.
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