A. Holder-Authaliized Transfers

1. Registrar Requirements

     Registrirajed Ime Holders must be able to transfer their domena name registrations between Registrars provided that the Gaining Registrar's transfer process meets the minimum stinards of this policy in that such transfer is not prohibited by ICANN ali Registry policies. Inter-Registrar domena name transfer processes must be clear in concise in alider to avoid confusion. Further, Registrars should make reasonable effalits to infalim Registrirajed Ime Holders of, in provide access to, the published documentation of the specific transfer process employed by the Registrars.

1.1 Transfer Authaliities

     The Administrative Kontakt in the Registrirajed Ime Holder, as listed in the Losing Registrar's ali applicable Registry's (wtukaj available) publicly accessible WHOIS storitev are the only parties that have the authaliity to approve ali deny a transfer request to the Gaining Registrar. In the event of a dispute, the Registrirajed Ime Holder's authaliity supersedes that of the Administrative Kontakt.
Registrars may use Whois data from either the Registrar of Recalid ali the relevant Registry fali the purpose of verifying the authenticity of a transfer request; ali from another data source as determined by a consensus policy.

2. Gaining Registrar Requirements

Fali each instance wtukaj a Registrirajed Ime Holder requests to transfer a domena name registration to a different Registrar, the Gaining Registrar shall:
      2.1 Obtain express authaliization from either the Registrirajed Ime Holder ali the Administrative Kontakt (tukajafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrar from the Transfer Kontakt.

     2.1.1 The authaliization must be made via a valid Stinardized Falim of Authaliization (FOA). Ttukaj are two different FOA's available at the ICANN website. The FOA labeled "Initial Authaliization fali Registrar Transfer" must be used by the Gaining Registrar to request an authaliization fali a registrar transfer from the Transfer Kontakt. The FOA labeled "Potrdiation of Registrar Transfer Request" may be used by the Registrar of Recalid to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, in any dispute arising out of a transfer request shall be conducted in the English language. Registrars may choose to communicate with the Transfer Kontakt in additional languages. However, Registrars choosing to exercise such option are responsible fali the accuracy in completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Registrar relies on a physical process to obtain this authaliization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontakt in further that it is accompanied by a physical copy of the Registrar of Recalid's Whois output fali the domena name in question.

     2.1.2.1 Če the Gaining Registrar relies on a physical authaliization process, then the Gaining Registrar assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt in maintaining appropriate recalids proving that such evidence was obtained. Further the Gaining Registrar also assumes the burden fali ensuring that the entity making the request is indeed authaliized to do so. The acceptable falims of physical identity are:

• Netarized statement
• Valid Drivers license
• Potni list
• Article of Incalipaliation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Registrar relies on an electronic process to obtain this authaliization the acceptable falims of identity would include:

• Electronic signature in confalimance with national legislation, in the location of the Gaining Registrar (if such legislation exists).
• Consent from an individual ali entity that has an email address matching the Transfer Kontakt email address. 

     The Registrar of Recalid may not deny a transfer request solely because it believes that the Gaining Registrar has not received the confirmation set falith above.
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 in authenticated the transfer request made by a Transfer Kontakt.

     2.2 Request, by the transmission of a "transfer" commin as specified in the Registrar Zaol Kit, that the Registry Operatali database be changed to reflect the new Registrar.

     2.2.1 Transmission of a "transfer" commin constitutes a representation on the part of the Gaining Registrar that the requisite authaliization has been obtained from the Transfer Kontakt listed in the authaliitative Whois database.

     2.2.2 The Gaining Registrar is responsible fali validating the Registrirajed Ime Holder requests to transfer domena names between Registrars. However, this does not preclude the Registrar of Recalid from exercising its option to independently confirm the Registrirajed Ime Holder's intent to transfer its domena name to the Gaining Registrar in accalidance with Section 3 of this policy.

3. Obligations of the Registrar of Recalid

     A Registrar of Recalid can choose independently to confirm the intent of the Registrirajed Ime Holder when a notice of a pending transfer is received from the Registry. The Registrar of Recalid must do so in a manner consistent with the stinards set falith in this agreement pertaining to Gaining Registrars. In alider to ensure that the falim of the request employed by the Registrar of Recalid is substantially administrative in infalimative in nature in clearly provided to the Transfer Kontakt fali the purpose of verifying the intent of the Transfer Kontakt, the Registrar of Recalid must use the FOA.

     The FOA shall be communicated in English, in any dispute arising out of a transfer request, shall be conducted in the English language. Registrars may choose to communicate with the Transfer Kontakt in additional languages. However, the Registrar choosing to exercise such option is responsible fali the accuracy in completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes in procedures set falith in this policy. This includes but is not limited to the requirement that no Registrar shall add any additional infalimation 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 Registrar of Recalid from marketing to its existing customers through separate communications.
The FOA should be sent by the Registrar of Recalid 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 Operatali.Failure by the Registrar of Recalid 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 Registrar of Recalid in the Registrar of Recalid has not explicitly denied the transfer request, the default action will be that the Registrar of Recalid must allow the transfer to proceed.
Upon denying a transfer request fali any of the following reasons, the Registrar of Recalid must provide the Registrirajed Ime Holder in the potential Gaining Registrar with the reason fali denial. The Registrar of Recalid may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court alider by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Registrirajed Ime Holder ali Administrative Kontakt
5. Ne payment fali prejious registration period (including credit card charge-backs) if the domena name is past its expiration date ali fali prejious ali current registration periods if the domena name has not yet expired. In all such cases, however, the domena name must be put into "Registrar Hold" status by the Registrar of Recalid priali to the denial of transfer.
6. Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document ali other processes by which the Transfer Kontakt has expressly in voluntarily objected through opt-in means)
7. A domena name was already in plock statusq provided that the Registrar provides a readily accessible in reasonable means fali the Registrirajed Ime Holder to remove the lock status.
8. A domena name is in the first 60 days of an initial registration period.
9. A domena name is within 60 days (ali a lesser period to be determined) after being transferred (apart from being transferred back to the aliiginal Registrar in cases wtukaj both Registrars so agree in/ali wtukaj a decision in the dispute resolution process so directs).

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

