On 2026-10-01, ledgeer--live-doc.pages.dev returned HTTP status 403 when checked, a recorded response rather than a statement about all content on the domain. The same source set includes a phishdestroy internal listing for the domain, which is a separate recorded observation.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 403 for ledgeer--live-doc.pages.dev. VirusTotal, checked on 2026-09-11, recorded 9 detections across 89 scanners. External blocklists MetaMask and SEAL were recorded on 2026-10-01, the same date as the blocklist check. The domain was first observed on 2026-09-01, and the IP address 172.66.47.116 is associated with Cloudflare, Inc. in CA.
Interpretation
The named records describe a domain that appears on two external blocklists and in a phishdestroy internal listing, while its recorded HTTP response was a 403. These are separate source observations with different dates, so they should be compared as distinct records rather than combined into a single verdict. The chronology from first observation to the later checks is available, but the dates alone do not establish a trend or change in behavior.
Recommended Actions
Preserve the MetaMask and SEAL blocklist records for ledgeer--live-doc.pages.dev, and keep the phishdestroy internal listing as a separate record. Compare the VirusTotal detection record with the HTTP check record in separate reviews, since they come from different sources. Re-check the domain's HTTP response and blocklist status at a later date to build a dated comparison set.
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-01 00:28:07 UTCcurrent episode first observed: 2026-10-01 01:00:59 UTCobserved RIP window: 2026-09-01 00:28:07 UTC → 2026-10-01 01:00:59 UTC · 720.55hmidpoint estimate ≈ 2026-09-16 00:44:33 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.
技术 · 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: 9 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Fortinet
G-Data
卡巴斯基
LevelBlue
Sophos
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-11 01:00:15 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-10 23:03: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)
