Why this matters — ICANN RAA §3.18 obligation & victim-assistance
On PhishDestroy delivered an evidence-backed abuse report
(repeated 2 times, most recently ) to abuse@nic.io with the evidence stored for the case at that time.
More than 6 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 TLD Registry (.io) doesn't consider the listed detections enough proof — that is interesting in itself, given the volume of independent vendor confirmations. But after 2 separate notifications over 6 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.
amlwallets[.]io
Análisis de phishing y seguridad de amlwallets.io
“AML Wallet”
amlwallets.io: VirusTotal registra 16 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 amlwallets.io on Sep 8, 2025. 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 100/100.
The latest stored availability state is “Last known active” (HTTP 200) on Aug 2, 2026 at 22:14 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.
VirusTotal returned 16 detections from 91 scanners in the stored check on Jul 26, 2026 at 02:44 UTC. The independent blocklist snapshot recorded 3 matches (Polkadot, Enkrypt, Codeesura) across 10 configured external sources on Aug 2, 2026 at 22: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:26 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Mar 1, 2026 at 23:38 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 14, 2026 at 22:33 UTC. That result is not evidence of safety. A URLScan capture is stored from Mar 5, 2026 at 22:21 UTC.
Stored context lists registrar NameCheap, Inc., IP address 67.223.118.62, registration date Oct 10, 2024. 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
Proceso de respuesta ante amenazas Pipeline
Estado de la lista de bloqueados pública
Historial de denuncias de abuso · 2 stored reports over 54 days · click to expand
-
Report #1 Escalation 85h still active Jan 28, 2026 · 07:32 UTCESCALATION #3 (85h active): Phishing - amlwallets[.]ioabuse@namecheap.com
-
Report #4 ICANN CC 1363h still active Mar 22, 2026 · 16:37 UTCESCALATION #4 (1363h active): Phishing - amlwallets[.]ioabuse@nic.io compliance@icann.org
Tecnologías · 1 identified
High-performance web server compatible with Apache configurations.
Análisis de VirusTotal
Evidencias archivadas
Análisis del rendimiento del sitio
Google PageSpeed Insights — mobile performance audit of amlwallets.io · 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: amlwallets.io
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 “AML Wallet”.
A partir de 02/08/2026, amlwallets.io tuvo detecciones de los motores de seguridad 16.
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.