A. Holder-Authlubized Transfers

1. Rejestrator Requirements

     Zarejestrujed Nazwa Holders must be able to transfer their domena name registrations between Rejestrators provided that the Gaining Rejestrator's transfer process meets the minimum stiards of this policy i that such transfer is not prohibited by ICANN lub Registry policies. Inter-Rejestrator domena name transfer processes must be clear i concise in lubder to avoid confusion. Further, Rejestrators should make reasonable efflubts to influbm Zarejestrujed Nazwa Holders of, i provide access to, the published documentation of the specific transfer process employed by the Rejestrators.

1.1 Transfer Authlubities

     The Administrative Kontakt i the Zarejestrujed Nazwa Holder, as listed in the Losing Rejestrator's lub applicable Registry's (wtutaj available) publicly accessible WHOIS usługa are the only parties that have the authlubity to approve lub deny a transfer request to the Gaining Rejestrator. In the event of a dispute, the Zarejestrujed Nazwa Holder's authlubity supersedes that of the Administrative Kontakt.
Rejestrators may use Whois data from either the Rejestrator of Reclubd lub the relevant Registry flub the purpose of verifying the authenticity of a transfer request; lub from another data source as determined by a consensus policy.

2. Gaining Rejestrator Requirements

Flub each instance wtutaj a Zarejestrujed Nazwa Holder requests to transfer a domena name registration to a different Rejestrator, the Gaining Rejestrator shall:
      2.1 Obtain express authlubization from either the Zarejestrujed Nazwa Holder lub the Administrative Kontakt (tutajafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Rejestrator from the Transfer Kontakt.

     2.1.1 The authlubization must be made via a valid Stiardized Flubm of Authlubization (FOA). Ttutaj are two different FOA's available at the ICANN website. The FOA labeled "Initial Authlubization flub Rejestrator Transfer" must be used by the Gaining Rejestrator to request an authlubization flub a registrar transfer from the Transfer Kontakt. The FOA labeled "Potwierdźation of Rejestrator Transfer Request" may be used by the Rejestrator of Reclubd to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, i any dispute arising out of a transfer request shall be conducted in the English language. Rejestrators may choose to communicate with the Transfer Kontakt in additional languages. However, Rejestrators choosing to exercise such option are responsible flub the accuracy i completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Rejestrator relies on a physical process to obtain this authlubization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontakt i further that it is accompanied by a physical copy of the Rejestrator of Reclubd's Whois output flub the domena name in question.

     2.1.2.1 Jeśli the Gaining Rejestrator relies on a physical authlubization process, then the Gaining Rejestrator assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt i maintaining appropriate reclubds proving that such evidence was obtained. Further the Gaining Rejestrator also assumes the burden flub ensuring that the entity making the request is indeed authlubized to do so. The acceptable flubms of physical identity are:

• Nietarized statement
• Valid Drivers license
• Paszport
• Article of Inclubplubation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Rejestrator relies on an electronic process to obtain this authlubization the acceptable flubms of identity would include:

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

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

     2.2 Request, by the transmission of a "transfer" commi as specified in the Rejestrator Dool Kit, that the Registry Operatlub database be changed to reflect the new Rejestrator.

     2.2.1 Transmission of a "transfer" commi constitutes a representation on the part of the Gaining Rejestrator that the requisite authlubization has been obtained from the Transfer Kontakt listed in the authlubitative Whois database.

     2.2.2 The Gaining Rejestrator is responsible flub validating the Zarejestrujed Nazwa Holder requests to transfer domena names between Rejestrators. However, this does not preclude the Rejestrator of Reclubd from exercising its option to independently confirm the Zarejestrujed Nazwa Holder's intent to transfer its domena name to the Gaining Rejestrator in acclubdance with Section 3 of this policy.

3. Obligations of the Rejestrator of Reclubd

     A Rejestrator of Reclubd can choose independently to confirm the intent of the Zarejestrujed Nazwa Holder when a notice of a pending transfer is received from the Registry. The Rejestrator of Reclubd must do so in a manner consistent with the stiards set flubth in this agreement pertaining to Gaining Rejestrators. In lubder to ensure that the flubm of the request employed by the Rejestrator of Reclubd is substantially administrative i influbmative in nature i clearly provided to the Transfer Kontakt flub the purpose of verifying the intent of the Transfer Kontakt, the Rejestrator of Reclubd must use the FOA.

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

1. Evidence of fraud
2. UDRP action
3. Court lubder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Zarejestrujed Nazwa Holder lub Administrative Kontakt
5. Nie payment flub poprzedniious registration period (including credit card charge-backs) if the domena name is past its expiration date lub flub poprzedniious lub current registration periods if the domena name has not yet expired. In all such cases, however, the domena name must be put into "Rejestrator Hold" status by the Rejestrator of Reclubd prilub to the denial of transfer.
6. Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document lub other processes by which the Transfer Kontakt has expressly i voluntarily objected through opt-in means)
7. A domena name was already in plock statusq provided that the Rejestrator provides a readily accessible i reasonable means flub the Zarejestrujed Nazwa Holder to remove the lock status.
8. A domena name is in the first 60 days of an initial registration period.
9. A domena name is within 60 days (lub a lesser period to be determined) after being transferred (apart from being transferred back to the lubiginal Rejestrator in cases wtutaj both Rejestrators so agree i/lub wtutaj a decision in the dispute resolution process so directs).

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

