Data Escrow

This article is neutral, but is sponsored by Iron Mountain. Iron Mountain is an information & intellectual property management company and data escrow provicer. You can read more about their services here.

link={{{link}}}

ICANNWiki Silver Sponsor

Data Escrow is the act of storing data with a neutral third party in case of registry or registrar failure, accreditation termination, or accreditation relapse without renewal. ICANN requires all registrars and gTLD registries to contract with a data escrow provider in order to safeguard registrants. Both registry and registry escrows follow the same system: a weekly full deposit on sundays, and a partial deposit on all other days containing all new data since the last full deposit.

Registry Data Escrow

Registry data escrow procedures

Registry Data Escrow is one of the essential stakeholder protection mechanisms for gTLDs. Registry Data Escrow ensures that the data associated with registered domain names is never at risk of being lost or inaccessible. Registry Data Escrow is a specialized data protection service designed to meet the compliance and “best practice” needs of domain name registrants worldwide. The service ensures that up-to-date copies of domain name ownership and contact details are held in escrow by a trusted, neutral third party, to be accessed and released only under pre-defined and controlled conditions. The purpose of Registry Data Escrow is to help safeguard registrar and registrant interests in the event of a registry’s business or technical failure.

History

The original Registry Agreement, which lasted from 1999-2001, between ICANN and Network Solutions (and later Verisign) contained provisions for registry data escrow for the .com, .net, and .org gTLDs. In May 2001, ICANN entered into a new Registry Agreement with Verisign for .com, which included expanded escrow provisions. At that time they also entered into separate agreements for .org and .net.

In November 2000, ICANN selected seven new gTLDs as part of a proof-of-concept round to expand the Internet name space. Registry Agreements for all 7 of these TLDs contained language based on the draft for the 2001 .com agreement with Verisign. These agreements were entered into between 2001 and 2002, beginning with .biz and .info in May 2001.

Iron Mountain was selected in 2001 to serve as ICANN's preferred provider for registry data escrow.

There are currently 4 active versions of the Registry Escrow Agreement. Most gTLDs use Version 1, which is based off of the 2001 .com agreement; Version 2 is used by .travel; Version 3 by the .aero, .coop, and .museum Sponsored TLDs; and Version 4 by .name and .pro.

Several of the original ccTLD Sponsorship Agreements and MoUs also contained provisions for registry escrow. In 2004, however, ICANN moved away from the Sponsorship Agreement and MOU formats, opting for a lightweight Accountability Format, which does not contain detailed provisions for registry escrow, though it does encourage ccTLD managers to operate in a manner complaint to current IETF standards.

Registrar Data Escrow

The Registrar Data Escrow program was initiated by ICANN to protect data associated with registered domain names in a secure escrow environment.

History

Though registrar data escrow was already part of the Registrar Accreditation Agreement, a structured Registrar Data Escrow program was deemed to be necessary by ICANN and a committee of registrars in late 2001. A testbed consisting of a small number of volunteer registrars was conducted prior to the full rollout of the program.

In 2007, however, it came to light that ICANN had not followed through in ensuring that all of its registrars were doing so. After the failure of RegisterFly, the first registrar to go under, thousands of the company's customers lost their domain names or were forced to wait for months until their domains were eventually transferred to GoDaddy. Following this, ICANN made it a priority to review the RAA and more forcefully implement the Registrar Data Escrow program. Iron Mountain was selected to implement and execute Registrar Data Escrow. All registrars at that time were expected to enroll in the RDE program within six months.

Country code top-level domain