REGISTRAR NEGLIGENCE · EGREGIOUS NameSilo, LLC was notified 5 months ago — the threat is still operational.

Why this matters — ICANN RAA §3.18 obligation & victim-assistance

On 2026-02-15 16:48:31 UTC PhishDestroy delivered an evidence-backed abuse report (repeated 13 times, most recently 2026-02-15 16:48:31 UTC) to abuse@namesilo.com with the evidence stored for the case at that time. More than 5 months later, the phishing infrastructure remains reachable .

Under ICANN RAA §3.18 accredited registrars are contractually obliged to “take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse.” Silence beyond 24 hours after a documented notification with verifiable evidence is not a timing issue — it is a policy decision to let the operation continue. PhishDestroy\'s position: where a registrar fails to act on clear evidence, the registrar has aligned itself with the operator of the scheme and bears co-responsibility for downstream harm caused to victims from the moment of notification onward.

Victim-assistance obligation. If NameSilo, LLC doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 13 separate notifications over 5 months, with the operation still active, the registrar took no measurable action to mitigate the harm caused by their client. The reasonable next step is direct help to any identified victims — contact & payment-trail disclosure, abuse-thread transcripts, registrant data preservation — since the registrar chose, by inaction, to extend the window of damage.

Elapsed since first report

5 months

Reports sent

Latest case ID

PD-1771174106-xmrwallet.com

Current status

Serving traffic (alive)

ドメインのセキュリティと脅威インテリジェンス

xmrwallet[.]com

xmrwallet.com のフィッシング・安全性チェック

“Best Monero Wallet (XMR) - Send & Receive Monero Securely”

脅威の評決 クリティカル 83/100 証拠スコア

可用性 最後に確認されたアクティブな状態 最新の保存された到達可能性の観測

リスクシグナル

VirusTotal 検出数: 6/91 Spamhaus DBL: DBL_PHISH 保存されたブロックリストの一致: 1 詐欺タイプ: Crypto Scam 最後に確認されたアクティブな状態

6/91 VT OTX: 1 ref 2026年2月15日 1 Blocklist Crypto Scam 13 Reports Sent

リスクスコア: 83 (100 点中)。リスクレベル: クリティカル。

レポート概要

xmrwallet.com：VirusTotal の 91 エンジン中 6 件が検出。DNS、SSL、レジストラ、ブロックリスト、脅威情報を確認できます。

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

証拠の概要

重要

PhishDestroy first recorded xmrwallet.com on Feb 15, 2026. This English evidence brief is rebuilt from the current structured observations stored for the report. The current evidence score, computed from those stored observations, is 83/100.

The latest stored availability state is “Last known active” (HTTP 200) on Aug 4, 2026 at 10:50 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.

VirusTotal returned 6 detections from 91 scanners in the stored check on Jul 26, 2026 at 03:03 UTC. The independent blocklist snapshot recorded 1 match (CryptoFirewall) across 10 configured external sources on Aug 4, 2026 at 10:20 UTC. PhishDestroy's own listing is excluded from that count.

Other stored evidence. Google Safe Browsing stored no positive flag on Mar 2, 2026 at 20:57 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 1 pulse reference on Mar 1, 2026 at 08:16 UTC. OTX pulses are community-intelligence references, not vendor verdicts. Spamhaus DBL stored the result DBL_PHISH on Jul 14, 2026 at 10:32 UTC. A stored Cloudflare Radar snapshot labels the domain malicious. No source check timestamp is stored for this field. A URLScan capture is stored from Mar 25, 2026 at 11:38 UTC.

Stored context lists registrar NameSilo, LLC, IP address 186.2.165.49. Except for the registration date, these fields do not share a source timestamp in this report and may change.

Treat these as stored, time-bound observations rather than a live safety guarantee. Source verdicts and reachability can change, and zero or missing vendor matches never prove that a domain is safe. Avoid interacting with the domain while uncertainty remains, and use the appeal process if this report is inaccurate.

VirusTotal

6 det.

OTX references

1 community ref

CFレーダー

悪意あり

URLScan

レポート ↗

Gridinsoft

1/100

TLS証明書

期限切れまたは未検証

観測ステータス

最後に確認されたアクティブな状態 200

DestroyList

掲載あり

Reports Sent

13 ignored

