Security engines reporting a detection: 16. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ywjvqj-3hg2ysgb.vercel.app returned HTTP status 404 in an HTTP check dated 2026-10-01. The same domain was first observed on 2026-09-02, and it appears on the phishdestroy internal listing.
Recorded Evidence
An HTTP check on 2026-10-01 recorded status 404 for ywjvqj-3hg2ysgb.vercel.app. The domain was first observed on 2026-09-02. A blocklist check dated 2026-10-01 found two external blocklist entries, named MetaMask and SEAL. VirusTotal, checked on 2026-09-13, reported 16 detections across 89 scanners. The domain resolved to IP address 64.29.17.3, associated with the United States and Vercel, Inc.
Interpretation
The recorded HTTP 404 describes only the response captured on that check date, not the domain's content or status at other times. The blocklist entries named MetaMask and SEAL and the phishdestroy internal listing are separate source records, each reflecting its own listing decision rather than a shared finding. The VirusTotal detection count and the blocklist entries come from different sources and different dates, so they should be read as distinct observations rather than combined into one conclusion. The gap between the first observation and the later checks shows the domain was recorded across more than one date, but the available records do not establish what changed between them.
Recommended Actions
Preserve the HTTP check record for ywjvqj-3hg2ysgb.vercel.app and the phishdestroy internal listing as separate items for later comparison. Keep the MetaMask and SEAL blocklist entries alongside the VirusTotal record so each source can be reviewed on its own. Compare these records against future checks of the full domain ywjvqj-3hg2ysgb.vercel.app rather than relying on any single source. Treat the recorded HTTP response as one observation and verify current behavior directly before acting on it.
Detection-evasion analysis
Cloaking suspected: scanner and visitor titles differ
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 10:06:30 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 10:06:30 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Last analyzed First positive detection Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Netcraft
OpenPhish
Sophos
VIPRE
Webroot
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-10-09 01:25:32 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-13 10:00:24 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-13 09:33:14 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
ywjvqj-3hg2ysgb.vercel.app detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
4 evidence signal groups linked0 reports recordedReachable · access restricted
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · ywjvqj-3hg2ysgb.vercel.app
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches8
Same favicon hash or the same page title as this host.
(US)
