On 2026-10-01, an HTTP check of fb-meta-verified-3658-alpha.vercel.app returned status code 451. The same domain was first observed on 2026-09-07, and a PhishDestroy internal listing records it as listed.
Recorded Evidence
The HTTP check on 2026-10-01 returned status 451, while the first observation of fb-meta-verified-3658-alpha.vercel.app dates to 2026-09-07. VirusTotal recorded 17 detections across 89 scanners on 2026-09-17. A PhishDestroy internal listing is recorded as true. The SSL scan on 2026-09-15 identified Google Trust Services / WR1 as the issuer, and the PageSpeed check that same day returned a performance score of 100. The IP address 64.29.17.195 is associated with Vercel, Inc in the US.
Interpretation
The PhishDestroy internal listing and the VirusTotal detection count are separate source observations, each with its own scope and measurement method, so they should be read individually rather than merged into a single conclusion. The HTTP 451 response on 2026-10-01 describes only that recorded request, not all content that may be served by the domain. The gap between the first observation on 2026-09-07 and the later checks shows the domain was recorded across multiple dates, but different dates alone do not demonstrate a change in behavior.
Recommended Actions
Preserve the PhishDestroy internal listing record and the VirusTotal detection record for fb-meta-verified-3658-alpha.vercel.app, since each documents a distinct source observation. Compare the HTTP status record with the PageSpeed performance record in separate reviews, as they capture different aspects of the domain. Retain the SSL scan record alongside these sources so future comparisons rely on the same dated evidence set.
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-07 14:28:08 UTCcurrent episode first observed: 2026-10-01 01:39:24 UTCobserved RIP window: 2026-09-07 14:28:08 UTC → 2026-10-01 01:39:24 UTC · 563.19hmidpoint estimate ≈ 2026-09-19 08: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: 17 detections
alphaMountain.ai
BitDefender
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
MalwareURL
Netcraft
Sophos
URLQuery
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of fb-meta-verified-3658-alpha.vercel.app· checked Sep 15, 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.
VirusTotal Detections Update2026-09-17 09:00:31 UTC
VirusTotal scanner detections updated from 18 to 17. Resolved alerts: 卡巴斯基.
Domain Status Transition2026-09-15 22:00:17 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-15 17:31:09 UTC
VirusTotal scanner detections updated from 17 to 18. Added scanner alerts: MalwareURL.
Threat First Observed2026-09-15 12:33:11 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)
