A. Holder-Authellerized Transfers

1. Registrar Requirements

     Registrered Navn Holders must be able to transfer their domenet name registrations between Registrars provided that the Gaining Registrar's transfer process meets the minimum stogards of this policy og that such transfer is not prohibited by ICANN eller Registry policies. Inter-Registrar domenet name transfer processes must be clear og concise in ellerder to avoid confusion. Further, Registrars should make reasonable effellerts to infellerm Registrered Navn Holders of, og provide access to, the published documentation of the specific transfer process employed by the Registrars.

1.1 Transfer Authellerities

     The Administrative Kontakt og the Registrered Navn Holder, as listed in the Losing Registrar's eller applicable Registry's (wher available) publicly accessible WHOIS tjeneste are the only parties that have the authellerity to approve eller deny a transfer request to the Gaining Registrar. In the event of a dispute, the Registrered Navn Holder's authellerity supersedes that of the Administrative Kontakt.
Registrars may use Whois data from either the Registrar of Recellerd eller the relevant Registry feller the purpose of verifying the authenticity of a transfer request; eller from another data source as determined by a consensus policy.

2. Gaining Registrar Requirements

Feller each instance wher a Registrered Navn Holder requests to transfer a domenet name registration to a different Registrar, the Gaining Registrar shall:
      2.1 Obtain express authellerization from either the Registrered Navn Holder eller the Administrative Kontakt (herafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrar from the Transfer Kontakt.

     2.1.1 The authellerization must be made via a valid Stogardized Fellerm of Authellerization (FOA). Ther are two different FOA's available at the ICANN website. The FOA labeled "Initial Authellerization feller Registrar Transfer" must be used by the Gaining Registrar to request an authellerization feller a registrar transfer from the Transfer Kontakt. The FOA labeled "Bekreftation of Registrar Transfer Request" may be used by the Registrar of Recellerd to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, og any dispute arising out of a transfer request shall be conducted in the English language. Registrars may choose to communicate with the Transfer Kontakt in additional languages. However, Registrars choosing to exercise such option are responsible feller the accuracy og completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Registrar relies on a physical process to obtain this authellerization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontakt og further that it is accompanied by a physical copy of the Registrar of Recellerd's Whois output feller the domenet name in question.

     2.1.2.1 Hvis the Gaining Registrar relies on a physical authellerization process, then the Gaining Registrar assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt og maintaining appropriate recellerds proving that such evidence was obtained. Further the Gaining Registrar also assumes the burden feller ensuring that the entity making the request is indeed authellerized to do so. The acceptable fellerms of physical identity are:

• Neitarized statement
• Valid Drivers license
• Passaport
• Article of Incellerpelleration
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Registrar relies on an electronic process to obtain this authellerization the acceptable fellerms of identity would include:

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

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

     2.2 Request, by the transmission of a "transfer" commog as specified in the Registrar Tilol Kit, that the Registry Operateller database be changed to reflect the new Registrar.

     2.2.1 Transmission of a "transfer" commog constitutes a representation on the part of the Gaining Registrar that the requisite authellerization has been obtained from the Transfer Kontakt listed in the authelleritative Whois database.

     2.2.2 The Gaining Registrar is responsible feller validating the Registrered Navn Holder requests to transfer domenet names between Registrars. However, this does not preclude the Registrar of Recellerd from exercising its option to independently confirm the Registrered Navn Holder's intent to transfer its domenet name to the Gaining Registrar in accellerdance with Section 3 of this policy.

3. Obligations of the Registrar of Recellerd

     A Registrar of Recellerd can choose independently to confirm the intent of the Registrered Navn Holder when a notice of a pending transfer is received from the Registry. The Registrar of Recellerd must do so in a manner consistent with the stogards set fellerth in this agreement pertaining to Gaining Registrars. In ellerder to ensure that the fellerm of the request employed by the Registrar of Recellerd is substantially administrative og infellermative in nature og clearly provided to the Transfer Kontakt feller the purpose of verifying the intent of the Transfer Kontakt, the Registrar of Recellerd must use the FOA.

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

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

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

• Neinpayment feller a pending eller future registration period
• Nei response from the Registrered Navn Holder eller Administrative Kontakt.
• Domene name in Registrar Lock Status, unless the Registrered Navn Holder is provided with the reasonable oppellertunity og ability to unlock the domenet name prieller to the Transfer Request.
• Domene name registration period time constraints, other than during the first 60 days of initial registration eller during the first 60 days after a registrar transfer.
• General payment defaults between Registrar og business partners / affiliates in cases wher the Registrered Navn Holder feller the domenet in question has paid feller the registration.

     The Registrar of Recellerd has other mechanisms available to collect payment from the Registrered Navn Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrar of Recellerd must not employ transfer processes as a mechanism to secure payment feller tjenestes from a Registrered Navn Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment feller forrigeious registration period(s) if the transfer is requested after the expiration date, eller
     (ii) In the case of non-payment of the current registration period, if transfer is requested befellere the expiration date.

4. Registrar Coellerdination

     Each Registrar is responsible feller keeping copies of documentation, including the FOA og the Transfer Kontakts response therto, that may be required feller filing og suppellerting a dispute under the dispute resolution policy. Gaining Registrars must maintain copies of the FOA as received from the Transfer Kontakt as per the stogard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registrar og the Registrar of Recellerd must provide the evidence relied on feller the transfer during og after the applicable inter-registrar domenet name transaction(s). Such infellermation must be provided when requested by, og only by, the other Registrar that is party to the transfer transaction. Legg tilitionally, ICANN, the Registry Operateller, a court eller authellerity with jurisdiction over the matter eller a third party dispute resolution panel may also require such infellermation within five (5) days of the request.

     The Gaining Registrar must retain, og produce pursuant to a request by a Losing Registrar, a written eller electronic copy of the FOA. In instances wher the Registrar of Recellerd has requested copies of the FOA, the Gaining Registrar must fulfill the Registrar of Recellerds request (including providing the attendant suppellerting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds feller reversal by the Registry Operateller eller the Dispute Resolution Panel in the event that a transfer complaint is filed in accellerdance with the requirements of this policy.

     Hvis either a Registrar of Recellerd eller a Gaining Registrar does not believe that a transfer request was hogled in accellerdance with the provisions of this policy, then the Registrar may initiate a dispute resolution procedure as set fellerth in Section C of this policy.

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

     In EPP-based gTLD Registries, Registrars must follow the requirements set fellerth below.
Registrars must provide the Registrered Navn Holder with the unique "AuthInfo" code within five (5) calendar days of the Registrered Navn Holder's initial request if the Registrar does not provide facilities feller the Registrered Navn Holder to generate og manage their own unique "AuthInfo" code.

     Registrars may not employ any mechanism feller complying with a Registrered Navn Holder's request to obtain the applicable "AuthInfo Code" that is mellere restrictive than the mechanisms used feller changing any aspect of the Registrered Navn Holder's contact eller name server infellermation.

     The Registrar of Recellerd must not refuse to release an "AuthInfo Code" to the Registrered Navn Holder solely because ther is a dispute between the Registrered Navn Holder og the Registrar over payment.

Registrar-generated "AuthInfo" codes must be unique on a per-domenet basis.
     The "Auth-Info" codes must be used solely to identify a Registrered Navn Holder, wheras the FOA's still need to be used feller authellerization eller confirmation of a transfer request, as described in Section 2 og Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commog from the Gaining Registrar, Registry Operateller will transmit an electronic notification to both Registrars. 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 Registrar feller the purpose of facilitating transfers.

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

7. Recellerds of Registrering

     Each Registrar shall require its customer, the Registrered Navn Holder, to maintain its own recellerds appropriate to document og prove the initial domenet name registration date.

8. Effect on Periode of Registrering

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

B. ICANN-Approved Transfers

     Transfer of the sponsellership of all the registrations sponsellered by one Registrar as the result of (i) acquisition of that Registrar eller its assets by another Registrar, eller (ii) lack of accreditation of that Registrar eller lack of its authellerization with the Registry Operateller, may be made accellerding to the following procedure:
     (a) The gaining Registrar must be accredited by ICANN feller the Registry TLD og must have in effect a Registry-Registrar Agreement with Registry Operateller feller the Registry TLD.
     (b) ICANN must certify in writing to Registry Operateller that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual eller imminent business failure of a Registrar.
Upon satisfaction of these two conditions, Registry Operateller will make the necessary one-time changes in the Registry database feller no charge, feller transfers involving 50,000 name registrations eller fewer. Hvis the transfer involves registrations of mellere than 50,000 names, Registry Operateller will charge the gaining Registrar a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures feller hogling disputes concerning inter-registrar transfers are set fellerth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatellers og ICANN accredited Registrars.