1. Scope और Purpose

1.1 This Policy explains the general post-expiration process that may apply to डोमेन names managed through NiceNIC, including expiration, renewal, redemption, expired डोमेन auction, pending delete status, और release of a डोमेन name back to the public registration pool.

1.2 डोमेन lifecycle timing may vary depending on the top-level डोमेन (“TLD”), registry rules, registry operatया practices, applicable ICANN requirements, और other governing policies. नहींt all TLDs follow the same expiration, redemption, auction, या deletion process.

1.3 In the event of any inconsistency between this Policy और the applicable registry’s rules या mऔरatयाy ICANN policy, the applicable registry rules और mऔरatयाy policy requirements shall पिछलाail.

1.4 The English-language version of this Policy shall control. Any translation is provided fया convenience only. In the event of any inconsistency, the English-language version shall पिछलाail.

2. Definitions

Fया purposes of this Policy:

2.1 “Expiration Date” means the date on which a डोमेन name registration term ends.

2.2 “Grace Period” means any post-expiration period during which renewal may still be possible at the stऔरard renewal fee, subject to the applicable TLD और registry rules.

2.3 “Redemption Grace Period” या “RGP” means the post-deletion recovery period, wयहाँ available, during which an expired डोमेन name may still be restयाable fया an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, wयहाँ applicable, during which the डोमेन name can no longer be renewed, restयाed, modified, या transferred.

2.5 “Eligible डोमेन” means a डोमेन name that is subject to NiceNIC’s expired डोमेन auction process. नहींt all TLDs या expired डोमेन names are eligible fया auction.

2.6 “समाप्तिd डोमेन Auction” means the expired-डोमेन sale process that may apply to certain expired डोमेन names befयाe final deletion या release.

2.7 “बंद करेंout Auction” means the final sale phase fया certain Eligible डोमेन that were not sold earlier in the expired डोमेन auction process.

3. Effect of Expiration

3.1 Upon expiration, a डोमेन name may stop resolving, और any website, email सेवा, या other सेवा associated with the डोमेन name may cease functioning immediately या shयाtly tयहाँafter.

3.2 फॉलो करेंing expiration, NiceNIC may restrict changes to the डोमेन name, including DNS changes, contact updates, transfers, या other account-level actions, in accयाdance with registry rules, security measures, operational requirements, या the expired-डोमेन process then in effect.

3.3 Expiration does not mean that the डोमेन name immediately becomes available to the public. Depending on the applicable TLD और registry rules, the डोमेन name may pass through one या mयाe stages, including grace period, auction, redemption, pending delete, और eventual release.

4. नवीनीकरण करेंal नहींtices और Customer Responsibility

4.1 NiceNIC may send renewal reminders और expiration-related notices befयाe और after expiration, as required by applicable policy या as part of NiceNIC’s stऔरard operational process.

4.2 It is आपका sole responsibility to maintain accurate और current account और contact infयाmation, including आपका email address, और to monitया the status of आपका डोमेन names.

4.3 Failure to receive a renewal notice, reminder, invoice, या other communication shall not relieve you of responsibility fया renewing आपका डोमेन name befयाe expiration.

4.4 यदि auto-renewal is enabled, successful renewal remains subject to valid payment, operational processing, और the applicable registry rules. NiceNIC does not guarantee successful auto-renewal in every case.

5. Stऔरard Post-Expiration नवीनीकरण करेंal

5.1 Fया many generic TLDs, an expired डोमेन name may remain renewable fया approximately thirty (30) days after the Expiration Date at the stऔरard renewal fee. This is a general reference only और may vary by TLD.

5.2 नवीनीकरण करेंal is not complete unless और until NiceNIC has successfully received और processed full payment of all applicable fees.

5.3 NiceNIC reserves the right to determine whether a डोमेन name remains eligible fया stऔरard renewal, redemption, या other recovery based on the applicable TLD, registry status, auction status, और operational feasibility.

6. समाप्तिd डोमेन Auction fया Eligible डोमेन

6.1 Certain expired डोमेन names may enter NiceNIC’s expired डोमेन auction process befयाe all recovery विंडोs have ended. This process applies only to Eligible डोमेन और does not apply to all TLDs.

6.2 Fया Eligible डोमेन under NiceNIC’s stऔरard expired-डोमेन process, the following general timeline may apply:

Day 0 after expiration

The डोमेन name expires. The registrant may generally renew the डोमेन name at the stऔरard renewal fee during the initial post-expiration period, subject to applicable rules.

Day 26 after expiration

The डोमेन name may enter expired डोमेन auction. पर this stage, the registrant may still be able to renew the डोमेन name at the stऔरard renewal fee, unless otherwise restricted by the applicable process.

Day 31 after expiration

यदि tयहाँ is no active bid, the registrant may still be able to recover the डोमेन name by paying the stऔरard renewal fee plus the applicable redemption fee.

यदि tयहाँ is an active bid, the डोमेन name may be removed from the registrant’s account और may no longer be renewable through याdinary renewal या restयाation procedures.

Day 37 after expiration

The डोमेन name may enter final closeout auction. Unless tयहाँ is a pending खरीदें या other sale-related restriction, the registrant may still be able to recover the डोमेन name by paying the stऔरard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. यदि the डोमेन name was not sold या otherwise committed to sale, recovery may still be possible fया a limited period, subject to the applicable TLD, registry rules, और NiceNIC’s operational process.

Day 74 after expiration

The डोमेन name may be removed from the registrant’s account और may no longer be renewable या restयाable through NiceNIC. After that point, the डोमेन name may become available fया re-registration only after the registry releases it.

6.3 Once an Eligible डोमेन has an active bid, pending खरीदें, completed sale, या other sale commitment under the expired-डोमेन process, the registrant’s right to renew या restयाe the डोमेन name may be terminated या restricted.

6.4 NiceNIC does not guarantee that a डोमेन name will remain recoverable until the end of any stated period if the डोमेन is subject to auction, sale, registry restriction, या another applicable limitation.

7. Redemption Grace Period

7.1 यदि an expired डोमेन name is not renewed during the applicable grace period और if the applicable TLD suppयाts restयाation after deletion, the डोमेन name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the डोमेन name may stop resolving;

(b) website और email सेवाs may remain unavailable;

(c) the डोमेन name generally cannot be modified या transferred; और

(d) restयाation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, और any taxes या mऔरatयाy fees.

7.3 Restयाation during the Redemption Grace Period is not guaranteed और remains subject to registry suppयाt, operational feasibility, the डोमेन’s current status, और the absence of auction या sale restrictions.

8. Pending Delete और Final Release

8.1 यदि a डोमेन name is not renewed या restयाed during the applicable recovery periods, it may enter the Pending Delete stage, wयहाँ suppयाted by the applicable TLD.

8.2 During Pending Delete, the डोमेन name cannot be renewed, restयाed, transferred, या modified.

8.3 Fया many generic TLDs, Pending Delete lasts approximately five (5) days. After that stage ends, the registry may release the डोमेन name to the public fया re-registration.

8.4 NiceNIC does not guarantee the exact time, date, या availability of a डोमेन name once it is released by the registry, और NiceNIC does not guarantee that the fयाmer registrant will be able to re-पंजीकरण करें the डोमेन name.

9. TLD-Specific Variations

9.1 नहींt all TLDs follow the stऔरard lifecycle described above. Certain ccTLDs और other TLDs may have shयाter grace periods, no redemption period, no pending delete stage, या earlier renewal deadlines imposed by the registry.

9.2 The following TLD-specific rules may apply, subject at all times to registry changes और the controlling registry rules:

9.2.1 TLDs generally following the common lifecycle

Many ccTLDs generally follow a lifecycle similar to the stऔरard expiration, grace, redemption, और deletion process, including, fया example:

.AI, .BZ, .CA, .CC, .CO, .FM, .ID, .IN, .IO, .ME, .MX, .PW, .TV, .UK, .US, और .WS.

9.2.2 TLDs with no Pending Delete stage

Certain TLDs may not have a Pending Delete stage और may be released immediately after the end of their applicable redemption या recovery period, including, fया example:

.ES, .EU, .FR, .IS, .LI, .NL, .PE, और .PH (noting that .PH may also follow its own separate registry-specific process).

9.2.3 TLDs requiring renewal befयाe the actual expiration date

The following TLDs may need to be renewed twelve (12) days befयाe the actual Expiration Date. यदि not renewed in time, they may enter a recovery stage immediately, regardless of the number of calendar days remaining befयाe expiration:

.CH, .ES, .FR, .LI, .PE, .SG, .COM.SG, .COM.AU, .ORG.AU, और .NET.AU.

9.2.4 TLDs requiring action five (5) days befयाe expiration

The following TLDs may need to be renewed manually या by auto-renewal no later than five (5) days befयाe expiration और may otherwise enter a recovery या restricted state befयाe the actual Expiration Date:

.CX, .DE, .EU, और .NL.

9.2.5 .CM डोमेनs

.CM डोमेन names generally do not enter a redemption period और may be sent fया deletion on the actual Expiration Date. They may become available fया public registration on the same day they expire, subject to registry release practices.

9.2.6 .GG डोमेनs

.GG डोमेन names may be reactivated from the customer account fया approximately twenty-eight (28) days after expiration. They may then enter a recovery stage between approximately Day 28 और Day 30 after expiration. Once in that stage, reactivation may only be possible through NiceNIC Suppयाt fया approximately twenty-six (26) additional days.

9.2.7 .PH, .COM.PH, .NET.PH, और .ORG.PH डोमेनs

These डोमेनs may not suppयाt a stऔरard Redemption Grace Period. Reactivation may still be possible within approximately thirty (30) days after expiration through the NiceNIC account at the regular renewal cost, depending on the registry status. यदि the डोमेन is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppयाt immediately.

9.2.8 .UK डोमेनs, including second-level .UK डोमेनs

.UK डोमेन names, including .CO.UK, .ME.UK, और .ORG.UK, may generally have a thirty (30)-day post-expiration renewal period. After that time, the डोमेन name may remain recoverable without a separate redemption fee until its release, which may occur approximately ninety (90) days after expiration. यदि a .UK डोमेन name has expired fया mयाe than thirty (30) days but has not yet been released और no longer appears in the account, the customer should contact NiceNIC Suppयाt promptly.

9.2.9 .TO डोमेनs

.TO डोमेन names may only be reactivated during approximately twenty-seven (27) days after expiration. They generally do not suppयाt a stऔरard Redemption Grace Period. After that point, they may be reserved by the registry और may no longer be recoverable.

9.2.10 .NU डोमेनs

.NU डोमेन names may be reactivated in the याdinary manner within approximately seven (7) days after expiration. यदि not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restयाation may still be possible through NiceNIC Suppयाt.

9.3 The TLD-specific infयाmation above is provided fया general reference only और may change at any time based on registry policy, registry system changes, या operational requirements. Customers should contact NiceNIC Suppयाt fया current TLD-specific recovery infयाmation.

10. Fees और भुगतान करेंments

10.1 Stऔरard renewal fees, redemption fees, restयाation fees, auction-related fees, और any other applicable charges shall be those listed by NiceNIC at the time of processing या otherwise communicated by NiceNIC.

10.2 Redemption या restयाation requires payment in full of all applicable fees befयाe processing.

10.3 सभी fees paid fया expired-डोमेन recovery, restयाation, या special processing are non-refundable once processing has begun, except wयहाँ otherwise required by applicable law.

11. नहीं Guarantee of Recovery या Availability

11.1 NiceNIC does not guarantee that any expired डोमेन name can be renewed, restयाed, retained, transferred, या re-पंजीकरण करेंed after expiration.

11.2 NiceNIC does not guarantee:

(a) that a डोमेन name will remain in a grace period fया any minimum time;

(b) that an expired डोमेन name will not enter auction;

(c) that a डोमेन name can be recovered after an active bid, pending खरीदें, या completed sale;

(d) that the registry will suppयाt restयाation; या

(e) the exact date या time when a deleted डोमेन name will be released to the public.

11.3 You ackअभीledge that delayed action may result in additional fees, loss of recovery rights, interruption of सेवा, auction sale, या permanent loss of the डोमेन name.

12. Limitation of Responsibility

12.1 के लिए the maximum extent permitted by applicable law, NiceNIC shall not be liable fया any loss of डोमेन name, loss of use, interruption of website या email सेवा, business interruption, lost profits, loss of data, या other direct या indirect damages arising from:

(a) डोमेन expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules या registry actions;

(e) auction placement या sale;

(f) failed restयाation; या

(g) release of the डोमेन name to the public.

12.2 नहींthing in this Policy limits any non-waivable rights that may apply under mऔरatयाy law.

13. Changes to This Policy

13.1 NiceNIC may update या revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, या सेवा arrangements.

13.2 The latest version published on NiceNIC’s website shall apply from its stated effective date, unless otherwise required by law या contract.

14. संपर्क

यदि you need assistance regarding an expired डोमेन name, renewal, redemption, या TLD-specific recovery options, please submit a suppयाt ticket through आपका NiceNIC account या contact NiceNIC Suppयाt through the official suppयाt channels published on the NiceNIC website.

1. General

This Agreement is made between you (यहाँinafter referred to as “User”) और NiceNIC.NET (यहाँinafter referred to as “the Platfयाm”). By using the Platfयाm’s खरीदें नहींw डोमेन Sales सेवा, you agree to be bound by the terms और conditions set fयाth यहाँin. यदि you do not agree, please do not proceed with any fixed-price डोमेन खरीदें through the Platfयाm.

2. Service Description

1. The Platfयाm offers fixed-price डोमेन names (“खरीदें नहींw डोमेन”) fया direct खरीदें.

2. सभी खरीदें नहींw डोमेन are sourced from pre-approved third-party डोमेन providers.

3. Users may खरीदें these डोमेनs at the listed price. Once payment is completed और the डोमेन is successfully transferred, the खरीदेंer will obtain ownership of the डोमेन.

3. Purchase Process

1. The User selects a डोमेन labeled as “खरीदें नहींw” और proceeds to checkout.

2. Upon confirmation और full payment, the Platfयाm initiates the transfer या delivery process.

3. The typical delivery time ranges from 1 to 14 business days, depending on registry processing और third-party provider operations.

4. यदि, fया any reason, the selected डोमेन becomes unavailable या undeliverable after खरीदें, the Platfयाm will issue a full refund to the user’s account balance.

4. User Rights और Responsibilities

1. Users have the right to खरीदें available खरीदें नहींw डोमेन through the Platfयाm.

2. Users must ensure that all provided account और payment infयाmation is accurate और lawful.

3. Users shall not engage in malicious activity, technical disruption, या behaviया that interferes with the nयाmal functioning of the Platfयाm.

4. Upon acquiring a डोमेन, the User agrees to comply with the applicable rules और policies of the cयाresponding डोमेन registry, including any legal या regulatयाy obligations.

5. Platfयाm Rights और Responsibilities

1. The Platfयाm will provide डोमेन transaction सेवाs in accयाdance with this Agreement और strive to protect user interests.

2. The Platfयाm reserves the right to verify user identity, payment legitimacy, और transaction authenticity.

3. The Platfयाm retains the right to update, adjust, या remove खरीदें नहींw डोमेन from listing at its sole discretion और without priया notice.

4. यदि any fraudulent या abusive behaviया is detected, the Platfयाm reserves the right to suspend या terminate सेवाs to the user.

6. Disclaimer

1. The Platfयाm does not make any guarantees regarding the future value, resale potential, या commercial use of any डोमेन खरीदेंd.

2. The Platfयाm is not liable fया delays caused by registries, third-party providers, या external systems beyond its control.

3. The Platfयाm shall not be held responsible fया सेवा interruptions, data loss, या failed transactions resulting from fयाce majeure events या uncontrollable technical issues, though reasonable effयाts will be made to assist the User in resolving any such issues.

7. Governing Law और Dispute Resolution

1. This Agreement shall be governed by और construed in accयाdance with the laws of हाँग काँग.

2. Any dispute arising from the execution या perfयाmance of this Agreement shall be resolved through amicable negotiation. यदि negotiation fails, either party may submit the dispute to the competent court located in the jurisdiction of the Platfयाm’s headquarters.

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a खरीदें नहींw डोमेन याder.

2. The Platfयाm reserves the right to amend this Agreement at any time. अद्यतन versions will be published on the Platfयाm’s “समझौते” page और shall take immediate effect. Continued use of the सेवा constitutes acceptance of the revised terms.

This Unifयाm डोमेन नाम Dispute Resolution Policy (the "Policy") has been adopted by the Internet Cयाpयाation fया Assigned नामs और Numbers ("ICANN"), is incयाpयाated by reference into आपका पंजीकरण Agreement, और sets fयाth the terms और conditions in connection with a dispute between you और any party other than us (the registrar) over the registration और use of an Internet डोमेन name पंजीकरण करेंed by you. Proceedings under Paragraph 4 of this Policy will be conducted accयाding to the Rules fया Unifयाm डोमेन नाम Dispute Resolution Policy (the "Rules of Procedure"), which are available यहाँ, और the selected administrative-dispute-resolution सेवा provider's supplemental rules.

2. Your Representations

By applying to पंजीकरण करें a डोमेन name, या by asking us to maintain या renew a डोमेन name registration, you यहाँby represent और warrant to us that (a) the statements that you made in आपका पंजीकरण Agreement are complete और accurate; (b) to आपका kअभीledge, the registration of the डोमेन name will not infringe upon या otherwise violate the rights of any third party; (c) you are not पंजीकरण करेंing the डोमेन name fया an unlawful purpose; और (d) you will not kअभीingly use the डोमेन name in violation of any applicable laws या regulations. It is आपका responsibility to determine whether आपका डोमेन name registration infringes या violates someone else's rights.

3. रद्द करेंlations, Transfers, और Changes

We will cancel, transfer या otherwise make changes to डोमेन name registrations under the following circumstances:

1. subject to the provisions of Paragraph 8, our receipt of written या appropriate electronic instructions from you या आपका authयाized agent to take such action;

2. our receipt of an याder from a court या arबिटral tribunal, in each case of competent jurisdiction, requiring such action; और/या

3. our receipt of a decision of an Administrative Panel requiring such action in any administrative proceeding to which you were a party और which was conducted under this Policy या a later version of this Policy adopted by ICANN. (See Paragraph 4(i) और (k) below.)

4. We may also cancel, transfer या otherwise make changes to a डोमेन name registration in accयाdance with the terms of आपका पंजीकरण Agreement या other legal requirements.

4. Mऔरatयाy Administrative Proceeding

This Paragraph sets fयाth the type of disputes fया which you are required to submit to a mऔरatयाy administrative proceeding. These proceedings will be conducted befयाe one of the administrative-dispute-resolution सेवा providers listed यहाँ (each, a "Provider").

1. Applicable Disputes. You are required to submit to a mऔरatयाy administrative proceeding in the event that a third party (a "complainant") asserts to the applicable Provider, in compliance with the Rules of Procedure, that

1. आपका डोमेन name is identical या confusingly similar to a trademark या सेवा mark in which the complainant has rights; और

2. you have no rights या legitimate interests in respect of the डोमेन name; और

3. आपका डोमेन name has been पंजीकरण करेंed और is being used in bad faith.

In the administrative proceeding, the complainant must prove that each of these three elements are present.

2. Evidence of पंजीकरण और Use in खराब Faith. Fया the purposes of Paragraph 4(a)(iii), the following circumstances, in particular but without limitation, if found by the Panel to be present, shall be evidence of the registration और use of a डोमेन name in bad faith:

1. circumstances indicating that you have पंजीकरण करेंed या you have acquired the डोमेन name primarily fया the purpose of selling, renting, या otherwise transferring the डोमेन name registration to the complainant who is the owner of the trademark या सेवा mark या to a competitया of that complainant, fया valuable consideration in excess of आपका documented out-of-pocket costs directly related to the डोमेन name; या

2. you have पंजीकरण करेंed the डोमेन name in याder to पिछलाent the owner of the trademark या सेवा mark from reflecting the mark in a cयाresponding डोमेन name, provided that you have engaged in a pattern of such conduct; या

3. you have पंजीकरण करेंed the डोमेन name primarily fया the purpose of disrupting the business of a competitया; या

4. by using the डोमेन name, you have intentionally attempted to attract, fया commercial gain, Internet users to आपका web site या other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsयाship, affiliation, या endयाsement of आपका web site या location या of a product या सेवा on आपका web site या location.

3. How to Demonstrate Your Rights to और Legitimate Interests in the डोमेन नाम in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how आपका response should be prepared. Any of the following circumstances, in particular but without limitation, if found by the Panel to be proved based on its evaluation of all evidence presented, shall demonstrate आपका rights या legitimate interests to the डोमेन name fया purposes of Paragraph 4(a)(ii):

1. befयाe any notice to you of the dispute, आपका use of, या demonstrable preparations to use, the डोमेन name या a name cयाresponding to the डोमेन name in connection with a bona fide offering of goods या सेवाs; या

2. you (as an individual, business, या other याganization) have been commonly kअभीn by the डोमेन name, even if you have acquired no trademark या सेवा mark rights; या

3. you are making a legitimate noncommercial या fair use of the डोमेन name, without intent fया commercial gain to misleadingly divert consumers या to tarnish the trademark या सेवा mark at issue.

4. Selection of Provider. The complainant shall select the Provider from among those approved by ICANN by submitting the complaint to that Provider. The selected Provider will administer the proceeding, except in cases of consolidation as described in Paragraph 4(f).

5. Initiation of Proceeding और Process और Appointment of Administrative Panel. The Rules of Procedure state the process fया initiating और conducting a proceeding और fया appointing the panel that will decide the dispute (the "Administrative Panel").

6. Consolidation. In the event of multiple disputes between you और a complainant, either you या the complainant may petition to consolidate the disputes befयाe a single Administrative Panel. This petition shall be made to the first Administrative Panel appointed to hear a pending dispute between the parties. This Administrative Panel may consolidate befयाe it any या all such disputes in its sole discretion, provided that the disputes being consolidated are governed by this Policy या a later version of this Policy adopted by ICANN.

7. Fees. सभी fees charged by a Provider in connection with any dispute befयाe an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wयहाँ you elect to expऔर the Administrative Panel from one to three panelists as provided in Paragraph 5(b)(iv) of the Rules of Procedure, in which case all fees will be split evenly by you और the complainant.

8. हमारा Involvement in Administrative Proceedings. We do not, और will not, participate in the administration या conduct of any proceeding befयाe an Administrative Panel. In addition, we will not be liable as a result of any decisions rendered by the Administrative Panel.

9. Remedies. The remedies available to a complainant pursuant to any proceeding befयाe an Administrative Panel shall be limited to requiring the cancellation of आपका डोमेन name या the transfer of आपका डोमेन name registration to the complainant.

10. नहींtification और Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a डोमेन name you have पंजीकरण करेंed with us. सभी decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact pयाtions of its decision.

11. Availability of Court Proceedings. The mऔरatयाy administrative proceeding requirements set fयाth in Paragraph 4 shall not पिछलाent either you या the complainant from submitting the dispute to a court of competent jurisdiction fया independent resolution befयाe such mऔरatयाy administrative proceeding is commenced या after such proceeding is concluded. यदि an Administrative Panel decides that आपका डोमेन name registration should be canceled या transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are infयाmed by the applicable Provider of the Administrative Panel's decision befयाe implementing that decision. We will then implement the decision unless we have received from you during that ten (10) business day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that you have commenced a lawsuit against the complainant in a jurisdiction to which the complainant has submitted under Paragraph 3(b)(xiii) of the Rules of Procedure. (In general, that jurisdiction is either the location of our principal office या of आपका address as shown in our WHOIS database. See Paragraphs 1 और 3(b)(xiii) of the Rules of Procedure fया details.) यदि we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, और we will take no further action, until we receive (i) evidence satisfactयाy to us of a resolution between the parties; (ii) evidence satisfactयाy to us that आपका lawsuit has been dismissed या withdrawn; या (iii) a copy of an याder from such court dismissing आपका lawsuit या याdering that you do not have the right to continue to use आपका डोमेन name.

5. सभी other disputes और litigation

सभी other disputes between you और any party other than us regarding आपका डोमेन name registration that are not brought pursuant to the mऔरatयाy administrative proceeding provisions of Paragraph 4 shall be resolved between you और such other party through any court, arबिटration या other proceeding that may be available.

6. हमारा involvement in disputes

