On 2026-10-03, the domain bebjthman.vercel.app returned an HTTP 451 status code, indicating legal content restriction. The same domain appears in the PhishDestroy internal listing, and a VirusTotal scan on 2026-09-18 recorded 18 detections across 89 scanners.
Recorded Evidence
The domain was first observed on 2026-09-11 according to the evidence record. An HTTP check on 2026-10-03 returned status 451, while the IP address 216.198.79.3 was recorded in the United States under Lefkoff Industries. A VirusTotal scan on 2026-09-18 reported 18 detections out of 89 scanners, and an SSL scan on the same date identified the issuer as Google Trust Services / WR1. The PhishDestroy internal listing is recorded as true, and the blocklist check date is 2026-10-03.
Interpretation
The recorded HTTP 451 response describes only the response observed on that date and does not establish what content the domain may have served before or after. The VirusTotal detections and the PhishDestroy listing are separate source observations that should be read independently rather than combined into a single conclusion. The gap between the first observation on 2026-09-11 and the later checks on 2026-09-18 and 2026-10-03 shows the domain was recorded across multiple dates, but these dates alone do not demonstrate a change in behavior.
Recommended Actions
Preserve the PhishDestroy internal listing record and the VirusTotal scan result for bebjthman.vercel.app as separate source artifacts, since each carries its own detection context. Compare the HTTP 451 response record with the earlier first-observation record to see whether the recorded status differs across dates. Retain the SSL scan record and the IP organization record for reference, and review the domain against the PhishDestroy catalogue before deciding on any further handling.
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-11 10:28:07 UTCcurrent episode first observed: 2026-10-01 01:52:45 UTCobserved RIP window: 2026-09-11 10:28:07 UTC → 2026-10-01 01:52:45 UTC · 471.41hmidpoint estimate ≈ 2026-09-21 06:10:26 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.
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-18 22:00:20 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-18 17:03: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.
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)
