VirusTotal
3 / 89
“Suspected Phishing | Cloudflare”
On 2026-10-01, ledger--starrt.pages.dev returned HTTP status 403 in the recorded HTTP check. The same domain appears on two named external blocklists, MetaMask and SEAL, and is listed internally by PhishDestroy.
The domain ledger--starrt.pages.dev was first observed on 2026-09-01. The HTTP check on 2026-10-01 recorded status 403 from IP address 172.66.44.154, associated with Cloudflare, Inc. in CA. VirusTotal recorded 3 detections across 89 scanners on 2026-09-11. The external blocklists MetaMask and SEAL were checked on 2026-10-01. PhishDestroy's internal listing is also recorded for this domain.
The recorded HTTP 403 response describes only the response captured on that date, not all content the domain may serve. The external blocklist entries from MetaMask and SEAL reflect those sources' own listings, while the PhishDestroy internal listing is a separate record. The VirusTotal detection count and the blocklist entries come from different sources and dates, so they should be compared as distinct observations rather than merged into one conclusion.
For ledger--starrt.pages.dev, preserve the HTTP check record, the VirusTotal result, and the PhishDestroy internal listing as separate source records. Compare the external blocklist entries from MetaMask and SEAL against the internal listing to see where the sources agree or differ. Re-check the domain's HTTP response and blocklist status periodically, keeping each source's result distinct.
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.
9 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