VirusTotal
4 / 89
crypto-car.netlify.app returned HTTP 404 on 2026-10-01, a dated status recorded during the HTTP check. The same domain was first observed on 2026-09-08, according to the recorded timeline.
The VirusTotal scan on 2026-09-16 recorded 4 detections across 89 scanners. MetaMask and SEAL each listed the domain on the external blocklists checked 2026-10-01, and PhishDestroy's internal listing was also true. The SSL certificate, scanned 2026-09-08, was issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1. The page performance score on 2026-09-08 was 100.
The MetaMask and SEAL listings were checked on 2026-10-01, while the VirusTotal scan occurred on 2026-09-16, so those observations reflect different points in time. The HTTP 404 was recorded on 2026-10-01, distinct from the first observation on 2026-09-08. Because the dates differ, the records cannot be treated as a single simultaneous snapshot.
Reviewers should retain the dated records for crypto-car.netlify.app, including the MetaMask and SEAL listings and the VirusTotal scan, so later observations can be compared against them. Any subsequent checks should be logged with their own dates rather than merged with earlier results. During review, avoid submitting sensitive information to the domain until the records are 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-car.netlify.app · checked Sep 8, 2026
63.176.8.218. 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