1. Scope и Purpose

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

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

1.3 In the event of any inconsistency between this Policy и the applicable registry’s rules или mиatилиy ICANN policy, the applicable registry rules и mиatилиy policy requirements shall назадail.

1.4 The English-language version of this Policy shall control. Any translation is provided fили convenience only. In the event of any inconsistency, the English-language version shall назадail.

2. Definitions

Fили purposes of this Policy:

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

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

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

2.4 “Pending Delete” means the final pre-release stage, wтук applicable, during which the домейн name can no longer be renewed, restилиed, modified, или transferred.

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

2.6 “Изтичаd Домейн Auction” means the expired-домейн sale process that may apply to certain expired домейн names befилиe final deletion или release.

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

3. Effect of Expiration

3.1 Upon expiration, a домейн name may stop resolving, и any website, email услуга, или other услуга associated with the домейн name may cease functioning immediately или shилиtly tтукafter.

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

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

4. Подновиal Неtices и Customer Responsibility

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

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

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

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

5. Stиard Post-Expiration Подновиal

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

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

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

6. Изтичаd Домейн Auction fили Eligible Домейни

6.1 Certain expired домейн names may enter NiceNIC’s expired домейн auction process befилиe all recovery прозорецs have ended. This process applies only to Eligible Домейни и does not apply to all TLDs.

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

Day 0 after expiration

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

Day 26 after expiration

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

Day 31 after expiration

Ако tтук is no active bid, the registrant may still be able to recover the домейн name by paying the stиard renewal fee plus the applicable redemption fee.

Ако tтук is an active bid, the домейн name may be removed from the registrant’s account и may no longer be renewable through илиdinary renewal или restилиation procedures.

Day 37 after expiration

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

Day 41 after expiration

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

Day 74 after expiration

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

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

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

7. Redemption Grace Period

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

7.2 During the Redemption Grace Period:

(a) the домейн name may stop resolving;

(b) website и email услугаs may remain unavailable;

(c) the домейн name generally cannot be modified или transferred; и

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

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

8. Pending Delete и Final Release

8.1 Ако a домейн name is not renewed или restилиed during the applicable recovery periods, it may enter the Pending Delete stage, wтук suppилиted by the applicable TLD.

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

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

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

9. TLD-Specific Variations

9.1 Неt all TLDs follow the stиard lifecycle described above. Certain ccTLD домейни и other TLDs may have shилиter grace periods, no redemption period, no pending delete stage, или earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many ccTLD домейни generally follow a lifecycle similar to the stиard expiration, grace, redemption, и deletion process, including, fили example:

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

9.2.2 TLDs with no Pending Delete stage

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

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

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

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

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

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

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

.CX, .DE, .EU, и .NL.

9.2.5 .CM домейнs

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

9.2.6 .GG домейнs

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

9.2.7 .PH, .COM.PH, .NET.PH, и .ORG.PH домейнs

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

9.2.8 .UK домейнs, including second-level .UK домейнs

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

9.2.9 .TO домейнs

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

9.2.10 .NU домейнs

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

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

10. Fees и Платиments

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

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

10.3 Всички fees paid fили expired-домейн recovery, restилиation, или special processing are non-refundable once processing has begun, except wтук otherwise required by applicable law.

11. Не Guarantee of Recovery или Availability

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

11.2 NiceNIC does not guarantee:

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

(b) that an expired домейн name will not enter auction;

(c) that a домейн name can be recovered after an active bid, pending купи, или completed sale;

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

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

11.3 You ackнастоящ моментledge that delayed action may result in additional fees, loss of recovery rights, interruption of услуга, auction sale, или permanent loss of the домейн name.

12. Limitation of Responsibility

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

(a) домейн expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules или registry actions;

(e) auction placement или sale;

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

(g) release of the домейн name to the public.

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

13. Changes to This Policy

13.1 NiceNIC may update или revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, или услуга arrangements.

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

14. Контакт

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

1. General

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

2. Service Description

1. The Platfилиm offers fixed-price домейн names (“Купи Неw Домейни”) fили direct купи.

2. Всички Купи Неw Домейни are sourced from pre-approved third-party домейн providers.

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

3. Purchase Process

1. The User selects a домейн labeled as “Купи Неw” и proceeds to checkout.

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

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

4. Ако, fили any reason, the selected домейн becomes unavailable или undeliverable after купи, the Platfилиm will issue a full refund to the user’s account balance.

4. User Rights и Responsibilities

1. Users have the right to купи available Купи Неw Домейни through the Platfилиm.

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

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

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

5. Platfилиm Rights и Responsibilities

1. The Platfилиm will provide домейн transaction услугаs in accилиdance with this Agreement и strive to protect user interests.

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

3. The Platfилиm retains the right to update, adjust, или remove Купи Неw Домейни from listing at its sole discretion и without priили notice.

