A. Holder-Authoized Transfers

1. Registrador Requirements

     Registrared Nom Holders must be able to transfer their domini name registrations between Registradors provided that the Gaining Registrador's transfer process meets the minimum stiards of this policy i that such transfer is not prohibited by ICANN o Registry policies. Inter-Registrador domini name transfer processes must be clear i concise in oder to avoid confusion. Further, Registradors should make reasonable effots to infom Registrared Nom Holders of, i provide access to, the published documentation of the specific transfer process employed by the Registradors.

1.1 Transfer Authoities

     The Administrative Contacte i the Registrared Nom Holder, as listed in the Losing Registrador's o applicable Registry's (waquí available) publicly accessible WHOIS servei are the only parties that have the authoity to approve o deny a transfer request to the Gaining Registrador. In the event of a dispute, the Registrared Nom Holder's authoity supersedes that of the Administrative Contacte.
Registradors may use Whois data from either the Registrador of Recod o the relevant Registry fo the purpose of verifying the authenticity of a transfer request; o from another data source as determined by a consensus policy.

2. Gaining Registrador Requirements

Fo each instance waquí a Registrared Nom Holder requests to transfer a domini name registration to a different Registrador, the Gaining Registrador shall:
      2.1 Obtain express authoization from either the Registrared Nom Holder o the Administrative Contacte (aquíafter, "Transfer Contacte"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrador from the Transfer Contacte.

     2.1.1 The authoization must be made via a valid Stiardized Fom of Authoization (FOA). Taquí are two different FOA's available at the ICANN website. The FOA labeled "Initial Authoization fo Registrador Transfer" must be used by the Gaining Registrador to request an authoization fo a registrar transfer from the Transfer Contacte. The FOA labeled "Confirmaation of Registrador Transfer Request" may be used by the Registrador of Recod to request confirmation of the transfer from the Transfer Contacte.
The FOA shall be communicated in English, i any dispute arising out of a transfer request shall be conducted in the English language. Registradors may choose to communicate with the Transfer Contacte in additional languages. However, Registradors choosing to exercise such option are responsible fo the accuracy i completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Registrador relies on a physical process to obtain this authoization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Contacte i further that it is accompanied by a physical copy of the Registrador of Recod's Whois output fo the domini name in question.

     2.1.2.1 Si the Gaining Registrador relies on a physical authoization process, then the Gaining Registrador assumes the burden of obtaining reliable evidence of the identity of the Transfer Contacte i maintaining appropriate recods proving that such evidence was obtained. Further the Gaining Registrador also assumes the burden fo ensuring that the entity making the request is indeed authoized to do so. The acceptable foms of physical identity are:

• Notarized statement
• Valid Drivers license
• Passaport
• Article of Incopoation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Registrador relies on an electronic process to obtain this authoization the acceptable foms of identity would include:

• Electronic signature in confomance with national legislation, in the location of the Gaining Registrador (if such legislation exists).
• Consent from an individual o entity that has an email address matching the Transfer Contacte email address. 

     The Registrador of Recod may not deny a transfer request solely because it believes that the Gaining Registrador has not received the confirmation set foth above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registrador. The presumption in all cases will be that the Gaining Registrador has received i authenticated the transfer request made by a Transfer Contacte.

     2.2 Request, by the transmission of a "transfer" commi as specified in the Registrador Perol Kit, that the Registry Operato database be changed to reflect the new Registrador.

     2.2.1 Transmission of a "transfer" commi constitutes a representation on the part of the Gaining Registrador that the requisite authoization has been obtained from the Transfer Contacte listed in the authoitative Whois database.

     2.2.2 The Gaining Registrador is responsible fo validating the Registrared Nom Holder requests to transfer domini names between Registradors. However, this does not preclude the Registrador of Recod from exercising its option to independently confirm the Registrared Nom Holder's intent to transfer its domini name to the Gaining Registrador in accodance with Section 3 of this policy.

3. Obligations of the Registrador of Recod

     A Registrador of Recod can choose independently to confirm the intent of the Registrared Nom Holder when a notice of a pending transfer is received from the Registry. The Registrador of Recod must do so in a manner consistent with the stiards set foth in this agreement pertaining to Gaining Registradors. In oder to ensure that the fom of the request employed by the Registrador of Recod is substantially administrative i infomative in nature i clearly provided to the Transfer Contacte fo the purpose of verifying the intent of the Transfer Contacte, the Registrador of Recod must use the FOA.

     The FOA shall be communicated in English, i any dispute arising out of a transfer request, shall be conducted in the English language. Registradors may choose to communicate with the Transfer Contacte in additional languages. However, the Registrador choosing to exercise such option is responsible fo the accuracy i completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes i procedures set foth in this policy. This includes but is not limited to the requirement that no Registrador shall add any additional infomation to the FOA used to obtain the consent of the Transfer Contacte in the case of a transfer request.
This requirement does not preclude the Registrador of Recod from marketing to its existing customers through separate communications.
The FOA should be sent by the Registrador of Recod to the Transfer Contacte as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operato.Failure by the Registrador of Recod 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.

     In the event that a Transfer Contacte listed in the Whois has not confirmed their request to transfer with the Registrador of Recod i the Registrador of Recod has not explicitly denied the transfer request, the default action will be that the Registrador of Recod must allow the transfer to proceed.
Upon denying a transfer request fo any of the following reasons, the Registrador of Recod must provide the Registrared Nom Holder i the potential Gaining Registrador with the reason fo denial. The Registrador of Recod may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court oder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Registrared Nom Holder o Administrative Contacte
5. No payment fo anteriorious registration period (including credit card charge-backs) if the domini name is past its expiration date o fo anteriorious o current registration periods if the domini name has not yet expired. In all such cases, however, the domini name must be put into "Registrador Hold" status by the Registrador of Recod prio to the denial of transfer.
6. Express written objection to the transfer from the Transfer Contacte. (e.g. - email, fax, paper document o other processes by which the Transfer Contacte has expressly i voluntarily objected through opt-in means)
7. A domini name was already in plock statusq provided that the Registrador provides a readily accessible i reasonable means fo the Registrared Nom Holder to remove the lock status.
8. A domini name is in the first 60 days of an initial registration period.
9. A domini name is within 60 days (o a lesser period to be determined) after being transferred (apart from being transferred back to the oiginal Registrador in cases waquí both Registradors so agree i/o waquí a decision in the dispute resolution process so directs).

Instances when the requested change of Registrador may not be denied include, but are not limited to:

• Nonpayment fo a pending o future registration period
• No response from the Registrared Nom Holder o Administrative Contacte.
• Domini name in Registrador Lock Estat, unless the Registrared Nom Holder is provided with the reasonable oppotunity i ability to unlock the domini name prio to the Transfer Request.
• Domini name registration period time constraints, other than during the first 60 days of initial registration o during the first 60 days after a registrar transfer.
• General payment defaults between Registrador i business partners / affiliates in cases waquí the Registrared Nom Holder fo the domini in question has paid fo the registration.

     The Registrador of Recod has other mechanisms available to collect payment from the Registrared Nom Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrador of Recod must not employ transfer processes as a mechanism to secure payment fo serveis from a Registrared Nom Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fo anteriorious registration period(s) if the transfer is requested after the expiration date, o
     (ii) In the case of non-payment of the current registration period, if transfer is requested befoe the expiration date.

4. Registrador Coodination

     Each Registrador is responsible fo keeping copies of documentation, including the FOA i the Transfer Contactes response taquíto, that may be required fo filing i suppoting a dispute under the dispute resolution policy. Gaining Registradors must maintain copies of the FOA as received from the Transfer Contacte as per the stiard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registrador i the Registrador of Recod must provide the evidence relied on fo the transfer during i after the applicable inter-registrar domini name transaction(s). Such infomation must be provided when requested by, i only by, the other Registrador that is party to the transfer transaction. Afegiritionally, ICANN, the Registry Operato, a court o authoity with jurisdiction over the matter o a third party dispute resolution panel may also require such infomation within five (5) days of the request.

     The Gaining Registrador must retain, i produce pursuant to a request by a Losing Registrador, a written o electronic copy of the FOA. In instances waquí the Registrador of Recod has requested copies of the FOA, the Gaining Registrador must fulfill the Registrador of Recods request (including providing the attendant suppoting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fo reversal by the Registry Operato o the Dispute Resolution Panel in the event that a transfer complaint is filed in accodance with the requirements of this policy.

     Si either a Registrador of Recod o a Gaining Registrador does not believe that a transfer request was hiled in accodance with the provisions of this policy, then the Registrador may initiate a dispute resolution procedure as set foth in Section C of this policy.

     Fo purposes of facilitating transfer requests, Registradors should provide i maintain a unique i private email address fo use only by other Registradors i the Registry:
     i. This email address is fo issue related to transfer requests i the procedures set foth in this policy only.
     ii. The email address should be managed to ensure messages are received by someone who can respond to the transfer issue.
     iii. Messages received at such email address must be responded to within a commercial reasonable timeframe not to exceed seven (7) calendar days.

5. EPP - based Registry Requirements fo Registradors

     In EPP-based gTLD Registries, Registradors must follow the requirements set foth below.
Registradors must provide the Registrared Nom Holder with the unique "AuthInfo" code within five (5) calendar days of the Registrared Nom Holder's initial request if the Registrador does not provide facilities fo the Registrared Nom Holder to generate i manage their own unique "AuthInfo" code.

     Registradors may not employ any mechanism fo complying with a Registrared Nom Holder's request to obtain the applicable "AuthInfo Code" that is moe restrictive than the mechanisms used fo changing any aspect of the Registrared Nom Holder's contact o name server infomation.

     The Registrador of Recod must not refuse to release an "AuthInfo Code" to the Registrared Nom Holder solely because taquí is a dispute between the Registrared Nom Holder i the Registrador over payment.

Registrador-generated "AuthInfo" codes must be unique on a per-domini basis.
     The "Auth-Info" codes must be used solely to identify a Registrared Nom Holder, waquías the FOA's still need to be used fo authoization o confirmation of a transfer request, as described in Section 2 i Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commi from the Gaining Registrador, Registry Operato will transmit an electronic notification to both Registradors. In the case of those Registries that use electronic mail notifications, the response notification may be sent to the unique email address established by each Registrador fo the purpose of facilitating transfers.

     The Registry Operato shall complete the requested transfer unless, within five (5) calendar days, Registry Operato receives a NACK protocol commi from the Registrador of Recod.
When the Registry's database has been updated to reflect the change to the Gaining Registrador, Registry Operato will transmit an electronic notification to both Registradors. The notification may be sent to       the unique email address established by each Registrador fo the purpose of facilitating transfers o such other email address agreed to by the parties.
The Registry Operato shall undo a transfer if, after a transfer has occurred, the Registry Operato receives one of the notices as set foth below. In such case, the transfer will be reversed i the domini name reset to its oiginal state. The Registry Operato 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 Registry Operato must undo the transfer within fourteen calendar days unless a court action is filed. The notice required shall be one of the following:
     i. Agreement of the Registrador of Recod i the Gaining Registrador sent by email, letter o fax that the transfer was made by mistake o was otherwise not in accodance with the procedures set foth in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; o
     iii. Order of a court having jurisdiction over the transfer.

7. Recods of Registre

     Each Registrador shall require its customer, the Registrared Nom Holder, to maintain its own recods appropriate to document i prove the initial domini name registration date.

8. Effect on Període of Registre

     The completion by Registry Operato of a holder-authoized transfer under this Part A shall result in a one-any extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) anys.

B. ICANN-Approved Transfers

     Transfer of the sponsoship of all the registrations sponsoed by one Registrador as the result of (i) acquisition of that Registrador o its assets by another Registrador, o (ii) lack of accreditation of that Registrador o lack of its authoization with the Registry Operato, may be made accoding to the following procedure:
     (a) The gaining Registrador must be accredited by ICANN fo the Registry TLD i must have in effect a Registry-Registrador Agreement with Registry Operato fo the Registry TLD.
     (b) ICANN must certify in writing to Registry Operato that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual o imminent business failure of a Registrador.
Upon satisfaction of these two conditions, Registry Operato will make the necessary one-time changes in the Registry database fo no charge, fo transfers involving 50,000 name registrations o fewer. Si the transfer involves registrations of moe than 50,000 names, Registry Operato will charge the gaining Registrador a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures fo hiling disputes concerning inter-registrar transfers are set foth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatos i ICANN accredited Registradors.