Generic Top-Level Domain (gTLD) Registry Agreements
.NAME Agreement Appendix 6 | Schedule of Reserved Names
Schedule of Reserved Names
(25 March 2011)
Except to the extent that ICANN otherwise expressly authorizes in writing, the Registry Operator shall reserve names formed with the following labels from initial (i.e. other than renewal) registration within the TLD:
A. Labels Reserved at All Levels. The following names shall be reserved at the second level and at all other levels within the TLD at which Registry Operator makes registrations:
B. Additional Second-Level Reservations. In addition, and subject to the provisions of Appendix 9, the following names shall be reserved at the second level:
- All single-character labels.
- All two-character labels shall be initially reserved. The reservation of a two-character label string shall be released to the extent that the Registry Operator reaches agreement with the government and country-code manager, or the ISO 3166 maintenance agency, whichever appropriate. The Registry Operator may also propose release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes.
C. Tagged Domain Names. All labels with hyphens in the third and fourth character positions (e.g., "bq--1k2n4h4b" or "xn--ndk061n")
D. Second-Level Reservations for Registry Operations. The following names are reserved for use in connection with the operation of the registry for the Registry TLD. Registry Operator may use them, but upon conclusion of Registry Operator's designation as operator of the registry for the Registry TLD they shall be transferred as specified by ICANN:
E. Third-Level Reservations for Registry Operations. The following names are reserved for use in connection with the operation of the registry for the Registry TLD:
- mx[followed by a number from 0 to 100] ([0-10] and [11-100])
- ns[followed by a number from 0 to 100] ([0-10] and [11-100])
- www[followed by a number from 0 to 100] ([0-10] and [11-100])
F. Names transferred together with the registry database in the event of reassignment
G. Names staying with The Global Name Registry in the event of reassignment
employee names - Registry Operator will register the firstname.lastname.name versions of all current employees' names, provided no more than 1000 such names are under registration at any time. These names can be transferred to an ICANN Accredited Registrar by the employee.
If the corporate identity of The Global Name Registry is changed, Appendix 6 will be amended to incorporate second level domain variations on the new identity.
H. Patterns of names staying with Registry in the event of reassignment:
Whenever any Registered Name is registered (e.g., john.smith.name or firstname.lastname@example.org), the following domains will be delegated directly to Registry Operator:
- <second level domain>.name
- directory.<second level domain>.name
- www.<second level domain>.name
In each of the foregoing examples, "<second level domain>" is the corresponding second level of the Registered Name.
I. Registry Common Name reservations
The Registry will from time to time use names gathered from name statistics in a series of countries around the world to reserve names on the 2nd level. Names from these lists will be reserved on the 2nd level and made available only for 3rd level registrations.
J. Post-fix Reservations
The Registry has reserved all 2nd level names ending in a particular set of strings. Such names are reserved on the second level by default, and only 3rd level registrations are allowed on such 2nd levels. The following post-fix strings are reserved:
|Post-fix (English version)||Post-fix (Translated version)||Language|
As an example, the reservation of these post-fix strings means that all second level names ending in e.g. "-parivaar", for example "patel-parivaar" are reserved on the second level for third level registrations only.