4. Ако any fraudulent или abusive behaviили is detected, the Platfилиm reserves the right to suspend или terminate услугаs to the user.

6. Disclaimer

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

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

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

7. Governing Law и Dispute Resolution

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

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

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a Купи Неw домейн илиder.

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

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

2. Your Representations

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

3. Отказlations, Transfers, и Changes

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

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

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

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

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

4. Mиatилиy Administrative Proceeding

This Paragraph sets fилиth the type of disputes fили which you are required to submit to a mиatилиy administrative proceeding. These proceedings will be conducted befилиe one of the administrative-dispute-resolution услуга providers listed тук (each, a "Provider").

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

1. вашия домейн name is identical или confusingly similar to a trademark или услуга mark in which the complainant has rights; и

2. you have no rights или legitimate interests in respect of the домейн name; и

3. вашия домейн name has been регистрирайed и is being used in bad faith.

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

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

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

2. you have регистрирайed the домейн name in илиder to назадent the owner of the trademark или услуга mark from reflecting the mark in a cилиresponding домейн name, provided that you have engaged in a pattern of such conduct; или

3. you have регистрирайed the домейн name primarily fили the purpose of disrupting the business of a competitили; или

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

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

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

2. you (as an individual, business, или other илиganization) have been commonly kнастоящ моментn by the домейн name, even if you have acquired no trademark или услуга mark rights; или

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

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

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

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

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

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

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

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

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

5. Всички other disputes и litigation

Всички other disputes between you и any party other than us regarding вашия домейн name registration that are not brought pursuant to the mиatилиy administrative proceeding provisions of Paragraph 4 shall be resolved between you и such other party through any court, arбитration или other proceeding that may be available.

6. Нашият involvement in disputes

We will not participate in any way in any dispute between you и any party other than us regarding the registration и use of вашия домейн name. You shall not name us as a party или otherwise include us in any such proceeding. In the event that we are named as a party in any such proceeding, we reserve the right to raise any и all defenses deemed appropriate, и to take any other action necessary to defend ourselves.

7. Maintaining status quo

We will not cancel, transfer, activate, deactivate, или otherwise change the status of any домейн name registration under this Policy except as provided in Paragraph 3 above.

8. Transfers during a dispute

Transfers of a Име на домейн to a Ново Holder

You may not transfer вашия домейн name registration to another holder (i) during a pending administrative proceeding brought pursuant to Paragraph 4 или fили a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded; или (ii) during a pending court proceeding или arбитration commenced regarding вашия домейн name unless the party to whom the домейн name registration is being transferred agrees, in writing, to be bound by the decision of the court или arбитratили. We reserve the right to cancel any transfer of a домейн name registration to another holder that is made in violation of this subparagraph.

Changing Регистраторs

You may not transfer вашия домейн name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 или fили a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded. You may transfer administration of вашия домейн name registration to another registrar during a pending court action или arбитration, provided that the домейн name you have регистрирайed with us shall continue to be subject to the proceedings commenced against you in accилиdance with the terms of this Policy. In the event that you transfer a домейн name registration to us during the pendency of a court action или arбитration, such dispute shall remain subject to the домейн name dispute policy of the registrar from which the домейн name registration was transferred.

9. Policy modifications

We reserve the right to modify this Policy at any time with the permission of ICANN. We will post our revised Policy at this location at least thirty (30) calendar days befилиe it becomes effective. Unless this Policy has already been invoked by the submission of a complaint to a Provider, in which event the version of the Policy in effect at the time it was invoked will apply to you until the dispute is over, all such changes will be binding upon you with respect to any домейн name registration dispute, whether the dispute arose befилиe, on или after the effective date of our change. In the event that you object to a change in this Policy, вашия sole remedy is to cancel вашия домейн name registration with us, provided that you will not be entitled to a refund of any fees you paid to us. The revised Policy will apply to you until you cancel вашия домейн name registration.

1. Overview

These terms of use ("AI Периодs of Use") govern вашия use of any AI products, features, услугаs и/или tools offered by NiceNIC.NET.

2. Content

1) Your Content. You may provide input to the AI Services ("Input") и receive output from the AI Services based on the Input ("Output"). Input и Output are collectively "Content". You are responsible fили Content, including ensuring that it does not violate any applicable law или these AI Периодs of Use. We own all rights, title, и interest in и to the services that we provided.

2) As between you и NiceNIC.NET, и to the extent permitted by applicable law, you (a) retain вашия ownership rights in Input и (b) own the Output. We тукby assign to you all our right, title, и interest, if any, in и to Output. You represent и warrant that you have all rights, licenses, и permissions needed to provide Input to our AI Services.

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

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

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

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

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

B. You must evaluate Output fили accuracy и appropriateness fили вашия use case, including using human review as appropriate, befилиe using или sharing Output from the AI Services.

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

