A. Holder-Authoseized Transfers

1. Regjistrues Requirements

     Regjistrohued Emër Holders must be able to transfer their domain name registrations between Regjistruess provided that the Gaining Regjistrues's transfer process meets the minimum stdheards of this policy dhe that such transfer is not prohibited by ICANN ose Registry policies. Inter-Regjistrues domain name transfer processes must be clear dhe concise in oseder to avoid confusion. Further, Regjistruess should make reasonable effosets to infosem Regjistrohued Emër Holders of, dhe provide access to, the published documentation of the specific transfer process employed by the Regjistruess.

1.1 Transfer Authoseities

     The Administrative Kontakt dhe the Regjistrohued Emër Holder, as listed in the Losing Regjistrues's ose applicable Registry's (wkëtu available) publicly accessible WHOIS shërbimi are the only parties that have the authoseity to approve ose deny a transfer request to the Gaining Regjistrues. In the event of a dispute, the Regjistrohued Emër Holder's authoseity supersedes that of the Administrative Kontakt.
Regjistruess may use Whois data from either the Regjistrues of Recosed ose the relevant Registry fose the purpose of verifying the authenticity of a transfer request; ose from another data source as determined by a consensus policy.

2. Gaining Regjistrues Requirements

Fose each instance wkëtu a Regjistrohued Emër Holder requests to transfer a domain name registration to a different Regjistrues, the Gaining Regjistrues shall:
      2.1 Obtain express authoseization from either the Regjistrohued Emër Holder ose the Administrative Kontakt (këtuafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Regjistrues from the Transfer Kontakt.

     2.1.1 The authoseization must be made via a valid Stdheardized Fosem of Authoseization (FOA). Tkëtu are two different FOA's available at the ICANN website. The FOA labeled "Initial Authoseization fose Regjistrues Transfer" must be used by the Gaining Regjistrues to request an authoseization fose a registrar transfer from the Transfer Kontakt. The FOA labeled "Konfirmoation of Regjistrues Transfer Request" may be used by the Regjistrues of Recosed to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, dhe any dispute arising out of a transfer request shall be conducted in the English language. Regjistruess may choose to communicate with the Transfer Kontakt in additional languages. However, Regjistruess choosing to exercise such option are responsible fose the accuracy dhe completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Regjistrues relies on a physical process to obtain this authoseization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontakt dhe further that it is accompanied by a physical copy of the Regjistrues of Recosed's Whois output fose the domain name in question.

     2.1.2.1 Nëse the Gaining Regjistrues relies on a physical authoseization process, then the Gaining Regjistrues assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt dhe maintaining appropriate recoseds proving that such evidence was obtained. Further the Gaining Regjistrues also assumes the burden fose ensuring that the entity making the request is indeed authoseized to do so. The acceptable fosems of physical identity are:

• Jotarized statement
• Valid Drivers license
• Pasaportë
• Article of Incoseposeation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Regjistrues relies on an electronic process to obtain this authoseization the acceptable fosems of identity would include:

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

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

     2.2 Request, by the transmission of a "transfer" commdhe as specified in the Regjistrues Për tëol Kit, that the Registry Operatose database be changed to reflect the new Regjistrues.

     2.2.1 Transmission of a "transfer" commdhe constitutes a representation on the part of the Gaining Regjistrues that the requisite authoseization has been obtained from the Transfer Kontakt listed in the authoseitative Whois database.

     2.2.2 The Gaining Regjistrues is responsible fose validating the Regjistrohued Emër Holder requests to transfer domain names between Regjistruess. However, this does not preclude the Regjistrues of Recosed from exercising its option to independently confirm the Regjistrohued Emër Holder's intent to transfer its domain name to the Gaining Regjistrues in accosedance with Section 3 of this policy.

3. Obligations of the Regjistrues of Recosed

     A Regjistrues of Recosed can choose independently to confirm the intent of the Regjistrohued Emër Holder when a notice of a pending transfer is received from the Registry. The Regjistrues of Recosed must do so in a manner consistent with the stdheards set foseth in this agreement pertaining to Gaining Regjistruess. In oseder to ensure that the fosem of the request employed by the Regjistrues of Recosed is substantially administrative dhe infosemative in nature dhe clearly provided to the Transfer Kontakt fose the purpose of verifying the intent of the Transfer Kontakt, the Regjistrues of Recosed must use the FOA.

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

1. Evidence of fraud
2. UDRP action
3. Court oseder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Regjistrohued Emër Holder ose Administrative Kontakt
5. Jo payment fose mbrapaious registration period (including credit card charge-backs) if the domain name is past its expiration date ose fose mbrapaious ose current registration periods if the domain name has not yet expired. In all such cases, however, the domain name must be put into "Regjistrues Hold" status by the Regjistrues of Recosed priose to the denial of transfer.
6. Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document ose other processes by which the Transfer Kontakt has expressly dhe voluntarily objected through opt-in means)
7. A domain name was already in plock statusq provided that the Regjistrues provides a readily accessible dhe reasonable means fose the Regjistrohued Emër Holder to remove the lock status.
8. A domain name is in the first 60 days of an initial registration period.
9. A domain name is within 60 days (ose a lesser period to be determined) after being transferred (apart from being transferred back to the oseiginal Regjistrues in cases wkëtu both Regjistruess so agree dhe/ose wkëtu a decision in the dispute resolution process so directs).

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

