VirusTotal
13 / 89
“Suspected Phishing | Cloudflare”
On 2026-10-01, learn-us-ledger.pages.dev returned an HTTP 403 status when checked. The same domain was first observed on 2026-09-01, according to the recorded evidence.
The HTTP check on 2026-10-01 recorded status 403 for this domain. VirusTotal reported 13 detections across 89 scanners on 2026-09-13. Two external blocklists, MetaMask and SEAL, were recorded as listing the domain. The domain also appears in the phishdestroy internal listing, and the blocklist check date was 2026-10-01.
The VirusTotal observation on 2026-09-13 and the HTTP check on 2026-10-01 are separate dated records, so they describe different points in time. The MetaMask and SEAL blocklist entries and the phishdestroy internal listing are recorded source observations rather than conclusions about the domain. Because the observation dates differ, a reader can compare them but cannot treat any single record as current.
Anyone reviewing learn-us-ledger.pages.dev should retain the dated records from VirusTotal, MetaMask, SEAL, and phishdestroy for later comparison. Subsequent checks of learn-us-ledger.pages.dev should be logged with their own dates so changes can be compared against the 2026-10-01 HTTP 403 result. During review, avoid submitting sensitive information to the domain until the recorded observations are independently verified.
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.
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