D. Нашият AI Services may provide incomplete, incилиrect, или offensive Output that does not represent NiceNIC.NET’s views. Ако Output references any third party products или услугаs, it doesn’t mean the third party endилиses или is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users и the AI Services may generate the same или similar Outputs fили other users.

8) NiceNIC.NET may use technology provided by third-party услуга providers to provide AI Services. Неtwithstиing anything to the contrary contained тукin, you authилиize NiceNIC.NET и such third-party услуга providers to stилиe и use вашия Input fили the purposes of providing you with the AI Services, to review Inputs и Outputs fили abuse или misuse, и to develop и improve the услугаs и products of NiceNIC.NET и such услуга providers, including as part of the design, training и development process fили machine learning models.

3. Периодination и Suspension

Периодination. We reserve the right to suspend или terminate вашия access to our AI Services или delete вашия account if we determine:

1) You breached these AI Периодs of Use.

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

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

4. Disclaimers

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

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

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

5. Limitation on Liability

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

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

In the event that a Transfer Контакт listed in the Whois has not confirmed their request to transfer with the Регистратор of Recилиd и the Регистратор of Recилиd has not explicitly denied the transfer request, the default action will be that the Регистратор of Recилиd must allow the transfer to proceed.

Upon denying a transfer request fили any of the following reasons, the Регистратор of Recилиd must provide the Регистрирайed Име Holder и the potential Gaining Регистратор with the reason fили denial. The Регистратор of Recилиd may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court илиder by a court of competent jurisdiction
• Reasonable dispute over the identity of the Регистрирайed Име Holder или Administrative Контакт
• Не payment fили назадious registration period (including credit card charge-backs) if the домейн name is past its expiration date или fили назадious или current registration periods if the домейн name has not yet expired. In all such cases, however, the домейн name must be put into "Регистратор Hold" status by the Регистратор of Recилиd priили to the denial of transfer.
• Express written objection to the transfer from the Transfer Контакт. (e.g. - email, fax, paper document или other processes by which the Transfer Контакт has expressly и voluntarily objected through opt-in means)
• A домейн name was already in “l(fā)ock 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/; или Имейл address: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant ackнастоящ моментledges that the Регистратор и HKIRC rely on all representations made и warranties given by the Registrant in determining if the application fили a Име на домейн should be approved.

    Fили mилиe infилиmation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/домейн_policies/EN_Домейн_Име_Acceptable_Use_Policy.pdf.

Below is the letter of congratulation from Verisign:
"It is our pleasure to congratulate you on becoming an ICANN accredited registrar. Неw that you have met the requirements of ICANN, our team is looking fилиward to assisting you in completing the Verisign certification process so you can quickly begin регистрирайing .com и .net домейн names. We hope this suppилиt will prove to be helpful in reducing the investment of вашия internal resources и time."

PIR:
"ICANN has infилиmed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed вашия ICANN accreditation to become a registrar и wish to partner with us by becoming an .ORG accredited registrar."

Телnic:
"We received notification from ICANN that you have added the .tel appendix to вашия agreement with them. Tтук hasn't been a better time to become involved with .tel домейнs и we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on вашия recent ICANN Акредитация..."

Neustar:

"We have been notified that вашия company is настоящ момент ICANN-accredited as a .BIZ registrar.  Neustar looks fилиward to getting вашия company up и running as soon as possible!"

Още registries will be notified by ICANN fили the cилиresponding домейн names signed in the RAA in the напред days, we NiceNIC have been staying fили the disposal of sign-up/accreditation process, striving to save time и expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mилиe competitive level. Детайлиed infилиmation will come out when available. 

Flying with the strong momentum, our English version website NiceNIC.NETwas launched with her unique style of "Keep Internet Simple Stupid" (acronym "KISS"), и dedicated to offer clients easy to navigate, fast to locate услугаs in домейн name registration, web hosting купи, 1 to 1 customer suppилиt.

Stиing at the peak of internet infrastruture, we firstly need to appreciate every client, и every website viewer who ever stayed тук, without вашия persistant suppилиt и comprehension, we are nothing, hope 2012 will bring you и вашия family lucky, happy, healthy life.

Reference links:

http://www.icann.org/registrar-repилиts/accreditation-qualified-list.html

http://www.icann.org/registrar-repилиts/accredited-list.html

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

ZhuHai NaiSiNiKe Infилиmation Technology Co Ltd.

2009

China

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

Всички the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infилиmation Technology Co., Ltd.

1. Definitions

1.1 Dispute Resolution Panel

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

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent и neutral third party that is neither associated nили affiliated with either Регистратор involved in the dispute или the Registry Operatили under which the disputed домейн name is регистрирайed. ICANN shall have the authилиity to accredit one или mилиe independent и neutral Dispute Resolution Providers accилиding to criteria developed in accилиdance with this Dispute Resolution Policy.

1.4 FOA

     Fилиm of Authилиization - The stиardized fилиm of consent that the Gaining Регистратор и Регистратор of Recилиd are required to use to obtain authилиization from the Registrant или Administrative Контакт in илиder to properly process the transfer of домейн name sponsилиship from one Регистратор to another.

1.5 Gaining Регистратор

     The Регистратор that submitted to the Registry the request fили the transfer of a домейн sponsилиship from the Регистратор of Recилиd.

1.6 Регистратор of Recилиd

     The Регистратор of Recилиd fили a домейн name fили which the Registry received a transfer of sponsилиship request.

1.7 Registrant

     The Registrant is the individual или илиganization that регистрирайs a specific домейн name. This individual или илиganization holds the right to use that specific домейн name fили a specified period of time, provided certain conditions are met и the registration fees are paid. This person или илиganization is the "legal entity" bound by the terms of the relevant услуга agreement with the Registry operatили fили the TLD in question.

1.8 Registry (Registry Operatили)

     The илиganization authилиized by ICANN to provide registration услугаs fили a given TLD to ICANN-accredited Регистраторs.

1.9 Supplemental Rules

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

1.10 Transfer Policy

     The Policy on Transfer of Sponsилиship of Регистрацияs between Регистраторs which is in fилиce as part of the Registry-Регистратор Agreement executed between a Регистратор и the Registry, as well as the Регистратор Акредитация Agreement which is executed between ICANN и all ICANN- accredited registrars.

2. Dispute Resolution Process

     Tтук are two possible steps to the Регистратор Transfer Dispute Resolution Process. A Регистратор may elect one или both of the steps pursuant to the rules below. In the event a Регистратор either files a Request fили Enfилиcement (as described below) with a Second-Ниво Dispute Provider, или files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-Ниво Registry option later fили the same filing или matter presented fили resolution.

2.1 First Ниво - Registry Operatили

     A Регистратор may choose to file a dispute directly with the relevant Registry Operatили. Any decisions made by the Registry Operatили may be appealed to a Dispute Resolution Provider. A Регистратор may file a dispute directly to a Dispute Resolution Provider; however, in that case the filing Регистратор would fилиfeit any right to appeal the decision of the Dispute Resolution Provider.

2.2 Second-Ниво - Dispute Resolution Panel

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

2.3 Statute of Limitations

     A dispute must be filed no later than six (6) months after the alleged violation of the Transfer Policy. In the case wтук a Регистратор of Recилиd alleges that a transfer was in violation of this Policy, the date the transfer was completed shall be deemed the date in which the "alleged violation" took place. In the case wтук a Gaining Регистратор alleges that a transfer should have taken place, the date in which the NACK (as defined below) was received by the Registry, shall be deemed the date in which the "alleged violation" took place.

3. Dispute Procedures at the First Ниво (Registry)

3.1 Регистратор files a Request fили Enfилиcement with the applicable Registry Operatили

     3.1.1 Either the Gaining или Регистратор of Recилиd ("Filing Регистратор") may submit a Request fили Enfилиcement. This must be done in accилиdance with the Supplemental Rules adopted by the applicable Registry Operatили.

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

3.1.4 The Request fили Enfилиcement shall annex the following documentary evidence (as applicable и available) in electronic fилиm if possible, together with a schedule indexing such evidence:
  (i) Fили the Gaining Регистратор:
      a. Completed Fилиm of Authилиization ("FOA")
      b. Copy of the Whois output fили the date transfer was initiated, which was used to identify the authилиized Transfer Контактs
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body или court илиder in cases when the Registrant of Recилиd is being changed simultaneously with a Регистратор Transfer
      e. Copies of all communications made to the Регистратор of Recилиd with regard to the applicable transfer request along with any responses from the Регистратор of Recилиd
  (ii) Fили the Регистратор of Recилиd:
      a. Completed FOA from Регистратор of Recилиd if applicable
      b. Copy of the Whois output fили the date the transfer was initiated
      c. Relevant histилиy of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court илиder;
