VirusTotal
12 / 89
“Suspected Phishing | Cloudflare”
The domain ai-ledger-en-main.pages.dev returned an HTTP 403 status on 2026-10-01, a dated response recorded during an HTTP check. Separately, the same domain was first observed on 2026-08-10, giving a recorded starting point for later comparison.
On 2026-10-01, ai-ledger-en-main.pages.dev appeared on two external blocklists, MetaMask and SEAL. VirusTotal, checked on 2026-09-14, reported 12 detections across 89 scanners. The SSL certificate, issued by Google Trust Services / WE1, was scanned on 2026-09-13. Phishdestroy recorded an internal listing, and the blocklist check date was 2026-10-01.
The MetaMask and SEAL listings dated 2026-10-01 and the VirusTotal result dated 2026-09-14 come from different sources on different days, so they describe separate moments rather than one snapshot. The SSL scan of 2026-09-13 and the first observation of 2026-08-10 likewise sit at other points on the timeline. Comparing these dated records shows how observations accumulated over time without treating any single entry as current.
Retain the dated records for ai-ledger-en-main.pages.dev so later checks can be compared against them. When new observations arrive, line up their dates and source names with the entries already held. Avoid submitting sensitive information to ai-ledger-en-main.pages.dev while any review is in progress.
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.
edc1dd18a777b1e4fad4508d54aa62563556065c338f79f9b37d9f9f3f318008Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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