Generic Top-Level Domain (gTLD) Registry Agreements

gTLD Registry Agreements establish the rights, duties, liabilities, and obligations ICANN requires of registry operators to run gTLDs.

.name Registry Agreement Appendix 6

Schedule of Reserved Names

(1 December 2012)

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:

ICANN-related names:

  • aso
  • gnso
  • icann
  • internic
  • ccnso

IANA-related names:

  • afrinic
  • apnic
  • arin
  • example
  • gtld-servers
  • iab
  • iana
  • iana-servers
  • iesg
  • ietf
  • irtf
  • istf
  • lacnic
  • latnic
  • rfc-editor
  • ripe
  • root-servers

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 shared at the second-level and maintained by the Registry Operator. Two-character names shall be released by the Registry Operator for third-level registrations and SLD email addresses only. 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:

  • nic
  • whois
  • www

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:

  1. dir
  2. directory
  3. email
  4. genealogy
  5. http
  6. mail
  7. mx
  8. mx[followed by a number from 0 to 100] ([0-10] and [11-100])
  9. ns
  10. ns[followed by a number from 0 to 100] ([0-10] and [11-100])
  11. wap
  12. www
  13. www[followed by a number from 0 to 100] ([0-10] and [11-100])
  14. administrator
  15. hostmaster
  16. postmaster
  17. complaints
  18. mailer-daemon
  19. abuse
  20. root
  21. webmaster
  22. infomaster

F. Names transferred together with the registry database in the event of reassignment

  1. alerts.name
  2. celebrity.name
  3. cert.name
  4. certificate.name
  5. directory.name
  6. dns.name
  7. dotname.name
  8. famous.name
  9. findyour.name
  10. findyourfamily.name
  11. findyourname.name
  12. finger.name
  13. ftp.name
  14. getyour.name
  15. getyourname.name
  16. gopher.name
  17. hostmaster.name
  18. imap.name
  19. ldap.name
  20. login.name
  21. myname.name
  22. namedomain.name
  23. nameregistry.name
  24. nntp.name
  25. no1.name
  26. ntp.name
  27. pop.name
  28. pop3.name
  29. registeryour.name
  30. registeryourname.name
  31. registry.name
  32. scp.name
  33. security.name
  34. smtp.name
  35. snmp.name
  36. telnet.name
  37. thefamous.name
  38. thenamedomain.name
  39. thenameregistry.name
  40. yourname.name
  41. zone.name
  42. global.name

G. Names staying with Registry Operator 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.

  1. verisign.name
  2. verisigninc.name

If the corporate identity of Registry Operator 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 john@smith.name), the following domains will be delegated directly to Registry Operator:

  1. <second level domain>.name
  2. directory.<second level domain>.name
  3. 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
Family -familie Dutch
Family -family English
Family -perhe Finnish
Family -famille French
Family -familie German
Family -parivaar Hindi
Family -keluarga Indonesian
Family -famiglia Italian
Family -angkan Philipino
Family -rodzina Polish
Family -familia Portugués
Family -familie Scandinavian
Family -familia Spanish
Family -mischpoche Yiddish
Family -umdeni Zulu

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.