On 2026-10-01 te19fgy1vslruxbkt8h.vercel.app returned HTTP 404, and the domain was first observed on 2026-09-14. A separate check on 2026-10-01 recorded IP address 64.29.17.3 in the US under Vercel, Inc.
Recorded Evidence
The PhishDestroy internal listing for te19fgy1vslruxbkt8h.vercel.app was recorded as present on 2026-10-01. VirusTotal recorded 15 detections across 89 scanners on 2026-09-22. The first observation of the domain was logged on 2026-09-14.
Interpretation
The HTTP 404 describes only the response recorded on 2026-10-01, not all content that may exist on the domain. The PhishDestroy listing and the VirusTotal scan are separate source records, and their different dates do not by themselves show a change in the domain's status. The IP record and the HTTP response were captured on the same date, but a shared date does not establish that the two measurements were simultaneous or directly comparable.
Recommended Actions
For te19fgy1vslruxbkt8h.vercel.app, preserve the HTTP 404 record and the VirusTotal scan results as separate items for comparison with later checks. Retain the PhishDestroy internal listing entry alongside those records. Compare the PhishDestroy listing against the VirusTotal record in future reviews, and compare the HTTP response record against later observations of the same domain.
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.
Primary outcomeReachable but protectedreason: HTTP access restricted50% confidence
Attributionmechanism: Access Restrictionsource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: StaleRegistration: Unknown
Latest HTTP observationReachable but protectedHTTP access restrictedAccess Restriction50%2026-10-13 10:07:27 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 10:07:27 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: 15 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
Sophos
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:43:08 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-20 22:00:19 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-20 20:13:12 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
te19fgy1vslruxbkt8h.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.
3 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 →
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)
