What is a Registry vs a Registrar vs a Registrant?
A domain name registry is an organization that manages top-level domain names. Verisign is a registry. They create domain name extensions, set the rules for that domain name, and work with registrars to sell domain names to the public. Network Solutions and GoDaddy are popular registrars. A registrant is the person or company who registers a domain…
Concern #1: Verisign does not enforce its contracts
Verisign does not enforce its contracts with registrars who allow CSAM to flourish. Verisign has the power to shut them down. Verisign, who has had the ultimate authority over .com and .net since their creation, refuses to enforce contract terms with registrars who allow child sexual abuse material to proliferate on their platforms. If Verisign…
Concern #2: Verisign refuses to implement a Thick WHOIS
Verisign refuses to collect the necessary information for a secure and safe Internet through a Thick WHOIS despite requirements and many years to do so. As explained by the NTIA: “The WHOIS databases are the internet’s white pages. Every entity, whether individual, business, organization or government, which registers domain names, must provide identifying and…
What is Thick vs. Thin WHOIS?
ICANN specifies what information must be collected with respect to domain names in its Registry Agreement (RA) with accredited registries and its Registrar Accreditation Agreement (RAA) with registrars. The registration data is commonly referred to as WHOIS data. Thick WHOIS data refers to both information associated with the domain name itself as well the registrant…
What are the advantages for Registries to have Thick WHOIS?
For nearly a decade, ICANN and the ICANN multistakeholder community have agreed on the substantial benefits of requiring all registries to hold Thick WHOIS data. These include centralization of data (e.g., usually there are multiple registrars that sell and register domain names in any particular top level domain, such as .com or .net), data preservation,…
What Registry doesn’t have Thick WHOIS?
The 2013 Final Report on Thick WHOIS Policy Development Process noted that as of that time, only the registry for .com, .net, and .jobs operated as a thin WHOIS registry. All other legacy generic top-level domain name registries already were operating under Thick WHOIS. Verisign is the registry for .com, .net and .jobs. Therefore, Verisign…
Doesn’t the GDPR prevent Verisign from implementing Thick WHOIS?
Verisign has argued that the GDPR (EU General Data Protection Regulation) is preventing it from implementing Thick WHOIS. But given that every single other registry for generic top level domain names, whether they be U.S. based registries, such as Public Interest Registry for .org and Neustar for .biz, or foreign registries have adopted Thick WHOIS…
But, has there been enough time for Verisign to transition to a Thick WHOIS?
ICANN began working on policy towards a Thick WHOIS 2011. ICANN formerly adopted the policy and instructed Verisign to transition to a Thick WHOIS in Feb 2014. Despite the fact that from the time the Board adopted the policy recommendations over four years were granted for the transition to Thick WHOIS for new domain name…
Concern #3: Verisign still has not implemented a trusted notifier program.
Verisign promised to implement a trusted notifier program to provide transparency and accountability in the .com top level domain. After two years, it appears no progress has been made. While the above two reasons are highly concerning and pressure must be applied by the public and governments around the world to correct, the main reason…
What are the Characteristics of a Trusted Notifier Program
Find an outline of characteristics of a trusted notifier program here. Background: Verisign promised to implement this program in 2018 in connection with the execution of Amendment 35 to the Cooperative Agreement with ICANN. In February 2019, The National Center on Sexual Exploitation, together with five other organizations working for child safety including ECPAT-USA, Enough…