As of 2026-10-01, verification-blueticks-fb36.vercel.app returned an HTTP status code 451, per the recorded HTTP check. The same source set records a first observation of this domain on 2026-09-08.
Recorded Evidence
The PhishDestroy internal catalogue listed verification-blueticks-fb36.vercel.app on 2026-10-01. A VirusTotal check dated 2026-09-18 recorded 17 detections across 89 scanners. The SSL certificate scan of 2026-09-16 named Google Trust Services / WR1 as issuer. PageSpeed data from 2026-09-16 recorded a performance score of 100. The IP address 216.198.79.3 was recorded with country US and organization Lefkoff Industries.
Interpretation
The PhishDestroy listing and the HTTP check share the 2026-10-01 date, so those two records describe the same day. The VirusTotal and SSL observations fall earlier, on 2026-09-18 and 2026-09-16, while first observation is earlier still at 2026-09-08. Because these sources were collected on different dates, a reader can compare them only as separate dated snapshots rather than as one simultaneous measurement.
Recommended Actions
Retain the PhishDestroy, VirusTotal, SSL, PageSpeed and HTTP records for verification-blueticks-fb36.vercel.app together with their dates. Compare any later HTTP status, certificate or detection observations against these baselines to see what changed. During review, avoid submitting sensitive information to verification-blueticks-fb36.vercel.app.
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-10-13 01:28:29 UTCcurrent episode first observed: 2026-10-13 10:00:41 UTCobserved RIP window: 2026-10-13 01:28:29 UTC → 2026-10-13 10:00:41 UTC · 8.54hmidpoint estimate ≈ 2026-10-13 05:44:35 UTC · precision medium · 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
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
MalwareURL
Netcraft
Sophos
URLQuery
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of verification-blueticks-fb36.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-10-13 10:00:41 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-10-13 01:28:29 UTC
Domain state transitioned from dead to alive.
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
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)
