VirusTotal
1 / 92
“Google”
swap-y3v6.vercel.app returned HTTP status 404 when checked on 2026-10-01, according to the recorded HTTP observation. The same record notes the domain was first observed on 2026-08-26, giving a dated starting point for later comparisons.
The HTTP check on 2026-10-01 recorded status 404, while the page speed check on 2026-09-03 recorded a performance score of 100. VirusTotal, checked on 2026-09-04, reported 1 detection across 90 scanners. The external blocklist count was 2 on 2026-10-01, listing MetaMask and SEAL, and the internal listing was recorded as true.
The MetaMask and SEAL blocklist entries and the VirusTotal result come from different dates, so their observations cannot be treated as a single snapshot. The HTTP 404 on 2026-10-01 and the page speed score on 2026-09-03 describe separate checks, and the first observation on 2026-08-26 predates both. These dated records allow comparison of what each source reported at its own check time.
Reviewers should retain the dated records for swap-y3v6.vercel.app so later checks can be compared against the 2026-08-26 first observation and the 2026-10-01 HTTP result. Any new observation should be matched to the same source and date before conclusions are drawn. During review, avoid submitting sensitive information to the domain until its status is independently confirmed.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
VercelScanner note: redirect: raw=redirect_308; http=308; via=http_proxy; location=https://swap-y3v6.vercel.app/; server=Vercel
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093Saved 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 swap-y3v6.vercel.app · checked Sep 3, 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.
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