VirusTotal
14 / 89
“Suspected Phishing | Cloudflare”
On 2026-10-01, ledger-live-home-app.pages.dev returned an HTTP 403 status code in the recorded HTTP check. The same domain was first observed on 2026-08-31, according to the recorded first-observation date.
The HTTP check dated 2026-10-01 recorded status 403 for ledger-live-home-app.pages.dev. A VirusTotal check dated 2026-09-11 recorded 14 detections across 89 scanners. The external blocklists MetaMask and SEAL each listed the domain as of 2026-10-01. The domain was first observed on 2026-08-31. The IP address 188.114.96.3 is recorded with country CA and organization CloudFlare, Inc.
The HTTP 403 record describes only the response to one request on its recorded date, not all content or responses on the domain. The MetaMask and SEAL listings and the VirusTotal detection count are separate source observations with their own recorded dates, so they should be read as distinct records rather than combined into a single measure. The first-observation date marks when the domain entered the recorded dataset, while the later checks document what each source reported afterward.
For ledger-live-home-app.pages.dev, preserve the MetaMask and SEAL blocklist records and the VirusTotal report as separate reference points. Compare each of those records against later observations of the domain rather than merging them. Retain the HTTP status record alongside them so future reviews can distinguish response-level findings from blocklist and scanner findings.
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