Skip to main content
Resources

Registry Agreement Termination Information Page

As part of ICANN's efforts to be open and transparent with the ICANN community, ICANN will use this page as the source of current information related to any requests for termination.

Termination Process

Under the New gTLD Registry Agreement, either party may terminate pursuant to certain requirements in the Registry Agreement ("Termination"), including but not limited to the following:

  • Section 4.3 – Termination by ICANN
  • Section 4.4 – Termination by Registry Operator

Pursuant to the above sections, in the event of termination by either party and after consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the  Registry to a sucessor registry operator in its sole discretion and in conformance with the Registry Transition Process ("Preliminary Determination").

For the avoidance of doubt, ICANN's Preliminary Determination shall not prohibit ICANN from delegating the gTLD purusuant to a future application process for the delegation of top-level-domains, subject to any processes and objection procedures instituted by ICANN in connection with such application process intended to protect the rights of third parties.

Following ICANN's consultation with Registry Operator, the Termination Notice and ICANN's Preliminary Determination will be published on this webpage. Interested parties may review and provide input regarding a Termination Notice and ICANN's Preliminary Determination by emailing comments to ra-termination-comments@icann.org. The deadline to provide input for a given Termination Notice is noted in the "Notices of Termination and Status of gTLD" table. Comments may be viewed at http://forum.icann.org/lists/ra-termination-comments.

Notices of Termination and Status of gTLD

View status descriptions of Terminations

Date of Termination Notice gTLD Registry Operator Comment Open Date Comment Close Date Status Documents Comments
3 Sept 2015
  • .DOOSAN
 Doosan Corporation 9 Oct. 2015 9 Nov. 2015 Implementation of Final Determination: Revocation of TLD Delegation

Termination Notice by Doosan Corporation [PDF, 36 KB] (3 Sept. 2015)

Preliminary Determination by ICANN on need for Transition of gTLD [PDF, 415 KB] (9 Oct. 2015)

Final Determination by ICANN on need for Transition of gTLD [PDF, 321 KB] (30 Nov. 2015)

View Comments

Termination Statuses

Open for Comment ICANN is seeking input from interested parties regarding its Preliminary Determination whether or not to transition operation of the gTLD to a successor registry operator.
Comments Under Review The Termination is closed for comment and the comments are under review.
Implementation of Final Determination

After considering comments regarding Termination Notice and ICANN's Preliminary Determination, a final determination has been made and is being implemented. Possible final determinations include the following:

  • Transition to Successor: the Registry Agreement will be terminated and operation of the gTLD will be transitioned to a successor registry operator.
  • Revocation of TLD Delegation: Registry Agreement will be terminated and the gTLD's delegation will be revoked from the Root Zone. ICANN's final determination shall not prohibit the gTLD from becoming available again in future rounds of gTLD applications.
Transition to Successor Registry Operator In Process ICANN is working to identify a successor registry operator for the gTLD.
TLD Transitioned to Successor ICANN has successfully completed the process of identifying and transitioning a successor registry operator for the gTLD.
TLD Delegation Revoked ICANN has completed revocation of the delegation in the Root Zone.

A note about tracking cookies:

This site is using "tracking cookies" on your computer to deliver the best experience possible. Read more to see how they are being used.

This notice is intended to appear only the first time you visit the site on any computer.Dismiss

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."