VirusTotal
2 / 92
“404: NOT_FOUND”
dapp-zwy6.vercel.app returned HTTP status 404 when checked on 2026-10-01, a dated response that does not establish present availability. The domain was first observed on 2026-08-28 and appears on the phishdestroy internal listing.
The external blocklist count was 2 on 2026-10-01, naming MetaMask and SEAL. VirusTotal recorded 3 detections across 89 scanners when checked on 2026-09-08. The HTTP check on 2026-10-01 returned status 404. The domain resolved to IP address 64.29.17.3, associated with Vercel, Inc in the US. PageSpeed recorded a performance score of 100 on 2026-09-06.
The MetaMask and SEAL listings and the phishdestroy internal listing are dated records that can be compared with the VirusTotal result from 2026-09-08 and the HTTP response from 2026-10-01. Because these observations fall on different dates, a later check may not reflect the same conditions as an earlier one. The PageSpeed score from 2026-09-06 describes a separate measurement occasion.
Retain dated copies of each observation for dapp-zwy6.vercel.app, including the blocklist checks, VirusTotal result, and HTTP response, so later comparisons use the same source values. Compare subsequent checks against these recorded dates rather than assuming continuity. Avoid submitting sensitive information while reviewing the domain.
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://dapp-zwy6.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 dapp-zwy6.vercel.app · checked Sep 6, 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.
79 stored lookalike domains
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