A. Holder-Authнемесеized Transfers

1. Тіркеуші Requirements

     Тіркелуed Аты Holders must be able to transfer their домен name registrations between Тіркеушіs provided that the Gaining Тіркеуші's transfer process meets the minimum stжәнеards of this policy және that such transfer is not prohiбитed by ICANN немесе Registry policies. Inter-Тіркеуші домен name transfer processes must be clear және concise in немесеder to avoid confusion. Further, Тіркеушіs should make reasonable effнемесеts to infнемесеm Тіркелуed Аты Holders of, және provide access to, the published documentation of the specific transfer process employed by the Тіркеушіs.

1.1 Transfer Authнемесеities

     The Administrative Байланыс және the Тіркелуed Аты Holder, as listed in the Losing Тіркеуші's немесе applicable Registry's (wмұнда available) publicly accessible WHOIS қызмет are the only parties that have the authнемесеity to approve немесе deny a transfer request to the Gaining Тіркеуші. In the event of a dispute, the Тіркелуed Аты Holder's authнемесеity supersedes that of the Administrative Байланыс.
Тіркеушіs may use Whois data from either the Тіркеуші of Recнемесеd немесе the relevant Registry fнемесе the purpose of verifying the authenticity of a transfer request; немесе from another data source as determined by a consensus policy.

2. Gaining Тіркеуші Requirements

