The domain verification-blueticks-fb25.vercel.app returned HTTP status 451 on 2026-10-01, the date of the recorded HTTP check. A separate performance measurement on 2026-09-15 recorded a PageSpeed performance score of 100.
Recorded Evidence
The PhishDestroy internal listing was recorded as true, and the earliest observation of this domain in the evidence is dated 2026-09-06. VirusTotal recorded 16 detections across 89 scanners on 2026-09-17, with observation time known marked false. The HTTP check on 2026-10-01 returned status 451, and the IP address 216.198.79.195 was recorded in the United States under Vercel, Inc.
Interpretation
The PhishDestroy listing, VirusTotal result and HTTP check were captured on different dates, so they describe separate moments rather than one synchronized state. Because the VirusTotal observation time is not known, its detections cannot be aligned precisely with the other dated records. Comparing these named sources shows only what each recorded on its own date, and the differing dates limit direct comparison.
Recommended Actions
Retain the dated records for verification-blueticks-fb25.vercel.app, including the PhishDestroy listing, the VirusTotal result and the HTTP check, so later observations can be compared against them. When reviewing the domain, avoid submitting passwords, payment details or other sensitive information. Compare any subsequent observations with the recorded dates and values rather than treating one snapshot as a current description.
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-06 14:28:09 UTCcurrent episode first observed: 2026-10-01 01:39:24 UTCobserved RIP window: 2026-09-06 14:28:09 UTC → 2026-10-01 01:39:24 UTC · 587.19hmidpoint estimate ≈ 2026-09-18 20:03:46 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: 16 detections
alphaMountain.ai
BitDefender
Ermes
ESET
Emsisoft
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
MalwareURL
Netcraft
OpenPhish
Sophos
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of verification-blueticks-fb25.vercel.app· checked Sep 15, 2026
100
Good
Performance
FCP
0.8s
First Contentful Paint
LCP
0.8s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.8s
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-17 05:38:40 UTC
VirusTotal scanner detections updated from 15 to 16. Added scanner alerts: MalwareURL.
Domain Status Transition2026-09-15 10:00:20 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 07:43:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 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)