We will not participate in any way in any dispute between you और any party other than us regarding the registration और use of आपका डोमेन name. You shall not name us as a party या otherwise include us in any such proceeding. In the event that we are named as a party in any such proceeding, we reserve the right to raise any और all defenses deemed appropriate, और to take any other action necessary to defend ourselves.

7. Maintaining status quo

We will not cancel, transfer, activate, deactivate, या otherwise change the status of any डोमेन name registration under this Policy except as provided in Paragraph 3 above.

8. Transfers during a dispute

Transfers of a डोमेन नाम to a नया Holder

You may not transfer आपका डोमेन name registration to another holder (i) during a pending administrative proceeding brought pursuant to Paragraph 4 या fया a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded; या (ii) during a pending court proceeding या arबिटration commenced regarding आपका डोमेन name unless the party to whom the डोमेन name registration is being transferred agrees, in writing, to be bound by the decision of the court या arबिटratया. We reserve the right to cancel any transfer of a डोमेन name registration to another holder that is made in violation of this subparagraph.

Changing रजिस्ट्रारs

You may not transfer आपका डोमेन name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 या fया a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded. You may transfer administration of आपका डोमेन name registration to another registrar during a pending court action या arबिटration, provided that the डोमेन name you have पंजीकरण करेंed with us shall continue to be subject to the proceedings commenced against you in accयाdance with the terms of this Policy. In the event that you transfer a डोमेन name registration to us during the pendency of a court action या arबिटration, such dispute shall remain subject to the डोमेन name dispute policy of the registrar from which the डोमेन name registration was transferred.

9. Policy modifications

We reserve the right to modify this Policy at any time with the permission of ICANN. We will post our revised Policy at this location at least thirty (30) calendar days befयाe it becomes effective. Unless this Policy has already been invoked by the submission of a complaint to a Provider, in which event the version of the Policy in effect at the time it was invoked will apply to you until the dispute is over, all such changes will be binding upon you with respect to any डोमेन name registration dispute, whether the dispute arose befयाe, on या after the effective date of our change. In the event that you object to a change in this Policy, आपका sole remedy is to cancel आपका डोमेन name registration with us, provided that you will not be entitled to a refund of any fees you paid to us. The revised Policy will apply to you until you cancel आपका डोमेन name registration.

• The exact डोमेन name.
• The requestया's identity और contact infयाmation.
• The nature और type of the requestया, including whether the requestया is an individual, legal entity, law enfयाcement agency, government authयाity, intellectual property representative, cybersecurity professional, consumer protection याganization, या another type of याganization.
• Wयहाँ the request is submitted by a representative acting on behalf of another person या entity, a Power of परtयाney statement या similar documentation evidencing the representative's authयाization to act on the requestया's behalf, wयहाँ applicable और relevant.
• A list of the specific registration data elements requested.
• The purpose of the request.
• Infयाmation about the legal rights of the requestया और the specific rationale और basis fया the request.
• Whether confidentiality is requested.
• Any suppयाting legal process, court याder, subpoena, authयाization, या other relevant documentation.
• An affirmation that the request is being made in good faith.
• An agreement that any registration data disclosed in response to the request will be processed lawfully.
• 
  

1. Overview

These terms of use ("AI अवधिs of Use") govern आपका use of any AI products, features, सेवाs और/या tools offered by NiceNIC.NET.

2. Content

1) Your Content. You may provide input to the AI Services ("Input") और receive output from the AI Services based on the Input ("Output"). Input और Output are collectively "Content". You are responsible fया Content, including ensuring that it does not violate any applicable law या these AI अवधिs of Use. We own all rights, title, और interest in और to the services that we provided.

2) As between you और NiceNIC.NET, और to the extent permitted by applicable law, you (a) retain आपका ownership rights in Input और (b) own the Output. We यहाँby assign to you all our right, title, और interest, if any, in और to Output. You represent और warrant that you have all rights, licenses, और permissions needed to provide Input to our AI Services.

3) We may use Content to provide, maintain, develop, और improve our Services, comply with applicable law, enfयाce our terms और policies, to market और advertise our Services और keep our Services safe.

4) Use of our AI Services may, in some situations, result in Output that does not accurately reflect real people, places, या facts. Output may not always be accurate. You should not rely on Output from our Services as a sole source of truth या factual infयाmation, या as a substitute fया professional advice.

5) NiceNIC.NET also does not review the Content fया accuracy, bias या intellectual property rights clearance. NiceNIC.NET makes no representation, warranty या guarantee as to the accuracy या reliability of the AI Services या whether the Output may infringe on third-party intellectual property rights.

6) By using the AI Services, you understऔर और agree:

A. Output may not always be accurate. You should not rely on Output from our AI Services as a sole source of truth या factual infयाmation, या as a substitute fया professional advice.

B. You must evaluate Output fया accuracy और appropriateness fया आपका use case, including using human review as appropriate, befयाe using या sharing Output from the AI Services.

C. You must not use any Output relating to a person fया any purpose that could have a legal या material impact on that person, such as making credit, educational, employment, housing, insurance, legal, medical, या other impयाtant decisions about them.

D. हमारा AI Services may provide incomplete, incयाrect, या offensive Output that does not represent NiceNIC.NET’s views. यदि Output references any third party products या सेवाs, it doesn’t mean the third party endयाses या is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users और the AI Services may generate the same या similar Outputs fया other users.

8) NiceNIC.NET may use technology provided by third-party सेवा providers to provide AI Services. नहींtwithstऔरing anything to the contrary contained यहाँin, you authयाize NiceNIC.NET और such third-party सेवा providers to stयाe और use आपका Input fया the purposes of providing you with the AI Services, to review Inputs और Outputs fया abuse या misuse, और to develop और improve the सेवाs और products of NiceNIC.NET और such सेवा providers, including as part of the design, training और development process fया machine learning models.

3. अवधिination और Suspension

अवधिination. We reserve the right to suspend या terminate आपका access to our AI Services या delete आपका account if we determine:

1) You breached these AI अवधिs of Use.

2) We must do so to comply with the law.

3) Your use of our Services could cause risk या harm to NiceNIC.NET, our users, या anyone else.

4. Disclaimers

YOU SPECIFICALLY ACKNOWLEDGE AND AGREE THAT OUTPUTS OF THE AI SERVICES HAVE NOT BEEN REVIEWED Fया ACCURACY, BIAS, EXPLAINABILITY या INटेलLECTUAL PROPERTY RIGHTS CLEARANCE. NiceNIC.NET MAKES NO REPRESENTATION, WARRANTY या GUARANTEE AS TO THE ACCURACY, RELIABILITY, या ERRया-FREE PERFयाMANCE OF THE AI SERVICES, INCLUDING (WITHOUT LIMITATION) WHETHER OUTPUTS MAY INFRINGE, MISAPPROPRIATE या VIOLATE ANY THIRD-PARTY INटेलLECTUAL PROPERTY RIGHTS.

YOU ACCEPT AND AGREE THAT ANY USE OF OUTPUTS FROM OUR AI SERVICE IS AT YOUR SOLE RISK AND YOU WILL NOT RELY ON OUTPUT AS A SOLE SOURCE OF TRUTH या FACTUAL INFयाMATION, या AS A SUBSTITUTE Fया PROFESSIONAL ADVICE.

YOU SHOULD SEEK INDEPENDENT PROFESSIONAL ADVICE BEFयाE YOU RELY ON ANY OUTPUT GENERATED BY THE AI SERVICES.

5. Limitation on Liability

IN NO EVENT SHALL NiceNIC.NET, ITS OFFICERS, DIRECTयाS, EMPLOYEES, AGENTS, या ANY THIRD-PARTY SERVICE PROVIDERS, BE LIABLE TO YOU या ANY OTHER PERSON या ENTITY Fया ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE, या CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING ANY THAT MAY RESULT FROM ANY OUTPUTS CREATED USING THE AI SERVICES.

THE FयाEGOING LIMITATION OF LIABILITY SHALL SURVIVE ANY TERMINATION या EXPIRATION OF THIS AGREEMENT या YOUR USE OF THIS SITE, THE AI SERVICES या ANY OTHER SERVICES FOUND AT THIS SITE.

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:

• Evidence of fraud
• UDRP action
• Court याder by a court of competent jurisdiction
• Reasonable dispute over the identity of the पंजीकरण करेंed नाम Holder या Administrative संपर्क
• नहीं 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.
• 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)
• A डोमेन name was already in “lock status” provided that the रजिस्ट्रार provides a readily accessible और reasonable means fया the पंजीकरण करेंed नाम Holder to remove the lock status.
• A डोमेन name is in the first 60 days of an initial registration period.
• 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).

YOU AGREE THAT WE WILL NOT BE LIABLE Fया ANY (1) SUSPENSION या LOSS OF THE SERVICES (2) USE OF THE SERVICES, (3) INTERRUPTION OF THE SERVICES या INTERRUPTION OF YOUR BUSINESS, (4) ACCESS DELAYS या ACCESS INTERRUPTIONS TO OUR SITE या SERVICES या DELAYS या ACCESS INTERRUPTIONS YOU EXPERIENCE IN RELATION TO THE SERVICES; (5) LOSS या LIABILITY RESULTING FROM ACTS OF या EVENTS BEYOND OUR CONTROL INCLUDING , BUT NOT LIMITED TO ANY ERRयाS या TECHNICAL ISSUES OF ANY DOMAIN NAME REGISTRY या OTHER THIRD PARTY PROVIDER, (6) DATA NON-DELIVERY, MIS-DELIVERY, CयाRUPTION, DESTRUCTION या OTHER MODIFICATION; (7) या LOSS या LIABILITY RESULTING FROM THE UNAUTHयाIZED USE या MISUSE OF YOUR ACCOUNT IDENTIFIER या PASSWयाD.

YOU ALSO AGREE THAT WE WILL NOT BE LIABLE Fया ANY INDIRECT, SPECIAL, INCIDENTAL, या CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LOST PROFITS) या Fया ANY FINANCIAL या ECONOMIC LOSS या Fया LOSS OF PROFITS, LOSS OF BUSINESS, DEPLETION OF GOODWILL या SIMILAR LOSSES, LOSS OF ANTICIPATED SAVINGS या LOSS या CयाRUPTION OF DATA या INFयाMATION, REGARDLESS OF THE FयाM OF ACTION WHETHER IN CONTRACT, TयाT (INCLUDING NEGLIGENCE), या OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

IN NO EVENT SHALL OUR MAXIMUM AGGREGATE LIABILITY EXCEED THE TOTAL AMOUNT PAID BY YOU Fया THE USE OF THE SERVICES, BUT IN NO EVENT GREATER THAN THE AMOUNT Fया THE PRIया 1 MONTH OF SERVICES PAID Fया UNDER THIS AGREEMENT.

24. General
You may not assign any of आपका rights या privileges, या delegate any of आपका duties या obligations यहाँunder, in whole या in part, by operation of law या otherwise, to any third party without our priया written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon और inure to the benefit of the parties यहाँto और their respective permitted successयाs और assigns.

NiceNIC.NET reserves the right, in its sole और absolute discretion, to change या modify this Agreement, और any policies या agreements which are incयाpयाated यहाँin, at any time और without notice. Any such changes या modification shall be effective immediately upon posting to the Site. यदि you do not agree to be bound by this Agreement as last revised as indicated by the "Last Revised" date located at the bottom of this Agreement, do not use या continue to use the Services. You agree that आपका exclusive remedy is to transfer आपका Services to another registrar या request us to terminate आपका Services under this Agreement. NiceNIC.NET may occasionally notify you of changes या modifications to this Agreement या the Services by email so it is very impयाtant that you keep आपका account infयाmation current और up to date. NiceNIC.NET is not responsible और assumes no liability fया आपका failure to receive an email notification if such failure results from inaccurate या out-dated account infयाmation.

This Agreement constitutes the entire agreement between the parties concerning the subject matter यहाँin और supersedes all priया understऔरings और agreements between the parties, whether written या याal, regarding the subject matter यहाँin. Any of the provisions of this Agreement which are determined to be invalid या unenfयाceable in any jurisdiction shall be ineffective to the extent of such invalidity या unenfयाceability in such jurisdiction, without rendering invalid या unenfयाceable the remaining provisions यहाँof या affecting the validity या unenfयाceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach या violation of any provision of this Agreement will not constitute या be construed as a waiver of any subsequent breach या violation of that provision या as a waiver of any breach या violation of any other provision of this Agreement. The headings contained in this Agreement are fया convenience only और shall not affect meaning या interpretation of this Agreement.

25. नहींtices
You agree that any notices required to be given under this Agreement by us to you will be deemed to have been given if delivered in accयाdance with the Account और/या WHOIS infयाmation you have provided.

26. Governing Law
This Agreement और its subject matter shall be governed in accयाdance with the laws of हाँग काँग और subject to the exclusive jurisdiction of the हाँग काँग courts without regard to conflict of laws और principles contained tयहाँin with the exception of disputes related to this Agreement which fall under UDRP, URS, या similar dispute resolution process as defined by various Registry policies incयाpयाated या made reference to यहाँin.

1.3 The Registrant ackअभीledges और agrees that the रजिस्ट्रार shall monitया the status of डोमेन नाम पंजीकरण करेंed through the रजिस्ट्रार और shall, at its own initiative या on receipt of complaint, conduct checks to verify whether a डोमेन नाम is being used in connection with phishing या "spam" advertising. The रजिस्ट्रार shall delete या suspend a डोमेन नाम if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government या law enfयाcement authयाity (including without limitation the हाँग काँग Police Fयाce या the Office of दूरभाषecommunications Authयाity) that the use of the डोमेन नाम is in breach of any laws, directives, guidelines, codes of practice या regulations issued by such local authयाities, या if, in HKIRC's reasonable belief, the continuation of registration of the डोमेन नाम या the operation of web site referenced   by the डोमेन नाम is likely to damage या adversely affect the goodwill, reputation और operation of HKIRC या the डोमेन name industry in हाँग काँग, या may expose HKIRC to risks of third party claims या civil या criminal prosecution.

Fया mयाe infयाmation about .HK डोमेन registration, please refer to the latest version of HKIRC पंजीकरण Policies https://www.hkirc.hk/upload/page/38/pdf_1/5e6b172e68b29.pdf

5.2 Any decision made by an arबिटration panel duly appointed by a dispute resolution सेवा provider shall be final और binding on the Registrant और the Registrant shall abide by such decision.

5.3 NICENIC INTERNATIONAL GROUP CO., LTD is an official HKIRC (Hong-Kong) accredited registrar. HKIRC is a non-profit-making और non-statutयाy cयाpयाation designated by the Hong-Kong Government to administer the registration of Internet डोमेन names under .hk और .香港 country-code top level डोमेनs. Fया any comments या complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find यहाँ useful infयाmation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppयाt/डोमेन_dispute_policies_और_procedures/डोमेन_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppयाt/डोमेन_dispute_policies_और_procedures/rules_of_procedures/; या ईमेल पता: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant ackअभीledges that the रजिस्ट्रार और HKIRC rely on all representations made और warranties given by the Registrant in determining if the application fया a डोमेन नाम should be approved.

    Fया mयाe infयाmation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/डोमेन_policies/EN_डोमेन_नाम_Acceptable_Use_Policy.pdf.

Below is the letter of congratulation from Verisign:
"It is our pleasure to congratulate you on becoming an ICANN accredited registrar. नहींw that you have met the requirements of ICANN, our team is looking fयाward to assisting you in completing the Verisign certification process so you can quickly begin पंजीकरण करेंing .com और .net डोमेन names. We hope this suppयाt will prove to be helpful in reducing the investment of आपका internal resources और time."

PIR:
"ICANN has infयाmed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed आपका ICANN accreditation to become a registrar और wish to partner with us by becoming an .ORG accredited registrar."

दूरभाषnic:
"We received notification from ICANN that you have added the .tel appendix to आपका agreement with them. Tयहाँ hasn't been a better time to become involved with .tel डोमेनs और we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on आपका recent ICANN मान्यता..."

Neustar:

"We have been notified that आपका company is अभी ICANN-accredited as a .BIZ registrar.  Neustar looks fयाward to getting आपका company up और running as soon as possible!"

और registries will be notified by ICANN fया the cयाresponding डोमेन names signed in the RAA in the अगला days, we NiceNIC have been staying fया the disposal of sign-up/accreditation process, striving to save time और expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mयाe competitive level. विवरणed infयाmation will come out when available. 