データの網羅性 VirusTotal 6 / 91 URLQuery チェックされていない OTX 1 community reference CFレーダー provider verdict: malicious URLScan capture 保存されたレポート URLScan verdict 分析完了 DNSブロックチェックされていない TLS 期限切れまたは未検証 WHOIS not parsed スクリーンショット 2 captures · 2 sources リダイレクトチェーン調査されていない Gridinsoft 1/100

セキュリティシグナル

Gridinsoft Analysis 1 / 100

'', 00 AM 23 PM 6/29 Phishing Blacklisted Blacklisted by Security Providers Clean Cryptocurrency

ネットワークセキュリティインテリジェンス Registrar Integrity Alert

Registrar Integrity Alert

This domain is registered via NameSilo — a registrar that publicly lies, shields scammers, and retaliates against researchers.

NameSilo was documented protecting a $20M+ Monero-theft operation (xmrwallet[.]com) across ten continuous years while publicly denying abuse reports that PhishDestroy personally filed 20+ times. When we published the evidence, NameSilo’s response was to get our X account banned — on a justification X’s own automated review later called “no violation.”

Publicly lied about receiving abuse reports — 20+ notices sent by us over 3 years with preserved delivery receipts.
Shielded a $20M+ theft operation for 10 years behind bulletproof DDoS-Guard infrastructure.
Retaliated against researchers by weaponizing X’s abuse channel to silence our account.
Offered to help remove VirusTotal detections for a known phishing domain — on record.

Advisory for researchers, journalists & victims

Expect active deception from NameSilo — not merely abuse-report indifference, but false statements about how many reports they received. After exposure, they will typically claim no reports existed and pressure platforms to remove your published evidence.

Always CC a second authority (compliance@icann.org, sponsoring TLD registry, or CERT/LEA) on every abuse ticket.
Preserve delivery receipts — SMTP return-paths, auto-responder confirmations, ticket IDs.
Archive publicly before publishing — Wayback Machine, archive.today.

Read: How NameSilo Got Our Twitter Banned The $20M xmrwallet Case

Cloudflare Radar Verdict 悪意あり

Phishing Scam Phishing Security threats

脅威対応 Pipeline

ディスカバリー

Checks

Reports

可用性

29/30

URLScan.io Capture

Stored URLScan report with capture artifacts

2026年3月25日

URLScan Verdict

URLScan 分析が完了しました。この Web キャプチャの結果は、ページの脅威の判定を変更しません。 · score 0

2026年7月29日

Cloudflare Radar Report

A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.

Web Archive

Preserved in ウェイバック・マシン — historical evidence archived

VirusTotal

6/91 recorded on VirusTotal

2026年7月26日

Google Safe Browsing

Checked via Google 透明性レポート

2026年3月2日

ブロックリストの検出

掲載先 1 blocklist: CryptoFirewall

2026年8月4日

OTX Community References

1 community publication reference on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.

2026年3月1日

Registrar Warning: NameSilo

Caught publicly lying to protect scam clients & offering VT detection removal. Read investigation

CF Radar: Malicious

Cloudflare Radar classified this domain as phishing, Scam, Phishing, Security threats

Forensic Evidence Collected

Stored evidence from URLScan.io, stored screenshot

2026年3月25日

Technical Analysis Recorded

レポートには、保存されたテクノロジーまたはフォレンジック分析の結果が含まれます。

2026年8月4日

Cloudflare Radar Scan

Cloudflareレーダーでスキャン。ネットワーク解析が完了しました。

2026年3月2日

Initial Abuse Report (#1)

Sent to 1 abuse contact at NameSilo, LLC with forensic evidence

support@namesilo.com

2026年2月15日

ICANN Escalation #2

Escalation #2 sent to 3 recipients including ICANN Compliance — follow-up record after a previous report

support@namesilo.comabuse@verisign-grs.comcompliance@icann.org

2026年2月18日

ICANN Escalation #3

Escalation #3 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports

support@namesilo.comabuse@verisign-grs.comcompliance@icann.org

2026年2月19日

ICANN Escalation #4

Escalation #4 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports

support@namesilo.comabuse@verisign-grs.comcompliance@icann.org

2026年2月22日

ICANN Escalation #5

Escalation #5 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports

support@namesilo.comabuse@verisign-grs.comcompliance@icann.org

2026年2月23日

ICANN Escalation #6

Escalation #6 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports

support@namesilo.comabuse@verisign-grs.comcompliance@icann.org

2026年2月24日

ICANN Escalation #7

Escalation #7 sent to 3 recipients including ICANN Compliance — follow-up record after multiple previous reports