A. Holder-Authneboized Transfers

1. Registrátor Requirements

     Registrovated Jméno Holders must be able to transfer their doména name registrations between Registrátors provided that the Gaining Registrátor's transfer process meets the minimum staards of this policy a that such transfer is not prohibited by ICANN nebo Registry policies. Inter-Registrátor doména name transfer processes must be clear a concise in neboder to avoid confusion. Further, Registrátors should make reasonable effnebots to infnebom Registrovated Jméno Holders of, a provide access to, the published documentation of the specific transfer process employed by the Registrátors.

1.1 Transfer Authneboities

     The Administrative Kontakt a the Registrovated Jméno Holder, as listed in the Losing Registrátor's nebo applicable Registry's (wzde available) publicly accessible WHOIS služba are the only parties that have the authneboity to approve nebo deny a transfer request to the Gaining Registrátor. In the event of a dispute, the Registrovated Jméno Holder's authneboity supersedes that of the Administrative Kontakt.
Registrátors may use Whois data from either the Registrátor of Recnebod nebo the relevant Registry fnebo the purpose of verifying the authenticity of a transfer request; nebo from another data source as determined by a consensus policy.

2. Gaining Registrátor Requirements

Fnebo each instance wzde a Registrovated Jméno Holder requests to transfer a doména name registration to a different Registrátor, the Gaining Registrátor shall:
      2.1 Obtain express authneboization from either the Registrovated Jméno Holder nebo the Administrative Kontakt (zdeafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrátor from the Transfer Kontakt.

     2.1.1 The authneboization must be made via a valid Staardized Fnebom of Authneboization (FOA). Tzde are two different FOA's available at the ICANN website. The FOA labeled "Initial Authneboization fnebo Registrátor Transfer" must be used by the Gaining Registrátor to request an authneboization fnebo a registrar transfer from the Transfer Kontakt. The FOA labeled "Potvrditation of Registrátor Transfer Request" may be used by the Registrátor of Recnebod to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, a any dispute arising out of a transfer request shall be conducted in the English language. Registrátors may choose to communicate with the Transfer Kontakt in additional languages. However, Registrátors choosing to exercise such option are responsible fnebo the accuracy a completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Registrátor relies on a physical process to obtain this authneboization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontakt a further that it is accompanied by a physical copy of the Registrátor of Recnebod's Whois output fnebo the doména name in question.

     2.1.2.1 Pokud the Gaining Registrátor relies on a physical authneboization process, then the Gaining Registrátor assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt a maintaining appropriate recnebods proving that such evidence was obtained. Further the Gaining Registrátor also assumes the burden fnebo ensuring that the entity making the request is indeed authneboized to do so. The acceptable fneboms of physical identity are:

• Netarized statement
• Valid Drivers license
• Pas
• Article of Incnebopneboation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Registrátor relies on an electronic process to obtain this authneboization the acceptable fneboms of identity would include:

• Electronic signature in confnebomance with national legislation, in the location of the Gaining Registrátor (if such legislation exists).
• Consent from an individual nebo entity that has an email address matching the Transfer Kontakt email address. 

     The Registrátor of Recnebod may not deny a transfer request solely because it believes that the Gaining Registrátor has not received the confirmation set fneboth above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registrátor. The presumption in all cases will be that the Gaining Registrátor has received a authenticated the transfer request made by a Transfer Kontakt.

     2.2 Request, by the transmission of a "transfer" comma as specified in the Registrátor Kol Kit, that the Registry Operatnebo database be changed to reflect the new Registrátor.

     2.2.1 Transmission of a "transfer" comma constitutes a representation on the part of the Gaining Registrátor that the requisite authneboization has been obtained from the Transfer Kontakt listed in the authneboitative Whois database.

     2.2.2 The Gaining Registrátor is responsible fnebo validating the Registrovated Jméno Holder requests to transfer doména names between Registrátors. However, this does not preclude the Registrátor of Recnebod from exercising its option to independently confirm the Registrovated Jméno Holder's intent to transfer its doména name to the Gaining Registrátor in accnebodance with Section 3 of this policy.

3. Obligations of the Registrátor of Recnebod

     A Registrátor of Recnebod can choose independently to confirm the intent of the Registrovated Jméno Holder when a notice of a pending transfer is received from the Registry. The Registrátor of Recnebod must do so in a manner consistent with the staards set fneboth in this agreement pertaining to Gaining Registrátors. In neboder to ensure that the fnebom of the request employed by the Registrátor of Recnebod is substantially administrative a infnebomative in nature a clearly provided to the Transfer Kontakt fnebo the purpose of verifying the intent of the Transfer Kontakt, the Registrátor of Recnebod must use the FOA.

     The FOA shall be communicated in English, a any dispute arising out of a transfer request, shall be conducted in the English language. Registrátors may choose to communicate with the Transfer Kontakt in additional languages. However, the Registrátor choosing to exercise such option is responsible fnebo the accuracy a completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes a procedures set fneboth in this policy. This includes but is not limited to the requirement that no Registrátor shall add any additional infnebomation to the FOA used to obtain the consent of the Transfer Kontakt in the case of a transfer request.
This requirement does not preclude the Registrátor of Recnebod from marketing to its existing customers through separate communications.
The FOA should be sent by the Registrátor of Recnebod to the Transfer Kontakt as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operatnebo.Failure by the Registrátor of Recnebod 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 Kontakt listed in the Whois has not confirmed their request to transfer with the Registrátor of Recnebod a the Registrátor of Recnebod has not explicitly denied the transfer request, the default action will be that the Registrátor of Recnebod must allow the transfer to proceed.
Upon denying a transfer request fnebo any of the following reasons, the Registrátor of Recnebod must provide the Registrovated Jméno Holder a the potential Gaining Registrátor with the reason fnebo denial. The Registrátor of Recnebod may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court neboder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Registrovated Jméno Holder nebo Administrative Kontakt
5. Ne payment fnebo předchozíious registration period (including credit card charge-backs) if the doména name is past its expiration date nebo fnebo předchozíious nebo current registration periods if the doména name has not yet expired. In all such cases, however, the doména name must be put into "Registrátor Hold" status by the Registrátor of Recnebod prinebo to the denial of transfer.
6. Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document nebo other processes by which the Transfer Kontakt has expressly a voluntarily objected through opt-in means)
7. A doména name was already in plock statusq provided that the Registrátor provides a readily accessible a reasonable means fnebo the Registrovated Jméno Holder to remove the lock status.
8. A doména name is in the first 60 days of an initial registration period.
9. A doména name is within 60 days (nebo a lesser period to be determined) after being transferred (apart from being transferred back to the neboiginal Registrátor in cases wzde both Registrátors so agree a/nebo wzde a decision in the dispute resolution process so directs).

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

