On 2026-10-01, meta-seven-sigma.vercel.app returned HTTP status 451 according to the recorded HTTP check. The same evidence set records a PhishDestroy internal listing for this domain, first observed on 2026-09-17.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 451, while the first observation date for the domain is 2026-09-17. VirusTotal, checked on 2026-09-21, reported 16 detections across 89 scanners. The SSL scan on 2026-09-21 identified Google Trust Services / WR1 as the certificate issuer. PageSpeed on 2026-09-21 recorded a performance score of 100. The domain resolved to IP address 64.29.17.131, associated with Vercel, Inc in the US.
Interpretation
The recorded HTTP response and the PhishDestroy internal listing are separate source observations that describe different aspects of the domain. The VirusTotal detection count and scanner total describe one dated snapshot, and the PageSpeed score describes a separate performance measurement. Because the HTTP check, VirusTotal check, SSL scan, and PageSpeed check fall on different dates, they should be compared as distinct records rather than as a single combined signal.
Recommended Actions
Preserve the recorded HTTP status for meta-seven-sigma.vercel.app alongside the PhishDestroy internal listing as separate source records. Compare the VirusTotal detection count and scanner total with the PageSpeed performance score only as distinct dated observations. Retain the SSL scan and IP resolution records for future reference, and review the domain's recorded HTTP response against the first observation date when assessing the timeline.
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:13 UTCcurrent episode first observed: 2026-10-01 01:53:58 UTCobserved RIP window: 2026-09-17 04:28:13 UTC → 2026-10-01 01:53:58 UTC · 333.43hmidpoint estimate ≈ 2026-09-24 03:11:05 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 meta-seven-sigma.vercel.app· checked Sep 21, 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-09-21 22:00:21 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-21 10:23:09 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.
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)
