On 2026-10-01, the domain w24os1ku4e-a6c2df4953.vercel.app returned an HTTP status code 451, as recorded by the HTTP check on that date. Additionally, a PageSpeed performance assessment on 2026-09-10 reported a perfect score of 100 for the same domain.
Recorded Evidence
VirusTotal conducted a scan on 2026-09-10, noting 17 detections out of 89 total scanners for w24os1ku4e-a6c2df4953.vercel.app. The domain was first observed on 2026-08-31, and it is listed in the PhishDestroy internal catalogue as of the same evidence set. The HTTP status code 451 was specifically recorded on 2026-10-01, while the PageSpeed score of 100 was observed on 2026-09-10.
Interpretation
Comparing the sources, each provides a distinct perspective based on its observation date. The VirusTotal scan and PageSpeed evaluation both occurred on 2026-09-10, allowing for direct comparison between those two assessments, while the HTTP status and PhishDestroy listing offer additional context from different dates. The range of dates highlights how the domain's recorded characteristics may vary over time, and underscores the importance of considering the timing of each observation.
Recommended Actions
To ensure a thorough review of w24os1ku4e-a6c2df4953.vercel.app, retain all dated evidence from VirusTotal, PhishDestroy, HTTP, and PageSpeed sources. Compare any new findings with these specific records to track changes or trends. During examination, avoid submitting sensitive information to w24os1ku4e-a6c2df4953.vercel.app or related services, and preserve the original evidence for future reference.
Detection-evasion analysis
Cloaking and traffic-distribution check
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.
IP ContextVercel shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerVercel(US)
HTTP Status451 Unavailable For Legal Reasons
Time to First Unavailability11 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 31, 2026
Page Title
Deployment Unavailable
TLS Certificate
Hostname coverage not recorded·
Issued by WR1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
64.29.17.131
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
WR1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-08-31 08:28:20 UTCcurrent episode first observed: 2026-10-01 01:37:13 UTCobserved RIP window: 2026-08-31 08:28:20 UTC → 2026-10-01 01:37:13 UTC · 737.15hmidpoint estimate ≈ 2026-09-15 17:02:46 UTC · precision very low · basis bounded
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: 17 detections
Criminal IP
alphaMountain.ai
BitDefender
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Kaspersky
LevelBlue
Lionic
Netcraft
Sophos
URLQuery
VIPRE
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of w24os1ku4e-a6c2df4953.vercel.app· checked Sep 10, 2026
100
Good
Performance
FCP
0.81s
First Contentful Paint
LCP
0.81s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.81s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-09-10 22:00:30 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-10 19:33:12 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
w24os1ku4e-a6c2df4953.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 latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 11, 2026
Time to First Unavailability
254 hours elapsed from detection to the first unavailable 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 recordedContent unavailable
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 matches4
Same favicon hash or the same page title as this host.
(US)
