VirusTotal
3 / 91 engine detections
レポートを開く“Xaman Wallet – Secure & Powerful XRP Ledger Wallet for Web3”
Ledgerなりすまし: xaman-x.online — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 3/91 (alphaMountain.ai, Chong Lua Dao, Gridinsoft); URLQuery 2 alerts; 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 91 engine detections
レポートを開く2 threat-system alerts
レポートを開く25 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くPage capture
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | xaman-x.online |
malicious | Sinkholed |
| DNS4EU | xaman-x.online |
malicious | Sinkholed |
PhishDestroy threat report
This domain, xaman-x.online, is identified as a brand impersonation threat targeting Ledger, a cryptocurrency hardware wallet provider. Analysis indicates the site mimics the Xaman Wallet interface, presenting itself as a "Secure & Powerful XRP Ledger Wallet for Web3" to deceive users into interacting with malicious infrastructure. The domain does not exhibit direct indicators of a crypto drainer kit but employs social engineering tactics to harvest sensitive credentials or wallet access details. Infrastructure analysis reveals the domain was registered on April 30, 2026, through NameCheap, Inc., a registrar frequently associated with malicious domains. It resolves to the IP address 188.114.96.3 and holds an SSL certificate issued by Google Trust Services, which may lend an appearance of legitimacy. Detection metrics include a VirusTotal score of 4/95 security vendors flagging the domain, presence on three security blocklists, and inclusion in one AlienVault OTX threat intelligence pulse. Gridinsoft assigns a trust score of 0/100, further corroborating its malicious classification. The domain is currently offline, likely due to takedown efforts or voluntary suspension by the registrar. It has been blocked by multiple security entities, including MetaMask, PhishDestroy, and SEAL. Despite its inactive status, residual risk persists for users who may have interacted with the domain prior to its removal. Organizations and individuals are advised to monitor for unauthorized access attempts, revoke any compromised credentials, and implement multi-factor authentication to mitigate potential exposure from this campaign.
Last checked
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.
Edge-IP の評判はこのドメインに起因しません。
roxy.ns.cloudflare.comLocation describes the IP network.
6d74394722314128aa8373993158ae3cf12e330325a3467822adb930d7a63996Saved 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 xaman-x.online · checked Jun 26, 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://xaman-x.online/; server=cloudflare
xaman-x.online
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
利用不可→到達可能
到達可能→利用不可
3→4
0→3
25 community references
View source3/91 engine detections
View sourceNo threat flag
View sourcexaman-x.online
View source保存された類似ドメイン:151 件
151 件中 100 件を表示
コミュニティの 1 人が報告・初回確認 2026年4月30日
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 ↗
xaman-x.online)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.