ledgrr-livv-app.pages.dev returned HTTP status 403 in an HTTP check dated 2026-10-01, a recorded response rather than a statement about all content on the domain. The same source data records an IP address of 188.114.96.9, located in CA and attributed to CloudFlare, Inc.
Recorded Evidence
The domain was first observed on 2026-09-08, and a phishdestroy internal listing is recorded as true. An external blocklist count of 2 is recorded, naming MetaMask and SEAL, with the blocklist check dated 2026-10-01. VirusTotal, checked on 2026-09-18, reported 15 detections across 89 scanners, and the observation time is not known. A PageSpeed check dated 2026-09-16 recorded a performance score of 100.
Interpretation
The HTTP 403 response describes one dated request outcome, while the external blocklist count and the phishdestroy internal listing reflect separate listing records that a reader can compare. The first-observed date and the later checks fall on different calendar dates, so the chronology shows when records were captured rather than a measured change. The VirusTotal detections and total scanners describe that scanner set at its check date, and the PageSpeed score describes a separate performance measurement.
Recommended Actions
For ledgrr-livv-app.pages.dev, preserve the HTTP check record and the external blocklist entries as distinct source records, and compare them separately rather than merging their values. Retain the VirusTotal scanner result and the PageSpeed measurement in the same way, since each documents a different kind of observation. Review the phishdestroy internal listing alongside the named external blocklists when deciding what follow-up the recorded evidence supports.
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-08 20:28:27 UTCcurrent episode first observed: 2026-10-01 01:39:30 UTCobserved RIP window: 2026-09-08 20:28:27 UTC → 2026-10-01 01:39:30 UTC · 533.18hmidpoint estimate ≈ 2026-09-19 23:03:58 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: 15 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
MalwareURL
Sophos
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of ledgrr-livv-app.pages.dev· checked Sep 16, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.83s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
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-16 10:00:31 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-16 08: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)
