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 Вайс. 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 Вайс. 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 Вайс. 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 Вайс. 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.