Why this matters — ICANN RAA §3.18 obligation & victim-assistance
On PhishDestroy delivered an evidence-backed abuse report
(repeated 4 times, most recently ) to abuse@nic.io with VirusTotal detections, urlscan capture, legal violations, and full screenshot evidence.
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 4 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
Verifica phishing e sicurezza per amlwallets.io
“AML Wallet”
amlwallets.io: 16 rilevamenti su 91 scanner VirusTotal. Consulta DNS, SSL, registrar, blocklist e dati sulle minacce.
L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.
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 00:13 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 04:44 UTC. The independent blocklist snapshot recorded 3 matches (Polkadot, Enkrypt, Codeesura) across 10 configured external sources on Aug 2, 2026 at 04: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 21:26 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Mar 2, 2026 at 00:38 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 15, 2026 at 00:33 UTC. That result is not evidence of safety. A URLScan capture is stored from Mar 5, 2026 at 23: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.
Indicatori di sicurezza
Pipeline di risposta alle minacce
Stato della lista di blocco pubblica
Cronologia delle segnalazioni di 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
Tecnologie · 1 identified
High-performance web server compatible with Apache configurations.
Analisi di VirusTotal
Prove archiviate
Analisi delle prestazioni del sito
Google PageSpeed Insights — mobile performance audit of amlwallets.io · checked Mar 2, 2026
Dati e relazioni esterne
Questo sito ti ha influenzato in qualche modo?
Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.
Segnalalo alle autorità locali
Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.
Informazioni su questo rapporto: amlwallets.io
Questo rapporto presenta le ultime prove archiviate disponibili per PhishDestroy. I timestamp della sorgente vengono mostrati ove disponibili; la disponibilità e i verdetti del fornitore possono cambiare dopo il ritiro.
Il sito acquisito mostrava il titolo della pagina “AML Wallet”.
Al momento di 02/08/2026, amlwallets.io ha ricevuto rilevamenti dai motori di sicurezza 16.
Se ritieni che questo elenco sia impreciso, presentare ricorso. Per conoscere la nostra metodologia, visita Pagina delle domande frequenti.
Verifica qualsiasi dominio
Analisi delle minacce utilizzando blocklist archiviate, WHOIS, DNS e prove di scansione pubblica
Scansiona oraSegnala un tentativo di phishing
Segnala i domini sospetti al nostro database delle minacce — proteggi la comunità
SegnalaFeed in tempo reale sulle minacce
Segnalazioni recenti di phishing e modifiche osservate della disponibilità
MonitoraRimani informato, rimani al sicuro
Controlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo