We have created this site to provide updates on our approach to combating domain name abuse and improving DNS safety.
We believe that Registries, Registrars, and other members of the ICANN community must take a holistic approach that leverages new technologies to enable key policy changes and legal accountability mechanisms that drive down domain abuse. The approach must also help better address the various concerns community members.
A user creates a compatible digital identity with their preferred Identity Provider (IdP). Experts at a designated verifying party review their qualifications for a designated lawful purpose. The user’s digital identity is updated to indicate their verified credentials for accessing non-public registration data. Registries may also enable the use of verified credentials for Registrants.
Non-public data requests require authentication and attestation of a specified purpose and scope of use. Requests for personal data are subject to an “ex post” dispute resolution process. A Contracting Party may choose additional “due process” rules for certain data. Contracting Parties retain existing privacy services or may add a new IdP escrow approach.
A pseudonymized, auditable log of designated activity may be shared. This includes Requestor (except “do not track”) or Registrant activity (e.g., domain transfers). Requests to unmask requests may follow a process similar to requests for registration data. Personal data for all verified parties would be retained for appropriate designated retention periods.