This DNSAI post is the first in a three-part series that will attempt to provide reasonable, bite size introductions to the key components of developing anti-abuse practices.
In early March 2022 the DNSAI received a letter requesting input from the ICANN GNSO on behalf of their ‘Small Team on DNS Abuse’. This is the DNSAI response.
The DNSAI’s new centralized DNS Abuse reporting tool, NetBeacon, is going to provide real value to registries and registrars and simplify the work and greatly improve the experience for those who are reporting DNS Abuse.
Learn what is meant by malicious registrations, how to manually distinguish between malicious registrations and compromised websites, and what the best practices are for mitigation in each circumstance.
the DNSAI researched the reporting processes of the largest registries and registrars in order to better understand how they accept reports of abuse. This article summarizes the findings of this initiative.
This post is a thought experiment intended to provide a new alternative method for defining DNS Abuse – and the criteria to most effectively mitigate it. Our current definition of DNS Abuse was arrived at by identifying and categorizing online harms based on how the harm is executed. Instead, we propose that a definition could be derived by considering the attributes of how a harm can be mitigated. Through this approach, DNS Abuse is not a list of harms selected by their category, but instead consists of harms that are appropriately mitigated by the DNS. The rest of this post is an elaboration of what appropriate means in this context.