The domain i8hucq6n6njye1vl5z.vercel.app returned HTTP status 451 on 2026-10-01, according to the recorded HTTP check. The same record set shows a PhishDestroy internal listing, and the domain was first observed on 2026-08-26.
Recorded Evidence
The HTTP check dated 2026-10-01 recorded status 451 for i8hucq6n6njye1vl5z.vercel.app. VirusTotal, checked on 2026-09-04, reported 14 detections across 90 scanners. The PhishDestroy internal listing records the domain in that publisher-owned catalogue. A PageSpeed check on 2026-09-02 produced a performance score of 100. The first observation of the domain is dated 2026-08-26.
Interpretation
The HTTP status and the VirusTotal detections come from separate sources with separate dates, so they describe different measurements rather than one combined result. The PhishDestroy listing and the first-observation date frame when the domain entered the recorded set, while the PageSpeed score reflects a distinct performance measurement. Because the source dates differ, the records should be read as a sequence of observations, not as a single snapshot.
Recommended Actions
For i8hucq6n6njye1vl5z.vercel.app, preserve the HTTP response record and the VirusTotal record as separate items for later comparison. Compare the PhishDestroy listing against the first-observation record to track when the domain appeared in each source. Review the PageSpeed record independently from the detection and HTTP records. Recheck the domain's HTTP response and detection counts before relying on any earlier observation.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
IP ContextVercel shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerVercel(US)
HTTP Status451 Unavailable For Legal Reasons
Time to First Unavailability8 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 26, 2026
Page Title
Deployment Unavailable
TLS Certificate
Hostname coverage not recorded·
Issued by Google Trust Services· stored validity ends in 84 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
64.29.17.3
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services
Valid until
2026-11-27 00:00:00
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection source
PhishDestroy collector
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-08-26 10:28:22 UTCcurrent episode first observed: 2026-10-01 01:35:34 UTCobserved RIP window: 2026-08-26 10:28:22 UTC → 2026-10-01 01:35:34 UTC · 855.12hmidpoint estimate ≈ 2026-09-13 06:01:58 UTC · precision very 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.
Technologies · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Last analyzed First positive detection Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
G-Data
Kaspersky
LevelBlue
Lionic
MalwareURL
Netcraft
SafeToOpen
Sophos
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of i8hucq6n6njye1vl5z.vercel.app· checked Sep 2, 2026
100
Good
Performance
FCP
0.85s
First Contentful Paint
LCP
0.85s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.06s
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-02 22:00:22 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-02 19:23:09 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
i8hucq6n6njye1vl5z.vercel.app detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 3, 2026
Time to First Unavailability
180 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
3 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(US)
