The domain ledgeer-lived.pages.dev returned HTTP status 403 on 2026-10-01, according to the recorded HTTP check. A separate internal listing for this domain also exists in the phishdestroy dataset, dated by its inclusion in that record set.
Recorded Evidence
The domain ledgeer-lived.pages.dev was first observed on 2026-09-01. External blocklist records name MetaMask and SEAL, with two external blocklist entries counted as of 2026-10-01. VirusTotal recorded 8 detections across 89 scanners on 2026-09-11. The domain resolved to IP address 172.66.44.60, associated with Cloudflare, Inc. in country CA.
Interpretation
The MetaMask and SEAL blocklist records, the phishdestroy internal listing, and the VirusTotal scan were collected on different dates, so their observations describe separate points in time rather than one synchronized snapshot. Because the HTTP check and blocklist check share the 2026-10-01 date while the VirusTotal scan is earlier, a reader can compare the later status observation against the earlier detection count without treating either as current.
Recommended Actions
Retain the recorded evidence for ledgeer-lived.pages.dev, including the dated HTTP status, blocklist names, and VirusTotal figures, so later observations can be compared against these exact values. When reviewing ledgeer-lived.pages.dev again, record new dates and values rather than assuming the prior HTTP status or detection count still applies. Avoid submitting passwords, payment details, or other sensitive information while examining this domain, since the recorded sources do not establish what the domain currently serves.
From Wallet to Web3 — Unlock Possibilities with Ledger Live
TLS 证书
Hostname coverage not recorded·
颁发者 WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.66.44.60
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP 声誉不属于此域。
Location describes the IP network.
TLS 证书
Issuer
WE1
Hostname coverage
Hostname coverage not recorded
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-09-01 00:28:07 UTCcurrent episode first observed: 2026-10-01 01:00:58 UTCobserved RIP window: 2026-09-01 00:28:07 UTC → 2026-10-01 01:00:58 UTC · 720.55hmidpoint estimate ≈ 2026-09-16 00:44:32 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: 8 detections
alphaMountain.ai
BitDefender
ESET
Fortinet
G-Data
卡巴斯基
Lionic
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:17 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-10 22:53:13 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)
