Skip to main content

Continued Operations Instrument (COI)

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 purpose of the Continuing Operations Instrument (COI) is to ensure the availability of funds to provide continuity of service to registrants of new gTLDs should an issue with a registry arise. Per Specification 8 of the base Registry Agreement, Registry Operators shall have a Continued Operations Instrument that provides for sufficient financial resources to cover the five critical registry functions in Section 6 of Specification 10, for a determined time period as defined in Section 1 of Specification 8.

COI Obligation Release Service

The Registry Agreement requires that sufficient COI coverage is maintained for a term of six years from contract execution. As Registry Operators fulfill their 6-year obligation, TLDs will no longer be required to maintain a COI.

The COI Obligation End Release Service allows ICANN org to process the release of COI(s) that are no longer required per Specification 8 of the Registry Agreement.

COI Obligation Release Service Process Flow

COI Obligation Release Service Process Flow

*Processing may take up to 45 days

Processing will be completed in batches (based upon the expiry of COI obligations) at monthly intervals and may take up to 45 days to complete.

Registry Operators that utilize a COI allocation schedule will be notified of gTLD(s) coverage that may be removed from their COI document. While no action is required, Registry Operators may choose to work with their Issuing Bank to submit an amendment for the removal of gTLD(s) no longer requiring coverage.

Once the obligation to maintain COI coverage for all gTLDs listed on an allocation schedule of an instrument passes, ICANN organization will process the release of the COI document as per the above-outlined process.

Should a contracted party wish to seek a more expedited release of their document, they may choose to pro-actively amend their COI's Final Expiry date to match the date of their COI obligation end date via the COI Amendment Service, as an alternative to the above-outlined service.

COI Amendment Service

The COI Amendment Service provides a method for registry operators to request permission from the ICANN organization to change the value of their COI funds to align with the domain registrations under management (DUMs) projections for the gTLD.

The ICANN organization will be ensuring sufficiency of COIs as set forth in the Registry Agreement. Should ICANN find a COI is insufficiently funded at any time after a gTLD has been delegated, the registry operator will be referred to the COI Amendment Service and asked to amend their COI within 60 days.

Registry operators should submit a request via a service case in the Naming Services portal. A registry must be in good standing with the ICANN organization and its TLD must have been in General Availability/Registration (GA) for a minimum of six months prior to the request date in order to be eligible for a COI Amendment.


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