Policy on Transfer of Sponsorship of Registrations between Registrars
I. Inter-Registrar Transfers
A. Holder-Authorized Transfers
1. Registrar Requirements
The Registration Agreement between each registrar and its Registrant must allow for Registrants to transfer their domain name registrations between Registrars provided that the Gaining Registrar’s transfer process meets the minimum standards of this policy. Inter-Registrar domain name transfer processes must be clear and concise in order to avoid confusion. Further, Registrars should inform Registrants of, and provide access to, the published documentation of the specific transfer process employed by the Registrars.
Both the Administrative Contact and the Registrant, as listed in the usTLD Administrator’s publicly accessible WHOIS service, are the only parties that have the authority to approve or deny a transfer request to the Gaining Registrar. In the event of a dispute, the Registrant’s authority supersedes that of the Administrative Contact. For the purposes of this Exhibit, the Registrant and the Administrative Contact are collectively referred to as the “Registered Name Holder.”
2. Gaining Registrar Requirements
For each instance where a Registered Name Holder requests to transfer a domain name registration to a different Registrar, the Gaining Registrar shall:
2.1 Obtain express authorization from Registered Name Holder including the standard form of authorization and the Registered Name Holder’s unique “AuthInfo” code.
2.1.1 The authorization must be made via a valid Standardized Form of Authorization (FOA).
a) There are two different FOA’s available on the usTLD Administrator’s website. The FOA labeled “Initial Authorization for Registrar Transfer” must be used by the Gaining Registrar to request an authorization for a registrar transfer from the Registered Name Holder. The FOA labeled “Confirmation of Registrar Transfer Request” may be used by the Registrar of Record to request confirmation of the transfer from the Registered Name Holder. The FOA shall be communicated in English, and any dispute arising out of a transfer request shall be conducted in the English language.
b) In the event that the Gaining Registrar relies on a paper-based process to obtain this authorization, a paper copy of the FOA will suffice insofar as it has been signed by the Registered Name Holder.
c) If the Gaining Registrar relies on a paper-based authorization process, then the Gaining Registrar assumes the burden of obtaining reliable evidence of the identity of the Registered Name Holder and maintaining appropriate records proving that such evidence was obtained. Further the Gaining Registrar also assumes the burden for ensuring that the entity making the request is indeed authorized to do so. The acceptable forms of identification for these purposes are:
- Notarized statement
- Policy on Transfer of Sponsorship of Registrations Between Registrars continued
- Valid Drivers license
- Articles of Incorporation
- Military ID
- State/Government issued ID
- Birth Certificate
d) In the event that the Gaining Registrar relies on an electronic process to obtain this authorization the acceptable forms of identity would include:
Electronic signature in conformance with United States legislation, in the location of the Gaining Registrar (if such legislation exists).
Consent from an individual or entity that has an email address or phone number matching the Registered Name Holder’s email address or phone number.
e) The Registrar of Record may not deny a transfer request solely because it believes that the Gaining Registrar has not received the confirmation set forth above.
f) A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registrar. The presumption in all cases will be that the Gaining Registrar has received and authenticated the transfer request made by a Registered Name Holder.
2.1.2 Collection of unique “AuthInfo” code from Registered Name Holder. a) Registrars must provide all Registered Name Holders with their unique “AuthInfo” code within five (5) calendar days of the Registered Name Holder’s initial request if the Registrar does not provide facilities for the Registered Name Holder to generate and manage their own unique “AuthInfo” code
b) In addition, Registrars may not employ any mechanism for complying with a Registered Name Holder’s request to obtain the applicable “AuthInfo” code that is more restrictive than the mechanisms used for changing any aspect of the Registered Name Holder’s contact or name server information.
c) The Registrar must not refuse to release an “AuthInfo” code to the Registered Name Holder solely because there is a dispute between the Registered Name Holder and the Registrar over payment.
d) Registrar-generated “AuthInfo” codes must be unique on a per-domain basis. The “AuthInfo” codes must be used solely to identify a Registered Name Holder.
2.2 Request by the transmission of a “transfer” command as specified in the Registrar Tool Kit that the usTLD Administrator database be changed to reflect the new Registrar.
2.2.1 Transmission of a “transfer” command constitutes a representation on the part of the Gaining Registrar that the requisite authorization has been obtained from the Registered Name Holder listed in the authoritative Whois database.
2.2.2 The Gaining Registrar is responsible for validating the Registered Name Holder requests to transfer domain names between Registrars. However, the Registrar of Record (also referred to as the “Losing Registrar”) must still confirm the Registered Name Holder’s intent to transfer its domain name to the Gaining Registrar in accordance with Section 3 of this policy.
2.2.3 The FOA labeled "Initial Authorization for Registrar Transfer" shall expire under the following circumstances:
a) a period of sixty (60) days has passed since the FOA was issued by the Gaining Registrar, unless the Gaining Registrar allows automatic renewal of the FOA and the Registered Name Holder has expressly opted in to the automatic renewal;
b) the domain name expires before the inter-registrar transfer is completed;
c) a Change of Registrant is completed further to Section II.C of this policy.
d) the inter-registrar transfer is completed.
e) If the FOA expires pursuant to one of the aforementioned circumstances described in I.A.126.96.36.199 – I.A.188.8.131.52, prior to submitting the “transfer” request to the registry, in order to proceed with the transfer, the Gaining Registrar must re-authorize the transfer request via a new FOA.
3. Obligations of the Registrar of Record
3.1 A Registrar of Record can choose independently to confirm the intent of the Registered Name Holder when a notice of a pending transfer is received from the Registry. The Registrar of Record must do so in a manner consistent with the standards set forth in this policy pertaining to Gaining Registrars and must use the FOA for the purposes of verifying intent.
3.2 The FOA shall be communicated in English and any dispute arising out of a transfer request shall be conducted in the English language. This requirement does not preclude the Registrar of Record from marketing to its existing customers through separate communications in a language other than English. Further, such non-English communications must follow the processes and procedures set forth in this policy. This includes but is not limited to the requirement that no Registrar shall add any additional information to an FOA used to obtain the consent of the Transfer Contact in the case of a transfer request.
In the event the Registered Name Holder preapproves a transfer, the Registrar of Record has the option of sending a modified version of the FOA, which informs the Registered Name Holder that the preapproved transfer has been initiated.
3.3. The FOA should be sent by the Registrar of Record to the Registered Name Holder as soon as possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the usTLD Administrator.
3.4 Failure by the Registrar of Record to respond within five (5) calendar days to a notification from the Registry regarding a transfer request will result in a default “approval” of the transfer.
3.5 In the event that a Registered Name Holder listed in the WHOIS has not confirmed its request to transfer with the Registrar of Record and the Registrar of Record has not explicitly denied the transfer request, the default action will be that the Registrar of Record must allow the transfer to proceed.
3.6 Upon denying a transfer request for any of the following reasons, the Registrar of Record must provide the Registered Name Holder and the potential Gaining Registrar with the reason for denial. The Registrar of Record may deny a transfer request only in the following specific instances:
Evidence of fraud
usTLD Dispute Resolution action
Court order by a court of competent jurisdiction
Reasonable dispute over the identity of the Registrant or Administrative Contact
No payment for previous registration period (including credit card charge-backs) if the domain name is past its expiration date or for previous or current registration periods if the domain name has not yet expired. In all such cases, however, the domain name must be put into “Registrar Hold” status by the Registrar of Record prior to the denial of transfer.
Express written objection to the transfer from the Registered Name Holder (e.g., email, fax, paper document or other processes by which the Registered Name Holder has expressly and voluntarily objected through opt-in means).
A domain name was already in “lock status” provided that the Registrar provides a readily accessible and reasonable means for the Registered Name Holder to remove the lock status.
A domain name is in the first 60 days of an initial registration period.
A domain name is within 60 days after being transferred (apart from being transferred back to the original Registrar in cases where both Registrars so agree and/or where a decision in the dispute resolution process so directs).
3.7 The Registrar of Record must deny a transfer request in the following circumstances:
A pending usDRP proceeding that the Registrar has been informed of.
Court order by a court of competent jurisdiction.
Pending dispute related to a previous transfer pursuant to the usTLD Registrar Transfer Dispute Resolution Policy (“usTDRP”).
usRS proceeding or usRS suspension that the Registrar has been informed of.
The Registrar imposed a 60-day inter-registrar transfer lock following a Change of Registrant, and the Registered Name Holder did not opt out of the 60-day inter-registrar transfer lock prior to the Change of Registrant request.
3.8 Instances when the requested change of Registrar may not be denied include, but are not limited to:
Nonpayment for a pending or future registration period
No response within seven (7) calendar days of sending a communication to the Registrant or Administrative Contact.
Domain name in Registrar Lock Status, unless the Registered Name Holder has been provided with the reasonable opportunity and ability to unlock the domain name prior to the Transfer Request.
Domain name registration period time constraints, other than during the first 60 days of initial registration or during the first 60 days after a registrar transfer, or during the 60-day lock following a Change of Registrant pursuant to Section II.C.2.
General payment disputes between Registrar and business partners / affiliates in cases in which the Registered Name Holder for the domain in question has paid for the registration.
A dispute over payment. The Registrar of Records must not employ transfer processes as a mechanism to secure payment for services from a Registered Name Holder. Exceptions to this requirement are as follows: (i) in the case of non-payment for previous registration period(s) if the transfer is requested after the expiration date, or (ii) in the case of non-payment of the previous or current registration period, if transfer is requested before the expiration date.
4. Registrar Coordination
4.1 Each Registrar is responsible for keeping copies of documentation, including the FOA and the Registered Name Holders response thereto that may be required for filing and supporting a dispute under the dispute resolution policy. Gaining Registrars must maintain copies of the FOA as received from the Registered Name Holder. Copies of the reliable evidence of identity must be kept with the FOA.
4.2 The Gaining Registrar must retain and produce pursuant to a request by a Losing Registrar a written or electronic copy of the FOA. In instances in which the Registrar of Record has requested copies of the FOA, the Gaining Registrar must fulfill the Registrar of Record’s request (including providing the attendant supporting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds for reversal by the usTLD Administrator in the event that a transfer complaint is filed in accordance with the requirements of this policy.
4.3 If either a Registrar of Record or a Gaining Registrar does not believe that a transfer request was handled in accordance with the provisions of this policy, then the Registrar may initiate a complaint with the usTLD Administrator.
4.4 For purposes of facilitating transfer requests, Registrars should provide and maintain a unique and private email address for use only by other Registrars and the usTLD Administrator:
4.4.1 This email address is for issues related to transfer requests and the procedures set forth in this policy only.
4.4.2 The email address should be managed to ensure messages are received by someone who can respond to the transfer issue.
4.4.3 Messages received at such email address must be responded to within a commercially reasonable timeframe not to exceed seven (7) calendar days.
5. usTLD Administrator Requirements
5.1 Upon receipt of the “transfer” command from the Gaining Registrar, the usTLD Administrator will transmit an electronic notification to both Registrars.
5.2 The usTLD Administrator shall complete the requested transfer unless within five (5) calendar days it receives a NACK protocol command from the Registrar of Record.
5.3. The usTLD Administrator shall undo a transfer if, after a transfer has occurred, the usTLD Administrator receives one of the notices as set forth below. In such case, the transfer will be reversed and the domain name reset to its original state. The usTLD Administrator must undo the transfer within five (5) calendar days of receipt of the notice except in the case of a Registry dispute decision, in which case the usTLD Administrator must undo the transfer within fourteen (14) calendar days unless a court action is filed. The notice required shall be one of the following:
5.3.1 Agreement of the Registrar of Record and the Gaining Registrar sent by email, letter or fax that the transfer was made by mistake or was otherwise not in accordance with the procedures set forth in this policy;
5.3.2 The final determination of a dispute resolution body having jurisdiction over the transfer; or
5.3.3 Order of a court having jurisdiction over the transfer.
6. Records of Registration
Each Registrar shall require its customer, the Registered Name Holder, to maintain its own records appropriate to document and prove the initial domain name registration date.
7. Effect on Term of Registration
The completion by usTLD Administrator of a holder-authorized transfer under this Part A shall result in a one-year extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) years.
B. usTLD Administrator Approved Transfers
Transfer of all of the registrations held by one registrar as (i) the result of acquisition of that registrar or its assets by another registrar, or (ii) lack of accreditation of that Registrar may be made according to the following procedure:
(a) The acquiring registrar must be accredited by usTLD Administrator for the usTLD under an Accreditation Agreement and must have in effect a usTLD Administrator-Registrar Agreement with usTLD Administrator for the usTLD.
(b) The usTLD Administrator shall determine in its sole discretion that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual or imminent business failure of a registrar.
Upon satisfaction of these two conditions, the usTLD Administrator will make the necessary one-time changes in the registry database for no charge for transfers involving 50,000 name registrations or fewer; provided that the data to be transferred to the usTLD Administrator is in the form specified by the usTLD Administrator (“Approved Format”). If the transfer involves registrations of more than 50,000 names, and the data to be transferred to the usTLD Administrator is in the Approved format, the usTLD Administrator will charge the acquiring registrar a one-time flat fee of US $50,000. If the data to be transferred is not in the Approved Format, the usTLD Administrator may charge a reasonable fee, as determined by the usTLD Administrator, in connection with the cost associated with reformatting such data.
II. Inter-Registrant Transfer (Change of Registrant)
1 Terms & Definitions
1.1 “Change of Registrant” means a Material Change to any of the following:
1.1.1 Prior Registrant name
1.1.2 Prior Registrant organization
1.1.3 Prior Registrant email address
1.1.4 Administrative Contact email address, if there is no Prior Registrant email address.
1.2 “Designated Agent” means an individual or entity that the Prior Registrant or New Registrant explicitly authorizes to approve a Change of Registrant on its behalf.
1.3 “Material Change” means a change which is not a typographical correction. The following will be considered material changes:
1.3.1 A change to the Registered Name Holder’s name or organization that does not appear to be merely a typographical correction;
1.3.2 Any change to the Registered Name Holder’s name or organization that is accompanied by a change of address or phone number;
1.3.3 Any change to the Registered Name Holder’s email address.
1.4 “Prior Registrant” means the Registered Name Holder at the time a Change of Registrant is initiated.
1.5 “New Registrant” means the entity or person to whom the Prior Registrant proposes to transfer its domain name registration.
B. Availability of Change of Registrant
1 Registration/Whois Data Updates
In general, registrants must be permitted to update their registration/Whois data and transfer their registration rights to other registrants freely.
2 Denial of Change of Registrant Request
A Registrar must deny a Change of Registrant request under the following circumstances:
2.1 The domain name registration agreement has expired, and the Registered Name Holder no longer has the right to renew or transfer the domain name to another registrar;
2.2 The Change of Registrant was not properly authorized by the Prior Registrant and the New Registrant, further to Section II.C below;
2.3 The domain name is subject to a domain name related dispute, including but not limited to:
2.3.1 A pending usDRP proceeding that the Registrar has been informed of;
2.3.2 A pending usRS proceeding that the Registrar has been informed of;
2.3.3 A pending usTDRP proceeding;
2.3.4 A court order by a court of competent jurisdiction, prohibiting a Change of Registrant,that the Registrar has been informed of.
3 Non-Applicable Change of Registrant Requests
In the following circumstances, the Change of Registrant process described in Section II.C below does not apply:
3.1 the registration agreement expires;
3.2 the registration agreement is terminated by the Registrar;
3.3 the Registrar or usTLD Administrator updates the Prior Registrant’s information pursuant to a court order;
3.4 the Registrar updates the Prior Registrant’s information in the implementation of a usDRP decision;
3.5 the Registrar updates the Prior Registrant’s information in response to an abuse complaint.
C. Change of Registrant Process
To process a Change of Registrant from the Prior Registrant to a New Registrant, the Registrar must do all of the following:
1. Confirm the domain name is eligible for Change of Registrant further to Section II.B;
2. Obtain confirmation of the Change of Registrant request from the New Registrant, or a Designated Agent of the New Registrant. The Registrar must use a secure mechanism to confirm that the New Registrant and/or their respective Designated Agents have explicitly consented to the Change of Registrant. In obtaining the confirmation, the Registrar must inform the New Registrant or its Designated Agent, if applicable, that the New Registrant must enter into a registration agreement with the Registrar (a link to the registration agreement itself can be provided). The Registrar must also inform the New Registrant or Designated Agent, if applicable, that the request will not proceed if it is not confirmed in a number of days set by the Registrar, not to exceed sixty (60) days);
3. Inform the Prior Registrant or its Designated Agent that if its final goal is to transfer the domain name to a different registrar, the Prior Registrant is advised to request the inter-registrar transfer before the Change of Registrant to avoid triggering the 60-day lock described in Section II.C.2 (unless the Registrar gave the Prior Registrant the option to opt out of the 60-day lock, and the Prior Registrant opted out the 60-day lock);
4. Upon or after informing the Prior Registrant or its Designated Agent, if applicable, as described in II.C.1.3 above, obtain confirmation of the Change of Registrant request from the Prior Registrant, or the Designated Agent of the Prior Registrant. The Registrar must use a secure mechanism to confirm that the Prior Registrant and/or their respective Designated Agents have explicitly consented to the Change of Registrant. In obtaining the confirmation, the Registrar must inform the Prior Registrant or Designated Agent, if applicable, that the Change of Registrant request will not proceed if it is not confirmed in a number of days set by the Registrar, not to exceed sixty (60) days); The registrar may use additional contact information on file when obtaining confirmation from the Prior Registrant and is not limited to the publicly accessible Whois.
5. Process the Change of Registrant within one (1) day of obtaining the confirmations described above;
6. Notify the Prior Registrant and New Registrant before or within one day of the completion of the Change of Registrant. The notification must:
6.1 always be sent to both the New Registrant and Prior Registrant before or within one day of the Change of Registrant being performed;
6.2 explain the request that was received and list the domain(s) in question;
6.3. include contact information for questions.
6.4. advise the Prior Registrant and New Registrant of the 60-day inter-registrar transfer lock as described in Section II.C.2 or advise the Prior Registrant that it previously opted out of the 60-day inter-registrar transfer lock as described in Section II.C.2.
7. The Registrar must impose a 60-day inter-registrar transfer lock following a Change of Registrant, provided, however, that the Registrar may allow the Registered Name Holder to opt out of the 60-day inter-registrar transfer lock prior to any Change of Registrant request.
Inter-Registrar Transfer Lock following a Change of Registrant: Registrars are not required to apply a specific EPP status code for the 60-day inter-registrar transfer lock described in section II.C.2; however, if a registrar chooses to apply the clientTransferProhibited EPP status code, it must also lock the name in a way that prohibits the Registered Name Holder from removing
Updated: 1 December 2016