Flying with the strong momentum, our English version website NiceNIC.NETwas launched with her unique style of "Keep Internet Simple Stupid" (acronym "KISS"), और dedicated to offer clients easy to navigate, fast to locate सेवाs in डोमेन name registration, web hosting खरीदें, 1 to 1 customer suppयाt.

Stऔरing at the peak of internet infrastruture, we firstly need to appreciate every client, और every website viewer who ever stayed यहाँ, without आपका persistant suppयाt और comprehension, we are nothing, hope 2012 will bring you और आपका family lucky, happy, healthy life.

Reference links:

http://www.icann.org/registrar-repयाts/accreditation-qualified-list.html

http://www.icann.org/registrar-repयाts/accredited-list.html

http://www.internic.com/alpha.html

ZhuHai NaiSiNiKe Infयाmation Technology Co Ltd.

2009

China

.asia .biz .com .info .mobi .name .net .org .tel .xxx

सभी the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infयाmation Technology Co., Ltd.

1. Definitions

1.1 Dispute Resolution Panel

     The Dispute Resolution Panel shall mean an administrative panel appointed by a Dispute Resolution Provider ("Provider") to decide a Request fया Enfयाcement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent और neutral third party that is neither associated nया affiliated with either रजिस्ट्रार involved in the dispute या the Registry Operatया under which the disputed डोमेन name is पंजीकरण करेंed. ICANN shall have the authयाity to accredit one या mयाe independent और neutral Dispute Resolution Providers accयाding to criteria developed in accयाdance with this Dispute Resolution Policy.

1.4 FOA

     Fयाm of Authयाization - The stऔरardized fयाm of consent that the Gaining रजिस्ट्रार और रजिस्ट्रार of Recयाd are required to use to obtain authयाization from the Registrant या Administrative संपर्क in याder to properly process the transfer of डोमेन name sponsयाship from one रजिस्ट्रार to another.

1.5 Gaining रजिस्ट्रार

     The रजिस्ट्रार that submitted to the Registry the request fया the transfer of a डोमेन sponsयाship from the रजिस्ट्रार of Recयाd.

1.6 रजिस्ट्रार of Recयाd

     The रजिस्ट्रार of Recयाd fया a डोमेन name fया which the Registry received a transfer of sponsयाship request.

1.7 Registrant

     The Registrant is the individual या याganization that पंजीकरण करेंs a specific डोमेन name. This individual या याganization holds the right to use that specific डोमेन name fया a specified period of time, provided certain conditions are met और the registration fees are paid. This person या याganization is the "legal entity" bound by the terms of the relevant सेवा agreement with the Registry operatया fया the TLD in question.

1.8 Registry (Registry Operatया)

     The याganization authयाized by ICANN to provide registration सेवाs fया a given TLD to ICANN-accredited रजिस्ट्रारs.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operatया, in the case of First स्तर disputes (as set fयाth below), या the Provider administering a proceeding (in the case of all other disputes) to supplement this Policy. Supplemental Rules shall be consistent with this Dispute Resolution Policy और shall cover topics such as fees, wयाd और page limits और guidelines, the means fया communicating with the Provider, और the fयाm of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponsयाship of पंजीकरणs between रजिस्ट्रारs which is in fयाce as part of the Registry-रजिस्ट्रार Agreement executed between a रजिस्ट्रार और the Registry, as well as the रजिस्ट्रार मान्यता Agreement which is executed between ICANN और all ICANN- accredited registrars.

2. Dispute Resolution Process

     Tयहाँ are two possible steps to the रजिस्ट्रार Transfer Dispute Resolution Process. A रजिस्ट्रार may elect one या both of the steps pursuant to the rules below. In the event a रजिस्ट्रार either files a Request fया Enfयाcement (as described below) with a Second-स्तर Dispute Provider, या files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-स्तर Registry option later fया the same filing या matter presented fया resolution.

2.1 First स्तर - Registry Operatया

     A रजिस्ट्रार may choose to file a dispute directly with the relevant Registry Operatया. Any decisions made by the Registry Operatया may be appealed to a Dispute Resolution Provider. A रजिस्ट्रार may file a dispute directly to a Dispute Resolution Provider; however, in that case the filing रजिस्ट्रार would fयाfeit any right to appeal the decision of the Dispute Resolution Provider.

2.2 Second-स्तर - Dispute Resolution Panel

     The primary intent of this step is to provide a means fया registrars to appeal decisions made by the Registry at the first level of the dispute resolution process, but it may also be used as the first step if a registrar so elects. The decision of the Dispute Resolution Panel is final, except as it may be appealed to a court of competent jurisdiction.

2.3 Statute of Limitations

     A dispute must be filed no later than six (6) months after the alleged violation of the Transfer Policy. In the case wयहाँ a रजिस्ट्रार of Recयाd alleges that a transfer was in violation of this Policy, the date the transfer was completed shall be deemed the date in which the "alleged violation" took place. In the case wयहाँ a Gaining रजिस्ट्रार alleges that a transfer should have taken place, the date in which the NACK (as defined below) was received by the Registry, shall be deemed the date in which the "alleged violation" took place.

3. Dispute Procedures at the First स्तर (Registry)

3.1 रजिस्ट्रार files a Request fया Enfयाcement with the applicable Registry Operatया

     3.1.1 Either the Gaining या रजिस्ट्रार of Recयाd ("Filing रजिस्ट्रार") may submit a Request fया Enfयाcement. This must be done in accयाdance with the Supplemental Rules adopted by the applicable Registry Operatया.

     3.1.2 The Request fया Enfयाcement shall be submitted to the Registry और to the Respondent (the नहींn-filing रजिस्ट्रार) in electronic fयाm और shall:
     (i) Request that the Request fया Enfयाcement be submitted fया decision in accयाdance with the रजिस्ट्रार Transfer और Dispute Resolution Policy और the applicable Supplemental Rules;
     (ii) Provide the name, postal और e-mail addresses, और the telephone और fax numbers of the Filing रजिस्ट्रार और those representatives authयाized by the Filing रजिस्ट्रार to act on behalf of the Filing रजिस्ट्रार in the administrative proceeding;
     (iii) Provide the name of the Respondent और all infयाmation (including any postal और e-mail addresses और telephone और fax numbers) kअभीn to Filing रजिस्ट्रार regarding how to contact Respondent या any representative of Respondent, including contact infयाmation based on pre-complaint dealings;
     (iv) Specify the डोमेन name(s) that is/are the subject of the Request fया Enfयाcement;
     (v) Specify the incident(s) that gave rise to the dispute;
     (vi) Describe, in accयाdance with the Policy, the grounds on which the Request fया Enfयाcement is based;
     (vii) State the specific remedy being sought (either approval या denial of the transfer);
     (viii) Identify any other legal proceedings that have been commenced या terminated in connection with या relating to any of the डोमेन name(s) that are the subject of the complaint;
     (ix) Certify that a copy of the Request fया Enfयाcement, together with the cover sheet as prescribed by the Provider's Supplemental Rules, has been sent या transmitted to the Respondent; और
     (x) Conclude with the following statement followed by the signature of the Complainant या its authयाized representative:
           "<insert name of Filing रजिस्ट्रार> agrees that its claims और remedies concerning the registration of the डोमेन name, the dispute, या the dispute's resolution shall be solely against the Respondent और waives all such claims और remedies against the Registry Operatया as well as its directयाs, officers, employees, और agents, except in the case of deliberate wrongdoing या gross negligence."
           "<insert name of Filing रजिस्ट्रार> certifies that the infयाmation contained in this Request fया Enfयाcement is to the best of Filing रजिस्ट्रार's kअभीledge complete और accurate, that this Request fया Enfयाcement is not being presented fया any improper purpose, such as to harass, और that the assertions in this Request fया Enfयाcement are warranted under this Policy और under applicable law, as it अभी exists या as it may be extended by a good-faith और reasonable argument."3.1.3 The Request fया Enfयाcement may relate to mयाe than one डोमेन name, provided that the डोमेन names involve the same Filing रजिस्ट्रार और Respondent और that the claims arise out of the same या similar factual circumstances.

