Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@name.com.
The latest stored availability evidence still shows the domain reachable; 6 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
ledger-recovery.support presents a significant brand impersonation threat targeting users of the Ledger cryptocurrency platform. This domain attempts to deceive victims by masquerading as an official Ledger recovery support site, potentially harvesting sensitive credentials or initiating fraudulent transactions. Such impersonation exploits users' trust in the Ledger brand to facilitate financial theft or identity compromise.
According to current threat intelligence, ledger-recovery.support has been flagged by 18 out of 95 security vendors on VirusTotal, indicating substantial consensus on its malicious nature. The domain was registered recently on January 08, 2026, through the registrar Name.com, Inc., suggesting it is a newly created threat actor. Its SSL certificate is issued by Let's Encrypt, which may lend superficial legitimacy to unsuspecting users. The domain resolves to IP address 34.111.179.208, and it remains active and operational, maintaining an elevated risk level within brand impersonation categories.
Users who have encountered or interacted with ledger-recovery.support should immediately cease engagement and refrain from submitting any personal or financial data. It is advisable to run comprehensive malware and credential scan tools on affected devices, update passwords associated with Ledger accounts, and remain vigilant for further fraudulent communications. Organizations are urged to block this domain at network perimeters and educate users about this specific threat to prevent potential losses.
RegistrationCreated Mar 27, 2026 (206d)—Expires Jan 8, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedMar 28, 2026
DOM Analysisanalyzed Oct 9, 2026score 98/1001 brand signal
Submitted URLhttps://ledger-recovery.support/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-19 10:17:38 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-19 10:17:38 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 7 identified
N
Node.js
Programming languages
JavaScript runtime built on Chrome V8 engine for server-side development.
Google Cloud
PaaSIaaS
Suite of cloud computing services running on Google infrastructure.
E
Express
H
HSTS
Security
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google Cloud Trace
Google Cloud CDN
CDN
Content delivery network built on Google global edge infrastructure.
H
HTTP/3
Miscellaneous
Third major version of HTTP protocol, built on QUIC for faster, more reliable connections.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · ledger-recovery.support
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches5
Same favicon hash or the same page title as this host.
7 evidence signal groups linked1 stored notification recordsLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
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 →
Template-based draft · optional AI wording assistance requires separate consent
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.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
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 ledger-recovery.support)
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)
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
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.
