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.