VirusTotal
16 / 89 engine detections
보고서 열기“Secure Wallet Management”
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 사칭: ledger-recovery.support — 마지막으로 알려진 활성 (HTTP 301). 증거 요약: VirusTotal 16/89 (Criminal IP, alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar)…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
16 / 89 engine detections
보고서 열기2 threat-system alerts
보고서 열기1/12
DBL_PHISH
악성
보고서 열기checked — no match recorded
24 community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
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.
ns1cny.name.comLocation describes the IP network.
3ce86364b5dfc7157dd6b14ee6d05ea7280793de966138a5c397de1b33b7b88dSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of ledger-recovery.support · checked Mar 28, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://ledger-recovery.support:443/
ledger-recovery.support
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
알 수 없음→redirected
http_redirect
No threat flag
View source24 community references
View source16/89 engine detections
View sourcePD-20260328-99EEEF
ledger-recovery.support
View source저장된 유사 도메인 151개
전체 151개 중 100개 표시
커뮤니티 구성원 1명이 신고 · 최초 확인 2026년 3월 27일
PD-20260328-99EEEF Recipient: abuse@name.com 계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
ledger-recovery.support)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.