CF Radar
provider verdict: malicious
Report“Get Started with Ledger Hardware Wallet”
On 2026-10-01, ledger-us-com-start.pages.dev returned an HTTP 403 status code in a recorded check, a server reply declining the request. The same domain was also listed on two external blocklists, MetaMask and SEAL, and appeared in PhishDestroy's internal listing.
The HTTP check on 2026-10-01 recorded a 403 status for ledger-us-com-start.pages.dev. External blocklist checks on the same date listed the domain on MetaMask and SEAL. VirusTotal reported 0 detections out of 89 scanners on 2026-09-11. The domain was first observed on 2026-08-31. PhishDestroy's internal listing is recorded as true.
These records describe separate source observations of ledger-us-com-start.pages.dev rather than a single conclusion. The HTTP 403 reply, the MetaMask and SEAL listings, and the PhishDestroy internal listing each capture a different kind of source record, while the VirusTotal scan result reflects a separate measurement. The first observation date and the later checks show the span over which these records were collected, without indicating what the domain served.
For ledger-us-com-start.pages.dev, preserve the HTTP status record and the MetaMask and SEAL blocklist entries as separate evidence. Compare the VirusTotal scan result with the blocklist listings in distinct reviews. Retain the PhishDestroy internal listing and the first observation record for future reference and monitoring.
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.
10 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