Skip to security report
Recorded security signals
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. Use caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
io-ledgr--startt.pages.dev favicon

io-ledgr--startt.pages.dev

In short

PhishDestroy 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”

Registrar
United StatesCloudflare
Resolved IP
Canada172.66.44.100Cloudflare, Inc. · CDN
First observed
Oct 22, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Reachable · access restricted Reachable response; page content was not verified Observed HTTP probe
Stored blocklist matches: 2 Last known active
VirusTotal
engine detections ·
Blocklist matches
MetaMask, SEAL
URLQuery
detections
URLScan
Page captures
open gallery
Oct 23, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy 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. Risk: critical (100/100). Registrar: Cloudflare. Status: Reachable · access restricted. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Reachable · access restricted
VirusTotal
0 / 92
Blocklist matches
2
Scam type (automated label)
Seed Phrase Theft
Hosting
Canada172.66.44.100Cloudflare, Inc. · CDN
Registrar
United StatesCloudflare
Page captures
9

PhishDestroy analysis, earlier unreviewed version

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Source evidenceVirusTotal 0 / 92 8 sources

URLScan

Malicious

SHA-256 fba59d7e0b2bc0d5d3a518aff30b17b83a304b9d2378e4c8f077b5d8a22b9785

Open report
URLScanOriginal source recordObserved: 18 fields
Separate monitor record · 2026-10-23 03:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a165e1-49b0-768b-a3d3-bcb5e1312b97
Score
100
Malicious
✓
Result at
2026-10-23T03:30:26Z
Enriched at
2026-10-23T08:17:50Z
Source timestamps
Urlscan result at: 2026-10-23 05:30:26; Urlscan enriched at: 2026-10-23 10:17:50

VirusTotal

0 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields
Separate collector summary

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.

Source
VirusTotal
Result state
observed
Numerator
15
Denominator
92
Vendors
alphaMountain.ai, BitDefender, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Netcraft, SafeToOpen, SOCRadar, Sophos, Webroot
Observed at
2026-10-23 02:37:23
Checked at
2026-10-25 02:01:57
Fetched at
2026-10-25 00:01:57

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

75 / 100 · heuristic score · 4 brand references · 1 classification

Open report
Separate monitor score · 75 / 100 · 2026-10-23T02:20:24Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
75
Analyzed at
2026-10-23T02:20:24Z
Source timestamp
2026-10-23 04:20:24

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

Ai summary
Overview 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. How the scam works 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. Evidence 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. Infrastructure 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. What to do 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. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a165e1-49b0-768b-a3d3-bcb5e1312b97/ Stored capture screenshot: https://i.ibb.co/xKCR0Hq6/ec75db44f5c7.png URLScan screenshot (2026-09-25T13:56:01Z): https://screenshots.phishdestroy.io/us/01a0d8d9-ec82-75dc-a9f0-e2ca63bb7261.png URLScan capture report: https://urlscan.io/result/01a0d8d9-ec82-75dc-a9f0-e2ca63bb7261/ URLScan screenshot (2026-10-22T18:16:42Z): https://screenshots.phishdestroy.io/us/01a164d4-2197-7059-b0aa-2ad43fd46f57.png URLScan capture report: https://urlscan.io/result/01a164d4-2197-7059-b0aa-2ad43fd46f57/ VirusTotal report: https://www.virustotal.com/gui/domain/io-ledgr--startt.pages.dev Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=io-ledgr--startt.pages.dev Archived copy: https://web.archive.org/web/20260925135220/https://io-ledgr--startt.pages.dev/ Revoke token approvals: https://revoke.cash/ Report crypto fraud (Chainabuse): https://www.chainabuse.com/report Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
Ai generated by
threat-v3-groq
Ai generated at
2026-10-25 03:33:40
Revision
7f2cf33a99d327ce90a16360b18ca9d79f5c69a9da44320171c696928b0b1011
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 24 fields

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

HTTP response

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 estimate

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: ✗

Web application firewall

Waf: Cloudflare; Has waf: ✓

Get IP

IP: 2606:4700:310c::ac42:2f9c; Family: 6

