VirusTotal
11 / 89
“Suspected Phishing | Cloudflare”
On 2026-10-01, ledgerr-livess.pages.dev returned an HTTP 403 status code, indicating server access was denied. The domain was also listed on MetaMask and SEAL blocklists.
MetaMask and SEAL listed ledgerr-livess.pages.dev on their external blocklists on 2026-10-02. VirusTotal reported 11 detections out of 89 scanners on 2026-09-13. The domain received a Pagespeed performance score of 99 on 2026-09-11.
The HTTP 403 status code indicates that the server refused access during the recorded check. The blocklist entries from MetaMask and SEAL reflect external assessments of the domain. VirusTotal's detection record and the high Pagespeed score provide additional technical context from different dates.
Review the blocklist entries for ledgerr-livess.pages.dev from MetaMask and SEAL. Retain the VirusTotal detection record for future comparison. Preserve the Pagespeed performance score as a reference for technical performance over time.
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.
Google PageSpeed Insights — mobile performance audit of ledgerr-livess.pages.dev · checked Sep 11, 2026
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