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
Pemeriksaan phishing dan keamanan amlwallets.io
“AML Wallet”
amlwallets.io: 16 dari 91 pemindai VirusTotal menandai domain ini. Tinjau DNS, SSL, registrar, daftar blokir, dan data ancaman.
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
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 10:07 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 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: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.
Sinyal Keamanan
Alur Tanggapan Ancaman Pipeline
Status Daftar Blokir Publik
Riwayat Laporan Penyalahgunaan · 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
Teknologi · 1 identified
High-performance web server compatible with Apache configurations.
Analisis VirusTotal
Bukti Terarsip
Analisis Performa Situs
Google PageSpeed Insights — mobile performance audit of amlwallets.io · checked Mar 2, 2026
Bukti & Laporan Eksternal
Apakah Anda Terpengaruh oleh Situs Ini?
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Laporkan kepada Pihak Berwenang di Daerah Anda
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Tentang Laporan Ini: amlwallets.io
Laporan ini menyajikan bukti tersimpan terbaru yang tersedia untuk PhishDestroy. Stempel waktu sumber ditampilkan jika tersedia; ketersediaan dan keputusan vendor dapat berubah setelah pengumpulan.
Situs yang diambil menampilkan judul halaman “AML Wallet”.
Pada 02/08/2026, amlwallets.io memiliki deteksi dari mesin keamanan 16.
Jika Anda yakin daftar ini tidak akurat, mengajukan banding. Untuk mempelajari metodologi kami, kunjungi halaman pertanyaan umum.
Periksa Domain Apa Pun
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan Phishing
Laporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanPemberitahuan Ancaman Real-Time
Laporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauTetap Terinformasi, Tetap Aman
Pantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive