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.
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.
技术 · 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
卡巴斯基
LevelBlue
Lionic
Netcraft
Sophos
URLQuery
VIPRE
Webroot
网站性能分析
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.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
(US)
