On 2026-10-01, an HTTP request to da51ca.pages.dev returned status 403, according to the recorded HTTP check. The domain was first observed on 2026-09-06, and a PhishDestroy internal listing is recorded as true.
Recorded Evidence
The HTTP check dated 2026-10-01 recorded status 403 for da51ca.pages.dev. VirusTotal, checked on 2026-09-17, reported 13 detections across 89 scanners. A PageSpeed check on 2026-09-15 recorded a performance score of 100. The domain resolves to IP address 188.114.96.9, associated with CloudFlare, Inc. and country CA. The first observation of da51ca.pages.dev is dated 2026-09-06, and the PhishDestroy internal listing is recorded as true.
Interpretation
The recorded HTTP 403 response describes only the response observed at that check, not the domain's full content or present availability. The VirusTotal detections and scanner total reflect one dated scan, while the PageSpeed score reflects a separate measurement on a different date. The PhishDestroy internal listing and the first-observation date are catalogue records, and the CloudFlare association describes the recorded IP organization rather than the domain's operator.
Recommended Actions
Preserve the HTTP check record for da51ca.pages.dev alongside the PhishDestroy internal listing. Compare the VirusTotal scan record with the PageSpeed measurement as separate source records. Retain the first-observation record for da51ca.pages.dev to document when the domain entered the dataset. Review the recorded HTTP status and listing together when deciding on further monitoring.
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-06 14:28:09 UTCcurrent episode first observed: 2026-10-01 01:39:24 UTCobserved RIP window: 2026-09-06 14:28:09 UTC → 2026-10-01 01:39:24 UTC · 587.19hmidpoint estimate ≈ 2026-09-18 20: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.
技术 · 3 identified
H
HSTS
安全
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Lionic
MalwareURL
Netcraft
SafeToOpen
Sophos
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of da51ca.pages.dev· checked Sep 15, 2026
100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
1.84s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.77s
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 05:38:43 UTC
VirusTotal scanner detections updated from 12 to 13. Added scanner alerts: MalwareURL.
Domain Status Transition2026-09-15 10:00:21 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 07:43:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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)
