Skip to main content

Community gTLD Change Requests

Please note that the English language version of all translated content and documents are the official versions and that translations in other languages are for informational purposes only.

The Procedure for Community gTLD Change Requests permits a Community gTLD Registry Operator to seek approval from ICANN to modify the Community Registration Policies enumerated in Specification 12 of its Registry Agreement.

Per the guidelines of the procedure, the registry operator may not seek changes that would remove the Community Registration Policies, excessively broaden or narrow registrant eligibility and/or name selection requirements, or result in significant negative impact to the TLD Community. The ICANN org will notify the registry operator if the change request falls outside of these guidelines. Any change request outside of these guidelines will not be considered.


Changes under this service may only be requested by the registry operator of a Community gTLD. A Community gTLD is:

  1. A gTLD that has a Registry Agreement that includes Specification 12 and
  2. The section title of its Specification 12 is "Community Registration Policies" or "TLD Policies."


To submit a Community gTLD Change Request to the ICANN org, eligible registry operators should follow the instructions in the How to Guide [PDF, 244 KB].

Submissions and Status

Following the ICANN org's preliminary review of a request submitted according to the procedure, the ICANN org will post the request including all required documentation for a comment period of 30 days. Interested parties may review and provide input regarding the request by emailing comments to the address below. The deadline to comment for a particular request is noted in the table below.

By submitting any personal data to the email address below, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy, and agree to abide by the website Terms of Service.

gTLD Registry Operator Questionnaire and Draft Amendment Supporting Documents Date Posted Comment Deadline Status

Explanation of Statuses:

  • Comment Period: the submission is currently in the 30-day comment period.
  • Pending: the ICANN org is reviewing the change request and any comments received in order to make its determination.
  • Approved: the ICANN org approved the change request. The amendment is either in progress or already published on the gTLD specific Registry Agreement webpage.
  • Rejected: the ICANN org rejected the change request.
  • Withdrawn: the registry operator withdrew the change request.
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"""" is not an IDN."