fb-meta-verified-3658-tau.vercel.app returned HTTP status 451 on 2026-10-01, the most recent HTTP check recorded for this host. The same record set shows an IP address of 216.198.79.67, held by CYPRESS COMMUNICATIONS, LLC in the US.
Recorded Evidence
Google Safe Browsing flagged the domain for social engineering on 2026-09-21. VirusTotal recorded 18 detections across 89 scanners on 2026-09-21. PhishDestroy's internal listing was active, and the SSL certificate was issued by Google Trust Services / WR1 on 2026-09-21. The first observation date was 2026-09-17, and PageSpeed recorded a performance score of 100 on 2026-09-21.
Interpretation
The Safe Browsing flag and the VirusTotal detection count describe separate checks made on the same calendar date, so they should be read as independent observations rather than a combined score. The HTTP 451 response on 2026-10-01 describes only that recorded response, not the full content of the domain. The first observation on 2026-09-17 predates the later checks, but the available records do not establish what changed between those dates.
Recommended Actions
For fb-meta-verified-3658-tau.vercel.app, preserve the Safe Browsing flag and the VirusTotal detection record as separate artifacts for later comparison. Compare the PhishDestroy listing against the Safe Browsing flag in a future review rather than merging them. Retain the HTTP response record alongside the PageSpeed score so that availability and performance can be examined independently.
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-17 04:28:14 UTCcurrent episode first observed: 2026-10-01 01:54:00 UTCobserved RIP window: 2026-09-17 04:28:14 UTC → 2026-10-01 01:54:00 UTC · 333.43hmidpoint estimate ≈ 2026-09-24 03:11:07 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.
Google PageSpeed Insights — mobile performance audit of fb-meta-verified-3658-tau.vercel.app· checked Sep 21, 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.
Domain Status Transition2026-09-21 22:00:22 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-21 13:29:21 UTC
Telemetry event observed.
Threat First Observed2026-09-21 12:53:10 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
15 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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)
