VirusTotal
14 / 89
“Suspected Phishing | Cloudflare”
On 2026-10-01, ledger---l-ive.pages.dev returned HTTP status 403, a dated response recorded during the HTTP check. The same domain appears on the MetaMask and SEAL external blocklists, and it carries a phishdestroy internal listing.
The domain was first observed on 2026-09-01, and the HTTP check on 2026-10-01 returned status 403. VirusTotal recorded 14 detections across 89 scanners on 2026-09-11. The external blocklist count of 2 covers MetaMask and SEAL, while the IP address 188.114.96.9 is associated with CloudFlare, Inc. in CA.
The MetaMask and SEAL listings, the phishdestroy internal listing, and the VirusTotal scan were recorded on different dates, so they reflect separate observation points rather than one synchronized snapshot. Because the HTTP check and blocklist review occurred later than the first observation, a reader can compare the sequence of dated records without treating any single entry as a current verdict.
Anyone reviewing ledger---l-ive.pages.dev should retain the dated blocklist, VirusTotal, and HTTP records together so later observations can be compared against them. During that review, avoid submitting passwords, wallet credentials, or other sensitive information to the domain, and note any new dated entries as they appear.
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.
188.114.96.9. 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