verifybluecheckmark-eight.vercel.app returned HTTP status 451 in an HTTP check dated 2026-10-01. The same domain was first observed on 2026-09-08, according to the recorded observation timeline.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 451 for verifybluecheckmark-eight.vercel.app. A VirusTotal scan dated 2026-09-18 reported 17 detections across 89 scanners. PhishDestroy's internal listing was recorded as true, and the domain was first observed on 2026-09-08. The SSL scan on 2026-09-16 identified the issuer as Google Trust Services / WR1. A PageSpeed check on 2026-09-16 recorded a performance score of 100.
Interpretation
These records describe separate measurements taken by different sources on different dates, so they should be compared as individual observations rather than combined into a single judgment. The HTTP status reflects only the response recorded on that date, while the VirusTotal detections and PhishDestroy listing reflect their own separate checks. The chronology from first observation to the later checks shows the domain was tracked over several weeks, but the dates alone do not establish a trend.
Recommended Actions
Preserve the HTTP check record for verifybluecheckmark-eight.vercel.app alongside the VirusTotal and PhishDestroy entries for future comparison. Compare the HTTP status record with the PhishDestroy listing in separate reviews, since each source captures a different kind of observation. Retain the PageSpeed and SSL scan records as additional reference points for the same domain. Re-check the domain periodically and store each new result with its own source and date.
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-08 20:28:34 UTCcurrent episode first observed: 2026-10-01 01:51:30 UTCobserved RIP window: 2026-09-08 20:28:34 UTC → 2026-10-01 01:51:30 UTC · 533.38hmidpoint estimate ≈ 2026-09-19 23:10:02 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: 17 detections
alphaMountain.ai
BitDefender
CyRadar
Ermes
ESET
Emsisoft
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
Netcraft
OpenPhish
Sophos
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of verifybluecheckmark-eight.vercel.app· checked Sep 16, 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-09-16 22:00:22 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-16 16:13: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)
