CF Radar
provider verdict: malicious
Report“Suspected Phishing | Cloudflare”
The domain ledger---live-web.pages.dev returned an HTTP 403 status on 2026-10-01, a dated response recorded during an HTTP check. Separately, the same domain was listed on two external blocklists, MetaMask and SEAL, as recorded on 2026-10-01.
The HTTP check on 2026-10-01 recorded status 403, and the blocklist check on 2026-10-01 recorded two external blocklists, MetaMask and SEAL. A VirusTotal scan on 2026-09-11 reported 0 detections across 89 scanners, while phishdestroy recorded an internal listing. The domain was first observed on 2026-09-01, and its IP address 172.66.44.210 was recorded in CA under Cloudflare, Inc.
The MetaMask and SEAL blocklist entries and the HTTP 403 response share the 2026-10-01 date, so they describe the same snapshot, whereas the VirusTotal scan on 2026-09-11 and the first observation on 2026-09-01 predate that snapshot. Because these named sources were collected on different dates, comparisons between them reflect separate points in time rather than a single synchronized measurement.
Retain the dated records for ledger---live-web.pages.dev so later checks can be compared against the 2026-10-01 HTTP and blocklist observations and the 2026-09-11 VirusTotal scan. When reviewing subsequent observations, compare each source's date and value to identify changes over time. Avoid submitting sensitive information to ledger---live-web.pages.dev during any review.
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