This article demonstrates the opportunities for retail domain registrars to prevent abusive registrations while reducing potential impacts to registrants and anti-abuse teams.
Discover the latest and greatest news and information from the DNS Abuse Institute.
The DNS Abuse Institute has published its 2021 Annual Report, which recounts an impressive milestone inaugural year and covers 2/2021 to 3/2022.
The DNS Abuse Institute is excited to welcome Rowena Schoo as the Director of Programs and Policy. Schoo will serve as a critical part of the team whose mission is to combat DNS Abuse.
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.
Join our Executive Director of the DNS Abuse Institute, Graeme Bunton, as he shares updates on NetBeacon, ICANN 73, and a recent DNS Abuse study by the European Commission.
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.
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.