CF Radar
provider verdict: malicious
Report“Suspected Phishing | Cloudflare”
On 2026-10-01, ledger-com-en-x.pages.dev returned an HTTP 403 status during a recorded check, indicating that access to the domain was denied at that time. The domain was also listed on two external blocklists, MetaMask and SEAL, according to a blocklist check from the same date.
The domain ledger-com-en-x.pages.dev was first observed on 2026-09-01. On 2026-10-01, an HTTP check recorded a 403 response. A blocklist check on 2026-10-01 found the domain listed by MetaMask and SEAL. An internal listing was also present. VirusTotal, as of 2026-09-13, reported 0 detections out of 89 scanners for this domain.
These records document multiple types of monitoring for ledger-com-en-x.pages.dev, with external blocklists and an internal listing reflecting different listing criteria. The HTTP 403 response and VirusTotal scan were recorded on separate dates, so their findings are not directly comparable. The first observation date provides a reference point for the timing of subsequent checks and listings.
Review the MetaMask and SEAL blocklist records for ledger-com-en-x.pages.dev as part of ongoing monitoring. Retain the internal listing and the HTTP 403 response as distinct source records for future comparison. Compare the VirusTotal scan with other security sources to track any changes in detection status over time. Maintain all dated records to document the domain’s observed history.
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.
12 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