Security engines reporting a detection: 12. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-01, an HTTP check of ledger-lpog-in.pages.dev returned status 403, meaning the server declined to serve the request at that time. The same record shows the domain resolved to IP address 172.66.47.120, associated with Cloudflare, Inc. and country code CA.
Recorded Evidence
The domain ledger-lpog-in.pages.dev was first observed on 2026-08-31, according to the recorded timeline. An internal listing on the PhishDestroy list was also recorded, and the HTTP check on 2026-10-01 returned status 403. External blocklists MetaMask and SEAL each listed the domain as of the blocklist check on 2026-10-01. VirusTotal recorded 12 detections across 89 scanners on 2026-09-11.
Interpretation
The MetaMask and SEAL listings and the PhishDestroy internal listing were all recorded on 2026-10-01, while the VirusTotal scan dates to 2026-09-11. Because these observations come from different dates, a reader can compare them only as separate snapshots rather than a single synchronized measurement. The first observation on 2026-08-31 predates all of these checks, so the timeline spans roughly a month of recorded activity.
Recommended Actions
Anyone reviewing ledger-lpog-in.pages.dev should retain the dated records, including the 2026-10-01 HTTP status and the 2026-09-11 VirusTotal result, in case later comparison is needed. Subsequent checks of the full domain can be compared against these snapshots to see whether the recorded status or listings change. During any review, avoid submitting passwords, wallet credentials or other sensitive information to the domain until its status is independently clarified.
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 ContextCloudflare shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerCloudflare Pages
HTTP Status403 Forbidden
Elapsed Since First Report10 days
What we count
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
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 31, 2026
Page Title
Suspected Phishing | Cloudflare
Impersonates
Ledger
TLS Certificate
Hostname coverage not recorded·
Issued by WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.66.47.120
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
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-08-31 20:28:20 UTCcurrent episode first observed: 2026-10-01 01:37:20 UTCobserved RIP window: 2026-08-31 20:28:20 UTC → 2026-10-01 01:37:20 UTC · 725.15hmidpoint estimate ≈ 2026-09-15 23:02:50 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 · 3 identified
H
HSTS
Security
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: 12 detections
alphaMountain.ai
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
OpenPhish
Sophos
VIPRE
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-10 22:00:33 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-10 21:43:11 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
ledger-lpog-in.pages.dev 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 domain remains reachable or access-restricted; future checks may update this 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 recordedReachable · access restricted
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · ledger-lpog-in.pages.dev
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.
