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.