VirusTotal
2 / 89
crypto-nmf.netlify.app returned an HTTP 404 status code on 2026-10-01, a recorded response from that date's HTTP check. The same domain was first observed on 2026-09-08, the date of its earliest recorded observation in this evidence set.
An HTTP check recorded a 404 status for crypto-nmf.netlify.app on 2026-10-01. External blocklist checks on 2026-10-02 named MetaMask, ScamSniffer, and SEAL, giving an external blocklist count of 3. VirusTotal reported 2 detections across 89 scanners on 2026-09-16. The phishdestroy internal listing was recorded as present, and the SSL scan on 2026-09-08 named DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1.
The named blocklists and the VirusTotal scanner results describe separate source observations, each with its own scope and measurement method. The HTTP 404 record describes only the response captured on its check date, not all content that may exist on the domain. The 2026-09-08 first observation and the later checks fall on different dates, so the records can be compared as dated snapshots rather than as a single measurement.
For crypto-nmf.netlify.app, preserve the MetaMask, ScamSniffer, and SEAL blocklist records alongside the phishdestroy internal listing for later comparison. Retain the HTTP check record and the VirusTotal scanner results as separate source documents, and compare each against future checks of the same source. Keep the SSL scan record with its named issuer for reference when reviewing the domain's recorded history.
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-nmf.netlify.app · checked Sep 8, 2026
63.176.8.218. 14 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