The domain verifiedbadge-azex.vercel.app returned an HTTP 451 status code on 2026-10-01, as recorded in a source check. This domain was first observed on 2026-09-17, and multiple technical checks have been performed since then.
Recorded Evidence
On 2026-09-21, VirusTotal recorded 18 detections out of 89 scanners for verifiedbadge-azex.vercel.app. PageSpeed measured a performance score of 100 on 2026-09-21. The SSL certificate was issued by Google Trust Services / WR1 and scanned on 2026-09-21. The domain is listed in the PhishDestroy internal catalogue, and a blocklist check was performed on 2026-10-01.
Interpretation
These records provide a snapshot of verifiedbadge-azex.vercel.app across several technical and catalogue sources. The HTTP 451 status code documents a specific response at one point in time, while VirusTotal and PageSpeed offer distinct metrics from their respective checks. The PhishDestroy internal catalogue listing reflects a publisher record, and the SSL certificate details are based on a scan from the same period.
Recommended Actions
For verifiedbadge-azex.vercel.app, retain the HTTP response record and VirusTotal detection results for future comparison. Keep the PageSpeed score and SSL certificate scan as separate technical references. Preserve the PhishDestroy internal catalogue entry and blocklist check for ongoing monitoring and review.
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-17 04:28:14 UTCcurrent episode first observed: 2026-10-01 01:54:01 UTCobserved RIP window: 2026-09-17 04:28:14 UTC → 2026-10-01 01:54:01 UTC · 333.43hmidpoint estimate ≈ 2026-09-24 03:11:07 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.
Google PageSpeed Insights — mobile performance audit of verifiedbadge-azex.vercel.app· checked Sep 21, 2026
100
Good
Performance
FCP
0.82s
First Contentful Paint
LCP
0.82s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.82s
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-21 22:00:22 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-21 12:53:10 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
14 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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)
