VirusTotal
13 / 89
“404: NOT_FOUND”
nfyenkryj6v4oeqwluc.vercel.app returned an HTTP status 404 when checked on 2026-10-01, meaning no content was served at that recorded request. The same domain also appears in the PhishDestroy internal listing, a publisher-owned catalogue entry.
The domain was first observed on 2026-09-13. An SSL scan on 2026-09-19 recorded the issuer as Google Trust Services / WR1. VirusTotal reported 13 detections across 89 scanners on 2026-09-21. The PhishDestroy internal listing was recorded, and a blocklist check occurred on 2026-10-03.
The HTTP 404 describes only the response recorded on 2026-10-01, not the domain's content at other times. The VirusTotal detection count and the PhishDestroy internal listing are separate source observations with their own dates, so they should not be merged into a single trend. The first observation and SSL scan dates place the domain in a monitored window, but each record stands alone.
For nfyenkryj6v4oeqwluc.vercel.app, preserve the PhishDestroy internal listing and the VirusTotal scan as separate records for later comparison. Compare the recorded HTTP response with any future checks to see whether the status changes. Retain the first observation and SSL scan entries so the timeline remains complete.
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.
9 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