VirusTotal
9 / 89
“Ledger Live | Manage Your Crypto™ Assets Safely”
On 2026-10-01, ledgeer--live-doc.pages.dev returned HTTP status 403 when checked, a recorded response rather than a statement about all content on the domain. The same source set includes a phishdestroy internal listing for the domain, which is a separate recorded observation.
The HTTP check on 2026-10-01 recorded status 403 for ledgeer--live-doc.pages.dev. VirusTotal, checked on 2026-09-11, recorded 9 detections across 89 scanners. External blocklists MetaMask and SEAL were recorded on 2026-10-01, the same date as the blocklist check. The domain was first observed on 2026-09-01, and the IP address 172.66.47.116 is associated with Cloudflare, Inc. in CA.
The named records describe a domain that appears on two external blocklists and in a phishdestroy internal listing, while its recorded HTTP response was a 403. These are separate source observations with different dates, so they should be compared as distinct records rather than combined into a single verdict. The chronology from first observation to the later checks is available, but the dates alone do not establish a trend or change in behavior.
Preserve the MetaMask and SEAL blocklist records for ledgeer--live-doc.pages.dev, and keep the phishdestroy internal listing as a separate record. Compare the VirusTotal detection record with the HTTP check record in separate reviews, since they come from different sources. Re-check the domain's HTTP response and blocklist status at a later date to build a dated comparison set.
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.
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