VirusTotal
14 / 89
“Get started with Ledger — Ledger.com/start”
us-ledgrlive.pages.dev returned an HTTP 403 status on 2026-10-01, a recorded response indicating restricted access at that check. The domain was first observed on 2026-09-15, and a Phishdestroy internal listing was also recorded.
MetaMask and SEAL each appeared as an external blocklist entry for the domain, with the blocklist check dated 2026-10-01. VirusTotal recorded 14 detections across 89 scanners on 2026-09-22. The SSL certificate, issued by Google Trust Services / WE1, was scanned on 2026-09-21. The IP address 188.114.97.9 was recorded in Canada under CloudFlare, Inc.
MetaMask, SEAL, and VirusTotal reflect separate observation dates, so their records describe different points in time rather than one synchronized snapshot. The Phishdestroy internal listing and the 2026-10-01 HTTP response add further dated context. Comparing these sources requires attention to when each observation was made.
For us-ledgrlive.pages.dev, preserve the dated records from MetaMask, SEAL, VirusTotal, and Phishdestroy together with the HTTP and SSL observations. Compare any later observations against these dates to see what changed. Avoid submitting sensitive information to the domain while reviewing the collected evidence.
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.
8dc04f32122ea71bf363673208d67ddfb5dfcc00b356b15cea59596d069b71abSaved 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