VirusTotal
12 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Ledgerなりすまし: us-ledger-us.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 12/89 (alphaMountain.ai, BitDefender, ESET, Emsisoft, Forcepoint…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 89 engine detections
レポートを開く悪意あり
レポートを開くno community references
レポートを開く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
us-ledger-us.pages.dev is a phishing page that impersonated Ledger. It targeted owners of Ledger hardware wallets, and the doubled "us" in the name was likely meant to look like an official regional support address. PhishDestroy first detected it on 2026-09-15. The site has been offline since 2026-09-21, and on 2026-10-19 it was still dead, with its content blocked by the hosting provider.
Ledger impersonation pages usually copy the brand's look and claim that the user's device needs a firmware update, a security sync or a wallet verification. The goal is to get the visitor to type their 24-word recovery phrase into a web form. Ledger never asks for this phrase online. Anyone holding it can rebuild the wallet on their own device and empty every account it controls, and the hardware wallet gives no protection against that. The page title now reads "Suspected Phishing | Cloudflare", which is Cloudflare's warning screen rather than Ledger-branded content, while we classify the domain as Ledger impersonation.
On 2026-09-21, 12 of 89 VirusTotal engines flagged the domain. The vendors included alphaMountain.ai, BitDefender, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data and Kaspersky. That is a modest share of engines, but these are established security vendors reaching the same verdict on their own. The domain is also listed on the MetaMask and SEAL blocklists as well as PhishDestroy's, so wallet users running those protections would have been warned.
The page ran on a free Cloudflare Pages subdomain, which costs nothing to create and needs no domain registration. It was served from Cloudflare, Inc. infrastructure geolocated to Canada. Its TLS certificate came from the WE1 issuer, which is issued automatically, so the padlock in the browser said nothing about whether the site was genuine. The provider block is the reason the content is no longer reachable.
If you entered your recovery phrase on this site, treat the wallet as compromised. Set up a new seed on a reset or new device and move any remaining funds to it right away. If you connected a software wallet, review and revoke token approvals you do not recognise. Get firmware and support only through Ledger Live and Ledger's official channels, and never type your recovery phrase into a website. Defenders should block the domain and watch for similar Ledger-themed pages on free hosting subdomains.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
Saved 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 us-ledger-us.pages.dev · checked Sep 21, 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.
us-ledger-us.pages.dev
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
到達可能
No threat flag
View source12/89 engine detections
View sourceus-ledger-us.pages.dev
View source保存された類似ドメイン:151 件
151 件中 100 件を表示
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
us-ledger-us.pages.dev)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.