Why this matters — ICANN RAA §3.18 obligation & victim-assistance
On PhishDestroy delivered an evidence-backed abuse report
(repeated 13 times, most recently ) 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.
xmrwallet[.]com
Análisis de phishing y seguridad de xmrwallet.com
“Best Monero Wallet (XMR) - Send & Receive Monero Securely”
xmrwallet.com: VirusTotal registra 6 detecciones de 91. Consulta DNS, SSL, registrador, listas de bloqueo y datos sobre amenazas.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
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 5, 2026 at 02:08 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 5, 2026 at 06: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.
Señales de seguridad
Inteligencia de seguridad de red Registrar Integrity Alert
Proceso de respuesta ante amenazas Pipeline
Estado de la lista de bloqueados pública
Captura guardada
Inteligencia de dominios
Detalles técnicosDNS, SAN de SSL, marcas de tiempo
ICANN OVERSIGHT
Acreditación y contexto RAA
Acreditación y contexto RAA
ICANN cobró. La rendición de cuentas no llegó.
Para este gTLD, el registrador indicado arriba opera bajo un contrato con ICANN. ICANN cobra tasas anuales, variables y basadas en transacciones vinculadas a registros, renovaciones y transferencias.
Acreditación: monetizada. Rendición de cuentas: vuelva a comprobarlo más tarde.
Entonces empieza la magia: ICANN redacta el RAA §3.18, el registrador investiga los abusos dentro de su propia base de clientes y las víctimas aportan las pruebas gratis, mientras cada nivel espera que actúe otro. Si eso hace que las víctimas se sientan más seguras, excelente: la factura funcionó.
Historial de denuncias de abuso · 13 stored reports over 83 days · click to expand
-
Report #1 Feb 15, 2026 · 16:48 UTCPhishing Abuse Report: xmrwallet[.]comsupport@namesilo.com
-
Report #2 ICANN CC 67h still active Feb 18, 2026 · 12:11 UTCESCALATION #2 (67h active): Phishing - xmrwallet[.]comsupport@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #3 ICANN CC 91h still active Feb 19, 2026 · 11:58 UTCESCALATION #3 (91h active): Phishing - xmrwallet[.]comsupport@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #4 ICANN CC 164h still active Feb 22, 2026 · 13:45 UTCESCALATION #4 (164h active): Phishing - xmrwallet[.]comsupport@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #5 ICANN CC 196h still active Feb 23, 2026 · 21:45 UTCESCALATION #5 (196h active): Phishing - xmrwallet[.]comsupport@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #6 ICANN CC 213h still active Feb 24, 2026 · 14:05 UTCESCALATION #6 (213h active): Phishing - xmrwallet[.]comsupport@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #7 ICANN CC 420h still active Mar 5, 2026 · 05:15 UTCESCALATION #7 (420h active): Phishing - xmrwallet[.]comabuse@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #8 ICANN CC 500h still active Mar 8, 2026 · 13:04 UTCESCALATION #8 (500h active): Phishing - xmrwallet[.]comabuse@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #9 ICANN CC 597h still active Mar 12, 2026 · 14:16 UTCESCALATION #9 (597h active): Phishing - xmrwallet[.]comabuse@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #10 ICANN CC 644h still active Mar 14, 2026 · 12:51 UTCESCALATION #10 (644h active): Phishing - xmrwallet[.]comabuse@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #11 ICANN CC 691h still active Mar 16, 2026 · 12:37 UTCESCALATION #11 (691h active): Phishing - xmrwallet[.]comabuse@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #12 ICANN CC 1296h still active Apr 10, 2026 · 20:33 UTCESCALATION #12 (1296h active): Phishing - xmrwallet[.]comabuse@namesilo.com abuse@verisign-grs.com compliance@icann.org
-
Report #13 ICANN CC 1985h still active May 9, 2026 · 13:13 UTCESCALATION #13 (1985h active): Phishing - xmrwallet[.]comabuse@namesilo.com abuse@verisign-grs.com compliance@icann.org
Tecnologías · 4 identified
Server-side scripting language designed for web development.
Fast, small JavaScript library simplifying HTML manipulation, event handling, and Ajax.
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Análisis de VirusTotal
Evidencias archivadas
Análisis del rendimiento del sitio
Google PageSpeed Insights — mobile performance audit of xmrwallet.com · checked Mar 2, 2026
Datos y informes externos
¿Te ha afectado esta página web?
Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.
Informa a las autoridades locales
Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.
Acerca de este informe: xmrwallet.com
Este informe presenta la última evidencia almacenada disponible para PhishDestroy. Las marcas de tiempo de origen se muestran cuando están disponibles; La disponibilidad y los veredictos de los proveedores pueden cambiar después de la recolección.
El sitio capturado mostraba el título de la página “Best Monero Wallet (XMR) - Send & Receive Monero Securely”.
A partir de 05/08/2026, xmrwallet.com tuvo detecciones de los motores de seguridad 6.
Si cree que esta lista es inexacta, presentar una apelación. Para conocer nuestra metodología, visita el Página de preguntas frecuentes.
Comprobar cualquier dominio
Análisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público
Escanear ahoraDenunciar un intento de phishing
Envía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad
DenunciarFlujo de amenazas en tiempo real
Informes de phishing recientes y cambios de disponibilidad observados
MonitorizarMantente informado, mantente a salvo
Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.