URLQuery
1 det.
Open reportPhishDestroy first recorded io-ledgr--startt.pages.dev on 2026-10-22. Stored VirusTotal result: 0/92 engines flagged. Analysis time (as stored): 2026-10-09 16:18 UTC. Retrieved (as stored): 2026-10-22 23:29 UTC. Listed by external blocklists: MetaMask, SEAL.
“Get started with Ledger — Ledger.com/start”
PhishDestroy analysis, earlier unreviewed version
PhishDestroy’s automated assessment labeled the domain as a seed‑phrase theft page because it mimics Ledger’s branding and uses a Ledger‑related title. The page was first seen by PhishDestroy on 2026-10-23, and the intake system had already flagged it as malicious on 2026-09-25 for the same impersonation reason. An HTTP check on 2026-10-25 returned a 403 status and the site was marked offline on 2026-10-24.
In a seed‑phrase theft scheme, attackers present a legitimate‑looking interface that asks users to enter their wallet recovery phrase, then capture the phrase to gain full control of the associated crypto assets. The victim’s funds can be moved without further interaction once the phrase is known. No specific form or request was captured on this page, but the classification reflects the typical risk of such impersonations.
VirusTotal reported 15 detections out of 92 engines on 2026-10-25, indicating malicious content. Google Safe Browsing showed no flag on 2026-10-23. urlscan recorded a malicious verdict with a 100 score on 2026-10-23 and identified Ledger as the targeted brand. External blocklists MetaMask and SEAL listed the domain, checked on 2026-10-25, and PhishDestroy’s internal blocklist also contains it (checked 2026-10-25). OTX recorded zero pulses as of 2026-10-23.
The recorded IP was 172.66.44.100 within Cloudflare’s network (AS13335) and the domain used Cloudflare DNS nameservers alan.ns.cloudflare.com and liberty.ns.cloudflare.com. The TLS certificate, issued by Google Trust Services, was valid from 2026-09-30 to 2026-12-29. The domain age was 376 days and the TLS certificate age was 22 days at the time of observation.
Anyone who entered a seed phrase on this site should treat the phrase as compromised, create a new hardware or software wallet, and transfer any assets to the new wallet. If any wallet approvals were granted, revoke them using the new wallet. Defenders should block the exact hostname, monitor logs for requests to the recorded IP, and apply threat‑intel alerts to prevent future exposure.
1 det.
Open reportMalicious
SHA-256 fba59d7e0b2bc0d5d3a518aff30b17b83a304b9d2378e4c8f077b5d8a22b9785
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
0 / 92 engine detections
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
no community references
Open reportNo threat flag
Open reportCheck recorded; verdict not retained
Open report75 / 100 · heuristic score · 4 brand references · 1 classification
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | Spf lookups: 0 |
|---|---|
| Caa records | Domain: io-ledgr--startt.pages.dev |
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Web archive observations | Last: 2026-09-25T13:52:20Z; First: 2026-09-25T13:52:20Z; Changes: 0; Days archived: 1; Avg page bytes: 5093 |
| Page title and metadata | Title: Get started with Ledger — Ledger.com/start |
| Trackers | Requests: 1 |
| Forms and mixed content | Third party scripts: 0 |
| Status | Up: ✓; Code: 200; Timings: DNS: 2; TLS: 16; Wait: 57; Connect: 18; Download: 0; Response ms: 93 |
| TLS connection | Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 80, 443, 8080 |
| Carbon | Bytes: 10955; Co2 grams: 0.0004; Cleaner than: 70 |
| DNS server | NS: (IP: 162.159.38.240; Host: liberty.ns.cloudflare.com), (IP: 172.64.33.57; Host: alan.ns.cloudflare.com); Zone: io-ledgr--startt.pages.dev |
| Location | IP: 2606:4700:310c::ac42:2c64; ASN: 13335; Org: Cloudflare, Inc.; City: San Francisco; Country: US |
| SSL | Issuer: Google Trust Services / WE1; Subject: io-ledgr--startt.pages.dev |
| DNS records | A: 172.66.44.100, 172.66.47.156; NS: liberty.ns.cloudflare.com, alan.ns.cloudflare.com; Soa: Nsname: alan.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2416887636; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:310c::ac42:2f9c, 2606:4700:310c::ac42:2c64 |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: ✗; Referrerpolicy: strict-origin-when-cross-origin; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Firewall | Waf: Cloudflare; Has waf: ✓ |
| Get IP | IP: 2606:4700:310c::ac42:2f9c; Family: 6 |
| Redirects | Chain: https://io-ledgr--startt.pages.dev |
| Tech stack | Technologies: HSTS, Cloudflare, HTTP/3 |
| Page links | External: https://www.ledger.com/start, https://www.ledger.com/ledger-live, https://www.ledger.com/support, https://www.ledger.com/academy, https://www.ledger.com/buy, https://www.ledger.com/security, https://www.ledger.com/wallets, https://www.ledger.com/resellers, https://www.ledger.com/company, https://www.ledger.com/blog; External count: 10 |
| HTTP headers | Headers: Server: cloudflare; Content type: text/html; charset=utf-8; X content type options: nosniff; Referrer policy: strict-origin-when-cross-origin |
PhishDestroy rates io-ledgr--startt.pages.dev as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-22. Stored VirusTotal result: 0/92 engines flagged. Analysis time (as stored): 2026-10-09 16:18 UTC. Retrieved (as stored): 2026-10-22 23:29 UTC. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
This report does not record which wallet requests io-ledgr--startt.pages.dev makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.
It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.
Checked, no match
Last checked
Edge-IP reputation is not attributed to this domain.
alan.ns.cloudflare.comliberty.ns.cloudflare.comnsname: alan.ns.cloudflare.comhostmaster: dns.cloudflare.comserial: 2416887636refresh: 10000retry: 2400expire: 604800minttl: 1800Location describes the IP network.
95ef3c4228679a3c16aef09300ab0497d71a9a5a2a93347c3dc1a674147f7c96io-ledgr--startt.pages.dev*.io-ledgr--startt.pages.devSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 2 SHA-256 hashes: 2 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 02:01 UTC.
Open this scan on URLScan 01a165e1-49b0-768b-a3d3-bcb5e1312b97 ↗
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Our scanner could not complete this check.
io-ledgr--startt.pages.dev Recorded events: 13. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
io-ledgr--startt.pages.dev
View sourcePage captured
View source0/92 engine detections
View sourcePage archived
View sourceWe 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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
52 stored lookalike domains
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Select your country to get official cybercrime contacts, or create a complaint draft →.
If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
Template-based draft • optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
io-ledgr--startt.pages.dev)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.