Skip to main content

Terminated Registrar Procedure

This page was archived as of 14 August 2018. The current De-Accredited Registrar Transition Procedure can be found here.

The purpose of this procedure is to enable registrants to transfer their names from a terminated registrar to any registrar in good standing. Broadly, a services provider (who may be a registrar) will be appointed as a temporary organization to hold the registrations and facilitate the transfers of all the names to accredited registrars chosen by registrants on a case-by-case basis. The service provider scope will be strictly limited to this role.

ICANN will make a tender to secure a provider of transfer services (a Failed Registrar Transfer Provider, or “Provider”) who will be compensated to perform the following duties only:

  • Provide a WHOIS service for the domain name affected
  • Provide a customer interface (with no branding identification) to facilitate transfers from the terminated registrar to any registrar in good standing
  • Update Whois contact information at the authenticated request of registrants - provide an appropriate paperwork authentication process in cases where the email address of other contact information is no longer correct
  • Send auth-codes to any affected registrant requesting them: registrant must consent to transfer via email sent to administrative contact
  • Unlock domain names for registrants requesting auth-codes
  • Send an email to registrants who have not transferred the name by the time of expiration stating that the name has expired and that the name must transferred or it will be deleted at the close of auto-renew, redemption grace and pending delete periods
  • Provide phone support as required for authentication problems only (i.e. no discussion of registrar choice)
  • Maintain the service until the names are transferred or are deleted
  • Provide a domain restore service to facilitate the redemption of names by passing the any Redemption Grace Period to the registry at registry cost.
  • No fees will be charged by the service provider except as provided in the implementation notes below.

To facilitate the process, gTLD registries having names from the registrar in interest shall:

  • Rewrite the registrar of record to the Provider
  • Issue credentials and passwords to the Provider
  • Write auth codes to the registry at the direction of the Provider
  • Provide “transfer out” reports for the Provider

ICANN will compose an email to be sent by the Provider to every registrant (admin contact) stating:

  • Terminated registrar’s accreditation has been terminated
  • Notice that domain names registered by the terminated registrar, have been temporarily transferred to the Failed Registrar Transfer Provider to facilitate transfer of the name to another registrar,
  • Asking registrants too choose a registrar from the list of ICANN accredited registrars at
  • Asking registrants to transfer domain names using the tool to obtain auth-code on the Provider’s site (link to be provided).

Application notes:

  • Given the fact based contingencies of each potential termination: tenders can be extended to selected registrars or other potential Providers at ICANN discretion. Tenders need not be open to any who wish to bid, the tender need not be announced publicly. Executive ICANN staff will make tender decisions according to an internal procedure taking into account the interests of registrants.
  • ICANN will ensure a separate accreditation credential is in place or issued for the purpose of keeping this work separate from other registrar work and to ensure the temporal nature of this assignment.
  • Provider’s compensation: compensation may be a lump sum payment by ICANN to the Provider at the outset; or a transaction fee for each transfer. Compensation is intended to offset direct costs of the Provider. Potential Providers in response to the tender will suggest compensation. The cash flow for transaction fee is: gaining registrar to pay ICANN usual ICANN fee; ICANN to pay Provider.
  • Selection among qualified applicants will be made in the best interests of registrants according to an internal procedure.
  • Provider shall not “park” or otherwise use registered names to derive other revenue.
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."