VirusTotal
11 / 89
“How to Set up Ledger Portfolio & Wallet App”
On 2026-10-01, ledgerr-comstart.pages.dev returned an HTTP 403 status in a recorded observation. The same domain was first observed on 2026-08-31, according to the recorded timeline.
The domain ledgerr-comstart.pages.dev appeared on two external blocklists, MetaMask and SEAL, as recorded at the 2026-10-01 check. VirusTotal recorded 11 detections across 89 scanners on 2026-09-11. The domain resolved to IP address 172.66.47.105, associated with Cloudflare, Inc. in CA, per the 2026-10-01 HTTP check. PhishDestroy's internal listing for this domain was recorded as true.
The MetaMask and SEAL blocklist entries and the PhishDestroy internal listing are dated 2026-10-01, while the VirusTotal scan is dated 2026-09-11, so the two sets of observations are not contemporaneous. Because the HTTP 403 response and the blocklist checks share the 2026-10-01 date, those records can be compared directly, but the earlier VirusTotal scan reflects a different point in time.
Reviewers should retain the recorded observations for ledgerr-comstart.pages.dev, including the dated HTTP 403 response and the blocklist entries, so later checks can be compared against them. Any subsequent observation of ledgerr-comstart.pages.dev should be logged with its own date and source. During review, avoid submitting sensitive information to the domain until the recorded status is clarified.
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