Skip to main content
Resources

Registrar Contact Updates

Depending on the request, changes to registrar contact information can be made in several ways:

Primary Contact Updates

Changes to the Primary Contact can be submitted by completing the Registrar Primary Contact Update Form [PDF, 638 KB] and emailing it to registrarupdates@icann.org.

ICANN-accredited registrars are required to provide ICANN with accurate and current Primary Contact information. Registrars on the 2013 RAA must notify ICANN of changes to Primary Contact details within five (5) days of the change. Registrars on the 2009 RAA must notify ICANN within thirty (30) days of any changes to their Primary Contact information.

Additional Contact Updates

RADAR contacts may be revised via self-service. To make modifications, please log into your RADAR account(s).

Supplementary contacts may be modified via the RADAR Supplementary Contact Form [PDF, 545 KB] and then emailed to registrarupdates@icann.org.

RADAR Contacts Supplementary Contacts
  • Billing Contact
  • Public Contact
  • Transfer Emergency Action Contact (TEAC)
  • Transfer Contact
  • Uniform Domain Name Dispute Resolution Policy (UDRP) Contact
  • WHOIS Contact
  • Abuse Contact
  • Complaint Contact
  • Corporate Contact
  • Data Escrow Contact

Registrar Information Specification Updates

ICANN-accredited registrars under the 2013 Registrar Accreditation Agreement must notify ICANN of changes to information contained in the Registrar Information Specification within 5 days of the change.

Applicable registrar information updates should be emailed to registrarupdates@icann.org using the Registrar Information Specification in a format that is convenient to the registrar (e.g. spreadsheet, Word document, PDF, etc.). For your convenience, a spreadsheet [XLS, 137 KB] containing the information in the Registrar Information Specification has been provided for download.

Domain Name System
Internationalized 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."