セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
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
VirusTotal 検出数: 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
engine detections
Google Safe Browsing
URLQuery
threat alerts
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
レポート概要

Ledgerなりすまし: ledger-recovery.support — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 16/89 (Criminal IP, alphaMountain.ai, BitDefender, Chong Lua Dao…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

Source evidenceVirusTotal 16 / 89 · OTX 24 references 9 sources

DNSブロック

1/12

Spamhaus DBL

DBL_PHISH

PhishStats

checked — no match recorded

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
Threat Detection Systems 2 alerts
Detection System Indicator Verdict Alert
DNS4EU ledger-recovery.support malicious Sinkholed
OpenDNS ledger-recovery.support phishing Phishing Block

Analysis

クリティカル
VirusTotal
16 / 89
OTX
24 community refs
Page captures
3

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

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) →
登録情報作成日 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.

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.

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
ソフォス
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 件

すべて表示(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

証拠および外部報告書

送信済み証拠のスナップショット
Sent: Ledger records: 1 Case ID: PD-20260328-99EEEF Recipient: abuse@name.com
Page title stored with report: Secure Wallet Management
PDF notice generated
詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

7 evidence signal groups linked 1 stored notification records 最後に確認されたアクティブな状態
If credentials were compromised, report immediately. Do not engage with recovery scammers.

アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。

Official reporting routes

復旧を装った詐欺に注意! 犯罪者は、捜査員、弁護士、または回収業者を装い、被害者に再び連絡を取る可能性があります。 前払い料金を支払ったり、資格情報を共有したりしないでください。 回復詐欺について詳しくはこちら →

お住まいの地域の当局へ報告してください

サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。

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アカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ(SMSではない)を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか?

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.
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した(以下を含む) ledger-recovery.support)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか?

  • FBI IC3 — インターネット犯罪通報センター(米国連邦政府の通報窓口)
  • ユーロポール — 欧州におけるサイバー犯罪の報告(EU)
  • 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?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか?

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する PhishDestroy 操作を行う前に、HTTPS、スペル、ドメインの登録期間を確認してください。
  • 「良すぎて怪しい」=詐欺 — 確実なリターン、有名人の推薦、差し迫った締め切り

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

最新情報を入手し、安全を確保しましょう

リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください

リアルタイム脅威情報フィード この掲載情報について異議を申し立てる
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.html
<iframe
  src="https://phishdestroy.io/ja/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>