I forgot to ask, I don 't recall what are the Registrars logging currently when mitigating, in terms of ICANN Compliance? el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (retired) el@lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply On Jun 3, 2026 at 01:32 +0200, John Gbadamosi via Gnso-dnsabuse-pdp <gnso-dnsabuse-pdp@icann.org>, wrote:
What you’re basically saying makes a lot of sense.
Without proper logs, it’s really hard, like almost impossible, for ICANN Compliance to confirm whether registrars actually followed the policy, especially when things are reviewed much later or when there’s no external complaint to trigger an investigation.
At the same time, I also understand the concern that too much logging could become heavy and slow down normal abuse handling work.
So a fair middle ground would be to keep logging simple and focused on only the key steps—like when the complaint came in, whether ADC was done, when it started and ended, what was checked, what was found, and what action was taken.
If this is captured in a lightweight way (even a simple form or spreadsheet), it should give Compliance enough visibility without creating too much extra burden on registrars.
[…]