Redirects

Chain: https://io-ledgr--startt.pages.dev

Technology 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
Original source fields · JSON
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

Questions about io-ledgr--startt.pages.dev

Is io-ledgr--startt.pages.dev legit?

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.

Is io-ledgr--startt.pages.dev safe to connect a wallet?

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.

What should I do if I used io-ledgr--startt.pages.dev?

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.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 9 captures

All capture links and hashes (9)
io-ledgr--startt.pages.dev: Crypto scam — Blocked by MetaMask, flagged by SEAL, 15/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card io-ledgr--startt.pages.dev: Crypto scam — Blocked by MetaMask, flagged by SEAL, 15/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 788155e99884

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Ledger report ↗
IP Context Canada172.66.44.100 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Cloudflare US(US)
HTTP Status403 Forbidden
Elapsed Since First Report 13 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 75/1004 brand signals
Submitted URLhttp://io-ledgr--startt.pages.dev/
Favicon Hash
Observed page title
Get started with Ledger — Ledger.com/start
Automated brand references
Across Base Ethereum Ledger
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 42 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.66.44.100
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • alan.ns.cloudflare.com
  • liberty.ns.cloudflare.com

SOA

  • nsname: alan.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2416887636
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-30 11:31:35
Valid until
2026-12-29 12:29:08
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint95ef3c4228679a3c16aef09300ab0497d71a9a5a2a93347c3dc1a674147f7c96
Certificate names · 2 SANs
  • io-ledgr--startt.pages.dev
  • *.io-ledgr--startt.pages.dev

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Report This Domain Submit evidence & help protect others

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

Registration & observation details2

Availability observations

Last reachable observation
Last content observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data107
Open complete records

Captured network requests

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 ↗

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

Page titles differ

Our scanner could not complete this check.

Browser
Get started with Ledger — Ledger.com/start
Crawler
Suspected Phishing | Cloudflare
io-ledgr--startt.pages.dev
Stored observation history16
Open complete records
All retained availability observations30
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 13. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    io-ledgr--startt.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · Blocklist Detection · Automated brand label: Ethereum · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable · Site Came Back Online · Content Observed Unavailable Recorded: 10 of 10
Publication & AvailabilityDestroyList Published · Time to First Unavailability · Monitoring Continues Recorded: 2 of 3
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 300
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. Added to PhishDestroy

    io-ledgr--startt.pages.dev

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    0/92 engine detections

    View source
  4. Wayback Machine

    Page archived

    View source
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

All stored records by source

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

Lookalike domains

52 stored lookalike domains

Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.

ethercum.org Lookalike letters Variant of ethereum.org Internal report A 188.114.96.3NS bart.ns.cloudflare.com etheruem.org Swapped characters Variant of ethereum.org Internal report A 212.99.218.66NS ns-1511.awsdns-60.org athereum.org Bit flip Variant of ethereum.org A 199.188.200.6MX mail.athereum.orgNS dns1.namecheaphosting.com dethereum.org Inserted character Variant of ethereum.org A 216.198.79.1NS liv.ns.cloudflare.com e.thereum.org Split into subdomain Variant of ethereum.org A 103.224.212.210MX park-mx.above.comNS ns15.abovedomains.com efhereum.org Replaced character Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ehereum.org Missing character Variant of ethereum.org A 15.197.225.128NS ns65.domaincontrol.com etereum.org Missing character Variant of ethereum.org A !ServFailNS !ServFail eth3reum.org Replaced character Variant of ethereum.org A 15.197.142.173NS ns31.domaincontrol.com ether.eum.org Split into subdomain Variant of ethereum.org A 13.248.169.48NS ns1.afternic.com etheream.org Vowel swap Variant of ethereum.org A 162.255.119.154MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethereim.org Replaced character Variant of ethereum.org A 15.197.142.173NS ns33.domaincontrol.com
Show all (40)
ethereium.org Inserted character Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com etherem.org Missing character Variant of ethereum.org A 15.197.225.128NS ns39.domaincontrol.com etheremu.org Swapped characters Variant of ethereum.org A 13.248.169.48NS ns1.afternic.com ethereom.org Vowel swap Variant of ethereum.org A 192.0.78.24NS ns1.wordpress.com etheresum.org Inserted character Variant of ethereum.org A 104.21.87.66NS aron.ns.cloudflare.com ethereujm.org Inserted character Variant of ethereum.org A 104.21.46.240NS jerry.ns.cloudflare.com ethereum2.org Added character Variant of ethereum.org A 24.199.74.33NS ns3.namefi.io ethereum3.org Added character Variant of ethereum.org NS a.share-dns.com ethereum4.org Added character Variant of ethereum.org A 198.54.117.242NS failed-whois-verification.namecheap.com ethereumc.org Added character Variant of ethereum.org A 188.114.96.3NS camilo.ns.cloudflare.com ethereumd.org Added character Variant of ethereum.org A 188.114.96.3NS earl.ns.cloudflare.com ethereumorg.com Variant Variant of ethereum.org NS ns1.openprovider.nl ethereumr.org Added character Variant of ethereum.org A 188.114.96.3NS monroe.ns.cloudflare.com ethereums.org Added character Variant of ethereum.org A 15.197.148.33MX mailstore1.secureserver.netNS ns73.domaincontrol.com ethereumx.org Added character Variant of ethereum.org A 64.190.63.222MX localhostNS ns1.sedoparking.com ethereun.org Lookalike letters Variant of ethereum.org A 52.20.84.62NS ns1.squadhelp.com ethereunm.org Lookalike letters Variant of ethereum.org A 104.21.86.145NS koa.ns.cloudflare.com ethereurm.org Lookalike letters Variant of ethereum.org A 188.114.96.3NS rita.ns.cloudflare.com ethereurn.org Lookalike letters Variant of ethereum.org MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethereuym.org Inserted character Variant of ethereum.org A 104.21.22.142NS everton.ns.cloudflare.com ethereuzm.org Inserted character Variant of ethereum.org A 188.114.96.3NS dale.ns.cloudflare.com ethereyum.org Inserted character Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com etherium.org Vowel swap Variant of ethereum.org A 32.216.8.188NS ns1.no-ip.com etherrum.org Replaced character Variant of ethereum.org MX eforward1.registrar-servers.comNS dns1.registrar-servers.com etherteum.org Inserted character Variant of ethereum.org A 13.248.243.5NS ns41.domaincontrol.com etherum.org Missing character Variant of ethereum.org A 103.224.212.201MX park-mx.above.comNS ns1.abovedomains.com ethezeum.org Bit flip Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ethireum.org Vowel swap Variant of ethereum.org A 192.64.119.29MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethnereum.org Inserted character Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ethreum.org Missing character Variant of ethereum.org A 15.197.225.128NS ns65.domaincontrol.com ethureum.org Bit flip Variant of ethereum.org A 162.255.119.109MX eforward1.registrar-servers.comNS dns1.registrar-servers.com etihereum.org Lookalike letters Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ithereum.org Vowel swap Variant of ethereum.org A 188.114.96.3NS celine.ns.cloudflare.com othereum.org Vowel swap Variant of ethereum.org NS ns-cloud-a1.googledomains.com rethereum.org Inserted character Variant of ethereum.org A 54.36.108.60MX eforward1.registrar-servers.comNS dns1.registrar-servers.com sethereum.org Inserted character Variant of ethereum.org A !ServFailNS !ServFail thereum.org Missing character Variant of ethereum.org A 103.224.212.210MX park-mx.above.comNS ns15.abovedomains.com uthereum.org Bit flip Variant of ethereum.org A 15.197.148.33NS ns15.domaincontrol.com zethereum.org Inserted character Variant of ethereum.org NS ns-1335.awsdns-38.org zthereum.org Replaced character Variant of ethereum.org NS ns-1294.awsdns-33.org

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Reachable · access restricted
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Official reporting routes

More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

Report to Your Local Authorities

Select 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.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including io-ledgr--startt.pages.dev)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/io-ledgr--startt.pages.dev"
  title="PhishDestroy threat report for io-ledgr--startt.pages.dev"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>