Skip to main content
Resources

Registrar Data Escrow Program

Registrars are required by their Registrar Accreditation Agreements (RAAs: 2009 and 2013) to escrow certain registration data with an ICANN approved escrow agent pursuant to the Registrar Data Escrow (RDE) program.

Registrars may use the escrow agent designated by ICANN (currently, Iron Mountain Intellectual Property Management, Inc.), at no charge, or a reputable escrow agent approved by both ICANN and the registrar (known as a Third Party Provider or TPP), at the registrar's expense. A list of approved TPPs is provided below. Escrow agents who wish to apply for approval as a TPP should review ICANN's TPP Approval Criteria [PDF, 17 KB] and TPP Approval Process Diagram [PDF, 119 KB], and submit a completed TPP Application [PDF, 48 KB] to ICANN.

All registrars and escrow agents must comply with the terms of the RDE Specifications [PDF, 30 KB].

ICANN-Approved Registrar Data Escrow Third Party Providers

Iron Mountain Intellectual Property Management, Inc.
Name: RDE Client Services
Email: rde-customerservice@ironmountain.com
Telephone: +1 858 492 2400
RDE Agreement Template

NCC Group Plc
Name: John Greaves
ICANN Relationship Manager
Email: john.greaves@nccgroup.trust
Telephone: +44 161 209 5215
RDE Agreement Template

Escrow4all B.V.
Name: Herman Kui
Email: rde@escrow4all.com
Telephone: +31 20 3420 250
RDE Agreement Template

China Organizational Name Administration Center (CONAC)
Name: Escrow Support
Email: dataescrow@conac.cn
Telephone: +86 10 6900 1158
RDE Agreement Template

Beilong Zedata (Beijing) Data Technology Co., Ltd
Name: Zhang Lili
Email: registrarescrow@cnic.cn
Telephone: +86 10 6252 3580
RDE Agreement Template

China Internet Network Information Center
Name: Escrow Service
Email: deagent@cnnic.cn
Telephone: +86 10 5881 3578
RDE Agreement Template

DENIC eG
Name: DENIC Escrow Services
Email: escrow@denic.de
Telephone: +49 69 272 35 320
RDE Agreement Template

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