CF Radar
provider verdict: malicious
Report“Suspected Phishing | Cloudflare”
ledger-liiveapp.pages.dev returned an HTTP 403 status during a check on 2026-10-01, indicating restricted access at that time. The domain was first observed in the evidence on 2026-08-31, marking the earliest recorded activity.
On 2026-10-01, the domain appeared on two external blocklists: MetaMask and SEAL, as well as on the PhishDestroy internal listing. VirusTotal checked ledger-liiveapp.pages.dev on 2026-09-11, recording 0 detections out of 89 scanners. The HTTP status check and blocklist observations both occurred on 2026-10-01.
The MetaMask and SEAL blocklist entries, as well as the PhishDestroy internal listing, are all documented on 2026-10-01, providing a consistent snapshot of external and internal blocklist status. The VirusTotal scan, however, was performed earlier, on 2026-09-11, so its results reflect a different point in time. Comparing these records allows for an analysis of how the domain's status may have changed across different dates and sources.
Retain all dated evidence for ledger-liiveapp.pages.dev, including the 2026-10-01 blocklist and HTTP records and the 2026-09-11 VirusTotal scan, to support future reviews. Compare any subsequent findings to these dated snapshots, and avoid submitting confidential or sensitive information to the domain during evaluation.
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