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 ccTLD-тер және 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 ccTLD-тер 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 НЕМЕСЕ LЖүйеS 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) LЖүйеS НЕМЕСЕ 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) НЕМЕСЕ LЖүйеS НЕМЕСЕ 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 LЖүйеT PROFITS) НЕМЕСЕ FНЕМЕСЕ ANY FINANCIAL НЕМЕСЕ ECONOMIC LЖүйеS НЕМЕСЕ FНЕМЕСЕ LЖүйеS OF PROFITS, LЖүйеS OF BUSINESS, DEPLETION OF GOODWILL НЕМЕСЕ SIMILAR LЖүйеSES, LЖүйеS OF ANTICIPATED SAVINGS НЕМЕСЕ LЖүйеS НЕМЕСЕ 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 PЖүйеSIBILITY 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