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.im with the evidence stored for the case at that time.
More than 4 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 (.im) 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 4 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.
amlbot[.]im
Verificação de phishing e segurança de amlbot.im
“AML Check”
amlbot.im — Último ativo conhecido (HTTP 200). Representação da marca: AMLBot; Tipo de golpe: Crypto Scam. Resumo das evidências: VT 6/91 (alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); URLQuery 0; URLScan no malicious verdict; GSB no flag; Spamhaus DBL_PHISH; BL 0; PD 80/100. Registrador: Redacted.
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
PhishDestroy first observed amlbot.im on Feb 1, 2026. The hostname explicitly references AMLBot; stored content metadata identifies the same apparent target. The captured page title is “AML Check”. Stored page analysis classifies the content as crypto scam. Current evidence score: 80/100 (critical).
Positive findings are stored from 2 sources: VirusTotal and Spamhaus DBL. VirusTotal recorded 6 detections among 91 engines: alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar on Aug 6, 2026 at 02:10 UTC. Spamhaus DBL: DBL_PHISH on Jul 14, 2026 at 10:36 UTC. Non-positive and contextual checks: The external blocklist snapshot contained no matches on Aug 7, 2026 at 22:20 UTC. URLQuery recorded no positive detection; no observation timestamp was retained. Google Safe Browsing returned no flag on Mar 3, 2026 at 04:14 UTC. URLScan completed without a malicious verdict (score 0) on Jul 29, 2026 at 03:26 UTC.
HTTP 200 was recorded on Aug 7, 2026 at 22:14 UTC. Registration records for the domain list Redacted as the registrar. At collection time, the hostname resolved to 172.67.148.110 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. DOM analysis on Jul 28, 2026 at 02:20 UTC returned 0/100; the source detections above were recorded separately. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Google Trust Services / WE1 as the certificate issuer with validity through Apr 15, 2026; checked Mar 15, 2026 at 05:58 UTC.
The content indicators and 2 positive source findings support the current AMLBot-themed crypto scam classification.
Pipeline de resposta a ameaças
Status da lista de bloqueios pública
Histórico de denúncias de abuso · 2 stored reports over 7 days · click to expand
-
Report #1 ICANN CC 815h still active Mar 15, 2026 · 01:44 UTCESCALATION #3 (815h active): Phishing - amlbot[.]imabuse@nic.im compliance@icann.org
-
Report #4 ICANN CC 965h still active Mar 21, 2026 · 10:28 UTCESCALATION #4 (965h active): Phishing - amlbot[.]imabuse@nic.im compliance@icann.org
Tecnologias · 3 identified
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
www.cloudflare.comThird major version of HTTP protocol, built on QUIC for faster, more reliable connections.
Análise do VirusTotal
Evidências arquivadas
Evidências e relatórios externos
Você foi afetado por este site?
Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.
Notifique as autoridades locais
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
Verificar qualquer domínio
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraDenunciar phishing
Envie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarFeed de ameaças em tempo real
Relatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMantenha-se informado, mantenha-se seguro
Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo