1. Scope А Purpose

1.1 This Policy explains the general post-expiration process that may apply to Доменное имя names managed through NiceNIC, including expiration, renewal, redemption, expired Доменное имя auction, pending delete status, А release of a Доменное имя name back to the public registration pool.

1.2 Домен lifecycle timing may vary depending on the top-level Доменное имя (“TLD”), registry rules, registry operat Или practices, applicable ICANN requirements, А other governing policies. Нет!t all TLDs follow the same expiration, redemption, auction, Или deletion process.

1.3 In the event of any inconsistency between this Policy А the applicable registry’s rules Или mАat Илиy ICANN policy, the applicable registry rules А mАat Илиy policy requirements shall предыдущийail.

1.4 The English-language version of this Policy shall control. Any translation is provided f Или convenience only. In the event of any inconsistency, the English-language version shall предыдущийail.

2. Definitions

F Или purposes of this Policy:

2.1 “Expiration Date” means the date on which a Доменное имя name registration term ends.

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

2.3 “Redemption Grace Period” Или “RGP” means the post-deletion recovery period, wздесь available, during which an expired Доменное имя name may still be rest Илиable f Или an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, wздесь applicable, during which the Доменное имя name can no longer be renewed, rest Илиed, modified, Или transferred.

2.5 “Eligible Домен” means a Доменное имя name that is subject to NiceNIC’s expired Доменное имя auction process. Нет!t all TLDs Или expired Доменное имя names are eligible f Или auction.

2.6 “Срок действияd Домен Auction” means the expired-Доменное имя sale process that may apply to certain expired Доменное имя names bef Илиe final deletion Или release.

2.7 “Закрытьout Auction” means the final sale phase f Или certain Eligible Доменами that were not sold earlier in the expired Доменное имя auction process.

3. Effect of Expiration

3.1 Upon expiration, a Доменное имя name may stop resolving, А any website, email обслуживание, Или other обслуживание associated with the Доменное имя name may cease functioning immediately Или sh Илиtly tздесьafter.

3.2 Подписатьсяing expiration, NiceNIC may restrict changes to the Доменное имя name, including DNS changes, contact updates, transfers, Или other account-level actions, in acc Илиdance with registry rules, security measures, operational requirements, Или the expired-Доменное имя process then in effect.

3.3 Expiration does not mean that the Доменное имя name immediately becomes available to the public. Depending on the applicable TLD А registry rules, the Доменное имя name may pass through one Или m Илиe stages, including grace period, auction, redemption, pending delete, А eventual release.

4. Продлениеal Нет!tices А Customer Responsibility

4.1 NiceNIC may send renewal reminders А expiration-related notices bef Илиe А after expiration, as required by applicable policy Или as part of NiceNIC’s stАard operational process.

4.2 It is Твой sole responsibility to maintain accurate А current account А contact inf Илиmation, including Твой email address, А to monit Или the status of Твой Доменное имя names.

4.3 Failure to receive a renewal notice, reminder, invoice, Или other communication shall not relieve you of responsibility f Или renewing Твой Доменное имя name bef Илиe expiration.

4.4 Если auto-renewal is enabled, successful renewal remains subject to valid payment, operational processing, А the applicable registry rules. NiceNIC does not guarantee successful auto-renewal in every case.

5. StАard Post-Expiration Продлениеal

5.1 F Или many generic TLDs, an expired Доменное имя name may remain renewable f Или approximately thirty (30) days after the Expiration Date at the stАard renewal fee. This is a general reference only А may vary by TLD.

5.2 Продлениеal is not complete unless А until NiceNIC has successfully received А processed full payment of all applicable fees.

5.3 NiceNIC reserves the right to determine whether a Доменное имя name remains eligible f Или stАard renewal, redemption, Или other recovery based on the applicable TLD, registry status, auction status, А operational feasibility.

6. Срок действияd Домен Auction f Или Eligible Доменами

6.1 Certain expired Доменное имя names may enter NiceNIC’s expired Доменное имя auction process bef Илиe all recovery окноs have ended. This process applies only to Eligible Доменами А does not apply to all TLDs.

6.2 F Или Eligible Доменами under NiceNIC’s stАard expired-Доменное имя process, the following general timeline may apply:

Day 0 after expiration

The Доменное имя name expires. The registrant may generally renew the Доменное имя name at the stАard renewal fee during the initial post-expiration period, subject to applicable rules.

Day 26 after expiration

The Доменное имя name may enter expired Доменное имя auction. Ат this stage, the registrant may still be able to renew the Доменное имя name at the stАard renewal fee, unless otherwise restricted by the applicable process.

Day 31 after expiration

Если tздесь is no active bid, the registrant may still be able to recover the Доменное имя name by paying the stАard renewal fee plus the applicable redemption fee.

Если tздесь is an active bid, the Доменное имя name may be removed from the registrant’s account А may no longer be renewable through Илиdinary renewal Или rest Илиation procedures.

Day 37 after expiration

The Доменное имя name may enter final closeout auction. Unless tздесь is a pending Покупка Или other sale-related restriction, the registrant may still be able to recover the Доменное имя name by paying the stАard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. Если the Доменное имя name was not sold Или otherwise committed to sale, recovery may still be possible f Или a limited period, subject to the applicable TLD, registry rules, А NiceNIC’s operational process.

Day 74 after expiration

The Доменное имя name may be removed from the registrant’s account А may no longer be renewable Или rest Илиable through NiceNIC. After that point, the Доменное имя name may become available f Или re-registration only after the registry releases it.

6.3 Once an Eligible Домен has an active bid, pending Покупка, completed sale, Или other sale commitment under the expired-Доменное имя process, the registrant’s right to renew Или rest Илиe the Доменное имя name may be terminated Или restricted.

6.4 NiceNIC does not guarantee that a Доменное имя name will remain recoverable until the end of any stated period if the Доменное имя is subject to auction, sale, registry restriction, Или another applicable limitation.

7. Redemption Grace Period

7.1 Если an expired Доменное имя name is not renewed during the applicable grace period А if the applicable TLD supp Илиts rest Илиation after deletion, the Доменное имя name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the Доменное имя name may stop resolving;

(b) website А email обслуживаниеs may remain unavailable;

(c) the Доменное имя name generally cannot be modified Или transferred; А

(d) rest Илиation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, А any taxes Или mАat Илиy fees.

7.3 Rest Илиation during the Redemption Grace Period is not guaranteed А remains subject to registry supp Илиt, operational feasibility, the Доменное имя’s current status, А the absence of auction Или sale restrictions.

8. Pending Delete А Final Release

8.1 Если a Доменное имя name is not renewed Или rest Илиed during the applicable recovery periods, it may enter the Pending Delete stage, wздесь supp Илиted by the applicable TLD.

8.2 During Pending Delete, the Доменное имя name cannot be renewed, rest Илиed, transferred, Или modified.

8.3 F Или many generic TLDs, Pending Delete lasts approximately five (5) days. After that stage ends, the registry may release the Доменное имя name to the public f Или re-registration.

8.4 NiceNIC does not guarantee the exact time, date, Или availability of a Доменное имя name once it is released by the registry, А NiceNIC does not guarantee that the f Илиmer registrant will be able to re-Регистрация the Доменное имя name.

9. TLD-Specific Variations

9.1 Нет!t all TLDs follow the stАard lifecycle described above. Certain ccTLDs А other TLDs may have sh Илиter grace periods, no redemption period, no pending delete stage, Или earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many ccTLDs generally follow a lifecycle similar to the stАard expiration, grace, redemption, А deletion process, including, f Или example:

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

9.2.2 TLDs with no Pending Delete stage

Certain TLDs may not have a Pending Delete stage А may be released immediately after the end of their applicable redemption Или recovery period, including, f Или example:

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

9.2.3 TLDs requiring renewal bef Илиe the actual expiration date

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

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

9.2.4 TLDs requiring action five (5) days bef Илиe expiration

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

.CX, .DE, .EU, А .NL.

9.2.5 .CM Доменное имяs

.CM Доменное имя names generally do not enter a redemption period А may be sent f Или deletion on the actual Expiration Date. They may become available f Или public registration on the same day they expire, subject to registry release practices.

9.2.6 .GG Доменное имяs

.GG Доменное имя names may be reactivated from the customer account f Или approximately twenty-eight (28) days after expiration. They may then enter a recovery stage between approximately Day 28 А Day 30 after expiration. Once in that stage, reactivation may only be possible through NiceNIC Supp Илиt f Или approximately twenty-six (26) additional days.

9.2.7 .PH, .COM.PH, .NET.PH, А .ORG.PH Доменное имяs

These Доменное имяs may not supp Илиt a stАard Redemption Grace Period. Reactivation may still be possible within approximately thirty (30) days after expiration through the NiceNIC account at the regular renewal cost, depending on the registry status. Если the Доменное имя is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Supp Илиt immediately.

9.2.8 .UK Доменное имяs, including second-level .UK Доменное имяs

.UK Доменное имя names, including .CO.UK, .ME.UK, А .ORG.UK, may generally have a thirty (30)-day post-expiration renewal period. After that time, the Доменное имя name may remain recoverable without a separate redemption fee until its release, which may occur approximately ninety (90) days after expiration. Если a .UK Доменное имя name has expired f Или m Илиe than thirty (30) days but has not yet been released А no longer appears in the account, the customer should contact NiceNIC Supp Илиt promptly.

9.2.9 .TO Доменное имяs

.TO Доменное имя names may only be reactivated during approximately twenty-seven (27) days after expiration. They generally do not supp Илиt a stАard Redemption Grace Period. After that point, they may be reserved by the registry А may no longer be recoverable.

9.2.10 .NU Доменное имяs

.NU Доменное имя names may be reactivated in the Илиdinary manner within approximately seven (7) days after expiration. Если not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which rest Илиation may still be possible through NiceNIC Supp Илиt.

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

10. Fees А Выплатыments

10.1 StАard renewal fees, redemption fees, rest Илиation fees, auction-related fees, А any other applicable charges shall be those listed by NiceNIC at the time of processing Или otherwise communicated by NiceNIC.

10.2 Redemption Или rest Илиation requires payment in full of all applicable fees bef Илиe processing.

10.3 Выбрать все fees paid f Или expired-Доменное имя recovery, rest Илиation, Или special processing are non-refundable once processing has begun, except wздесь otherwise required by applicable law.

11. Нет! Guarantee of Recovery Или Availability

11.1 NiceNIC does not guarantee that any expired Доменное имя name can be renewed, rest Илиed, retained, transferred, Или re-Регистрацияed after expiration.

11.2 NiceNIC does not guarantee:

(a) that a Доменное имя name will remain in a grace period f Или any minimum time;

(b) that an expired Доменное имя name will not enter auction;

(c) that a Доменное имя name can be recovered after an active bid, pending Покупка, Или completed sale;

(d) that the registry will supp Илиt rest Илиation; Или

(e) the exact date Или time when a deleted Доменное имя name will be released to the public.

11.3 You ackсейчасledge that delayed action may result in additional fees, loss of recovery rights, interruption of обслуживание, auction sale, Или permanent loss of the Доменное имя name.

12. Limitation of Responsibility

12.1 Б the maximum extent permitted by applicable law, NiceNIC shall not be liable f Или any loss of Доменное имя name, loss of use, interruption of website Или email обслуживание, business interruption, lost profits, loss of data, Или other direct Или indirect damages arising from:

(a) Доменное имя expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules Или registry actions;

(e) auction placement Или sale;

(f) failed rest Илиation; Или

(g) release of the Доменное имя name to the public.

12.2 Нет!thing in this Policy limits any non-waivable rights that may apply under mАat Илиy law.

13. Changes to This Policy

13.1 NiceNIC may update Или revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, Или обслуживание arrangements.

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

14. Контактная информация

Если you need assistance regarding an expired Доменное имя name, renewal, redemption, Или TLD-specific recovery options, please submit a supp Илиt ticket through Твой NiceNIC account Или contact NiceNIC Supp Илиt through the official supp Илиt channels published on the NiceNIC website.

1. General

This Agreement is made between you (здесьinafter referred to as “User”) А NiceNIC.NET (здесьinafter referred to as “the Platf Илиm”). By using the Platf Илиm’s Покупка Нет!w Домен Sales обслуживание, you agree to be bound by the terms А conditions set f Илиth здесьin. Если you do not agree, please do not proceed with any fixed-price Доменное имя Покупка through the Platf Илиm.

2. Service Description

1. The Platf Илиm offers fixed-price Доменное имя names (“Покупка Нет!w Доменами”) f Или direct Покупка.

2. Выбрать все Покупка Нет!w Доменами are sourced from pre-approved third-party Доменное имя providers.

3. Users may Покупка these Доменное имяs at the listed price. Once payment is completed А the Доменное имя is successfully transferred, the Покупкаer will obtain ownership of the Доменное имя.

3. Purchase Process

1. The User selects a Доменное имя labeled as “Покупка Нет!w” А proceeds to checkout.

2. Upon confirmation А full payment, the Platf Илиm initiates the transfer Или delivery process.

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

4. Если, f Или any reason, the selected Доменное имя becomes unavailable Или undeliverable after Покупка, the Platf Илиm will issue a full refund to the user’s account balance.

4. User Rights А Responsibilities

1. Users have the right to Покупка available Покупка Нет!w Доменами through the Platf Илиm.

2. Users must ensure that all provided account А payment inf Илиmation is accurate А lawful.

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

4. Upon acquiring a Доменное имя, the User agrees to comply with the applicable rules А policies of the c Илиresponding Доменное имя registry, including any legal Или regulat Илиy obligations.

5. Platf Илиm Rights А Responsibilities

1. The Platf Илиm will provide Доменное имя transaction обслуживаниеs in acc Илиdance with this Agreement А strive to protect user interests.

2. The Platf Илиm reserves the right to verify user identity, payment legitimacy, А transaction authenticity.

3. The Platf Илиm retains the right to update, adjust, Или remove Покупка Нет!w Доменами from listing at its sole discretion А without pri Или notice.

4. Если any fraudulent Или abusive behavi Или is detected, the Platf Илиm reserves the right to suspend Или terminate обслуживаниеs to the user.

6. Disclaimer

1. The Platf Илиm does not make any guarantees regarding the future value, resale potential, Или commercial use of any Доменное имя Покупкаd.

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

3. The Platf Илиm shall not be held responsible f Или обслуживание interruptions, data loss, Или failed transactions resulting from f Илиce majeure events Или uncontrollable technical issues, though reasonable eff Илиts will be made to assist the User in resolving any such issues.

7. Governing Law А Dispute Resolution

1. This Agreement shall be governed by А construed in acc Илиdance with the laws of Гонконг.

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

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a Покупка Нет!w Доменное имя Илиder.

2. The Platf Илиm reserves the right to amend this Agreement at any time. Обновлено versions will be published on the Platf Илиm’s “Соглашения” page А shall take immediate effect. Continued use of the обслуживание constitutes acceptance of the revised terms.

This Unif Илиm Имя домена Dispute Resolution Policy (the "Policy") has been adopted by the Internet C Илиp Илиation f Или Assigned Имяs А Numbers ("ICANN"), is inc Илиp Илиated by reference into Твой Регистрация Agreement, А sets f Илиth the terms А conditions in connection with a dispute between you А any party other than us (the registrar) over the registration А use of an Internet Доменное имя name Регистрацияed by you. Proceedings under Paragraph 4 of this Policy will be conducted acc Илиding to the Rules f Или Unif Илиm Имя домена Dispute Resolution Policy (the "Rules of Procedure"), which are available здесь, А the selected administrative-dispute-resolution обслуживание provider's supplemental rules.

2. Your Representations

By applying to Регистрация a Доменное имя name, Или by asking us to maintain Или renew a Доменное имя name registration, you здесьby represent А warrant to us that (a) the statements that you made in Твой Регистрация Agreement are complete А accurate; (b) to Твой kсейчасledge, the registration of the Доменное имя name will not infringe upon Или otherwise violate the rights of any third party; (c) you are not Регистрацияing the Доменное имя name f Или an unlawful purpose; А (d) you will not kсейчасingly use the Доменное имя name in violation of any applicable laws Или regulations. It is Твой responsibility to determine whether Твой Доменное имя name registration infringes Или violates someone else's rights.

3. Отменитьlations, Transfers, А Changes

We will cancel, transfer Или otherwise make changes to Доменное имя name registrations under the following circumstances:

1. subject to the provisions of Paragraph 8, our receipt of written Или appropriate electronic instructions from you Или Твой auth Илиized agent to take such action;

2. our receipt of an Илиder from a court Или arбитral tribunal, in each case of competent jurisdiction, requiring such action; А/ Или

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

4. We may also cancel, transfer Или otherwise make changes to a Доменное имя name registration in acc Илиdance with the terms of Твой Регистрация Agreement Или other legal requirements.

4. MАat Илиy Administrative Proceeding

This Paragraph sets f Илиth the type of disputes f Или which you are required to submit to a mАat Илиy administrative proceeding. These proceedings will be conducted bef Илиe one of the administrative-dispute-resolution обслуживание providers listed здесь (each, a "Provider").

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

1. Твой Доменное имя name is identical Или confusingly similar to a trademark Или обслуживание mark in which the complainant has rights; А

2. you have no rights Или legitimate interests in respect of the Доменное имя name; А

3. Твой Доменное имя name has been Регистрацияed А is being used in bad faith.

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

2. Evidence of Регистрация А Use in Плохо Faith. F Или the purposes of Paragraph 4(a)(iii), the following circumstances, in particular but without limitation, if found by the Panel to be present, shall be evidence of the registration А use of a Доменное имя name in bad faith:

1. circumstances indicating that you have Регистрацияed Или you have acquired the Доменное имя name primarily f Или the purpose of selling, renting, Или otherwise transferring the Доменное имя name registration to the complainant who is the owner of the trademark Или обслуживание mark Или to a competit Или of that complainant, f Или valuable consideration in excess of Твой documented out-of-pocket costs directly related to the Доменное имя name; Или

2. you have Регистрацияed the Доменное имя name in Илиder to предыдущийent the owner of the trademark Или обслуживание mark from reflecting the mark in a c Илиresponding Доменное имя name, provided that you have engaged in a pattern of such conduct; Или

3. you have Регистрацияed the Доменное имя name primarily f Или the purpose of disrupting the business of a competit Или; Или

4. by using the Доменное имя name, you have intentionally attempted to attract, f Или commercial gain, Internet users to Твой web site Или other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, spons Илиship, affiliation, Или end Илиsement of Твой web site Или location Или of a product Или обслуживание on Твой web site Или location.

3. How to Demonstrate Your Rights to А Legitimate Interests in the Имя домена in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how Твой response should be prepared. Any of the following circumstances, in particular but without limitation, if found by the Panel to be proved based on its evaluation of all evidence presented, shall demonstrate Твой rights Или legitimate interests to the Доменное имя name f Или purposes of Paragraph 4(a)(ii):

1. bef Илиe any notice to you of the dispute, Твой use of, Или demonstrable preparations to use, the Доменное имя name Или a name c Илиresponding to the Доменное имя name in connection with a bona fide offering of goods Или обслуживаниеs; Или

2. you (as an individual, business, Или other Илиganization) have been commonly kсейчасn by the Доменное имя name, even if you have acquired no trademark Или обслуживание mark rights; Или

3. you are making a legitimate noncommercial Или fair use of the Доменное имя name, without intent f Или commercial gain to misleadingly divert consumers Или to tarnish the trademark Или обслуживание mark at issue.

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

5. Initiation of Proceeding А Process А Appointment of Administrative Panel. The Rules of Procedure state the process f Или initiating А conducting a proceeding А f Или appointing the panel that will decide the dispute (the "Administrative Panel").

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

7. Fees. Выбрать все fees charged by a Provider in connection with any dispute bef Илиe an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wздесь you elect to expА the Administrative Panel from one to three panelists as provided in Paragraph 5(b)(iv) of the Rules of Procedure, in which case all fees will be split evenly by you А the complainant.

8. Наш Involvement in Administrative Proceedings. We do not, А will not, participate in the administration Или conduct of any proceeding bef Илиe an Administrative Panel. In addition, we will not be liable as a result of any decisions rendered by the Administrative Panel.

9. Remedies. The remedies available to a complainant pursuant to any proceeding bef Илиe an Administrative Panel shall be limited to requiring the cancellation of Твой Доменное имя name Или the transfer of Твой Доменное имя name registration to the complainant.

10. Нет!tification А Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a Доменное имя name you have Регистрацияed with us. Выбрать все decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact p Илиtions of its decision.

11. Availability of Court Proceedings. The mАat Илиy administrative proceeding requirements set f Илиth in Paragraph 4 shall not предыдущийent either you Или the complainant from submitting the dispute to a court of competent jurisdiction f Или independent resolution bef Илиe such mАat Илиy administrative proceeding is commenced Или after such proceeding is concluded. Если an Administrative Panel decides that Твой Доменное имя name registration should be canceled Или transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are inf Илиmed by the applicable Provider of the Administrative Panel's decision bef Илиe implementing that decision. We will then implement the decision unless we have received from you during that ten (10) business day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that you have commenced a lawsuit against the complainant in a jurisdiction to which the complainant has submitted under Paragraph 3(b)(xiii) of the Rules of Procedure. (In general, that jurisdiction is either the location of our principal office Или of Твой address as shown in our Вайс. 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 Вайс. 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 Вайс. 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 Вайс. output f Или the date the transfer was initiated
      c. Relevant hist Илиy of Вайс. 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 Вайс. 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 Вайс., 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 Вайс. 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 Вайс. is not accessible Или invalid, the Registry Operat Или's Вайс. should be used. In the case of a thin Registry, if the Регистратор of Rec Илиd's Вайс. 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 Вайс. 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 Вайс. 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 Вайс., 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 Вайс. 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 Вайс. is not accessible Или invalid, the applicable Registry Operat Или's Вайс. should be used. In the case of a thin Registry, if the Регистратор of Rec Илиd's Вайс. 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 Вайс. 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 Вайс. 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 Вайс. 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 Вайс. 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 Вайс. 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