跳转到安全报告
分析仪表盘
域安全和威胁情报
ledger-recovery.support favicon

ledger-recovery.support

“Secure Wallet Management”

注册商
Name.com
Resolved IP
34.111.179.208
Registered
2026年3月27日
PhishDestroy assessment 关键
可用性 最后已知的活跃状态 最新存储的可达性观察 观察到 · HTTP probe
风险信号
病毒检测总数：16/89 Spamhaus DBL: DBL_PHISH URLQuery threat systems: 2 alerts 自动品牌标签：Ledger
OTX: 24 refs 2026年3月28日 1 Report Sent
API
该域名已被标记为恶意域名
安全引擎报告检测：16。 请格外小心——不要输入凭据或个人信息。
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.

Elapsed since first report
6 months
Reports sent
1
Latest case ID
PD-20260328-99EEEF
Current status
HTTP 301 at latest stored check
VirusTotal
16 / 89
engine detections
Google Safe Browsing
No threat flag
URLQuery
2
threat alerts
OTX
24
community references
Page captures
3
open gallery
Domain age
206 days
Reports sent
1
view timeline
报告概览

冒充 Ledger: ledger-recovery.support — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 16/89 (Criminal IP, alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar)…

为保留原始取证记录，下方的 PhishDestroy AI 详细分析仍使用英文。

Source evidenceVirusTotal 16 / 89 · OTX 24 references 9 sources

VirusTotal

16 / 89 engine detections

打开报告

URLQuery

2 threat-system alerts

打开报告

DNS 阻断

1/12

Spamhaus DBL

DBL_PHISH

PhishStats

checked — no match recorded

Google Safe Browsing

No threat flag

打开报告

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

网络安全情报
DNS Provider Blocks 1 / 12
Brand Ledger
Suspicious · Checked 12 DNS providers: Quad9, AdGuard, ControlD, CleanBrowsing & more
Threat Detection Systems 2 alerts
Detection System Indicator Verdict Alert
DNS4EU ledger-recovery.support malicious Sinkholed
OpenDNS ledger-recovery.support phishing Phishing Block
Stored URLQuery scan evidence · Mar 28, 2026 01:13 UTC Open source report

Analysis

关键
VirusTotal
16 / 89
OTX
24 community refs
Page captures
3
Page captures Source results Registration record

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

已保存的截图 · 3 captures

Primary capture 1 / 3
来源Primary capture
Recorded2026-03-28 00:21 UTC
StateStored capture
Position1 / 3
Open capture Wayback 下载
Observed page title
Secure Wallet Management
Automated brand references
Ledger
TLS 证书
颁发者 Let's Encrypt · stored validity ends in 88 days

Domain details

域名
URLScan verdict 恶意 score 100 Phishing brand: Ledger report ↗
IP 信誉 abuse score 17/100 84 reports Fraud OrdersPhishingOpen ProxyEmail SpamPort ScanHackingSpoofingBad Web BotExploited HostWeb App Attack checked 2026年10月12日
OTX tags 2026-03activeall-domainsblocklistcontentcrypto域名drainerfraudlivemonthlyphishdestroyphishingscam
注册商 Name.com (Unknown)
滥用举报联系方式abuse@name.com
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询ledger-recovery.support 的 ICANN RDAP →
注册信息创建 2026年3月27日 (206d) — Expires 2027年1月8日
HTTP 状态码301 Moved Permanently
技术详情Provenance & timestamps
首次发现2026年3月28日
DOM Analysisanalyzed 2026年10月9日score 98/1001 brand signal
Submitted URLhttps://ledger-recovery.support/
Favicon Hash
案件 ID
ICANN OVERSIGHT

认证和 RAA 背景

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.

认证是一纸合同，不是安全印章。 核实 ICANN 费用 阅读 RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft 不会自动发送任何内容。

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
34.111.179.208
Network ASN
AS396982
Organization
Google Cloud
Observed location
Kansas City, US
Server header
Google Frontend

域名服务器 1

  • ns1cny.name.com

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt
Valid from
2026-03-26 00:24:10
Valid until
2026-06-24 00:24:09
Validity
Stored certificate expired
Collection time
2026-10-20 13:02:19 UTC
Collection source
PhishDestroy collector
Certificate fingerprint3ce86364b5dfc7157dd6b14ee6d05ea7280793de966138a5c397de1b33b7b88d

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

viewdns.info · 34.111.179.208rapiddns.io

Latest Classified Outcome 2026-10-19 22:16:56 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-19 22:16:56 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-19 22:16:56 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.
技术 · 7 identified
E
Express
Google Cloud Trace
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

16 / 89 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 18 detections
Criminal IP
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
Ermes
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
卡巴斯基
Lionic
Seclookup
Sophos
VIPRE
Webroot

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
网站性能分析

Google PageSpeed Insights — mobile performance audit of ledger-recovery.support · checked Mar 28, 2026

69
Needs Work
Performance
FCP
4.87s
First Contentful Paint
LCP
4.87s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
1ms
Total Blocking Time
SI
5.27s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

Check for cloaking

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

No cloaking flag in this check

redirect: raw=redirect_301; http=301; via=http_proxy; location=https://ledger-recovery.support:443/

ledger-recovery.support
Stored observation history17

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  2. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  3. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  4. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  5. Availability monitor · Recorded state

    未知→redirected

    http_redirect

