|
On July 10th Architelos released the first NameSentry Report, benchmarking abuse levels in the domain name industry. For some time now, a debate has raged about the potential impact of new gTLDs on Internet safety and security, namely abusive registrations such as phishing, spam, malware, and so on. However, without benchmarking the current state, how can we realistically evaluate if new gTLDs have made any measureable difference in the level of abuse?
The goal of the report was to establish a way to measure the level of abuse in the domain name space as a whole and across the top TLDs, in order to bring some transparency and encourage discussion and debate on what factors if any result in a safer namespace. The report is self-explanatory and can be downloaded from our site. The goal of this blog is not to reiterate the report findings, but to provide additional detail to the methodology we employed.
Before we get to the methodology, its important to note:
Principles and Goals
The first step was to establish some principles and goals from which we could then derive a methodology for analysis. Some of our key principles and goals were:
Methodology
The TLDs that comprise the Internet namespace vary widely in size. One challenge was to find the means to measure and compare TLDs with multi million domains under management with much smaller TLDs. Using actual TLD size and measuring abuse in absolute numbers would only provide part of the information, but would miss the larger picture. We settled on the choice of a logarithmic sale. A logarithmic scale can be helpful when the data covers a large range of values. Plus, the use of the logarithms of the values rather than the actual values reduces a wide range to a more manageable size. As a result, abuse was measured as “abuse-per-million” or specifically the number of unique 2nd level or 3rd level domains that were flagged for at least one type of abuse per million domains under management. This is similar to “part-per-million” which is one the most commonly used terms to describe very small amounts of contaminants in our environment. “Abuse-per-million” and “part-per-million” are measures of concentration, the amount of one material in a larger amount of another material. Using the logarithmic scale also allowed us to apply the same scale of measurement to each and every TLD, and indeed across the Internet namespace.
If the Internet has indeed become a utility that we rely on, then what measurements were already in use for other utilities such as air and water? Air Quality Index and Water Quality Index were easily communicable measurements that have been successfully used to evaluate relative safety and quality based on contaminants or pollutants on a parts per million basis. Assuming abusive domains are similar to pollutants in any given namespace, then a similar quality index could be used. We established the term “Namespace Quality Index” (NQI) since the same method of analysis and measurement could be applied to any given namespace: the Internet as a whole, any gTLD or ccTLD, any portfolio of domain names registered by a registrar, etc.
What’s Next
We are pleased that the NameSentry Report has not only provided a means of measuring and evaluating any changes to the Internet namespace going forward (i.e. new gTLDs) but that it has also generated debate and discussion about what factors or combination of factors would lead to a high quality or “Green” NQI. We believe that there is no one lever (such as price, restrictive registration policies, or aggressive takedown policies) that achieves this result, but rather a careful calibration of multiple levers. The next NameSentry report will focus on drawing correlations between the various levers and outcomes to identify potential best practices that can be successfully employed by existing and new gTLDs. In the meantime we are focused on enhancing our analysis to better serve the community and therefore very interested in constructive feedback and critique. Please contact us at [email protected] or send us your questions via our “contact us” page.
Sponsored byRadix
Sponsored byIPv4.Global
Sponsored byVerisign
Sponsored byWhoisXML API
Sponsored byCSC
Sponsored byVerisign
Sponsored byDNIB.com