Fнемесе each instance wмұнда a Тіркелуed Аты Holder requests to transfer a домен name registration to a different Тіркеуші, the Gaining Тіркеуші shall:
      2.1 Obtain express authнемесеization from either the Тіркелуed Аты Holder немесе the Administrative Байланыс (мұндаafter, "Transfer Байланыс"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Тіркеуші from the Transfer Байланыс.

     2.1.1 The authнемесеization must be made via a valid Stжәнеardized Fнемесеm of Authнемесеization (FOA). Tмұнда are two different FOA's available at the ICANN website. The FOA labeled "Initial Authнемесеization fнемесе Тіркеуші Transfer" must be used by the Gaining Тіркеуші to request an authнемесеization fнемесе a registrar transfer from the Transfer Байланыс. The FOA labeled "Растауation of Тіркеуші Transfer Request" may be used by the Тіркеуші of Recнемесеd to request confirmation of the transfer from the Transfer Байланыс.
The FOA shall be communicated in English, және any dispute arising out of a transfer request shall be conducted in the English language. Тіркеушіs may choose to communicate with the Transfer Байланыс in additional languages. However, Тіркеушіs choosing to exercise such option are responsible fнемесе the accuracy және completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Тіркеуші relies on a physical process to obtain this authнемесеization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Байланыс және further that it is accompanied by a physical copy of the Тіркеуші of Recнемесеd's Whois output fнемесе the домен name in question.

     2.1.2.1 Егер the Gaining Тіркеуші relies on a physical authнемесеization process, then the Gaining Тіркеуші assumes the burden of obtaining reliable evidence of the identity of the Transfer Байланыс және maintaining appropriate recнемесеds proving that such evidence was obtained. Further the Gaining Тіркеуші also assumes the burden fнемесе ensuring that the entity making the request is indeed authнемесеized to do so. The acceptable fнемесеms of physical identity are:

• Жоқtarized statement
• Valid Drivers license
• Паспорт
• Article of Incнемесеpнемесеation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Тіркеуші relies on an electronic process to obtain this authнемесеization the acceptable fнемесеms of identity would include:

• Electronic signature in confнемесеmance with national legislation, in the location of the Gaining Тіркеуші (if such legislation exists).
• Consent from an individual немесе entity that has an email address matching the Transfer Байланыс email address. 

     The Тіркеуші of Recнемесеd may not deny a transfer request solely because it believes that the Gaining Тіркеуші has not received the confirmation set fнемесеth above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Тіркеуші. The presumption in all cases will be that the Gaining Тіркеуші has received және authenticated the transfer request made by a Transfer Байланыс.

     2.2 Request, by the transmission of a "transfer" commжәне as specified in the Тіркеуші Сатып алу үшінol Kit, that the Registry Operatнемесе database be changed to reflect the new Тіркеуші.

     2.2.1 Transmission of a "transfer" commжәне constitutes a representation on the part of the Gaining Тіркеуші that the requisite authнемесеization has been obtained from the Transfer Байланыс listed in the authнемесеitative Whois database.

     2.2.2 The Gaining Тіркеуші is responsible fнемесе validating the Тіркелуed Аты Holder requests to transfer домен names between Тіркеушіs. However, this does not preclude the Тіркеуші of Recнемесеd from exercising its option to independently confirm the Тіркелуed Аты Holder's intent to transfer its домен name to the Gaining Тіркеуші in accнемесеdance with Section 3 of this policy.

3. Obligations of the Тіркеуші of Recнемесеd

     A Тіркеуші of Recнемесеd can choose independently to confirm the intent of the Тіркелуed Аты Holder when a notice of a pending transfer is received from the Registry. The Тіркеуші of Recнемесеd must do so in a manner consistent with the stжәнеards set fнемесеth in this agreement pertaining to Gaining Тіркеушіs. In немесеder to ensure that the fнемесеm of the request employed by the Тіркеуші of Recнемесеd is substantially administrative және infнемесеmative in nature және clearly provided to the Transfer Байланыс fнемесе the purpose of verifying the intent of the Transfer Байланыс, the Тіркеуші of Recнемесеd must use the FOA.

     The FOA shall be communicated in English, және any dispute arising out of a transfer request, shall be conducted in the English language. Тіркеушіs may choose to communicate with the Transfer Байланыс in additional languages. However, the Тіркеуші choosing to exercise such option is responsible fнемесе the accuracy және completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes және procedures set fнемесеth in this policy. This includes but is not limited to the requirement that no Тіркеуші shall add any additional infнемесеmation to the FOA used to obtain the consent of the Transfer Байланыс in the case of a transfer request.
This requirement does not preclude the Тіркеуші of Recнемесеd from marketing to its existing customers through separate communications.
The FOA should be sent by the Тіркеуші of Recнемесеd to the Transfer Байланыс as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operatнемесе.Failure by the Тіркеуші of Recнемесеd 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 Байланыс listed in the Whois has not confirmed their request to transfer with the Тіркеуші of Recнемесеd және the Тіркеуші of Recнемесеd has not explicitly denied the transfer request, the default action will be that the Тіркеуші of Recнемесеd must allow the transfer to proceed.
Upon denying a transfer request fнемесе any of the following reasons, the Тіркеуші of Recнемесеd must provide the Тіркелуed Аты Holder және the potential Gaining Тіркеуші with the reason fнемесе denial. The Тіркеуші of Recнемесеd may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court немесеder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Тіркелуed Аты Holder немесе Administrative Байланыс
5. Жоқ payment fнемесе артқаious registration period (including credit card charge-backs) if the домен name is past its expiration date немесе fнемесе артқаious немесе current registration periods if the домен name has not yet expired. In all such cases, however, the домен name must be put into "Тіркеуші Hold" status by the Тіркеуші of Recнемесеd priнемесе to the denial of transfer.
6. Express written objection to the transfer from the Transfer Байланыс. (e.g. - email, fax, paper document немесе other processes by which the Transfer Байланыс has expressly және voluntarily objected through opt-in means)
7. A домен name was already in plock statusq provided that the Тіркеуші provides a readily accessible және reasonable means fнемесе the Тіркелуed Аты Holder to remove the lock status.
8. A домен name is in the first 60 days of an initial registration period.
9. A домен name is within 60 days (немесе a lesser period to be determined) after being transferred (apart from being transferred back to the немесеiginal Тіркеуші in cases wмұнда both Тіркеушіs so agree және/немесе wмұнда a decision in the dispute resolution process so directs).

Instances when the requested change of Тіркеуші may not be denied include, but are not limited to:

• Жоқnpayment fнемесе a pending немесе future registration period
• Жоқ response from the Тіркелуed Аты Holder немесе Administrative Байланыс.
• Домен name in Тіркеуші Lock Мәртебе, unless the Тіркелуed Аты Holder is provided with the reasonable oppнемесеtunity және ability to unlock the домен name priнемесе to the Transfer Request.
• Домен name registration period time constraints, other than during the first 60 days of initial registration немесе during the first 60 days after a registrar transfer.
• General payment defaults between Тіркеуші және business partners / affiliates in cases wмұнда the Тіркелуed Аты Holder fнемесе the домен in question has paid fнемесе the registration.

     The Тіркеуші of Recнемесеd has other mechanisms available to collect payment from the Тіркелуed Аты Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Тіркеуші of Recнемесеd must not employ transfer processes as a mechanism to secure payment fнемесе қызметs from a Тіркелуed Аты Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fнемесе артқаious registration period(s) if the transfer is requested after the expiration date, немесе
     (ii) In the case of non-payment of the current registration period, if transfer is requested befнемесеe the expiration date.

4. Тіркеуші Coнемесеdination

     Each Тіркеуші is responsible fнемесе keeping copies of documentation, including the FOA және the Transfer Байланысs response tмұндаto, that may be required fнемесе filing және suppнемесеting a dispute under the dispute resolution policy. Gaining Тіркеушіs must maintain copies of the FOA as received from the Transfer Байланыс as per the stжәнеard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Тіркеуші және the Тіркеуші of Recнемесеd must provide the evidence relied on fнемесе the transfer during және after the applicable inter-registrar домен name transaction(s). Such infнемесеmation must be provided when requested by, және only by, the other Тіркеуші that is party to the transfer transaction. Қосуitionally, ICANN, the Registry Operatнемесе, a court немесе authнемесеity with jurisdiction over the matter немесе a third party dispute resolution panel may also require such infнемесеmation within five (5) days of the request.

     The Gaining Тіркеуші must retain, және produce pursuant to a request by a Losing Тіркеуші, a written немесе electronic copy of the FOA. In instances wмұнда the Тіркеуші of Recнемесеd has requested copies of the FOA, the Gaining Тіркеуші must fulfill the Тіркеуші of Recнемесеds request (including providing the attendant suppнемесеting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fнемесе reversal by the Registry Operatнемесе немесе the Dispute Resolution Panel in the event that a transfer complaint is filed in accнемесеdance with the requirements of this policy.

     Егер either a Тіркеуші of Recнемесеd немесе a Gaining Тіркеуші does not believe that a transfer request was hжәнеled in accнемесеdance with the provisions of this policy, then the Тіркеуші may initiate a dispute resolution procedure as set fнемесеth in Section C of this policy.

     Fнемесе purposes of facilitating transfer requests, Тіркеушіs should provide және maintain a unique және private email address fнемесе use only by other Тіркеушіs және the Registry:
     i. This email address is fнемесе issue related to transfer requests және the procedures set fнемесеth 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 fнемесе Тіркеушіs

     In EPP-based gTLD Registries, Тіркеушіs must follow the requirements set fнемесеth below.
Тіркеушіs must provide the Тіркелуed Аты Holder with the unique "AuthInfo" code within five (5) calendar days of the Тіркелуed Аты Holder's initial request if the Тіркеуші does not provide facilities fнемесе the Тіркелуed Аты Holder to generate және manage their own unique "AuthInfo" code.

     Тіркеушіs may not employ any mechanism fнемесе complying with a Тіркелуed Аты Holder's request to obtain the applicable "AuthInfo Code" that is mнемесеe restrictive than the mechanisms used fнемесе changing any aspect of the Тіркелуed Аты Holder's contact немесе name server infнемесеmation.

     The Тіркеуші of Recнемесеd must not refuse to release an "AuthInfo Code" to the Тіркелуed Аты Holder solely because tмұнда is a dispute between the Тіркелуed Аты Holder және the Тіркеуші over payment.

Тіркеуші-generated "AuthInfo" codes must be unique on a per-домен basis.
     The "Auth-Info" codes must be used solely to identify a Тіркелуed Аты Holder, wмұндаas the FOA's still need to be used fнемесе authнемесеization немесе confirmation of a transfer request, as described in Section 2 және Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commжәне from the Gaining Тіркеуші, Registry Operatнемесе will transmit an electronic notification to both Тіркеушіs. 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 Тіркеуші fнемесе the purpose of facilitating transfers.

     The Registry Operatнемесе shall complete the requested transfer unless, within five (5) calendar days, Registry Operatнемесе receives a NACK protocol commжәне from the Тіркеуші of Recнемесеd.
When the Registry's database has been updated to reflect the change to the Gaining Тіркеуші, Registry Operatнемесе will transmit an electronic notification to both Тіркеушіs. The notification may be sent to       the unique email address established by each Тіркеуші fнемесе the purpose of facilitating transfers немесе such other email address agreed to by the parties.
The Registry Operatнемесе shall undo a transfer if, after a transfer has occurred, the Registry Operatнемесе receives one of the notices as set fнемесеth below. In such case, the transfer will be reversed және the домен name reset to its немесеiginal state. The Registry Operatнемесе 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 Operatнемесе 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 Тіркеуші of Recнемесеd және the Gaining Тіркеуші sent by email, letter немесе fax that the transfer was made by mistake немесе was otherwise not in accнемесеdance with the procedures set fнемесеth in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; немесе
     iii. Order of a court having jurisdiction over the transfer.

7. Recнемесеds of Тіркеу

     Each Тіркеуші shall require its customer, the Тіркелуed Аты Holder, to maintain its own recнемесеds appropriate to document және prove the initial домен name registration date.

8. Effect on Мерзім of Тіркеу

     The completion by Registry Operatнемесе of a holder-authнемесеized transfer under this Part A shall result in a one-жыл extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) жылдар.

B. ICANN-Approved Transfers

     Transfer of the sponsнемесеship of all the registrations sponsнемесеed by one Тіркеуші as the result of (i) acquisition of that Тіркеуші немесе its assets by another Тіркеуші, немесе (ii) lack of accreditation of that Тіркеуші немесе lack of its authнемесеization with the Registry Operatнемесе, may be made accнемесеding to the following procedure:
     (a) The gaining Тіркеуші must be accredited by ICANN fнемесе the Registry TLD және must have in effect a Registry-Тіркеуші Agreement with Registry Operatнемесе fнемесе the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatнемесе that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual немесе imminent business failure of a Тіркеуші.
Upon satisfaction of these two conditions, Registry Operatнемесе will make the necessary one-time changes in the Registry database fнемесе no charge, fнемесе transfers involving 50,000 name registrations немесе fewer. Егер the transfer involves registrations of mнемесеe than 50,000 names, Registry Operatнемесе will charge the gaining Тіркеуші a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures fнемесе hжәнеling disputes concerning inter-registrar transfers are set fнемесеth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatнемесеs және ICANN accredited Тіркеушіs.