CF Radar
provider verdict: malicious
Report“Suspected Phishing | Cloudflare”
On 2026-10-01, ledgerliivedownload.pages.dev returned HTTP status 403 in an HTTP check, and the domain was first observed on 2026-08-31. The same HTTP check recorded IP address 172.66.47.195, located in CA and organized under Cloudflare, Inc.
The external blocklist count for ledgerliivedownload.pages.dev was 2 as of 2026-10-01, naming MetaMask and SEAL. A VirusTotal check on 2026-09-11 recorded 0 detections across 89 scanners, with observation time unknown. The domain also appeared on the phishdestroy internal listing, and the blocklist check date was 2026-10-01.
The MetaMask and SEAL listings and the phishdestroy internal listing reflect observations on 2026-10-01, while the VirusTotal scan reflects 2026-09-11 and the first observation is 2026-08-31. Because these dates differ, the records describe separate points in time rather than one simultaneous snapshot. The 403 response on 2026-10-01 shows the server declined that request, but it does not by itself establish present availability or content.
For ledgerliivedownload.pages.dev, retain the dated records from MetaMask, SEAL, phishdestroy, VirusTotal and the HTTP check so later observations can be compared against them. When reviewing the domain, avoid submitting passwords, wallet credentials or other sensitive information. If new checks are run, record their exact dates and values alongside the existing entries for ledgerliivedownload.pages.dev.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Provider response during scan: cloudflare_phishing_interstitial
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
151 stored lookalike domains
Showing 100 of 151
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive