On 2026-10-01, an HTTP request to codhub-one.vercel.app returned status code 451, a recorded response that describes only that single check. The domain was first observed on 2026-08-31, giving the earliest date in this evidence set.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 451, while the first observation of codhub-one.vercel.app dates to 2026-08-31. On 2026-09-10, VirusTotal reported 19 detections across 89 scanners, and the same date shows a PageSpeed performance score of 96. The SSL scan on 2026-09-10 identified the issuer as Google Trust Services / WR1, and the domain appears in the PhishDestroy internal listing. The IP address 216.198.79.195 is associated with Vercel, Inc in the US.
Interpretation
The PhishDestroy internal listing and the VirusTotal detection count are separate source records, and neither should be read as a verdict on the domain. The HTTP 451 response, the PageSpeed score, and the SSL observation each measure different things on different dates, so they cannot be combined into a trend. The gap between the first observation and the later checks shows only that records exist at those points in time.
Recommended Actions
Preserve the PhishDestroy internal listing and the VirusTotal record for codhub-one.vercel.app as separate source documents for later comparison. Compare the HTTP response record with the PageSpeed and SSL observations to see whether the recorded measurements align. Recheck codhub-one.vercel.app against the same sources to keep the evidence set current.
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:19 UTCcurrent episode first observed: 2026-10-01 01:37:03 UTCobserved RIP window: 2026-08-31 08:28:19 UTC → 2026-10-01 01:37:03 UTC · 737.15hmidpoint estimate ≈ 2026-09-15 17:02:41 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: 19 detections
alphaMountain.ai
Bfore.Ai PreCrime
BitDefender
Certego
CyRadar
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
Netcraft
OpenPhish
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of codhub-one.vercel.app· checked Sep 10, 2026
96
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
2.72s
Largest Contentful Paint
CLS
0.053
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
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:29 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-10 14:13:17 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
13 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)