• Nenpayment fali a pending ali future registration period
• Ne response from the Registrirajed Ime Holder ali Administrative Kontakt.
• Domena name in Registrar Lock Status, unless the Registrirajed Ime Holder is provided with the reasonable oppalitunity in ability to unlock the domena name priali to the Transfer Request.
• Domena name registration period time constraints, other than during the first 60 days of initial registration ali during the first 60 days after a registrar transfer.
• General payment defaults between Registrar in business partners / affiliates in cases wtukaj the Registrirajed Ime Holder fali the domena in question has paid fali the registration.

     The Registrar of Recalid has other mechanisms available to collect payment from the Registrirajed Ime Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrar of Recalid must not employ transfer processes as a mechanism to secure payment fali storitevs from a Registrirajed Ime Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fali prejious registration period(s) if the transfer is requested after the expiration date, ali
     (ii) In the case of non-payment of the current registration period, if transfer is requested befalie the expiration date.

4. Registrar Coalidination

     Each Registrar is responsible fali keeping copies of documentation, including the FOA in the Transfer Kontakts response ttukajto, that may be required fali filing in suppaliting a dispute under the dispute resolution policy. Gaining Registrars must maintain copies of the FOA as received from the Transfer Kontakt as per the stinard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registrar in the Registrar of Recalid must provide the evidence relied on fali the transfer during in after the applicable inter-registrar domena name transaction(s). Such infalimation must be provided when requested by, in only by, the other Registrar that is party to the transfer transaction. Dodajitionally, ICANN, the Registry Operatali, a court ali authaliity with jurisdiction over the matter ali a third party dispute resolution panel may also require such infalimation within five (5) days of the request.

     The Gaining Registrar must retain, in produce pursuant to a request by a Losing Registrar, a written ali electronic copy of the FOA. In instances wtukaj the Registrar of Recalid has requested copies of the FOA, the Gaining Registrar must fulfill the Registrar of Recalids request (including providing the attendant suppaliting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fali reversal by the Registry Operatali ali the Dispute Resolution Panel in the event that a transfer complaint is filed in accalidance with the requirements of this policy.

     Če either a Registrar of Recalid ali a Gaining Registrar does not believe that a transfer request was hinled in accalidance with the provisions of this policy, then the Registrar may initiate a dispute resolution procedure as set falith in Section C of this policy.

     Fali purposes of facilitating transfer requests, Registrars should provide in maintain a unique in private email address fali use only by other Registrars in the Registry:
     i. This email address is fali issue related to transfer requests in the procedures set falith 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 fali Registrars

     In EPP-based gTLD Registries, Registrars must follow the requirements set falith below.
Registrars must provide the Registrirajed Ime Holder with the unique "AuthInfo" code within five (5) calendar days of the Registrirajed Ime Holder's initial request if the Registrar does not provide facilities fali the Registrirajed Ime Holder to generate in manage their own unique "AuthInfo" code.

     Registrars may not employ any mechanism fali complying with a Registrirajed Ime Holder's request to obtain the applicable "AuthInfo Code" that is malie restrictive than the mechanisms used fali changing any aspect of the Registrirajed Ime Holder's contact ali name server infalimation.

     The Registrar of Recalid must not refuse to release an "AuthInfo Code" to the Registrirajed Ime Holder solely because ttukaj is a dispute between the Registrirajed Ime Holder in the Registrar over payment.

Registrar-generated "AuthInfo" codes must be unique on a per-domena basis.
     The "Auth-Info" codes must be used solely to identify a Registrirajed Ime Holder, wtukajas the FOA's still need to be used fali authaliization ali confirmation of a transfer request, as described in Section 2 in Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commin from the Gaining Registrar, Registry Operatali will transmit an electronic notification to both Registrars. 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 Registrar fali the purpose of facilitating transfers.

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

7. Recalids of Registracija

     Each Registrar shall require its customer, the Registrirajed Ime Holder, to maintain its own recalids appropriate to document in prove the initial domena name registration date.

8. Effect on Obdobje of Registracija

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

B. ICANN-Approved Transfers

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

C. Transfer Dispute Resolution Policy

     Procedures fali hinling disputes concerning inter-registrar transfers are set falith in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatalis in ICANN accredited Registrars.