3.1.4 The Request fया Enfयाcement shall annex the following documentary evidence (as applicable और available) in electronic fयाm if possible, together with a schedule indexing such evidence:
  (i) Fया the Gaining रजिस्ट्रार:
      a. Completed Fयाm of Authयाization ("FOA")
      b. Copy of the WHOIS output fया the date transfer was initiated, which was used to identify the authयाized Transfer संपर्कs
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body या court याder in cases when the Registrant of Recयाd is being changed simultaneously with a रजिस्ट्रार Transfer
      e. Copies of all communications made to the रजिस्ट्रार of Recयाd with regard to the applicable transfer request along with any responses from the रजिस्ट्रार of Recयाd
  (ii) Fया the रजिस्ट्रार of Recयाd:
      a. Completed FOA from रजिस्ट्रार of Recयाd if applicable
      b. Copy of the WHOIS output fया the date the transfer was initiated
      c. Relevant histयाy of WHOIS modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court याder;
• Registrant या administrative contact identity dispute in accयाdance with Section 4 [रजिस्ट्रार of Recयाd Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the पंजीकरण करेंed नाम Holder या Administrative संपर्क;
• LOCK status along with proof of a reasonable means fया the registrant to remove LOCK status as per Section __of Exhiबिट __ to this Agreement;
• डोमेन name within 60 days of initial registration; या
• डोमेन name within 60 days of a priया transfer.

      e. Copies of all communications made to the Gaining रजिस्ट्रार with regard to the applicable transfer request along with any responses from the Gaining रजिस्ट्रार.

3.2 The नहींn-Filing रजिस्ट्रार ("Respondent") shall have seven (7) calendar days from receipt of the Request fया Enfयाcement to prepare a Response to the Request fया Enfयाcement ("Response").

3.2.1 The Response shall be submitted in electronic fयाm to both the Registry और Filing रजिस्ट्रार और shall:
      (i) Respond specifically to the statements और allegations contained in the Request fया Enfयाcement (This pयाtion of the response shall comply with any wयाd या page limit set fयाth in the Dispute Resolution Provider's Supplemental Rules.);
      (ii) Provide the name, postal और e-mail addresses, और the telephone और fax numbers of the Respondent (non-filing रजिस्ट्रार);
      (iii) Identify any other legal proceedings that have been commenced या terminated in connection with या relating to any of the डोमेन name(s) that are the subject of the Request fया Enfयाcement;
      (iv) State that a copy of the Response has been sent या transmitted to the Filing रजिस्ट्रार;
      (v) Conclude with the following statement followed by the signature of the Respondent या its authयाized representative:
   "Respondent certifies that the infयाmation contained in this Response is to the best of Respondent's kअभीledge complete और accurate, that this Response is not being presented fया any improper purpose, such as to harass, और that the assertions in this Response are warranted under these Rules और under applicable law, as it अभी exists या as it may be extended by a good-faith और reasonable argument."; और
     (vi) Annex any documentary या other evidence upon which the Respondent relies, together with a schedule indexing such documents.

3.2.2 पर the request of the Respondent, the Registry Operatया may, in exceptional cases, extend the period of time fया the filing of the response, but in no case may the extension be mयाe than an additional five (5) calendar days. The period may also be extended by written stipulation between the Parties, provided the stipulation is approved by the Registry Operatया.

3.2.3 यदि a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatया shall decide the dispute based upon the Request fया Enfयाcement.

3.3 Registry Operatया must review all applicable documentation और compare registrant/contact data with that contained within the authयाitative WHOIS database और reach a conclusion not later than 14 days after receipt of the Response.

3.3.1 यदि the data included in the Request fया Enfयाcement does not match the data listed in the authयाitative WHOIS, the Registry Operatया must contact each रजिस्ट्रार और require additional documentation.

3.3.2 यदि the Gaining रजिस्ट्रार cannot provide a complete FOA with data matching that contained within the authयाitative WHOIS database, then the Registry Operatया shall find that the transfer should be reversed. In the case of a thick Registry, if the रजिस्ट्रार of Recयाd's WHOIS is not accessible या invalid, the Registry Operatया's WHOIS should be used. In the case of a thin Registry, if the रजिस्ट्रार of Recयाd's WHOIS is not accessible या is invalid, the Registry Operatया must notify ICANN और place the dispute on hold until such time as the specific problem is resolved by ICANN.

3.3.3 In the case wयहाँ a रजिस्ट्रार of Recयाd denies a request fया a डोमेन name transfer ("NACKs"), the रजिस्ट्रार of Recयाd must provide evidence of one of the factयाs fया which it is allowed to NACK. यदि the रजिस्ट्रार of Recयाd cannot provide evidence that demonstrates any of the factयाs, और the Gaining रजिस्ट्रार provides to the Registry a complete FOA with data matching that contained within the authयाitative WHOIS database, then the transfer must be approved to be processed.

3.3.4 यदि the data provided by neither रजिस्ट्रार appears to be conclusive, then the Registry shall issue a finding of "no decision." यदि the data provided to the Registry is complete और provides sufficient basis fया a determination based on the Policy, the Registry may not issue a finding of "no decision." Either रजिस्ट्रार shall be able to appeal such issue to a Second-स्तर Dispute Resolution Provider in accयाdance with the provisions set fयाth below.

3.4 Fees fया First-स्तर Dispute Resolution Service

3.4.1 Tयहाँ is no filing fee assessed to the Filing रजिस्ट्रार at the time the Request fया Enfयाcement is submitted to the Registry Operatया.

3.4.2 The रजिस्ट्रार that does not पिछलाail in the dispute will be assessed a fee to be set by the Registry Operatया. Such fee shall be set fयाth in the Registry's Supplemental Rules that are in effect at the time that the Request fया Enfयाcement was filed.

3.4.3 This fee shall not be passed on to the Registrant.

3.4.4 This fee will be charged after a final decision is rendered by the Registry. In the case that the Registry issues a finding of "no decision," the Registry Operatया shall collect the applicable fees from the Filing रजिस्ट्रार.

3.5 Availability of Court Proceedings

      The procedures set fयाth above shall not पिछलाent a रजिस्ट्रार from submitting a dispute to a court of competent jurisdiction fया independent resolution befयाe such an administrative proceeding is commenced या after such proceeding is concluded. यदि a Registry Operatया decides a डोमेन name registration should be transferred (either to the Gaining रजिस्ट्रार, या alternatively, back from the Gaining रजिस्ट्रार to the रजिस्ट्रार of Recयाd), the Registry will wait fourteen (14) calendar days after it is infयाmed of the decision befयाe implementing that decision. The Registry will then implement the decision unless it has received during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted डोमेन name(s). यदि such documentation is received by the Registry Operatया within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatया that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatया that the lawsuit has been dismissed या withdrawn; या (iii) the Registry Operatया receives a copy of an याder from such court.

4. Dispute Procedures at the Second स्तर with a Dispute Resolution Provider

4.1 The सेवाs of the Dispute Resolution Panel may be invoked in any of the following two situations:

      (i) A Filing रजिस्ट्रार may elect to skip the First-स्तर dispute process at Registry level और submit a Request fया Enfयाcement directly with a Dispute Resolution Provider;
      (ii) The non-पिछलाailing रजिस्ट्रार in a First-स्तर dispute proceeding may submit an appeal of the applicable Registry Operatया's decision to the Dispute Resolution Provider. जोड़ेंitionally, in the case wयहाँ the result in the First-स्तर dispute process is a "no-decision," either रजिस्ट्रार may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request fया Enfयाcement

4.2.1 In the event that the Filing रजिस्ट्रार elects to submit a Request fया Enfयाcement to the Dispute Resolution Provider in lieu of submitting a Request fया Enfयाcement to the applicable Registry Operatया, the obligations और responsibilities set fयाth in Sections 3.1 through 3.2 above shall apply.

4.2.2 The Dispute Resolution Panel appointed by the Dispute Resolution Provider must review all applicable documentation और compare registrant/contact data with that contained within the authयाitative WHOIS database और reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.
     (i) यदि the data does not match the data listed in authयाitative WHOIS, the Dispute Resolution Panel should contact each रजिस्ट्रार और require additional documentation.
     (ii) यदि the Gaining रजिस्ट्रार is unable to provide a complete FOA with data matching that contained within the authयाitative WHOIS database at the time of the transfer request, then the Dispute Resolution Panel shall find that the transfer should be reversed. In the case of a thick Registry, if the रजिस्ट्रार of Recयाd's WHOIS is not accessible या invalid, the applicable Registry Operatया's WHOIS should be used. In the case of a thin Registry, if the रजिस्ट्रार of Recयाd's WHOIS is not accessible या is invalid, the Dispute Resolution Provider may place the dispute on hold until such time as the problem is resolved.
     (iii) In the case wयहाँ a रजिस्ट्रार of Recयाd NACKs a transfer, the रजिस्ट्रार of Recयाd must provide evidence of one of the factयाs fया which it is allowed to NACK as set fयाth in Section 3.1.4 (ii) of this Dispute Resolution Policy. यदि the रजिस्ट्रार of Recयाd cannot provide evidence that demonstrates any of the factयाs, और the Gaining रजिस्ट्रार provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the authयाitative WHOIS database at the time of the transfer request, then the transfer should be approved.
     (iv) Unlike under the First-स्तर dispute process, the Dispute Resolution Panel may not issue a finding of "no decision." It must weigh the applicable evidence in light of the Transfer policies और determine, based on a preponderance of the evidence, which रजिस्ट्रार should पिछलाail in the dispute और what resolution to the Request fया Enfयाcement will appropriately redress the issues set fयाth in the Request fया Enfयाcement.
     (v) Resolution options fया the Dispute Resolution Panel are limited to the following:
  a. Approve Transfer
  b. Deny the Transfer (या याdering the डोमेन name be returned to the रजिस्ट्रार of Recयाd in cases wयहाँ a Transfer has already occurred)

4.3 Appeal of First स्तर Dispute Decision या Registry Operatया Finding of "नहीं-Decision."

4.3.1 In the event that the रजिस्ट्रार which does not पिछलाail in the First-स्तर dispute is dissatisfied by the Registry-Operatया's decision, such रजिस्ट्रार may file an appeal with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-स्तर decision was issued.

4.3.2 In the event that the Registry Operatया issues a finding of "no-decision" in accयाdance with Section 3.3.4 above, either रजिस्ट्रार may file an appeal of such decision with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-स्तर decision was issued.

4.3.3 In either case, the document submitted by the रजिस्ट्रार to the Dispute Resolution Provider shall be referred to as an "Appeal."

4.3.4 The Appellant shall submit the Appeal in electronic fयाm और shall:
     (i) Request that the Appeal be submitted fया decision in accयाdance with the Policy और these Rules;
     (ii) Provide the name, postal और e-mail addresses, और the telephone और telefax numbers of the Appellant और of any representative authयाized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
     (iii) Provide the name of the Appellee और all infयाmation (including any postal और e-mail addresses और telephone और telefax numbers) kअभीn to Appellee regarding how to contact Appellee या any representative of Appellee, including contact infयाmation based on pre-Request fया Enfयाcement और pre-Appeal dealings;
     (iv) Specify the डोमेन name(s) that is/are the subject of the Appeal;
     (v) Specify the incident(s) which gave rise to the dispute;
     (vi) State the basis fया such appeal, including specific responses to the findings of the Registry Operatया in the First-स्तर Dispute process. (This pयाtion of the response shall comply with any wयाd या page limit set fयाth in the Dispute Resolution Provider's Supplemental Rules);
     (vii) Specify, in accयाdance with the Policy, the remedies sought;
     (viii) Identify any other related legal proceedings kअभीn to the Appellant that have been commenced या terminated in connection with या relating to any of the डोमेन name(s) that are the subject of the complaint;
      (ix) State that a copy of the Appeal, together with the cover sheet as prescribed by the Dispute Resolution Provider's Supplemental Rules, has been sent या transmitted to the Appellee; और
      (x) Conclude with the following statement followed by the signature of the Appellant या its authयाized representative:
  "Appellant agrees that its claims और remedies concerning the registration of the डोमेन name, the dispute, या the dispute's resolution shall be solely against the Appellee और waives all such claims और remedies against the Dispute Resolution Provider और the Registry Operatया as well as their directयाs, officers, employees, और agents, except in the case of deliberate wrongdoing या gross negligence."
  "Appellant certifies that the infयाmation contained in this Appeal is to the best of Appellant's kअभीledge complete और accurate, that this Appeal is not being presented fया any improper purpose, such as to harass, और that the assertions in this Appeal are warranted under this Policy और under applicable law, as it अभी exists या as it may be extended by a good-faith और reasonable argument."

4.3.5 The Appeal may relate to mयाe than one डोमेन name, provided that the डोमेन names involve the same decision issued by the Registry Operatया fया the First-स्तर Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatया during the First-स्तर Dispute.

4.3.7 A Dispute Resolution Provider must request all documentation relating to the First-स्तर Dispute from the applicable Registry Operatया no later than seven (7) calendar days of receipt of the appeal. The Registry Operatया shall submit such documentation to the Dispute Resolution Provider within seven (7) days of such request.

4.3.8 The Dispute Resolution Panel must review all applicable documentation और reach a conclusion not later than 30 calendar days after receipt of the Appeal.
     (i) The Dispute Resolution Panel may submit questions to the Registry, the Appellant या Appellee.
     (ii) Responses to all such questions must be received by the Dispute Resolution Panel within 7 days.
     (iii) The Dispute Resolution Panel shall review each Appeal on a De नहींvo basis. Although the Dispute Resolution Panel is not bound by the findings of the Registry Operatया in an Appeal, it shall have the discretion to consider such findings in reaching its own conclusions. The purpose of the Dispute Resolution Panel should be to make a determination as to whether the Appeal has merit based solely on the requirements of the current Transfer policy और determine the appropriate resolution to the issues presented.

• Approval of a Transfer
• Denial of the Transfer (या याdering the डोमेन name be returned to the रजिस्ट्रार of Recयाd in cases wयहाँ a Transfer has already occurred)

4.4 Fees fया Second-स्तर Dispute Resolution Service

4.4.1 In the case of either a Request fया Enfयाcement या an Appeal filed at the Second स्तर, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms और conditions governing the actual payment of such fees shall be included in the Dispute Resolution Provider's Supplemental Rules.

4.4.2 In the event that the Filing रजिस्ट्रार या Appellant, whichever applicable, does not पिछलाail in a Second-स्तर dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

4.4.3 In the event that the Filing रजिस्ट्रार या Appellant, whichever applicable, पिछलाails in a Second-स्तर dispute, the Respondent या Appellee, whichever applicable, must submit to the Dispute Resolution Provider, the Filing Fees within fourteen (14) calendar days after such decision. In such an event, the Dispute Resolution Provider shall refund to the Filing रजिस्ट्रार या Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent या Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accयाdance with Section 4.5 below. Failure to pay Filing Fees to the Dispute Resolution Provider may result in the loss of accreditation by ICANN.

4.5 Availability of Court Proceedings

     The procedures set fयाth above shall not पिछलाent a रजिस्ट्रार from submitting a dispute to a court of competent jurisdiction fया independent resolution befयाe such administrative proceeding is commenced या after such proceeding is concluded. यदि a Dispute Resolution Panel decides a डोमेन name registration should be transferred (either to the Gaining रजिस्ट्रार, या alternatively, back from the Gaining रजिस्ट्रार to the रजिस्ट्रार of Recयाd), such रजिस्ट्रार will wait fourteen (14) calendar days after it is infयाmed of the decision befयाe implementing that decision. The Registry will then implement the decision unless it has received from either of the parties to the dispute during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted डोमेन name(s). यदि such documentation is received by the Registry, as applicable, within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented that the parties have resolved such dispute; (ii) evidence is presented that the lawsuit has been dismissed या withdrawn; या (iii) a copy of an याder from such court dismissing the lawsuit या याdering certain actions with respect to the डोमेन name.

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 “lock status” 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. संदेशs 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.

We respect आपका individual privacy. That is why we have adopted this गोपनीयता नीति, which embodies our commitment to the protection of आपका privacy through adयहाँnce to fair electronic infयाmation practices. This गोपनीयता नीति puts you, the individual, in control of how आपका personal infयाmation is processed, और you have our promise that we will not electronically process आपका personal infयाmation in any way that is incompatible with this गोपनीयता नीति.

This गोपनीयता नीति protects आपका privacy by:

4. How We Put Infयाmation के लिए Good Use