The domain fb-meta-verified-25017.vercel.app was recorded returning HTTP status 451 during an HTTP check on 2026-10-01, which documents only the response on that date. The domain was also first observed on 2026-09-08, and is listed in the PhishDestroy internal catalogue.
Recorded Evidence
An HTTP check on 2026-10-01 recorded a 451 status for fb-meta-verified-25017.vercel.app. VirusTotal, checked on 2026-09-18, reported 16 detections out of 89 scanners. PageSpeed recorded a performance score of 100 on 2026-09-16, and an SSL scan on the same date identified Google Trust Services / WR1 as the issuer. The domain is included in the PhishDestroy internal listing, and its first observation was on 2026-09-08.
Interpretation
These records provide separate insights into fb-meta-verified-25017.vercel.app, with each source measuring distinct aspects on different dates. The HTTP status documents only the response for a specific check, while VirusTotal reflects scanner detections as of its own check date. The PhishDestroy listing is a catalogue entry maintained by the publisher, and other checks such as PageSpeed and SSL offer technical observations.
Recommended Actions
For fb-meta-verified-25017.vercel.app, retain the HTTP check and PhishDestroy listing as distinct records for future reference. Compare the VirusTotal scanner results with PageSpeed and SSL scan findings individually, since each source covers different criteria. Revisit the domain's HTTP response and catalogue entry periodically to monitor for any changes in recorded evidence.
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 10:00:41 UTCcurrent episode first observed: 2026-10-13 22:00:27 UTCobserved RIP window: 2026-10-13 10:00:41 UTC → 2026-10-13 22:00:27 UTC · 12.00hmidpoint estimate ≈ 2026-10-13 16:00:34 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: 16 detections
alphaMountain.ai
BitDefender
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
MalwareURL
Netcraft
Sophos
URLQuery
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of fb-meta-verified-25017.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 22:00:27 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-10-13 01:28:28 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-16 22:00:23 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
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.
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)
