VirusTotal
5 / 89 engine detections
レポートを開く“Index of /”
Ledgerなりすまし: ledger-auth.com — コンテンツが利用できません. 証拠の概要: VirusTotal 5/89 (alphaMountain.ai, CRDF, Fortinet, Gridinsoft, LevelBlue); URLQuery 2 det.; Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 89 engine detections
レポートを開く2 det.
レポートを開くDBL_PHISH
4 community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ledger-auth.com is a phishing domain built to pass as an official Ledger authentication service, aimed at people who hold crypto on Ledger hardware wallets. PhishDestroy first flagged it on 2026-09-23. The site went offline on 2026-09-24, and when last checked on 2026-10-19 its DNS was no longer resolving.
Ledger impersonation sites usually claim the device needs verification, a firmware fix or a security check. They then ask the visitor to type in their 24-word recovery phrase. Anyone holding that phrase can rebuild the wallet on their own device and empty it, and no Ledger hardware protection can stop it. Ledger never asks for the recovery phrase on any website. When we checked, the page title was a bare "Index of /" directory listing, which does not match the Ledger impersonation we classified.
Five of 89 VirusTotal engines flagged the domain on 2026-09-23: alphaMountain.ai, CRDF, Fortinet, Gridinsoft and LevelBlue. That is a modest count, but it is not the only signal. Spamhaus lists the domain in its DBL under the phishing category, and it appears in four AlienVault OTX threat pulses. It is also on the PhishDestroy blocklist.
The domain was registered on 2026-06-01 through OwnRegistrar, Inc. That is roughly 16 weeks before it was detected, so it was not a throwaway registered the same day. Traffic ran through Cloudflare, Inc., with the hosting attributed to Canada, which hides the origin server behind a shared network. The site used a Google Trust Services certificate, so it showed a normal padlock. That padlock said nothing about who ran the site.
If you entered your recovery phrase on this site, treat the wallet as compromised. Set up a device with a brand-new phrase and move whatever funds remain right away. If you connected the wallet and signed anything, review and revoke token approvals as well. Never reuse the exposed phrase, and ignore any follow-up messages offering "recovery" help. Defenders should block ledger-auth.com and watch for lookalike domains that pair Ledger branding with words like auth, verify or support.
Edge-IP の評判はこのドメインに起因しません。
langston.ns.cloudflare.commaria.ns.cloudflare.comLocation describes the IP network.
45af764d1b6cbf21a542867b604073ab736abb13bb57df6893e0bc795d3394aeSaved 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-auth.com · checked Sep 23, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
到達可能
4 community references
View sourceNo threat flag
View source5/89 engine detections
View sourcePD-20260923-13682D
ledger-auth.com
View sourcePage captured
View source保存された類似ドメイン:151 件
151 件中 100 件を表示
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ledger-auth.com
PD-20260923-13682D Recipient: abuse@ownregistrar.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-auth.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.