Registrant Program Update: New Report on Registrant Issues and Challenges & ICANN Learn Course for Registrants
Today, the ICANN organization Registrant Program published the third edition of its ongoing reporting series on Issues and Challenges Impacting Domain Name Registrants [PDF, 263 KB] containing updated data (from the reporting period of September 2019 – February 2020) from the ICANN Global Support Center (GSC) and Contractual Compliance. The report also provides observations of registrant issues and challenges from GSC and Contractual Compliance based on their interactions with registrants. As always, we encourage everyone to take a look at the report and share any data you might have regarding issues impacting registrants to inform ongoing conversations and work. We’ll continue to work with departments across the organization who engage with registrants to gather and analyze data on an ongoing basis in addition to publishing similar data online at icann.org/registrants as part of our broader effort to raise awareness about the issues and challenges registrants face.
On 25 April, the Registrant Program published a blog about how to identify phishing scams, DNSSEC-signing domain names, and other tips to help registrants responsibly and securely manage their domain names. The “Do you have a domain name? Here’s what you need to know” blog series is part of the Registrant Program’s broader effort to educate registrants about their rights and responsibilities, the domain name ecosystem, how to navigate it, and the ICANN policies that impact them.
In March, ICANN Learn launched a new course entitled Registrant Basics: Essentials for Domain Name Holders aimed at educating registrants and the broader end user community about the rights and responsibilities of registrants and some of the ICANN policies that impact them. This course hopes to dispel confusion about domain names, ICANN’s role, and the policies that affect registrants when registering and managing domain names. We encourage you to sign up for ICANN Learn if you aren’t already and to check out this course, particularly if you are a registrant yourself.
Domain Name SystemInternationalized Domain Name ,IDN,”IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet “”a-z””. An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European “”0-9″”. The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed “”ASCII characters”” (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of “”Unicode characters”” that provides the basis for IDNs. The “”hostname rule”” requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen “”-“”. The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of “”labels”” (separated by “”dots””). The ASCII form of an IDN label is termed an “”A-label””. All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a “”U-label””. The difference may be illustrated with the Hindi word for “”test”” — परीका — appearing here as a U-label would (in the Devanagari script). A special form of “”ASCII compatible encoding”” (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an “”LDH label””. Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as””icann.org”” is not an IDN.”