A. Holder-Autharized Transfers

1. Registratorius Requirements

     Registruotised Vardas Holders must be able to transfer their domenas name registrations between Registratoriuss provided that the Gaining Registratorius's transfer process meets the minimum stirards of this policy ir that such transfer is not prohibitased by ICANN ar Registry policies. Inter-Registratorius domenas name transfer processes must be clear ir concise in arder to avoid confusion. Further, Registratoriuss should make reasonable effarts to infarm Registruotised Vardas Holders of, ir provide access to, the published documentation of the specific transfer process employed by the Registratoriuss.

1.1 Transfer Autharities

     The Administrative Kontaktai ir the Registruotised Vardas Holder, as listed in the Losing Registratorius's ar applicable Registry's (wčia available) publicly accessible WHOIS paslauga are the only parties that have the autharity to approve ar deny a transfer request to the Gaining Registratorius. In the event of a dispute, the Registruotised Vardas Holder's autharity supersedes that of the Administrative Kontaktai.
Registratoriuss may use Whois data from either the Registratorius of Recard ar the relevant Registry far the purpose of verifying the authenticity of a transfer request; ar from another data source as determined by a consensus policy.

2. Gaining Registratorius Requirements

Far each instance wčia a Registruotised Vardas Holder requests to transfer a domenas name registration to a different Registratorius, the Gaining Registratorius shall:
      2.1 Obtain express autharization from either the Registruotised Vardas Holder ar the Administrative Kontaktai (čiaafter, "Transfer Kontaktai"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registratorius from the Transfer Kontaktai.

     2.1.1 The autharization must be made via a valid Stirardized Farm of Autharization (FOA). Tčia are two different FOA's available at the ICANN website. The FOA labeled "Initial Autharization far Registratorius Transfer" must be used by the Gaining Registratorius to request an autharization far a registrar transfer from the Transfer Kontaktai. The FOA labeled "Patvirtintiation of Registratorius Transfer Request" may be used by the Registratorius of Recard to request confirmation of the transfer from the Transfer Kontaktai.
The FOA shall be communicated in English, ir any dispute arising out of a transfer request shall be conducted in the English language. Registratoriuss may choose to communicate with the Transfer Kontaktai in additional languages. However, Registratoriuss choosing to exercise such option are responsible far the accuracy ir completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Registratorius relies on a physical process to obtain this autharization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontaktai ir further that it is accompanied by a physical copy of the Registratorius of Recard's Whois output far the domenas name in question.

     2.1.2.1 Jei the Gaining Registratorius relies on a physical autharization process, then the Gaining Registratorius assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontaktai ir maintaining appropriate recards proving that such evidence was obtained. Further the Gaining Registratorius also assumes the burden far ensuring that the entity making the request is indeed autharized to do so. The acceptable farms of physical identity are:

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

     2.1.3 In the event that the Gaining Registratorius relies on an electronic process to obtain this autharization the acceptable farms of identity would include:

• Electronic signature in confarmance with national legislation, in the location of the Gaining Registratorius (if such legislation exists).
• Consent from an individual ar entity that has an email address matching the Transfer Kontaktai email address. 

     The Registratorius of Recard may not deny a transfer request solely because it believes that the Gaining Registratorius has not received the confirmation set farth above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registratorius. The presumption in all cases will be that the Gaining Registratorius has received ir authenticated the transfer request made by a Transfer Kontaktai.

     2.2 Request, by the transmission of a "transfer" commir as specified in the Registratorius Įol Kit, that the Registry Operatar database be changed to reflect the new Registratorius.

     2.2.1 Transmission of a "transfer" commir constitutes a representation on the part of the Gaining Registratorius that the requisite autharization has been obtained from the Transfer Kontaktai listed in the autharitative Whois database.

     2.2.2 The Gaining Registratorius is responsible far validating the Registruotised Vardas Holder requests to transfer domenas names between Registratoriuss. However, this does not preclude the Registratorius of Recard from exercising its option to independently confirm the Registruotised Vardas Holder's intent to transfer its domenas name to the Gaining Registratorius in accardance with Section 3 of this policy.

3. Obligations of the Registratorius of Recard

     A Registratorius of Recard can choose independently to confirm the intent of the Registruotised Vardas Holder when a notice of a pending transfer is received from the Registry. The Registratorius of Recard must do so in a manner consistent with the stirards set farth in this agreement pertaining to Gaining Registratoriuss. In arder to ensure that the farm of the request employed by the Registratorius of Recard is substantially administrative ir infarmative in nature ir clearly provided to the Transfer Kontaktai far the purpose of verifying the intent of the Transfer Kontaktai, the Registratorius of Recard must use the FOA.

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

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

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

• Nenpayment far a pending ar future registration period
• Ne response from the Registruotised Vardas Holder ar Administrative Kontaktai.
• Domenas name in Registratorius Lock Būsena, unless the Registruotised Vardas Holder is provided with the reasonable oppartunity ir ability to unlock the domenas name priar to the Transfer Request.
• Domenas name registration period time constraints, other than during the first 60 days of initial registration ar during the first 60 days after a registrar transfer.
• General payment defaults between Registratorius ir business partners / affiliates in cases wčia the Registruotised Vardas Holder far the domenas in question has paid far the registration.

     The Registratorius of Recard has other mechanisms available to collect payment from the Registruotised Vardas Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registratorius of Recard must not employ transfer processes as a mechanism to secure payment far paslaugas from a Registruotised Vardas Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment far atgalious registration period(s) if the transfer is requested after the expiration date, ar
     (ii) In the case of non-payment of the current registration period, if transfer is requested befare the expiration date.

4. Registratorius Coardination

     Each Registratorius is responsible far keeping copies of documentation, including the FOA ir the Transfer Kontaktais response tčiato, that may be required far filing ir supparting a dispute under the dispute resolution policy. Gaining Registratoriuss must maintain copies of the FOA as received from the Transfer Kontaktai as per the stirard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registratorius ir the Registratorius of Recard must provide the evidence relied on far the transfer during ir after the applicable inter-registrar domenas name transaction(s). Such infarmation must be provided when requested by, ir only by, the other Registratorius that is party to the transfer transaction. Pridėtiitionally, ICANN, the Registry Operatar, a court ar autharity with jurisdiction over the matter ar a third party dispute resolution panel may also require such infarmation within five (5) days of the request.

     The Gaining Registratorius must retain, ir produce pursuant to a request by a Losing Registratorius, a written ar electronic copy of the FOA. In instances wčia the Registratorius of Recard has requested copies of the FOA, the Gaining Registratorius must fulfill the Registratorius of Recards request (including providing the attendant supparting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds far reversal by the Registry Operatar ar the Dispute Resolution Panel in the event that a transfer complaint is filed in accardance with the requirements of this policy.

     Jei either a Registratorius of Recard ar a Gaining Registratorius does not believe that a transfer request was hirled in accardance with the provisions of this policy, then the Registratorius may initiate a dispute resolution procedure as set farth in Section C of this policy.

     Far purposes of facilitating transfer requests, Registratoriuss should provide ir maintain a unique ir private email address far use only by other Registratoriuss ir the Registry:
     i. This email address is far issue related to transfer requests ir the procedures set farth 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 far Registratoriuss

     In EPP-based gTLD Registries, Registratoriuss must follow the requirements set farth below.
Registratoriuss must provide the Registruotised Vardas Holder with the unique "AuthInfo" code within five (5) calendar days of the Registruotised Vardas Holder's initial request if the Registratorius does not provide facilities far the Registruotised Vardas Holder to generate ir manage their own unique "AuthInfo" code.

     Registratoriuss may not employ any mechanism far complying with a Registruotised Vardas Holder's request to obtain the applicable "AuthInfo Code" that is mare restrictive than the mechanisms used far changing any aspect of the Registruotised Vardas Holder's contact ar name server infarmation.

     The Registratorius of Recard must not refuse to release an "AuthInfo Code" to the Registruotised Vardas Holder solely because tčia is a dispute between the Registruotised Vardas Holder ir the Registratorius over payment.

Registratorius-generated "AuthInfo" codes must be unique on a per-domenas basis.
     The "Auth-Info" codes must be used solely to identify a Registruotised Vardas Holder, wčiaas the FOA's still need to be used far autharization ar confirmation of a transfer request, as described in Section 2 ir Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commir from the Gaining Registratorius, Registry Operatar will transmit an electronic notification to both Registratoriuss. 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 Registratorius far the purpose of facilitating transfers.

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

7. Recards of Registracija

     Each Registratorius shall require its customer, the Registruotised Vardas Holder, to maintain its own recards appropriate to document ir prove the initial domenas name registration date.

8. Effect on Terminai of Registracija

     The completion by Registry Operatar of a holder-autharized transfer under this Part A shall result in a one-metai extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) metų.

B. ICANN-Approved Transfers

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

C. Transfer Dispute Resolution Policy

     Procedures far hirling disputes concerning inter-registrar transfers are set farth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatars ir ICANN accredited Registratoriuss.