kk24zyj4cf-e20803a413.vercel.app returned HTTP status 451 on 2026-10-01, a recorded response for that request date. The domain was first observed on 2026-08-31, an earlier dated record of its presence.
Recorded Evidence
The PhishDestroy internal listing includes kk24zyj4cf-e20803a413.vercel.app as of 2026-10-01. On 2026-09-10, VirusTotal reported 17 detections across 89 scanners for this domain. PageSpeed recorded a performance score of 100 on 2026-09-10. The IP address 64.29.17.67 is associated with Vercel, Inc in the US.
Interpretation
The PhishDestroy listing and the VirusTotal report are separate source records, each carrying its own date and measurement scope. The HTTP 451 response describes only the request recorded on 2026-10-01, not all content served by the domain. The first observation on 2026-08-31 and the later checks fall on different dates, so the records can be compared chronologically without treating them as simultaneous measurements. The PageSpeed score reflects a separate performance measurement rather than a security judgment.
Recommended Actions
Review the PhishDestroy listing and the VirusTotal report for kk24zyj4cf-e20803a413.vercel.app as distinct records. Preserve the HTTP response record and the first observation record separately for later comparison. Compare the PageSpeed result against future measurements of the same domain. Retain each source record with its own date so later reviewers can trace how the observations relate.
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 01:15:03 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 01:15:03 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.
技术 · 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
alphaMountain.ai
BitDefender
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
卡巴斯基
LevelBlue
Lionic
Netcraft
SafeToOpen
Sophos
URLQuery
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of kk24zyj4cf-e20803a413.vercel.app· checked Sep 10, 2026
100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
0.79s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.79s
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-10-13 01:15:03 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-10 22:00:30 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-10 19:13:13 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)
