On 2026-10-01, an HTTP check of c17pu9o6k3-3755b1f233.vercel.app returned status 451, a recorded response code for that specific request. The same domain was first observed on 2026-09-05, and a PhishDestroy internal listing exists for it.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 451, while the first observation of c17pu9o6k3-3755b1f233.vercel.app dates to 2026-09-05. A VirusTotal scan on 2026-09-17 reported 20 detections across 89 scanners. The SSL certificate, scanned on 2026-09-15, was issued by Google Trust Services / WR1, and the PageSpeed check on 2026-09-15 produced a performance score of 100. The domain resolves to IP address 64.29.17.195, associated with Vercel, Inc in the US.
Interpretation
These records describe separate observations made by different sources on different dates, so they should be compared rather than merged. The HTTP response, VirusTotal detections, SSL scan, and PageSpeed score each measure a distinct aspect of the domain at their respective check times. The chronology from first observation to the later checks shows the domain has been recorded across multiple dates, but the records do not establish a trend or a current state.
Recommended Actions
Preserve the PhishDestroy internal listing and the VirusTotal scan record for c17pu9o6k3-3755b1f233.vercel.app as separate source artifacts. Compare the HTTP check record with the VirusTotal record to see whether the two sources describe the same domain consistently. Retain the PageSpeed and SSL scan records for c17pu9o6k3-3755b1f233.vercel.app so future checks can be compared against these dated observations.
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-09-05 16:28:16 UTCcurrent episode first observed: 2026-10-01 01:39:22 UTCobserved RIP window: 2026-09-05 16:28:16 UTC → 2026-10-01 01:39:22 UTC · 609.18hmidpoint estimate ≈ 2026-09-18 09:03:49 UTC · precision 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: 20 detections
Criminal IP
alphaMountain.ai
BitDefender
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
MalwareURL
Netcraft
SafeToOpen
Sophos
URLQuery
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of c17pu9o6k3-3755b1f233.vercel.app· checked Sep 15, 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.
VirusTotal Detections Update2026-09-16 23:14:32 UTC
VirusTotal scanner detections updated from 19 to 20. Added scanner alerts: MalwareURL.
Domain Status Transition2026-09-15 10:00:19 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 04:43:12 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 64.29.17.195.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 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)
