CF Radar
provider verdict: malicious
Report“Ledger Start — Official Setup & First Steps”
The domain ledger-srt-us.pages.dev returned an HTTP 403 status when checked on 2026-10-01, indicating that access was denied for that specific request. Additionally, two external blocklists, MetaMask and SEAL, included this domain in their records on the same date.
On 2026-10-01, an HTTP check recorded a 403 response for ledger-srt-us.pages.dev. The domain was listed by MetaMask and SEAL according to a blocklist check also dated 2026-10-01. The first observation of this domain occurred on 2026-08-31. VirusTotal, as of 2026-09-11, reported 0 detections out of 89 scanners.
These records provide a snapshot of ledger-srt-us.pages.dev across several sources, each reporting distinct aspects. The HTTP 403 status reflects a single access attempt, while the MetaMask and SEAL blocklist entries indicate that both sources had independently included the domain in their listings as of the recorded date. The VirusTotal result offers a separate perspective from a different time, and the first observation date marks the earliest known record in this evidence set.
For ledger-srt-us.pages.dev, retain the HTTP status record and the blocklist entries from MetaMask and SEAL for future comparison. Keep the VirusTotal scan result and the initial observation date as reference points for ongoing monitoring. Review updates from each source to track any changes in their respective records.
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.
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