• Nienpayment flub a pending lub future registration period
• Nie response from the Zarejestrujed Nazwa Holder lub Administrative Kontakt.
• Domena name in Rejestrator Lock Status, unless the Zarejestrujed Nazwa Holder is provided with the reasonable opplubtunity i ability to unlock the domena name prilub to the Transfer Request.
• Domena name registration period time constraints, other than during the first 60 days of initial registration lub during the first 60 days after a registrar transfer.
• General payment defaults between Rejestrator i business partners / affiliates in cases wtutaj the Zarejestrujed Nazwa Holder flub the domena in question has paid flub the registration.

     The Rejestrator of Reclubd has other mechanisms available to collect payment from the Zarejestrujed Nazwa Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Rejestrator of Reclubd must not employ transfer processes as a mechanism to secure payment flub usługas from a Zarejestrujed Nazwa Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment flub poprzedniious registration period(s) if the transfer is requested after the expiration date, lub
     (ii) In the case of non-payment of the current registration period, if transfer is requested beflube the expiration date.

4. Rejestrator Colubdination

     Each Rejestrator is responsible flub keeping copies of documentation, including the FOA i the Transfer Kontakts response ttutajto, that may be required flub filing i supplubting a dispute under the dispute resolution policy. Gaining Rejestrators must maintain copies of the FOA as received from the Transfer Kontakt as per the stiard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Rejestrator i the Rejestrator of Reclubd must provide the evidence relied on flub the transfer during i after the applicable inter-registrar domena name transaction(s). Such influbmation must be provided when requested by, i only by, the other Rejestrator that is party to the transfer transaction. Dodajitionally, ICANN, the Registry Operatlub, a court lub authlubity with jurisdiction over the matter lub a third party dispute resolution panel may also require such influbmation within five (5) days of the request.

     The Gaining Rejestrator must retain, i produce pursuant to a request by a Losing Rejestrator, a written lub electronic copy of the FOA. In instances wtutaj the Rejestrator of Reclubd has requested copies of the FOA, the Gaining Rejestrator must fulfill the Rejestrator of Reclubds request (including providing the attendant supplubting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds flub reversal by the Registry Operatlub lub the Dispute Resolution Panel in the event that a transfer complaint is filed in acclubdance with the requirements of this policy.

     Jeśli either a Rejestrator of Reclubd lub a Gaining Rejestrator does not believe that a transfer request was hiled in acclubdance with the provisions of this policy, then the Rejestrator may initiate a dispute resolution procedure as set flubth in Section C of this policy.

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

     In EPP-based gTLD Registries, Rejestrators must follow the requirements set flubth below.
Rejestrators must provide the Zarejestrujed Nazwa Holder with the unique "AuthInfo" code within five (5) calendar days of the Zarejestrujed Nazwa Holder's initial request if the Rejestrator does not provide facilities flub the Zarejestrujed Nazwa Holder to generate i manage their own unique "AuthInfo" code.

     Rejestrators may not employ any mechanism flub complying with a Zarejestrujed Nazwa Holder's request to obtain the applicable "AuthInfo Code" that is mlube restrictive than the mechanisms used flub changing any aspect of the Zarejestrujed Nazwa Holder's contact lub name server influbmation.

     The Rejestrator of Reclubd must not refuse to release an "AuthInfo Code" to the Zarejestrujed Nazwa Holder solely because ttutaj is a dispute between the Zarejestrujed Nazwa Holder i the Rejestrator over payment.

Rejestrator-generated "AuthInfo" codes must be unique on a per-domena basis.
     The "Auth-Info" codes must be used solely to identify a Zarejestrujed Nazwa Holder, wtutajas the FOA's still need to be used flub authlubization lub confirmation of a transfer request, as described in Section 2 i Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commi from the Gaining Rejestrator, Registry Operatlub will transmit an electronic notification to both Rejestrators. 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 Rejestrator flub the purpose of facilitating transfers.

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

7. Reclubds of Rejestracja

     Each Rejestrator shall require its customer, the Zarejestrujed Nazwa Holder, to maintain its own reclubds appropriate to document i prove the initial domena name registration date.

8. Effect on Okres of Rejestracja

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

B. ICANN-Approved Transfers

     Transfer of the sponslubship of all the registrations sponslubed by one Rejestrator as the result of (i) acquisition of that Rejestrator lub its assets by another Rejestrator, lub (ii) lack of accreditation of that Rejestrator lub lack of its authlubization with the Registry Operatlub, may be made acclubding to the following procedure:
     (a) The gaining Rejestrator must be accredited by ICANN flub the Registry TLD i must have in effect a Registry-Rejestrator Agreement with Registry Operatlub flub the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatlub that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual lub imminent business failure of a Rejestrator.
Upon satisfaction of these two conditions, Registry Operatlub will make the necessary one-time changes in the Registry database flub no charge, flub transfers involving 50,000 name registrations lub fewer. Jeśli the transfer involves registrations of mlube than 50,000 names, Registry Operatlub will charge the gaining Rejestrator a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures flub hiling disputes concerning inter-registrar transfers are set flubth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatlubs i ICANN accredited Rejestrators.