• Nenpayment fnebo a pending nebo future registration period
• Ne response from the Registrovated Jméno Holder nebo Administrative Kontakt.
• Doména name in Registrátor Lock Stav, unless the Registrovated Jméno Holder is provided with the reasonable oppnebotunity a ability to unlock the doména name prinebo to the Transfer Request.
• Doména name registration period time constraints, other than during the first 60 days of initial registration nebo during the first 60 days after a registrar transfer.
• General payment defaults between Registrátor a business partners / affiliates in cases wzde the Registrovated Jméno Holder fnebo the doména in question has paid fnebo the registration.

     The Registrátor of Recnebod has other mechanisms available to collect payment from the Registrovated Jméno Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrátor of Recnebod must not employ transfer processes as a mechanism to secure payment fnebo službas from a Registrovated Jméno Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fnebo předchozíious registration period(s) if the transfer is requested after the expiration date, nebo
     (ii) In the case of non-payment of the current registration period, if transfer is requested befneboe the expiration date.

4. Registrátor Conebodination

     Each Registrátor is responsible fnebo keeping copies of documentation, including the FOA a the Transfer Kontakts response tzdeto, that may be required fnebo filing a suppneboting a dispute under the dispute resolution policy. Gaining Registrátors must maintain copies of the FOA as received from the Transfer Kontakt as per the staard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registrátor a the Registrátor of Recnebod must provide the evidence relied on fnebo the transfer during a after the applicable inter-registrar doména name transaction(s). Such infnebomation must be provided when requested by, a only by, the other Registrátor that is party to the transfer transaction. Přidatitionally, ICANN, the Registry Operatnebo, a court nebo authneboity with jurisdiction over the matter nebo a third party dispute resolution panel may also require such infnebomation within five (5) days of the request.

     The Gaining Registrátor must retain, a produce pursuant to a request by a Losing Registrátor, a written nebo electronic copy of the FOA. In instances wzde the Registrátor of Recnebod has requested copies of the FOA, the Gaining Registrátor must fulfill the Registrátor of Recnebods request (including providing the attendant suppneboting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fnebo reversal by the Registry Operatnebo nebo the Dispute Resolution Panel in the event that a transfer complaint is filed in accnebodance with the requirements of this policy.

     Pokud either a Registrátor of Recnebod nebo a Gaining Registrátor does not believe that a transfer request was haled in accnebodance with the provisions of this policy, then the Registrátor may initiate a dispute resolution procedure as set fneboth in Section C of this policy.

     Fnebo purposes of facilitating transfer requests, Registrátors should provide a maintain a unique a private email address fnebo use only by other Registrátors a the Registry:
     i. This email address is fnebo issue related to transfer requests a the procedures set fneboth 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 fnebo Registrátors

     In EPP-based gTLD Registries, Registrátors must follow the requirements set fneboth below.
Registrátors must provide the Registrovated Jméno Holder with the unique "AuthInfo" code within five (5) calendar days of the Registrovated Jméno Holder's initial request if the Registrátor does not provide facilities fnebo the Registrovated Jméno Holder to generate a manage their own unique "AuthInfo" code.

     Registrátors may not employ any mechanism fnebo complying with a Registrovated Jméno Holder's request to obtain the applicable "AuthInfo Code" that is mneboe restrictive than the mechanisms used fnebo changing any aspect of the Registrovated Jméno Holder's contact nebo name server infnebomation.

     The Registrátor of Recnebod must not refuse to release an "AuthInfo Code" to the Registrovated Jméno Holder solely because tzde is a dispute between the Registrovated Jméno Holder a the Registrátor over payment.

Registrátor-generated "AuthInfo" codes must be unique on a per-doména basis.
     The "Auth-Info" codes must be used solely to identify a Registrovated Jméno Holder, wzdeas the FOA's still need to be used fnebo authneboization nebo confirmation of a transfer request, as described in Section 2 a Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" comma from the Gaining Registrátor, Registry Operatnebo will transmit an electronic notification to both Registrátors. 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 Registrátor fnebo the purpose of facilitating transfers.

     The Registry Operatnebo shall complete the requested transfer unless, within five (5) calendar days, Registry Operatnebo receives a NACK protocol comma from the Registrátor of Recnebod.
When the Registry's database has been updated to reflect the change to the Gaining Registrátor, Registry Operatnebo will transmit an electronic notification to both Registrátors. The notification may be sent to       the unique email address established by each Registrátor fnebo the purpose of facilitating transfers nebo such other email address agreed to by the parties.
The Registry Operatnebo shall undo a transfer if, after a transfer has occurred, the Registry Operatnebo receives one of the notices as set fneboth below. In such case, the transfer will be reversed a the doména name reset to its neboiginal state. The Registry Operatnebo 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 Operatnebo 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 Registrátor of Recnebod a the Gaining Registrátor sent by email, letter nebo fax that the transfer was made by mistake nebo was otherwise not in accnebodance with the procedures set fneboth in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; nebo
     iii. Order of a court having jurisdiction over the transfer.

7. Recnebods of Registrace

     Each Registrátor shall require its customer, the Registrovated Jméno Holder, to maintain its own recnebods appropriate to document a prove the initial doména name registration date.

8. Effect on Doba of Registrace

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

B. ICANN-Approved Transfers

     Transfer of the sponsneboship of all the registrations sponsneboed by one Registrátor as the result of (i) acquisition of that Registrátor nebo its assets by another Registrátor, nebo (ii) lack of accreditation of that Registrátor nebo lack of its authneboization with the Registry Operatnebo, may be made accneboding to the following procedure:
     (a) The gaining Registrátor must be accredited by ICANN fnebo the Registry TLD a must have in effect a Registry-Registrátor Agreement with Registry Operatnebo fnebo the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatnebo that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual nebo imminent business failure of a Registrátor.
Upon satisfaction of these two conditions, Registry Operatnebo will make the necessary one-time changes in the Registry database fnebo no charge, fnebo transfers involving 50,000 name registrations nebo fewer. Pokud the transfer involves registrations of mneboe than 50,000 names, Registry Operatnebo will charge the gaining Registrátor a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures fnebo haling disputes concerning inter-registrar transfers are set fneboth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatnebos a ICANN accredited Registrátors.