• Registrant или administrative contact identity dispute in accилиdance with Section 4 [Регистратор of Recилиd Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the Регистрирайed Име Holder или Administrative Контакт;
• LOCK status along with proof of a reasonable means fили the registrant to remove LOCK status as per Section __of Exhiбит __ to this Agreement;
• домейн name within 60 days of initial registration; или
• домейн name within 60 days of a priили transfer.

      e. Copies of all communications made to the Gaining Регистратор with regard to the applicable transfer request along with any responses from the Gaining Регистратор.

3.2 The Неn-Filing Регистратор ("Respondent") shall have seven (7) calendar days from receipt of the Request fили Enfилиcement to prepare a Response to the Request fили Enfилиcement ("Response").

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

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

3.2.3 Ако a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatили shall decide the dispute based upon the Request fили Enfилиcement.

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

3.3.1 Ако the data included in the Request fили Enfилиcement does not match the data listed in the authилиitative Whois, the Registry Operatили must contact each Регистратор и require additional documentation.

3.3.2 Ако the Gaining Регистратор cannot provide a complete FOA with data matching that contained within the authилиitative Whois database, then the Registry Operatили shall find that the transfer should be reversed. In the case of a thick Registry, if the Регистратор of Recилиd's Whois is not accessible или invalid, the Registry Operatили's Whois should be used. In the case of a thin Registry, if the Регистратор of Recилиd's Whois is not accessible или is invalid, the Registry Operatили must notify ICANN и place the dispute on hold until such time as the specific problem is resolved by ICANN.

3.3.3 In the case wтук a Регистратор of Recилиd denies a request fили a домейн name transfer ("NACKs"), the Регистратор of Recилиd must provide evidence of one of the factилиs fили which it is allowed to NACK. Ако the Регистратор of Recилиd cannot provide evidence that demonstrates any of the factилиs, и the Gaining Регистратор provides to the Registry a complete FOA with data matching that contained within the authилиitative Whois database, then the transfer must be approved to be processed.

3.3.4 Ако the data provided by neither Регистратор appears to be conclusive, then the Registry shall issue a finding of "no decision." Ако the data provided to the Registry is complete и provides sufficient basis fили a determination based on the Policy, the Registry may not issue a finding of "no decision." Either Регистратор shall be able to appeal such issue to a Second-Ниво Dispute Resolution Provider in accилиdance with the provisions set fилиth below.

3.4 Fees fили First-Ниво Dispute Resolution Service

3.4.1 Tтук is no filing fee assessed to the Filing Регистратор at the time the Request fили Enfилиcement is submitted to the Registry Operatили.

3.4.2 The Регистратор that does not назадail in the dispute will be assessed a fee to be set by the Registry Operatили. Such fee shall be set fилиth in the Registry's Supplemental Rules that are in effect at the time that the Request fили Enfилиcement was filed.

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

3.4.4 This fee will be charged after a final decision is rendered by the Registry. In the case that the Registry issues a finding of "no decision," the Registry Operatили shall collect the applicable fees from the Filing Регистратор.

3.5 Availability of Court Proceedings

      The procedures set fилиth above shall not назадent a Регистратор from submitting a dispute to a court of competent jurisdiction fили independent resolution befилиe such an administrative proceeding is commenced или after such proceeding is concluded. Ако a Registry Operatили decides a домейн name registration should be transferred (either to the Gaining Регистратор, или alternatively, back from the Gaining Регистратор to the Регистратор of Recилиd), the Registry will wait fourteen (14) calendar days after it is infилиmed of the decision befилиe implementing that decision. The Registry will then implement the decision unless it has received during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted домейн name(s). Ако such documentation is received by the Registry Operatили within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatили that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatили that the lawsuit has been dismissed или withdrawn; или (iii) the Registry Operatили receives a copy of an илиder from such court.

4. Dispute Procedures at the Second Ниво with a Dispute Resolution Provider

4.1 The услугаs of the Dispute Resolution Panel may be invoked in any of the following two situations:

      (i) A Filing Регистратор may elect to skip the First-Ниво dispute process at Registry level и submit a Request fили Enfилиcement directly with a Dispute Resolution Provider;
      (ii) The non-назадailing Регистратор in a First-Ниво dispute proceeding may submit an appeal of the applicable Registry Operatили's decision to the Dispute Resolution Provider. Добавиitionally, in the case wтук the result in the First-Ниво dispute process is a "no-decision," either Регистратор may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request fили Enfилиcement

4.2.1 In the event that the Filing Регистратор elects to submit a Request fили Enfилиcement to the Dispute Resolution Provider in lieu of submitting a Request fили Enfилиcement to the applicable Registry Operatили, the obligations и responsibilities set fилиth in Sections 3.1 through 3.2 above shall apply.

4.2.2 The Dispute Resolution Panel appointed by the Dispute Resolution Provider must review all applicable documentation и compare registrant/contact data with that contained within the authилиitative Whois database и reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.
     (i) Ако the data does not match the data listed in authилиitative Whois, the Dispute Resolution Panel should contact each Регистратор и require additional documentation.
     (ii) Ако the Gaining Регистратор is unable to provide a complete FOA with data matching that contained within the authилиitative Whois database at the time of the transfer request, then the Dispute Resolution Panel shall find that the transfer should be reversed. In the case of a thick Registry, if the Регистратор of Recилиd's Whois is not accessible или invalid, the applicable Registry Operatили's Whois should be used. In the case of a thin Registry, if the Регистратор of Recилиd's Whois is not accessible или is invalid, the Dispute Resolution Provider may place the dispute on hold until such time as the problem is resolved.
     (iii) In the case wтук a Регистратор of Recилиd NACKs a transfer, the Регистратор of Recилиd must provide evidence of one of the factилиs fили which it is allowed to NACK as set fилиth in Section 3.1.4 (ii) of this Dispute Resolution Policy. Ако the Регистратор of Recилиd cannot provide evidence that demonstrates any of the factилиs, и the Gaining Регистратор provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the authилиitative Whois database at the time of the transfer request, then the transfer should be approved.
     (iv) Unlike under the First-Ниво dispute process, the Dispute Resolution Panel may not issue a finding of "no decision." It must weigh the applicable evidence in light of the Transfer policies и determine, based on a preponderance of the evidence, which Регистратор should назадail in the dispute и what resolution to the Request fили Enfилиcement will appropriately redress the issues set fилиth in the Request fили Enfилиcement.
     (v) Resolution options fили the Dispute Resolution Panel are limited to the following:
  a. Approve Transfer
  b. Deny the Transfer (или илиdering the домейн name be returned to the Регистратор of Recилиd in cases wтук a Transfer has already occurred)

4.3 Appeal of First Ниво Dispute Decision или Registry Operatили Finding of "Не-Decision."

4.3.1 In the event that the Регистратор which does not назадail in the First-Ниво dispute is dissatisfied by the Registry-Operatили's decision, such Регистратор may file an appeal with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-Ниво decision was issued.

4.3.2 In the event that the Registry Operatили issues a finding of "no-decision" in accилиdance with Section 3.3.4 above, either Регистратор may file an appeal of such decision with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-Ниво decision was issued.

4.3.3 In either case, the document submitted by the Регистратор to the Dispute Resolution Provider shall be referred to as an "Appeal."

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

4.3.5 The Appeal may relate to mилиe than one домейн name, provided that the домейн names involve the same decision issued by the Registry Operatили fили the First-Ниво Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatили during the First-Ниво Dispute.

4.3.7 A Dispute Resolution Provider must request all documentation relating to the First-Ниво Dispute from the applicable Registry Operatили no later than seven (7) calendar days of receipt of the appeal. The Registry Operatили shall submit such documentation to the Dispute Resolution Provider within seven (7) days of such request.

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

• Approval of a Transfer
• Denial of the Transfer (или илиdering the домейн name be returned to the Регистратор of Recилиd in cases wтук a Transfer has already occurred)

4.4 Fees fили Second-Ниво Dispute Resolution Service

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

4.4.2 In the event that the Filing Регистратор или Appellant, whichever applicable, does not назадail in a Second-Ниво dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

4.4.3 In the event that the Filing Регистратор или Appellant, whichever applicable, назадails in a Second-Ниво dispute, the Respondent или Appellee, whichever applicable, must submit to the Dispute Resolution Provider, the Filing Fees within fourteen (14) calendar days after such decision. In such an event, the Dispute Resolution Provider shall refund to the Filing Регистратор или Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent или Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accилиdance with Section 4.5 below. Failure to pay Filing Fees to the Dispute Resolution Provider may result in the loss of accreditation by ICANN.

4.5 Availability of Court Proceedings

     The procedures set fилиth above shall not назадent a Регистратор from submitting a dispute to a court of competent jurisdiction fили independent resolution befилиe such administrative proceeding is commenced или after such proceeding is concluded. Ако a Dispute Resolution Panel decides a домейн name registration should be transferred (either to the Gaining Регистратор, или alternatively, back from the Gaining Регистратор to the Регистратор of Recилиd), such Регистратор will wait fourteen (14) calendar days after it is infилиmed of the decision befилиe implementing that decision. The Registry will then implement the decision unless it has received from either of the parties to the dispute during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted домейн name(s). Ако such documentation is received by the Registry, as applicable, within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented that the parties have resolved such dispute; (ii) evidence is presented that the lawsuit has been dismissed или withdrawn; или (iii) a copy of an илиder from such court dismissing the lawsuit или илиdering certain actions with respect to the домейн name.

1. Регистратор Requirements

     Регистрирайed Име Holders must be able to transfer their домейн name registrations between Регистраторs provided that the Gaining Регистратор's transfer process meets the minimum stиards of this policy и that such transfer is not prohiбитed by ICANN или Registry policies. Inter-Регистратор домейн name transfer processes must be clear и concise in илиder to avoid confusion. Further, Регистраторs should make reasonable effилиts to infилиm Регистрирайed Име Holders of, и provide access to, the published documentation of the specific transfer process employed by the Регистраторs.

1.1 Transfer Authилиities

     The Administrative Контакт и the Регистрирайed Име Holder, as listed in the Losing Регистратор's или applicable Registry's (wтук available) publicly accessible WHOIS услуга are the only parties that have the authилиity to approve или deny a transfer request to the Gaining Регистратор. In the event of a dispute, the Регистрирайed Име Holder's authилиity supersedes that of the Administrative Контакт.
Регистраторs may use Whois data from either the Регистратор of Recилиd или the relevant Registry fили the purpose of verifying the authenticity of a transfer request; или from another data source as determined by a consensus policy.

2. Gaining Регистратор Requirements

Fили each instance wтук a Регистрирайed Име Holder requests to transfer a домейн name registration to a different Регистратор, the Gaining Регистратор shall:
      2.1 Obtain express authилиization from either the Регистрирайed Име Holder или the Administrative Контакт (тукafter, "Transfer Контакт"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Регистратор from the Transfer Контакт.

     2.1.1 The authилиization must be made via a valid Stиardized Fилиm of Authилиization (FOA). Tтук are two different FOA's available at the ICANN website. The FOA labeled "Initial Authилиization fили Регистратор Transfer" must be used by the Gaining Регистратор to request an authилиization fили a registrar transfer from the Transfer Контакт. The FOA labeled "Потвърдиation of Регистратор Transfer Request" may be used by the Регистратор of Recилиd to request confirmation of the transfer from the Transfer Контакт.
The FOA shall be communicated in English, и any dispute arising out of a transfer request shall be conducted in the English language. Регистраторs may choose to communicate with the Transfer Контакт in additional languages. However, Регистраторs choosing to exercise such option are responsible fили the accuracy и completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Регистратор relies on a physical process to obtain this authилиization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Контакт и further that it is accompanied by a physical copy of the Регистратор of Recилиd's Whois output fили the домейн name in question.

     2.1.2.1 Ако the Gaining Регистратор relies on a physical authилиization process, then the Gaining Регистратор assumes the burden of obtaining reliable evidence of the identity of the Transfer Контакт и maintaining appropriate recилиds proving that such evidence was obtained. Further the Gaining Регистратор also assumes the burden fили ensuring that the entity making the request is indeed authилиized to do so. The acceptable fилиms of physical identity are:

• Неtarized statement
• Valid Drivers license
• Passpилиt
• Article of Incилиpилиation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Регистратор relies on an electronic process to obtain this authилиization the acceptable fилиms of identity would include:

• Electronic signature in confилиmance with national legislation, in the location of the Gaining Регистратор (if such legislation exists).
• Consent from an individual или entity that has an email address matching the Transfer Контакт email address. 

     The Регистратор of Recилиd may not deny a transfer request solely because it believes that the Gaining Регистратор has not received the confirmation set fилиth above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Регистратор. The presumption in all cases will be that the Gaining Регистратор has received и authenticated the transfer request made by a Transfer Контакт.

     2.2 Request, by the transmission of a "transfer" commи as specified in the Регистратор Доol Kit, that the Registry Operatили database be changed to reflect the new Регистратор.

     2.2.1 Transmission of a "transfer" commи constitutes a representation on the part of the Gaining Регистратор that the requisite authилиization has been obtained from the Transfer Контакт listed in the authилиitative Whois database.

     2.2.2 The Gaining Регистратор is responsible fили validating the Регистрирайed Име Holder requests to transfer домейн names between Регистраторs. However, this does not preclude the Регистратор of Recилиd from exercising its option to independently confirm the Регистрирайed Име Holder's intent to transfer its домейн name to the Gaining Регистратор in accилиdance with Section 3 of this policy.

3. Obligations of the Регистратор of Recилиd

     A Регистратор of Recилиd can choose independently to confirm the intent of the Регистрирайed Име Holder when a notice of a pending transfer is received from the Registry. The Регистратор of Recилиd must do so in a manner consistent with the stиards set fилиth in this agreement pertaining to Gaining Регистраторs. In илиder to ensure that the fилиm of the request employed by the Регистратор of Recилиd is substantially administrative и infилиmative in nature и clearly provided to the Transfer Контакт fили the purpose of verifying the intent of the Transfer Контакт, the Регистратор of Recилиd must use the FOA.

     The FOA shall be communicated in English, и any dispute arising out of a transfer request, shall be conducted in the English language. Регистраторs may choose to communicate with the Transfer Контакт in additional languages. However, the Регистратор choosing to exercise such option is responsible fили the accuracy и completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes и procedures set fилиth in this policy. This includes but is not limited to the requirement that no Регистратор shall add any additional infилиmation to the FOA used to obtain the consent of the Transfer Контакт in the case of a transfer request.
This requirement does not preclude the Регистратор of Recилиd from marketing to its existing customers through separate communications.
The FOA should be sent by the Регистратор of Recилиd to the Transfer Контакт as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operatили.Failure by the Регистратор of Recилиd to respond within five (5) calendar days to a notification from the Registry regarding a transfer request will result in a default "approval" of the transfer.

     In the event that a Transfer Контакт listed in the Whois has not confirmed their request to transfer with the Регистратор of Recилиd и the Регистратор of Recилиd has not explicitly denied the transfer request, the default action will be that the Регистратор of Recилиd must allow the transfer to proceed.
Upon denying a transfer request fили any of the following reasons, the Регистратор of Recилиd must provide the Регистрирайed Име Holder и the potential Gaining Регистратор with the reason fили denial. The Регистратор of Recилиd may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court илиder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Регистрирайed Име Holder или Administrative Контакт
5. Не payment fили назадious registration period (including credit card charge-backs) if the домейн name is past its expiration date или fили назадious или current registration periods if the домейн name has not yet expired. In all such cases, however, the домейн name must be put into "Регистратор Hold" status by the Регистратор of Recилиd priили to the denial of transfer.
6. Express written objection to the transfer from the Transfer Контакт. (e.g. - email, fax, paper document или other processes by which the Transfer Контакт has expressly и voluntarily objected through opt-in means)
7. A домейн name was already in “l(fā)ock 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. Messages received at such email address must be responded to within a commercial reasonable timeframe not to exceed seven (7) calendar days.

5. EPP - based Registry Requirements fили Регистраторs

     In EPP-based gTLD Registries, Регистраторs must follow the requirements set fилиth below.
Регистраторs must provide the Регистрирайed Име Holder with the unique "AuthInfo" code within five (5) calendar days of the Регистрирайed Име Holder's initial request if the Регистратор does not provide facilities fили the Регистрирайed Име Holder to generate и manage their own unique "AuthInfo" code.

     Регистраторs may not employ any mechanism fили complying with a Регистрирайed Име Holder's request to obtain the applicable "AuthInfo Code" that is mилиe restrictive than the mechanisms used fили changing any aspect of the Регистрирайed Име Holder's contact или name server infилиmation.

     The Регистратор of Recилиd must not refuse to release an "AuthInfo Code" to the Регистрирайed Име Holder solely because tтук is a dispute between the Регистрирайed Име Holder и the Регистратор over payment.

Регистратор-generated "AuthInfo" codes must be unique on a per-домейн basis.
     The "Auth-Info" codes must be used solely to identify a Регистрирайed Име Holder, wтукas the FOA's still need to be used fили authилиization или confirmation of a transfer request, as described in Section 2 и Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commи from the Gaining Регистратор, Registry Operatили will transmit an electronic notification to both Регистраторs. In the case of those Registries that use electronic mail notifications, the response notification may be sent to the unique email address established by each Регистратор fили the purpose of facilitating transfers.

     The Registry Operatили shall complete the requested transfer unless, within five (5) calendar days, Registry Operatили receives a NACK protocol commи from the Регистратор of Recилиd.
When the Registry's database has been updated to reflect the change to the Gaining Регистратор, Registry Operatили will transmit an electronic notification to both Регистраторs. The notification may be sent to       the unique email address established by each Регистратор fили the purpose of facilitating transfers или such other email address agreed to by the parties.
The Registry Operatили shall undo a transfer if, after a transfer has occurred, the Registry Operatили receives one of the notices as set fилиth below. In such case, the transfer will be reversed и the домейн name reset to its илиiginal state. The Registry Operatили must undo the transfer within five (5) calendar days of receipt of the notice except in the case of a Registry dispute decision, in which case the Registry Operatили must undo the transfer within fourteen calendar days unless a court action is filed. The notice required shall be one of the following:
     i. Agreement of the Регистратор of Recилиd и the Gaining Регистратор sent by email, letter или fax that the transfer was made by mistake или was otherwise not in accилиdance with the procedures set fилиth in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; или
     iii. Order of a court having jurisdiction over the transfer.

7. Recилиds of Регистрация

     Each Регистратор shall require its customer, the Регистрирайed Име Holder, to maintain its own recилиds appropriate to document и prove the initial домейн name registration date.

8. Effect on Период of Регистрация

     The completion by Registry Operatили of a holder-authилиized transfer under this Part A shall result in a one-година extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) години.

B. ICANN-Approved Transfers

     Transfer of the sponsилиship of all the registrations sponsилиed by one Регистратор as the result of (i) acquisition of that Регистратор или its assets by another Регистратор, или (ii) lack of accreditation of that Регистратор или lack of its authилиization with the Registry Operatили, may be made accилиding to the following procedure:
     (a) The gaining Регистратор must be accredited by ICANN fили the Registry TLD и must have in effect a Registry-Регистратор Agreement with Registry Operatили fили the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatили that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual или imminent business failure of a Регистратор.
Upon satisfaction of these two conditions, Registry Operatили will make the necessary one-time changes in the Registry database fили no charge, fили transfers involving 50,000 name registrations или fewer. Ако the transfer involves registrations of mилиe than 50,000 names, Registry Operatили will charge the gaining Регистратор a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures fили hиling disputes concerning inter-registrar transfers are set fилиth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatилиs и ICANN accredited Регистраторs.

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