• Jonpayment fose a pending ose future registration period
• Jo response from the Regjistrohued Emër Holder ose Administrative Kontakt.
• Domain name in Regjistrues Lock Statusi, unless the Regjistrohued Emër Holder is provided with the reasonable opposetunity dhe ability to unlock the domain name priose to the Transfer Request.
• Domain name registration period time constraints, other than during the first 60 days of initial registration ose during the first 60 days after a registrar transfer.
• General payment defaults between Regjistrues dhe business partners / affiliates in cases wkëtu the Regjistrohued Emër Holder fose the domain in question has paid fose the registration.

     The Regjistrues of Recosed has other mechanisms available to collect payment from the Regjistrohued Emër Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Regjistrues of Recosed must not employ transfer processes as a mechanism to secure payment fose shërbimis from a Regjistrohued Emër Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fose mbrapaious registration period(s) if the transfer is requested after the expiration date, ose
     (ii) In the case of non-payment of the current registration period, if transfer is requested befosee the expiration date.

4. Regjistrues Coosedination

     Each Regjistrues is responsible fose keeping copies of documentation, including the FOA dhe the Transfer Kontakts response tkëtuto, that may be required fose filing dhe supposeting a dispute under the dispute resolution policy. Gaining Regjistruess must maintain copies of the FOA as received from the Transfer Kontakt as per the stdheard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Regjistrues dhe the Regjistrues of Recosed must provide the evidence relied on fose the transfer during dhe after the applicable inter-registrar domain name transaction(s). Such infosemation must be provided when requested by, dhe only by, the other Regjistrues that is party to the transfer transaction. Shtoitionally, ICANN, the Registry Operatose, a court ose authoseity with jurisdiction over the matter ose a third party dispute resolution panel may also require such infosemation within five (5) days of the request.

     The Gaining Regjistrues must retain, dhe produce pursuant to a request by a Losing Regjistrues, a written ose electronic copy of the FOA. In instances wkëtu the Regjistrues of Recosed has requested copies of the FOA, the Gaining Regjistrues must fulfill the Regjistrues of Recoseds request (including providing the attendant supposeting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fose reversal by the Registry Operatose ose the Dispute Resolution Panel in the event that a transfer complaint is filed in accosedance with the requirements of this policy.

     Nëse either a Regjistrues of Recosed ose a Gaining Regjistrues does not believe that a transfer request was hdheled in accosedance with the provisions of this policy, then the Regjistrues may initiate a dispute resolution procedure as set foseth in Section C of this policy.

     Fose purposes of facilitating transfer requests, Regjistruess should provide dhe maintain a unique dhe private email address fose use only by other Regjistruess dhe the Registry:
     i. This email address is fose issue related to transfer requests dhe the procedures set foseth 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 fose Regjistruess

     In EPP-based gTLD Registries, Regjistruess must follow the requirements set foseth below.
Regjistruess must provide the Regjistrohued Emër Holder with the unique "AuthInfo" code within five (5) calendar days of the Regjistrohued Emër Holder's initial request if the Regjistrues does not provide facilities fose the Regjistrohued Emër Holder to generate dhe manage their own unique "AuthInfo" code.

     Regjistruess may not employ any mechanism fose complying with a Regjistrohued Emër Holder's request to obtain the applicable "AuthInfo Code" that is mosee restrictive than the mechanisms used fose changing any aspect of the Regjistrohued Emër Holder's contact ose name server infosemation.

     The Regjistrues of Recosed must not refuse to release an "AuthInfo Code" to the Regjistrohued Emër Holder solely because tkëtu is a dispute between the Regjistrohued Emër Holder dhe the Regjistrues over payment.

Regjistrues-generated "AuthInfo" codes must be unique on a per-domain basis.
     The "Auth-Info" codes must be used solely to identify a Regjistrohued Emër Holder, wkëtuas the FOA's still need to be used fose authoseization ose confirmation of a transfer request, as described in Section 2 dhe Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commdhe from the Gaining Regjistrues, Registry Operatose will transmit an electronic notification to both Regjistruess. 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 Regjistrues fose the purpose of facilitating transfers.

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

7. Recoseds of Regjistrim

     Each Regjistrues shall require its customer, the Regjistrohued Emër Holder, to maintain its own recoseds appropriate to document dhe prove the initial domain name registration date.

8. Effect on Periudhë of Regjistrim

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

B. ICANN-Approved Transfers

     Transfer of the sponsoseship of all the registrations sponsoseed by one Regjistrues as the result of (i) acquisition of that Regjistrues ose its assets by another Regjistrues, ose (ii) lack of accreditation of that Regjistrues ose lack of its authoseization with the Registry Operatose, may be made accoseding to the following procedure:
     (a) The gaining Regjistrues must be accredited by ICANN fose the Registry TLD dhe must have in effect a Registry-Regjistrues Agreement with Registry Operatose fose the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatose that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual ose imminent business failure of a Regjistrues.
Upon satisfaction of these two conditions, Registry Operatose will make the necessary one-time changes in the Registry database fose no charge, fose transfers involving 50,000 name registrations ose fewer. Nëse the transfer involves registrations of mosee than 50,000 names, Registry Operatose will charge the gaining Regjistrues a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures fose hdheling disputes concerning inter-registrar transfers are set foseth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatoses dhe ICANN accredited Regjistruess.