Earlier observations 12
  1. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  2. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  3. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  4. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  5. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  6. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  7. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  8. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  9. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  10. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  11. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  12. Availability monitor · Recorded state

    未知→redirected

    http_redirect

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    24 community references

    View source
  3. VirusTotal

    16/89 engine detections

    View source
  4. Abuse report sent

    PD-20260328-99EEEF

    abuse@name.com
  5. Added to PhishDestroy

    ledger-recovery.support

    View source

仿冒域名

已存储 151 个仿冒域名

ledfger.com insertion 内部报告 ledgfer.com insertion 内部报告 ledgher.com insertion 内部报告 ledgrr.com replacement 内部报告 lefdger.com insertion 内部报告 lesdger.com insertion 内部报告 lkedger.com insertion 内部报告 lredger.com insertion 内部报告 lwedger.com insertion 内部报告 xn--ledgr-9za.com homoglyph 内部报告 ledgerk.com addition 内部报告 edger.com omission
显示全部（88）
eldger.com transposition kedger.com replacement kledger.com insertion l3dger.com replacement ldeger.com transposition ldger.com omission le.dger.com subdomain lecger.com replacement ledber.com replacement ledegr.com transposition leder.com omission ledg3r.com replacement ledge.com omission ledged.com replacement ledgedr.com insertion ledgee.com replacement ledgeer.com repetition ledgercom.com various ledget.com replacement ledgewr.com insertion ledgger.com repetition ledgir.com vowel-swap ledgor.com vowel-swap ledgr.com omission ledgre.com transposition ledgrer.com insertion ledgsr.com replacement ledgwer.com insertion ledgwr.com replacement ledher.com replacement ledhger.com insertion ledsger.com insertion ledtger.com insertion ledyer.com replacement ledzer.com replacement leedger.com insertion legder.com transposition leger.com omission lerdger.com insertion lerger.com replacement lesger.com replacement lewdger.com insertion lidger.com vowel-swap lledger.com repetition lodger.com vowel-swap lrdger.com replacement lsdger.com replacement oedger.com replacement pedger.com replacement pledger.com insertion dedger.com bitsquatting hedger.com bitsquatting iedger.com homoglyph l-edger.com hyphenation ladger.com bitsquatting lcdlger.com homoglyph lddger.com bitsquatting lebger.com homoglyph leclger.com homoglyph ledcer.com bitsquatting leddger.com insertion ledeer.com bitsquatting ledeger.com insertion ledfer.com bitsquatting ledg-er.com hyphenation ledgar.com bitsquatting ledger0.com addition ledger1.com addition ledger4.com addition ledger5.com addition ledger6.com addition ledgerb.com addition ledgerc.com addition ledgerf.com addition ledgeri.com addition ledgern.com addition ledgerq.com addition ledgerx.com addition ledges.com bitsquatting ledgez.com bitsquatting ledgur.com bitsquatting lediger.com homoglyph ledqer.com homoglyph leeger.com bitsquatting leelger.com homoglyph lefger.com bitsquatting letger.com bitsquatting ludger.com bitsquatting

显示 151 个中的 100 个

社区报告

由 1 名社区成员报告；首次发现于 2026年3月27日

已存储报告
1
已报告的唯一 URL
1
已接受1

证据与外部报告

证券分析
URLScan 恶意 VirusTotal 16 det. ChainPatrol URLQuery 2 threat alerts SSL 实验室 CF雷达 打开报告 DNS Security 1/12 OTX 24 refs WOT ScamAdviser 黑名单检查器 URLVoid Sucuri SiteCheck MDN 观测站
已提交证据快照
Sent: Ledger records: 1 Case ID: PD-20260328-99EEEF Recipient: abuse@name.com
Page title stored with report: Secure Wallet Management
PDF notice generated
OSINT与情报分析
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox 哈德逊岩 Sign-in search IntelX crt.sh 证书 WHOIS Wayback Archived
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析
Help & reporting

您是否受到本网站的影响？

7 evidence signal groups linked 1 stored notification records 最后已知的活跃状态
If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息，或者从此域下载了文件，请立即采取措施。以下资源可帮助您报告事件并保护自己。

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review 不是执法报告
域名申诉
如果您拥有该域名并认为该列表不正确，请请求审核
警惕“数据恢复”诈骗！ 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

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

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident

针对受害者的建议与指导

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.

  • 更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息？

联邦调查局（FBI）指南

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.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的（包括 ledger-recovery.support)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整，对调查仍有帮助。

我应该向哪里举报这起诈骗？

  • 联邦调查局（FBI）IC3 — 互联网犯罪投诉中心（美国联邦举报渠道）
  • 欧洲刑警组织 — 欧洲网络犯罪报告（欧盟）
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 当地警方 — 即使无法立即采取行动，也能留下正式记录

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?

  • 虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站，使得欺诈行为更难被察觉

将来我该如何保护自己？

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前，请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

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

检查任意域名

使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析

立即扫描

举报网络钓鱼

将可疑域名提交至我们的威胁数据库——保护社区

报告

实时威胁动态

最近的网络钓鱼报告和观察到的可用性变化

监控

随时掌握最新信息，确保安全

请实时监控威胁，或者如果您认为这是误报，请对该条目提出异议

实时威胁动态 对该列表提出异议
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/ledger-recovery.support"
  title="PhishDestroy threat report for ledger-recovery.support"
  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>