VirusTotal
16 / 89
“404: NOT_FOUND”
boiwithyew.vercel.app returned an HTTP status 404 on 2026-10-01, as recorded during the most recent HTTP check. The domain is also listed in the PhishDestroy internal catalogue, which is maintained by the publisher.
The HTTP check on 2026-10-01 recorded a 404 response for boiwithyew.vercel.app. VirusTotal reported 16 detections out of 89 scanners on 2026-09-17. The domain appears in the PhishDestroy internal listing. PageSpeed recorded a performance score of 100 on 2026-09-15. The domain was first observed on 2026-09-06.
Each source provides a distinct observation about boiwithyew.vercel.app. The HTTP status 404 reflects only the response on the date of the check. VirusTotal’s detection count and scanner total are limited to a single scan, while the PhishDestroy entry indicates the domain’s inclusion in a publisher-managed catalogue. The PageSpeed score and first observation date supply additional context but do not indicate current content or use.
Review the HTTP check and VirusTotal scan results for boiwithyew.vercel.app as separate records. Retain the PhishDestroy listing for reference and compare it with the VirusTotal report for consistency. Conduct a new HTTP check for boiwithyew.vercel.app and keep the result with previous findings.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
VercelScanner note: alive_content: raw=content_403; http=403; via=https_direct; 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 boiwithyew.vercel.app · checked Sep 15, 2026
10 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