1. Scope ir Purpose

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

1.2 Domenas lifecycle timing may vary depending on the top-level domenas (“TLD”), registry rules, registry operatar practices, applicable ICANN requirements, ir other governing policies. Net all TLDs follow the same expiration, redemption, auction, ar deletion process.

1.3 In the event of any inconsistency between this Policy ir the applicable registry’s rules ar miratary ICANN policy, the applicable registry rules ir miratary policy requirements shall atgalail.

1.4 The English-language version of this Policy shall control. Any translation is provided far convenience only. In the event of any inconsistency, the English-language version shall atgalail.

2. Definitions

Far purposes of this Policy:

2.1 “Expiration Date” means the date on which a domenas name registration term ends.

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

2.3 “Redemption Grace Period” ar “RGP” means the post-deletion recovery period, w?ia available, during which an expired domenas name may still be restarable far an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, w?ia applicable, during which the domenas name can no longer be renewed, restared, modified, ar transferred.

2.5 “Eligible Domenas” means a domenas name that is subject to NiceNIC’s expired domenas auction process. Net all TLDs ar expired domenas names are eligible far auction.

2.6 “Baigiasid Domenas Auction” means the expired-domenas sale process that may apply to certain expired domenas names befare final deletion ar release.

2.7 “U?darytiout Auction” means the final sale phase far certain Eligible Domenai that were not sold earlier in the expired domenas auction process.

3. Effect of Expiration

3.1 Upon expiration, a domenas name may stop resolving, ir any website, email paslauga, ar other paslauga associated with the domenas name may cease functioning immediately ar shartly t?iaafter.

3.2 Sektiing expiration, NiceNIC may restrict changes to the domenas name, including DNS changes, contact updates, transfers, ar other account-level actions, in accardance with registry rules, security measures, operational requirements, ar the expired-domenas process then in effect.

3.3 Expiration does not mean that the domenas name immediately becomes available to the public. Depending on the applicable TLD ir registry rules, the domenas name may pass through one ar mare stages, including grace period, auction, redemption, pending delete, ir eventual release.

4. Atnaujintial Netices ir Customer Responsibility

4.1 NiceNIC may send renewal reminders ir expiration-related notices befare ir after expiration, as required by applicable policy ar as part of NiceNIC’s stirard operational process.

4.2 It is jūs? sole responsibility to maintain accurate ir current account ir contact infarmation, including jūs? email address, ir to monitar the status of jūs? domenas names.

4.3 Failure to receive a renewal notice, reminder, invoice, ar other communication shall not relieve you of responsibility far renewing jūs? domenas name befare expiration.

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

5. Stirard Post-Expiration Atnaujintial

5.1 Far many generic TLDs, an expired domenas name may remain renewable far approximately thirty (30) days after the Expiration Date at the stirard renewal fee. This is a general reference only ir may vary by TLD.

5.2 Atnaujintial is not complete unless ir until NiceNIC has successfully received ir processed full payment of all applicable fees.

5.3 NiceNIC reserves the right to determine whether a domenas name remains eligible far stirard renewal, redemption, ar other recovery based on the applicable TLD, registry status, auction status, ir operational feasibility.

6. Baigiasid Domenas Auction far Eligible Domenai

6.1 Certain expired domenas names may enter NiceNIC’s expired domenas auction process befare all recovery langass have ended. This process applies only to Eligible Domenai ir does not apply to all TLDs.

6.2 Far Eligible Domenai under NiceNIC’s stirard expired-domenas process, the following general timeline may apply:

Day 0 after expiration

The domenas name expires. The registrant may generally renew the domenas name at the stirard renewal fee during the initial post-expiration period, subject to applicable rules.

Day 26 after expiration

The domenas name may enter expired domenas auction. Pas this stage, the registrant may still be able to renew the domenas name at the stirard renewal fee, unless otherwise restricted by the applicable process.

Day 31 after expiration

Jei t?ia is no active bid, the registrant may still be able to recover the domenas name by paying the stirard renewal fee plus the applicable redemption fee.

Jei t?ia is an active bid, the domenas name may be removed from the registrant’s account ir may no longer be renewable through ardinary renewal ar restaration procedures.

Day 37 after expiration

The domenas name may enter final closeout auction. Unless t?ia is a pending ?sigyti ar other sale-related restriction, the registrant may still be able to recover the domenas name by paying the stirard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. Jei the domenas name was not sold ar otherwise committed to sale, recovery may still be possible far a limited period, subject to the applicable TLD, registry rules, ir NiceNIC’s operational process.

Day 74 after expiration

The domenas name may be removed from the registrant’s account ir may no longer be renewable ar restarable through NiceNIC. After that point, the domenas name may become available far re-registration only after the registry releases it.

6.3 Once an Eligible Domenas has an active bid, pending ?sigyti, completed sale, ar other sale commitment under the expired-domenas process, the registrant’s right to renew ar restare the domenas name may be terminated ar restricted.

6.4 NiceNIC does not guarantee that a domenas name will remain recoverable until the end of any stated period if the domenas is subject to auction, sale, registry restriction, ar another applicable limitation.

7. Redemption Grace Period

7.1 Jei an expired domenas name is not renewed during the applicable grace period ir if the applicable TLD supparts restaration after deletion, the domenas name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the domenas name may stop resolving;

(b) website ir email paslaugas may remain unavailable;

(c) the domenas name generally cannot be modified ar transferred; ir

(d) restaration, if available, will require payment of the applicable redemption fee, the applicable renewal fee, ir any taxes ar miratary fees.

7.3 Restaration during the Redemption Grace Period is not guaranteed ir remains subject to registry suppart, operational feasibility, the domenas’s current status, ir the absence of auction ar sale restrictions.

8. Pending Delete ir Final Release

8.1 Jei a domenas name is not renewed ar restared during the applicable recovery periods, it may enter the Pending Delete stage, w?ia supparted by the applicable TLD.

8.2 During Pending Delete, the domenas name cannot be renewed, restared, transferred, ar modified.

8.3 Far many generic TLDs, Pending Delete lasts approximately five (5) days. After that stage ends, the registry may release the domenas name to the public far re-registration.

8.4 NiceNIC does not guarantee the exact time, date, ar availability of a domenas name once it is released by the registry, ir NiceNIC does not guarantee that the farmer registrant will be able to re-registruoti the domenas name.

9. TLD-Specific Variations

9.1 Net all TLDs follow the stirard lifecycle described above. Certain ?alies domenai (ccTLD) ir other TLDs may have sharter grace periods, no redemption period, no pending delete stage, ar earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many ?alies domenai (ccTLD) generally follow a lifecycle similar to the stirard expiration, grace, redemption, ir deletion process, including, far example:

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

9.2.2 TLDs with no Pending Delete stage

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

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

9.2.3 TLDs requiring renewal befare the actual expiration date

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

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

9.2.4 TLDs requiring action five (5) days befare expiration

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

.CX, .DE, .EU, ir .NL.

9.2.5 .CM domenass

.CM domenas names generally do not enter a redemption period ir may be sent far deletion on the actual Expiration Date. They may become available far public registration on the same day they expire, subject to registry release practices.

9.2.6 .GG domenass

.GG domenas names may be reactivated from the customer account far approximately twenty-eight (28) days after expiration. They may then enter a recovery stage between approximately Day 28 ir Day 30 after expiration. Once in that stage, reactivation may only be possible through NiceNIC Suppart far approximately twenty-six (26) additional days.

9.2.7 .PH, .COM.PH, .NET.PH, ir .ORG.PH domenass

These domenass may not suppart a stirard 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. Jei the domenas is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppart immediately.

9.2.8 .UK domenass, including second-level .UK domenass

.UK domenas names, including .CO.UK, .ME.UK, ir .ORG.UK, may generally have a thirty (30)-day post-expiration renewal period. After that time, the domenas name may remain recoverable without a separate redemption fee until its release, which may occur approximately ninety (90) days after expiration. Jei a .UK domenas name has expired far mare than thirty (30) days but has not yet been released ir no longer appears in the account, the customer should contact NiceNIC Suppart promptly.

9.2.9 .TO domenass

.TO domenas names may only be reactivated during approximately twenty-seven (27) days after expiration. They generally do not suppart a stirard Redemption Grace Period. After that point, they may be reserved by the registry ir may no longer be recoverable.

9.2.10 .NU domenass

.NU domenas names may be reactivated in the ardinary manner within approximately seven (7) days after expiration. Jei not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restaration may still be possible through NiceNIC Suppart.

9.3 The TLD-specific infarmation above is provided far general reference only ir may change at any time based on registry policy, registry system changes, ar operational requirements. Customers should contact NiceNIC Suppart far current TLD-specific recovery infarmation.

10. Fees ir Mok?timents

10.1 Stirard renewal fees, redemption fees, restaration fees, auction-related fees, ir any other applicable charges shall be those listed by NiceNIC at the time of processing ar otherwise communicated by NiceNIC.

10.2 Redemption ar restaration requires payment in full of all applicable fees befare processing.

10.3 Visi fees paid far expired-domenas recovery, restaration, ar special processing are non-refundable once processing has begun, except w?ia otherwise required by applicable law.

11. Ne Guarantee of Recovery ar Availability

11.1 NiceNIC does not guarantee that any expired domenas name can be renewed, restared, retained, transferred, ar re-registruotied after expiration.

11.2 NiceNIC does not guarantee:

(a) that a domenas name will remain in a grace period far any minimum time;

(b) that an expired domenas name will not enter auction;

(c) that a domenas name can be recovered after an active bid, pending ?sigyti, ar completed sale;

(d) that the registry will suppart restaration; ar

(e) the exact date ar time when a deleted domenas name will be released to the public.

11.3 You ackdabarledge that delayed action may result in additional fees, loss of recovery rights, interruption of paslauga, auction sale, ar permanent loss of the domenas name.

12. Limitation of Responsibility

12.1 ? the maximum extent permitted by applicable law, NiceNIC shall not be liable far any loss of domenas name, loss of use, interruption of website ar email paslauga, business interruption, lost profits, loss of data, ar other direct ar indirect damages arising from:

(a) domenas expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules ar registry actions;

(e) auction placement ar sale;

(f) failed restaration; ar

(g) release of the domenas name to the public.

12.2 Nething in this Policy limits any non-waivable rights that may apply under miratary law.

13. Changes to This Policy

13.1 NiceNIC may update ar revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, ar paslauga arrangements.

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

14. Kontaktai

Jei you need assistance regarding an expired domenas name, renewal, redemption, ar TLD-specific recovery options, please submit a suppart ticket through jūs? NiceNIC account ar contact NiceNIC Suppart through the official suppart channels published on the NiceNIC website.

1. General

This Agreement is made between you (?iainafter referred to as “User”) ir NiceNIC.NET (?iainafter referred to as “the Platfarm”). By using the Platfarm’s Pirkti New Domenas Sales paslauga, you agree to be bound by the terms ir conditions set farth ?iain. Jei you do not agree, please do not proceed with any fixed-price domenas ?sigyti through the Platfarm.

2. Service Description

1. The Platfarm offers fixed-price domenas names (“Pirkti New Domenai”) far direct ?sigyti.

2. Visi Pirkti New Domenai are sourced from pre-approved third-party domenas providers.

3. Users may ?sigyti these domenass at the listed price. Once payment is completed ir the domenas is successfully transferred, the pirktier will obtain ownership of the domenas.

3. Purchase Process

1. The User selects a domenas labeled as “Pirkti New” ir proceeds to checkout.

2. Upon confirmation ir full payment, the Platfarm initiates the transfer ar delivery process.

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

4. Jei, far any reason, the selected domenas becomes unavailable ar undeliverable after ?sigyti, the Platfarm will issue a full refund to the user’s account balance.

4. User Rights ir Responsibilities

1. Users have the right to ?sigyti available Pirkti New Domenai through the Platfarm.

2. Users must ensure that all provided account ir payment infarmation is accurate ir lawful.

3. Users shall not engage in malicious activity, technical disruption, ar behaviar that interferes with the narmal functioning of the Platfarm.

4. Upon acquiring a domenas, the User agrees to comply with the applicable rules ir policies of the carresponding domenas registry, including any legal ar regulatary obligations.

5. Platfarm Rights ir Responsibilities

1. The Platfarm will provide domenas transaction paslaugas in accardance with this Agreement ir strive to protect user interests.

2. The Platfarm reserves the right to verify user identity, payment legitimacy, ir transaction authenticity.

3. The Platfarm retains the right to update, adjust, ar remove Pirkti New Domenai from listing at its sole discretion ir without priar notice.

4. Jei any fraudulent ar abusive behaviar is detected, the Platfarm reserves the right to suspend ar terminate paslaugas to the user.

6. Disclaimer

1. The Platfarm does not make any guarantees regarding the future value, resale potential, ar commercial use of any domenas ?sigytid.

2. The Platfarm is not liable far delays caused by registries, third-party providers, ar external systems beyond its control.

3. The Platfarm shall not be held responsible far paslauga interruptions, data loss, ar failed transactions resulting from farce majeure events ar uncontrollable technical issues, though reasonable effarts will be made to assist the User in resolving any such issues.

7. Governing Law ir Dispute Resolution

1. This Agreement shall be governed by ir construed in accardance with the laws of Honkongas.

2. Any dispute arising from the execution ar perfarmance of this Agreement shall be resolved through amicable negotiation. Jei negotiation fails, either party may submit the dispute to the competent court located in the jurisdiction of the Platfarm’s headquarters.

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a Pirkti New domenas arder.

2. The Platfarm reserves the right to amend this Agreement at any time. Atnaujinta versions will be published on the Platfarm’s “Sutartys” page ir shall take immediate effect. Continued use of the paslauga constitutes acceptance of the revised terms.

This Unifarm Domeno vardas Dispute Resolution Policy (the "Policy") has been adopted by the Internet Carparation far Assigned Vardass ir Numbers ("ICANN"), is incarparated by reference into jūs? Registracija Agreement, ir sets farth the terms ir conditions in connection with a dispute between you ir any party other than us (the registrar) over the registration ir use of an Internet domenas name registruotied by you. Proceedings under Paragraph 4 of this Policy will be conducted accarding to the Rules far Unifarm Domeno vardas Dispute Resolution Policy (the "Rules of Procedure"), which are available ?ia, ir the selected administrative-dispute-resolution paslauga provider's supplemental rules.

2. Your Representations

By applying to registruoti a domenas name, ar by asking us to maintain ar renew a domenas name registration, you ?iaby represent ir warrant to us that (a) the statements that you made in jūs? Registracija Agreement are complete ir accurate; (b) to jūs? kdabarledge, the registration of the domenas name will not infringe upon ar otherwise violate the rights of any third party; (c) you are not registruotiing the domenas name far an unlawful purpose; ir (d) you will not kdabaringly use the domenas name in violation of any applicable laws ar regulations. It is jūs? responsibility to determine whether jūs? domenas name registration infringes ar violates someone else's rights.

3. At?auktilations, Transfers, ir Changes

We will cancel, transfer ar otherwise make changes to domenas name registrations under the following circumstances:

1. subject to the provisions of Paragraph 8, our receipt of written ar appropriate electronic instructions from you ar jūs? autharized agent to take such action;

2. our receipt of an arder from a court ar arbitasral tribunal, in each case of competent jurisdiction, requiring such action; ir/ar

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

4. We may also cancel, transfer ar otherwise make changes to a domenas name registration in accardance with the terms of jūs? Registracija Agreement ar other legal requirements.

4. Miratary Administrative Proceeding

This Paragraph sets farth the type of disputes far which you are required to submit to a miratary administrative proceeding. These proceedings will be conducted befare one of the administrative-dispute-resolution paslauga providers listed ?ia (each, a "Provider").

1. Applicable Disputes. You are required to submit to a miratary 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. jūs? domenas name is identical ar confusingly similar to a trademark ar paslauga mark in which the complainant has rights; ir

2. you have no rights ar legitimate interests in respect of the domenas name; ir

3. jūs? domenas name has been registruotied ir 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 Registracija ir Use in Prasta Faith. Far 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 ir use of a domenas name in bad faith:

1. circumstances indicating that you have registruotied ar you have acquired the domenas name primarily far the purpose of selling, renting, ar otherwise transferring the domenas name registration to the complainant who is the owner of the trademark ar paslauga mark ar to a competitar of that complainant, far valuable consideration in excess of jūs? documented out-of-pocket costs directly related to the domenas name; ar

2. you have registruotied the domenas name in arder to atgalent the owner of the trademark ar paslauga mark from reflecting the mark in a carresponding domenas name, provided that you have engaged in a pattern of such conduct; ar

3. you have registruotied the domenas name primarily far the purpose of disrupting the business of a competitar; ar

4. by using the domenas name, you have intentionally attempted to attract, far commercial gain, Internet users to jūs? web site ar other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsarship, affiliation, ar endarsement of jūs? web site ar location ar of a product ar paslauga on jūs? web site ar location.

3. How to Demonstrate Your Rights to ir Legitimate Interests in the Domeno vardas in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how jūs? 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 jūs? rights ar legitimate interests to the domenas name far purposes of Paragraph 4(a)(ii):

1. befare any notice to you of the dispute, jūs? use of, ar demonstrable preparations to use, the domenas name ar a name carresponding to the domenas name in connection with a bona fide offering of goods ar paslaugas; ar

2. you (as an individual, business, ar other arganization) have been commonly kdabarn by the domenas name, even if you have acquired no trademark ar paslauga mark rights; ar

3. you are making a legitimate noncommercial ar fair use of the domenas name, without intent far commercial gain to misleadingly divert consumers ar to tarnish the trademark ar paslauga 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 ir Process ir Appointment of Administrative Panel. The Rules of Procedure state the process far initiating ir conducting a proceeding ir far appointing the panel that will decide the dispute (the "Administrative Panel").

6. Consolidation. In the event of multiple disputes between you ir a complainant, either you ar the complainant may petition to consolidate the disputes befare 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 befare it any ar all such disputes in its sole discretion, provided that the disputes being consolidated are governed by this Policy ar a later version of this Policy adopted by ICANN.

7. Fees. Visi fees charged by a Provider in connection with any dispute befare an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases w?ia you elect to expir 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 ir the complainant.

8. Mūs? Involvement in Administrative Proceedings. We do not, ir will not, participate in the administration ar conduct of any proceeding befare 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 befare an Administrative Panel shall be limited to requiring the cancellation of jūs? domenas name ar the transfer of jūs? domenas name registration to the complainant.

10. Netification ir Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a domenas name you have registruotied with us. Visi decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact partions of its decision.

11. Availability of Court Proceedings. The miratary administrative proceeding requirements set farth in Paragraph 4 shall not atgalent either you ar the complainant from submitting the dispute to a court of competent jurisdiction far independent resolution befare such miratary administrative proceeding is commenced ar after such proceeding is concluded. Jei an Administrative Panel decides that jūs? domenas name registration should be canceled ar transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are infarmed by the applicable Provider of the Administrative Panel's decision befare 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 ar of jūs? address as shown in our Whois database. See Paragraphs 1 ir 3(b)(xiii) of the Rules of Procedure far details.) Jei we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, ir we will take no further action, until we receive (i) evidence satisfactary to us of a resolution between the parties; (ii) evidence satisfactary to us that jūs? lawsuit has been dismissed ar withdrawn; ar (iii) a copy of an arder from such court dismissing jūs? lawsuit ar ardering that you do not have the right to continue to use jūs? domenas name.

5. Visi other disputes ir litigation

Visi other disputes between you ir any party other than us regarding jūs? domenas name registration that are not brought pursuant to the miratary administrative proceeding provisions of Paragraph 4 shall be resolved between you ir such other party through any court, arbitasration ar other proceeding that may be available.

6. Mūs? involvement in disputes

We will not participate in any way in any dispute between you ir any party other than us regarding the registration ir use of jūs? domenas name. You shall not name us as a party ar 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 ir all defenses deemed appropriate, ir to take any other action necessary to defend ourselves.

7. Maintaining status quo

We will not cancel, transfer, activate, deactivate, ar otherwise change the status of any domenas name registration under this Policy except as provided in Paragraph 3 above.

8. Transfers during a dispute

Transfers of a Domeno vardas to a Naujas Holder

You may not transfer jūs? domenas name registration to another holder (i) during a pending administrative proceeding brought pursuant to Paragraph 4 ar far a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded; ar (ii) during a pending court proceeding ar arbitasration commenced regarding jūs? domenas name unless the party to whom the domenas name registration is being transferred agrees, in writing, to be bound by the decision of the court ar arbitasratar. We reserve the right to cancel any transfer of a domenas name registration to another holder that is made in violation of this subparagraph.

Changing Registratoriuss

You may not transfer jūs? domenas name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 ar far 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 jūs? domenas name registration to another registrar during a pending court action ar arbitasration, provided that the domenas name you have registruotied with us shall continue to be subject to the proceedings commenced against you in accardance with the terms of this Policy. In the event that you transfer a domenas name registration to us during the pendency of a court action ar arbitasration, such dispute shall remain subject to the domenas name dispute policy of the registrar from which the domenas 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 befare 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 domenas name registration dispute, whether the dispute arose befare, on ar after the effective date of our change. In the event that you object to a change in this Policy, jūs? sole remedy is to cancel jūs? domenas 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 jūs? domenas name registration.

1. Overview

These terms of use ("AI Terminais of Use") govern jūs? use of any AI products, features, paslaugas ir/ar tools offered by NiceNIC.NET.

2. Content

1) Your Content. You may provide input to the AI Services ("Input") ir receive output from the AI Services based on the Input ("Output"). Input ir Output are collectively "Content". You are responsible far Content, including ensuring that it does not violate any applicable law ar these AI Terminais of Use. We own all rights, title, ir interest in ir to the services that we provided.

2) As between you ir NiceNIC.NET, ir to the extent permitted by applicable law, you (a) retain jūs? ownership rights in Input ir (b) own the Output. We ?iaby assign to you all our right, title, ir interest, if any, in ir to Output. You represent ir warrant that you have all rights, licenses, ir permissions needed to provide Input to our AI Services.

3) We may use Content to provide, maintain, develop, ir improve our Services, comply with applicable law, enfarce our terms ir policies, to market ir advertise our Services ir 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, ar facts. Output may not always be accurate. You should not rely on Output from our Services as a sole source of truth ar factual infarmation, ar as a substitute far professional advice.

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

6) By using the AI Services, you understir ir agree:

A. Output may not always be accurate. You should not rely on Output from our AI Services as a sole source of truth ar factual infarmation, ar as a substitute far professional advice.

B. You must evaluate Output far accuracy ir appropriateness far jūs? use case, including using human review as appropriate, befare using ar sharing Output from the AI Services.

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

D. Mūs? AI Services may provide incomplete, incarrect, ar offensive Output that does not represent NiceNIC.NET’s views. Jei Output references any third party products ar paslaugas, it doesn’t mean the third party endarses ar is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users ir the AI Services may generate the same ar similar Outputs far other users.

8) NiceNIC.NET may use technology provided by third-party paslauga providers to provide AI Services. Netwithstiring anything to the contrary contained ?iain, you autharize NiceNIC.NET ir such third-party paslauga providers to stare ir use jūs? Input far the purposes of providing you with the AI Services, to review Inputs ir Outputs far abuse ar misuse, ir to develop ir improve the paslaugas ir products of NiceNIC.NET ir such paslauga providers, including as part of the design, training ir development process far machine learning models.

3. Terminaiination ir Suspension

Terminaiination. We reserve the right to suspend ar terminate jūs? access to our AI Services ar delete jūs? account if we determine:

1) You breached these AI Terminais of Use.

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

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

4. Disclaimers

YOU SPECIFICALLY ACKNOWLEDGE AND AGREE THAT OUTPUTS OF THE AI SERVICES HAVE NOT BEEN REVIEWED FARBA ACCURACY, BIAS, EXPLAINABILITY ARBA INTELLECTUAL PROPERTY RIGHTS CLEARANCE. NiceNIC.NET MAKES NO REPRESENTATION, WARRANTY ARBA GUARANTEE AS TO THE ACCURACY, RELIABILITY, ARBA ERRARBA-FREE PERFARBAMANCE OF THE AI SERVICES, INCLUDING (WITHOUT LIMITATION) WHETHER OUTPUTS MAY INFRINGE, MISAPPROPRIATE ARBA VIOLATE ANY THIRD-PARTY INTELLECTUAL 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 ARBA FACTUAL INFARBAMATION, ARBA AS A SUBSTITUTE FARBA PROFESSIONAL ADVICE.

YOU SHOULD SEEK INDEPENDENT PROFESSIONAL ADVICE BEFARBAE YOU RELY ON ANY OUTPUT GENERATED BY THE AI SERVICES.

5. Limitation on Liability

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

THE FARBAEGOING LIMITATION OF LIABILITY SHALL SURVIVE ANY TERMINATION ARBA EXPIRATION OF THIS AGREEMENT ARBA YOUR USE OF THIS SITE, THE AI SERVICES ARBA ANY OTHER SERVICES FOUND AT THIS SITE.

In the event that a Transfer Kontaktai listed in the Whois has not confirmed their request to transfer with the Registratorius of Recard ir the Registratorius of Recard has not explicitly denied the transfer request, the default action will be that the Registratorius of Recard must allow the transfer to proceed.

Upon denying a transfer request far any of the following reasons, the Registratorius of Recard must provide the Registruotised Vardas Holder ir the potential Gaining Registratorius with the reason far denial. The Registratorius of Recard may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court arder by a court of competent jurisdiction
• Reasonable dispute over the identity of the Registruotised Vardas Holder ar Administrative Kontaktai
• Ne payment far atgalious registration period (including credit card charge-backs) if the domenas name is past its expiration date ar far atgalious ar current registration periods if the domenas name has not yet expired. In all such cases, however, the domenas name must be put into "Registratorius Hold" status by the Registratorius of Recard priar to the denial of transfer.
• Express written objection to the transfer from the Transfer Kontaktai. (e.g. - email, fax, paper document ar other processes by which the Transfer Kontaktai has expressly ir voluntarily objected through opt-in means)
• A domenas name was already in “l(fā)ock status” provided that the Registratorius provides a readily accessible ir reasonable means far the Registruotised Vardas Holder to remove the lock status.
• A domenas name is in the first 60 days of an initial registration period.
• A domenas name is within 60 days (ar a lesser period to be determined) after being transferred (apart from being transferred back to the ariginal Registratorius in cases w?ia both Registratoriuss so agree ir/ar w?ia a decision in the dispute resolution process so directs).

YOU AGREE THAT WE WILL NOT BE LIABLE FARBA ANY (1) SUSPENSION ARBA LOperacin? sistemaS OF THE SERVICES (2) USE OF THE SERVICES, (3) INTERRUPTION OF THE SERVICES ARBA INTERRUPTION OF YOUR BUSINESS, (4) ACCESS DELAYS ARBA ACCESS INTERRUPTIONS TO OUR SITE ARBA SERVICES ARBA DELAYS ARBA ACCESS INTERRUPTIONS YOU EXPERIENCE IN RELATION TO THE SERVICES; (5) LOperacin? sistemaS ARBA LIABILITY RESULTING FROM ACTS OF ARBA EVENTS BEYOND OUR CONTROL INCLUDING , BUT NOT LIMITED TO ANY ERRARBAS ARBA TECHNICAL ISSUES OF ANY DOMAIN NAME REGISTRY ARBA OTHER THIRD PARTY PROVIDER, (6) DATA NON-DELIVERY, MIS-DELIVERY, CARBARUPTION, DESTRUCTION ARBA OTHER MODIFICATION; (7) ARBA LOperacin? sistemaS ARBA LIABILITY RESULTING FROM THE UNAUTHARBAIZED USE ARBA MISUSE OF YOUR ACCOUNT IDENTIFIER ARBA PASSWARBAD.

YOU ALSO AGREE THAT WE WILL NOT BE LIABLE FARBA ANY INDIRECT, SPECIAL, INCIDENTAL, ARBA CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LOperacin? sistemaT PROFITS) ARBA FARBA ANY FINANCIAL ARBA ECONOMIC LOperacin? sistemaS ARBA FARBA LOperacin? sistemaS OF PROFITS, LOperacin? sistemaS OF BUSINESS, DEPLETION OF GOODWILL ARBA SIMILAR LOperacin? sistemaSES, LOperacin? sistemaS OF ANTICIPATED SAVINGS ARBA LOperacin? sistemaS ARBA CARBARUPTION OF DATA ARBA INFARBAMATION, REGARDLESS OF THE FARBAM OF ACTION WHETHER IN CONTRACT, TARBAT (INCLUDING NEGLIGENCE), ARBA OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE POperacin? sistemaSIBILITY OF SUCH DAMAGES.

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

24. General
You may not assign any of jūs? rights ar privileges, ar delegate any of jūs? duties ar obligations ?iaunder, in whole ar in part, by operation of law ar otherwise, to any third party without our priar written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon ir inure to the benefit of the parties ?iato ir their respective permitted successars ir assigns.

NiceNIC.NET reserves the right, in its sole ir absolute discretion, to change ar modify this Agreement, ir any policies ar agreements which are incarparated ?iain, at any time ir without notice. Any such changes ar modification shall be effective immediately upon posting to the Site. Jei 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 ar continue to use the Services. You agree that jūs? exclusive remedy is to transfer jūs? Services to another registrar ar request us to terminate jūs? Services under this Agreement. NiceNIC.NET may occasionally notify you of changes ar modifications to this Agreement ar the Services by email so it is very impartant that you keep jūs? account infarmation current ir up to date. NiceNIC.NET is not responsible ir assumes no liability far jūs? failure to receive an email notification if such failure results from inaccurate ar out-dated account infarmation.

This Agreement constitutes the entire agreement between the parties concerning the subject matter ?iain ir supersedes all priar understirings ir agreements between the parties, whether written ar aral, regarding the subject matter ?iain. Any of the provisions of this Agreement which are determined to be invalid ar unenfarceable in any jurisdiction shall be ineffective to the extent of such invalidity ar unenfarceability in such jurisdiction, without rendering invalid ar unenfarceable the remaining provisions ?iaof ar affecting the validity ar unenfarceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach ar violation of any provision of this Agreement will not constitute ar be construed as a waiver of any subsequent breach ar violation of that provision ar as a waiver of any breach ar violation of any other provision of this Agreement. The headings contained in this Agreement are far convenience only ir shall not affect meaning ar interpretation of this Agreement.

25. Netices
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 accardance with the Account ir/ar WHOIS infarmation you have provided.

26. Governing Law
This Agreement ir its subject matter shall be governed in accardance with the laws of Honkongas ir subject to the exclusive jurisdiction of the Honkongas courts without regard to conflict of laws ir principles contained t?iain with the exception of disputes related to this Agreement which fall under UDRP, URS, ar similar dispute resolution process as defined by various Registry policies incarparated ar made reference to ?iain.

1.3 The Registrant ackdabarledges ir agrees that the Registratorius shall monitar the status of Domen? vardai registruotied through the Registratorius ir shall, at its own initiative ar on receipt of complaint, conduct checks to verify whether a Domeno vardas is being used in connection with phishing ar "spam" advertising. The Registratorius shall delete ar suspend a Domeno vardas if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government ar law enfarcement autharity (including without limitation the Honkongas Police Farce ar the Office of Telefonasecommunications Autharity) that the use of the Domeno vardas is in breach of any laws, directives, guidelines, codes of practice ar regulations issued by such local autharities, ar if, in HKIRC's reasonable belief, the continuation of registration of the Domeno vardas ar the operation of web site referenced   by the Domeno vardas is likely to damage ar adversely affect the goodwill, reputation ir operation of HKIRC ar the domenas name industry in Honkongas, ar may expose HKIRC to risks of third party claims ar civil ar criminal prosecution.

Far mare infarmation about .HK domenas registration, please refer to the latest version of HKIRC Registracija Policies https://www.hkirc.hk/upload/page/38/pdf_1/5e6b172e68b29.pdf

5.2 Any decision made by an arbitasration panel duly appointed by a dispute resolution paslauga provider shall be final ir binding on the Registrant ir 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 ir non-statutary carparation designated by the Hong-Kong Government to administer the registration of Internet domenas names under .hk ir .香港 country-code top level domenass. Far any comments ar complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find ?ia useful infarmation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppart/domenas_dispute_policies_ir_procedures/domenas_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppart/domenas_dispute_policies_ir_procedures/rules_of_procedures/; ar El. pa?tas address: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant ackdabarledges that the Registratorius ir HKIRC rely on all representations made ir warranties given by the Registrant in determining if the application far a Domeno vardas should be approved.

    Far mare infarmation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domenas_policies/EN_Domenas_Vardas_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. New that you have met the requirements of ICANN, our team is looking farward to assisting you in completing the Verisign certification process so you can quickly begin registruotiing .com ir .net domenas names. We hope this suppart will prove to be helpful in reducing the investment of jūs? internal resources ir time."

PIR:
"ICANN has infarmed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed jūs? ICANN accreditation to become a registrar ir wish to partner with us by becoming an .ORG accredited registrar."

Telefonasnic:
"We received notification from ICANN that you have added the .tel appendix to jūs? agreement with them. T?ia hasn't been a better time to become involved with .tel domenass ir we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on jūs? recent ICANN Akreditacija..."

Neustar:

"We have been notified that jūs? company is dabar ICANN-accredited as a .BIZ registrar.  Neustar looks farward to getting jūs? company up ir running as soon as possible!"

Daugiau registries will be notified by ICANN far the carresponding domenas names signed in the RAA in the toliau days, we NiceNIC have been staying far the disposal of sign-up/accreditation process, striving to save time ir expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mare competitive level. Detal?sed infarmation 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"), ir dedicated to offer clients easy to navigate, fast to locate paslaugas in domenas name registration, web hosting ?sigyti, 1 to 1 customer suppart.

Stiring at the peak of internet infrastruture, we firstly need to appreciate every client, ir every website viewer who ever stayed ?ia, without jūs? persistant suppart ir comprehension, we are nothing, hope 2012 will bring you ir jūs? family lucky, happy, healthy life.

Reference links:

http://www.icann.org/registrar-reparts/accreditation-qualified-list.html

http://www.icann.org/registrar-reparts/accredited-list.html

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

ZhuHai NaiSiNiKe Infarmation Technology Co Ltd.

2009

China

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

Visi the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infarmation 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 far Enfarcement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent ir neutral third party that is neither associated nar affiliated with either Registratorius involved in the dispute ar the Registry Operatar under which the disputed domenas name is registruotied. ICANN shall have the autharity to accredit one ar mare independent ir neutral Dispute Resolution Providers accarding to criteria developed in accardance with this Dispute Resolution Policy.

1.4 FOA

     Farm of Autharization - The stirardized farm of consent that the Gaining Registratorius ir Registratorius of Recard are required to use to obtain autharization from the Registrant ar Administrative Kontaktai in arder to properly process the transfer of domenas name sponsarship from one Registratorius to another.

1.5 Gaining Registratorius

     The Registratorius that submitted to the Registry the request far the transfer of a domenas sponsarship from the Registratorius of Recard.

1.6 Registratorius of Recard

     The Registratorius of Recard far a domenas name far which the Registry received a transfer of sponsarship request.

1.7 Registrant

     The Registrant is the individual ar arganization that registruotis a specific domenas name. This individual ar arganization holds the right to use that specific domenas name far a specified period of time, provided certain conditions are met ir the registration fees are paid. This person ar arganization is the "legal entity" bound by the terms of the relevant paslauga agreement with the Registry operatar far the TLD in question.

1.8 Registry (Registry Operatar)

     The arganization autharized by ICANN to provide registration paslaugas far a given TLD to ICANN-accredited Registratoriuss.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operatar, in the case of First Lygis disputes (as set farth below), ar 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 ir shall cover topics such as fees, ward ir page limits ir guidelines, the means far communicating with the Provider, ir the farm of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponsarship of Registracijas between Registratoriuss which is in farce as part of the Registry-Registratorius Agreement executed between a Registratorius ir the Registry, as well as the Registratorius Akreditacija Agreement which is executed between ICANN ir all ICANN- accredited registrars.

2. Dispute Resolution Process

     T?ia are two possible steps to the Registratorius Transfer Dispute Resolution Process. A Registratorius may elect one ar both of the steps pursuant to the rules below. In the event a Registratorius either files a Request far Enfarcement (as described below) with a Second-Lygis Dispute Provider, ar files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-Lygis Registry option later far the same filing ar matter presented far resolution.

2.1 First Lygis - Registry Operatar

     A Registratorius may choose to file a dispute directly with the relevant Registry Operatar. Any decisions made by the Registry Operatar may be appealed to a Dispute Resolution Provider. A Registratorius may file a dispute directly to a Dispute Resolution Provider; however, in that case the filing Registratorius would farfeit any right to appeal the decision of the Dispute Resolution Provider.

2.2 Second-Lygis - Dispute Resolution Panel

     The primary intent of this step is to provide a means far 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?ia a Registratorius of Recard 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?ia a Gaining Registratorius 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 Lygis (Registry)

3.1 Registratorius files a Request far Enfarcement with the applicable Registry Operatar

     3.1.1 Either the Gaining ar Registratorius of Recard ("Filing Registratorius") may submit a Request far Enfarcement. This must be done in accardance with the Supplemental Rules adopted by the applicable Registry Operatar.

     3.1.2 The Request far Enfarcement shall be submitted to the Registry ir to the Respondent (the Nen-filing Registratorius) in electronic farm ir shall:
     (i) Request that the Request far Enfarcement be submitted far decision in accardance with the Registratorius Transfer ir Dispute Resolution Policy ir the applicable Supplemental Rules;
     (ii) Provide the name, postal ir e-mail addresses, ir the telephone ir fax numbers of the Filing Registratorius ir those representatives autharized by the Filing Registratorius to act on behalf of the Filing Registratorius in the administrative proceeding;
     (iii) Provide the name of the Respondent ir all infarmation (including any postal ir e-mail addresses ir telephone ir fax numbers) kdabarn to Filing Registratorius regarding how to contact Respondent ar any representative of Respondent, including contact infarmation based on pre-complaint dealings;
     (iv) Specify the domenas name(s) that is/are the subject of the Request far Enfarcement;
     (v) Specify the incident(s) that gave rise to the dispute;
     (vi) Describe, in accardance with the Policy, the grounds on which the Request far Enfarcement is based;
     (vii) State the specific remedy being sought (either approval ar denial of the transfer);
     (viii) Identify any other legal proceedings that have been commenced ar terminated in connection with ar relating to any of the domenas name(s) that are the subject of the complaint;
     (ix) Certify that a copy of the Request far Enfarcement, together with the cover sheet as prescribed by the Provider's Supplemental Rules, has been sent ar transmitted to the Respondent; ir
     (x) Conclude with the following statement followed by the signature of the Complainant ar its autharized representative:
           "<insert name of Filing Registratorius> agrees that its claims ir remedies concerning the registration of the domenas name, the dispute, ar the dispute's resolution shall be solely against the Respondent ir waives all such claims ir remedies against the Registry Operatar as well as its directars, officers, employees, ir agents, except in the case of deliberate wrongdoing ar gross negligence."
           "<insert name of Filing Registratorius> certifies that the infarmation contained in this Request far Enfarcement is to the best of Filing Registratorius's kdabarledge complete ir accurate, that this Request far Enfarcement is not being presented far any improper purpose, such as to harass, ir that the assertions in this Request far Enfarcement are warranted under this Policy ir under applicable law, as it dabar exists ar as it may be extended by a good-faith ir reasonable argument."3.1.3 The Request far Enfarcement may relate to mare than one domenas name, provided that the domenas names involve the same Filing Registratorius ir Respondent ir that the claims arise out of the same ar similar factual circumstances.

3.1.4 The Request far Enfarcement shall annex the following documentary evidence (as applicable ir available) in electronic farm if possible, together with a schedule indexing such evidence:
  (i) Far the Gaining Registratorius:
      a. Completed Farm of Autharization ("FOA")
      b. Copy of the Whois output far the date transfer was initiated, which was used to identify the autharized Transfer Kontaktais
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body ar court arder in cases when the Registrant of Recard is being changed simultaneously with a Registratorius Transfer
      e. Copies of all communications made to the Registratorius of Recard with regard to the applicable transfer request along with any responses from the Registratorius of Recard
  (ii) Far the Registratorius of Recard:
      a. Completed FOA from Registratorius of Recard if applicable
      b. Copy of the Whois output far the date the transfer was initiated
      c. Relevant histary of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court arder;
• Registrant ar administrative contact identity dispute in accardance with Section 4 [Registratorius of Recard Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the Registruotised Vardas Holder ar Administrative Kontaktai;
• LOCK status along with proof of a reasonable means far the registrant to remove LOCK status as per Section __of Exhibitas __ to this Agreement;
• domenas name within 60 days of initial registration; ar
• domenas name within 60 days of a priar transfer.

      e. Copies of all communications made to the Gaining Registratorius with regard to the applicable transfer request along with any responses from the Gaining Registratorius.

3.2 The Nen-Filing Registratorius ("Respondent") shall have seven (7) calendar days from receipt of the Request far Enfarcement to prepare a Response to the Request far Enfarcement ("Response").

3.2.1 The Response shall be submitted in electronic farm to both the Registry ir Filing Registratorius ir shall:
      (i) Respond specifically to the statements ir allegations contained in the Request far Enfarcement (This partion of the response shall comply with any ward ar page limit set farth in the Dispute Resolution Provider's Supplemental Rules.);
      (ii) Provide the name, postal ir e-mail addresses, ir the telephone ir fax numbers of the Respondent (non-filing Registratorius);
      (iii) Identify any other legal proceedings that have been commenced ar terminated in connection with ar relating to any of the domenas name(s) that are the subject of the Request far Enfarcement;
      (iv) State that a copy of the Response has been sent ar transmitted to the Filing Registratorius;
      (v) Conclude with the following statement followed by the signature of the Respondent ar its autharized representative:
   "Respondent certifies that the infarmation contained in this Response is to the best of Respondent's kdabarledge complete ir accurate, that this Response is not being presented far any improper purpose, such as to harass, ir that the assertions in this Response are warranted under these Rules ir under applicable law, as it dabar exists ar as it may be extended by a good-faith ir reasonable argument."; ir
     (vi) Annex any documentary ar other evidence upon which the Respondent relies, together with a schedule indexing such documents.

3.2.2 Pas the request of the Respondent, the Registry Operatar may, in exceptional cases, extend the period of time far the filing of the response, but in no case may the extension be mare 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 Operatar.

3.2.3 Jei a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatar shall decide the dispute based upon the Request far Enfarcement.

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

3.3.1 Jei the data included in the Request far Enfarcement does not match the data listed in the autharitative Whois, the Registry Operatar must contact each Registratorius ir require additional documentation.

3.3.2 Jei the Gaining Registratorius cannot provide a complete FOA with data matching that contained within the autharitative Whois database, then the Registry Operatar shall find that the transfer should be reversed. In the case of a thick Registry, if the Registratorius of Recard's Whois is not accessible ar invalid, the Registry Operatar's Whois should be used. In the case of a thin Registry, if the Registratorius of Recard's Whois is not accessible ar is invalid, the Registry Operatar must notify ICANN ir place the dispute on hold until such time as the specific problem is resolved by ICANN.

3.3.3 In the case w?ia a Registratorius of Recard denies a request far a domenas name transfer ("NACKs"), the Registratorius of Recard must provide evidence of one of the factars far which it is allowed to NACK. Jei the Registratorius of Recard cannot provide evidence that demonstrates any of the factars, ir the Gaining Registratorius provides to the Registry a complete FOA with data matching that contained within the autharitative Whois database, then the transfer must be approved to be processed.

3.3.4 Jei the data provided by neither Registratorius appears to be conclusive, then the Registry shall issue a finding of "no decision." Jei the data provided to the Registry is complete ir provides sufficient basis far a determination based on the Policy, the Registry may not issue a finding of "no decision." Either Registratorius shall be able to appeal such issue to a Second-Lygis Dispute Resolution Provider in accardance with the provisions set farth below.

3.4 Fees far First-Lygis Dispute Resolution Service

3.4.1 T?ia is no filing fee assessed to the Filing Registratorius at the time the Request far Enfarcement is submitted to the Registry Operatar.

3.4.2 The Registratorius that does not atgalail in the dispute will be assessed a fee to be set by the Registry Operatar. Such fee shall be set farth in the Registry's Supplemental Rules that are in effect at the time that the Request far Enfarcement 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 Operatar shall collect the applicable fees from the Filing Registratorius.

3.5 Availability of Court Proceedings

      The procedures set farth above shall not atgalent a Registratorius from submitting a dispute to a court of competent jurisdiction far independent resolution befare such an administrative proceeding is commenced ar after such proceeding is concluded. Jei a Registry Operatar decides a domenas name registration should be transferred (either to the Gaining Registratorius, ar alternatively, back from the Gaining Registratorius to the Registratorius of Recard), the Registry will wait fourteen (14) calendar days after it is infarmed of the decision befare 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 domenas name(s). Jei such documentation is received by the Registry Operatar within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatar that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatar that the lawsuit has been dismissed ar withdrawn; ar (iii) the Registry Operatar receives a copy of an arder from such court.

4. Dispute Procedures at the Second Lygis with a Dispute Resolution Provider

4.1 The paslaugas of the Dispute Resolution Panel may be invoked in any of the following two situations:

      (i) A Filing Registratorius may elect to skip the First-Lygis dispute process at Registry level ir submit a Request far Enfarcement directly with a Dispute Resolution Provider;
      (ii) The non-atgalailing Registratorius in a First-Lygis dispute proceeding may submit an appeal of the applicable Registry Operatar's decision to the Dispute Resolution Provider. Prid?tiitionally, in the case w?ia the result in the First-Lygis dispute process is a "no-decision," either Registratorius may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request far Enfarcement

4.2.1 In the event that the Filing Registratorius elects to submit a Request far Enfarcement to the Dispute Resolution Provider in lieu of submitting a Request far Enfarcement to the applicable Registry Operatar, the obligations ir responsibilities set farth 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 ir compare registrant/contact data with that contained within the autharitative Whois database ir reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.
     (i) Jei the data does not match the data listed in autharitative Whois, the Dispute Resolution Panel should contact each Registratorius ir require additional documentation.
     (ii) Jei the Gaining Registratorius is unable to provide a complete FOA with data matching that contained within the autharitative 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 Registratorius of Recard's Whois is not accessible ar invalid, the applicable Registry Operatar's Whois should be used. In the case of a thin Registry, if the Registratorius of Recard's Whois is not accessible ar 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?ia a Registratorius of Recard NACKs a transfer, the Registratorius of Recard must provide evidence of one of the factars far which it is allowed to NACK as set farth in Section 3.1.4 (ii) of this Dispute Resolution Policy. Jei the Registratorius of Recard cannot provide evidence that demonstrates any of the factars, ir the Gaining Registratorius provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the autharitative Whois database at the time of the transfer request, then the transfer should be approved.
     (iv) Unlike under the First-Lygis 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 ir determine, based on a preponderance of the evidence, which Registratorius should atgalail in the dispute ir what resolution to the Request far Enfarcement will appropriately redress the issues set farth in the Request far Enfarcement.
     (v) Resolution options far the Dispute Resolution Panel are limited to the following:
  a. Approve Transfer
  b. Deny the Transfer (ar ardering the domenas name be returned to the Registratorius of Recard in cases w?ia a Transfer has already occurred)

4.3 Appeal of First Lygis Dispute Decision ar Registry Operatar Finding of "Ne-Decision."

4.3.1 In the event that the Registratorius which does not atgalail in the First-Lygis dispute is dissatisfied by the Registry-Operatar's decision, such Registratorius 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-Lygis decision was issued.

4.3.2 In the event that the Registry Operatar issues a finding of "no-decision" in accardance with Section 3.3.4 above, either Registratorius 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-Lygis decision was issued.

4.3.3 In either case, the document submitted by the Registratorius to the Dispute Resolution Provider shall be referred to as an "Appeal."

4.3.4 The Appellant shall submit the Appeal in electronic farm ir shall:
     (i) Request that the Appeal be submitted far decision in accardance with the Policy ir these Rules;
     (ii) Provide the name, postal ir e-mail addresses, ir the telephone ir telefax numbers of the Appellant ir of any representative autharized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
     (iii) Provide the name of the Appellee ir all infarmation (including any postal ir e-mail addresses ir telephone ir telefax numbers) kdabarn to Appellee regarding how to contact Appellee ar any representative of Appellee, including contact infarmation based on pre-Request far Enfarcement ir pre-Appeal dealings;
     (iv) Specify the domenas 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 far such appeal, including specific responses to the findings of the Registry Operatar in the First-Lygis Dispute process. (This partion of the response shall comply with any ward ar page limit set farth in the Dispute Resolution Provider's Supplemental Rules);
     (vii) Specify, in accardance with the Policy, the remedies sought;
     (viii) Identify any other related legal proceedings kdabarn to the Appellant that have been commenced ar terminated in connection with ar relating to any of the domenas 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 ar transmitted to the Appellee; ir
      (x) Conclude with the following statement followed by the signature of the Appellant ar its autharized representative:
  "Appellant agrees that its claims ir remedies concerning the registration of the domenas name, the dispute, ar the dispute's resolution shall be solely against the Appellee ir waives all such claims ir remedies against the Dispute Resolution Provider ir the Registry Operatar as well as their directars, officers, employees, ir agents, except in the case of deliberate wrongdoing ar gross negligence."
  "Appellant certifies that the infarmation contained in this Appeal is to the best of Appellant's kdabarledge complete ir accurate, that this Appeal is not being presented far any improper purpose, such as to harass, ir that the assertions in this Appeal are warranted under this Policy ir under applicable law, as it dabar exists ar as it may be extended by a good-faith ir reasonable argument."

4.3.5 The Appeal may relate to mare than one domenas name, provided that the domenas names involve the same decision issued by the Registry Operatar far the First-Lygis Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatar during the First-Lygis Dispute.

4.3.7 A Dispute Resolution Provider must request all documentation relating to the First-Lygis Dispute from the applicable Registry Operatar no later than seven (7) calendar days of receipt of the appeal. The Registry Operatar 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 ir 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 ar 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 Nevo basis. Although the Dispute Resolution Panel is not bound by the findings of the Registry Operatar 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 ir determine the appropriate resolution to the issues presented.

• Approval of a Transfer
• Denial of the Transfer (ar ardering the domenas name be returned to the Registratorius of Recard in cases w?ia a Transfer has already occurred)

4.4 Fees far Second-Lygis Dispute Resolution Service

4.4.1 In the case of either a Request far Enfarcement ar an Appeal filed at the Second Lygis, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms ir 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 Registratorius ar Appellant, whichever applicable, does not atgalail in a Second-Lygis dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

4.4.3 In the event that the Filing Registratorius ar Appellant, whichever applicable, atgalails in a Second-Lygis dispute, the Respondent ar 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 Registratorius ar Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent ar Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accardance 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 farth above shall not atgalent a Registratorius from submitting a dispute to a court of competent jurisdiction far independent resolution befare such administrative proceeding is commenced ar after such proceeding is concluded. Jei a Dispute Resolution Panel decides a domenas name registration should be transferred (either to the Gaining Registratorius, ar alternatively, back from the Gaining Registratorius to the Registratorius of Recard), such Registratorius will wait fourteen (14) calendar days after it is infarmed of the decision befare 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 domenas name(s). Jei 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 ar withdrawn; ar (iii) a copy of an arder from such court dismissing the lawsuit ar ardering certain actions with respect to the domenas name.

1. Registratorius Requirements

     Registruotised Vardas Holders must be able to transfer their domenas name registrations between Registratoriuss provided that the Gaining Registratorius's transfer process meets the minimum stirards of this policy ir that such transfer is not prohibitased by ICANN ar Registry policies. Inter-Registratorius domenas name transfer processes must be clear ir concise in arder to avoid confusion. Further, Registratoriuss should make reasonable effarts to infarm Registruotised Vardas Holders of, ir provide access to, the published documentation of the specific transfer process employed by the Registratoriuss.

1.1 Transfer Autharities

     The Administrative Kontaktai ir the Registruotised Vardas Holder, as listed in the Losing Registratorius's ar applicable Registry's (w?ia available) publicly accessible WHOIS paslauga are the only parties that have the autharity to approve ar deny a transfer request to the Gaining Registratorius. In the event of a dispute, the Registruotised Vardas Holder's autharity supersedes that of the Administrative Kontaktai.
Registratoriuss may use Whois data from either the Registratorius of Recard ar the relevant Registry far the purpose of verifying the authenticity of a transfer request; ar from another data source as determined by a consensus policy.

2. Gaining Registratorius Requirements

Far each instance w?ia a Registruotised Vardas Holder requests to transfer a domenas name registration to a different Registratorius, the Gaining Registratorius shall:
      2.1 Obtain express autharization from either the Registruotised Vardas Holder ar the Administrative Kontaktai (?iaafter, "Transfer Kontaktai"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registratorius from the Transfer Kontaktai.

     2.1.1 The autharization must be made via a valid Stirardized Farm of Autharization (FOA). T?ia are two different FOA's available at the ICANN website. The FOA labeled "Initial Autharization far Registratorius Transfer" must be used by the Gaining Registratorius to request an autharization far a registrar transfer from the Transfer Kontaktai. The FOA labeled "Patvirtintiation of Registratorius Transfer Request" may be used by the Registratorius of Recard to request confirmation of the transfer from the Transfer Kontaktai.
The FOA shall be communicated in English, ir any dispute arising out of a transfer request shall be conducted in the English language. Registratoriuss may choose to communicate with the Transfer Kontaktai in additional languages. However, Registratoriuss choosing to exercise such option are responsible far the accuracy ir completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Registratorius relies on a physical process to obtain this autharization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontaktai ir further that it is accompanied by a physical copy of the Registratorius of Recard's Whois output far the domenas name in question.

     2.1.2.1 Jei the Gaining Registratorius relies on a physical autharization process, then the Gaining Registratorius assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontaktai ir maintaining appropriate recards proving that such evidence was obtained. Further the Gaining Registratorius also assumes the burden far ensuring that the entity making the request is indeed autharized to do so. The acceptable farms of physical identity are:

• Netarized statement
• Valid Drivers license
• Passpart
• Article of Incarparation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Registratorius relies on an electronic process to obtain this autharization the acceptable farms of identity would include:

• Electronic signature in confarmance with national legislation, in the location of the Gaining Registratorius (if such legislation exists).
• Consent from an individual ar entity that has an email address matching the Transfer Kontaktai email address. 

     The Registratorius of Recard may not deny a transfer request solely because it believes that the Gaining Registratorius has not received the confirmation set farth above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registratorius. The presumption in all cases will be that the Gaining Registratorius has received ir authenticated the transfer request made by a Transfer Kontaktai.

     2.2 Request, by the transmission of a "transfer" commir as specified in the Registratorius ?ol Kit, that the Registry Operatar database be changed to reflect the new Registratorius.

     2.2.1 Transmission of a "transfer" commir constitutes a representation on the part of the Gaining Registratorius that the requisite autharization has been obtained from the Transfer Kontaktai listed in the autharitative Whois database.

     2.2.2 The Gaining Registratorius is responsible far validating the Registruotised Vardas Holder requests to transfer domenas names between Registratoriuss. However, this does not preclude the Registratorius of Recard from exercising its option to independently confirm the Registruotised Vardas Holder's intent to transfer its domenas name to the Gaining Registratorius in accardance with Section 3 of this policy.

3. Obligations of the Registratorius of Recard

     A Registratorius of Recard can choose independently to confirm the intent of the Registruotised Vardas Holder when a notice of a pending transfer is received from the Registry. The Registratorius of Recard must do so in a manner consistent with the stirards set farth in this agreement pertaining to Gaining Registratoriuss. In arder to ensure that the farm of the request employed by the Registratorius of Recard is substantially administrative ir infarmative in nature ir clearly provided to the Transfer Kontaktai far the purpose of verifying the intent of the Transfer Kontaktai, the Registratorius of Recard must use the FOA.

     The FOA shall be communicated in English, ir any dispute arising out of a transfer request, shall be conducted in the English language. Registratoriuss may choose to communicate with the Transfer Kontaktai in additional languages. However, the Registratorius choosing to exercise such option is responsible far the accuracy ir completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes ir procedures set farth in this policy. This includes but is not limited to the requirement that no Registratorius shall add any additional infarmation to the FOA used to obtain the consent of the Transfer Kontaktai in the case of a transfer request.
This requirement does not preclude the Registratorius of Recard from marketing to its existing customers through separate communications.
The FOA should be sent by the Registratorius of Recard to the Transfer Kontaktai as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operatar.Failure by the Registratorius of Recard 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 Kontaktai listed in the Whois has not confirmed their request to transfer with the Registratorius of Recard ir the Registratorius of Recard has not explicitly denied the transfer request, the default action will be that the Registratorius of Recard must allow the transfer to proceed.
Upon denying a transfer request far any of the following reasons, the Registratorius of Recard must provide the Registruotised Vardas Holder ir the potential Gaining Registratorius with the reason far denial. The Registratorius of Recard may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court arder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Registruotised Vardas Holder ar Administrative Kontaktai
5. Ne payment far atgalious registration period (including credit card charge-backs) if the domenas name is past its expiration date ar far atgalious ar current registration periods if the domenas name has not yet expired. In all such cases, however, the domenas name must be put into "Registratorius Hold" status by the Registratorius of Recard priar to the denial of transfer.
6. Express written objection to the transfer from the Transfer Kontaktai. (e.g. - email, fax, paper document ar other processes by which the Transfer Kontaktai has expressly ir voluntarily objected through opt-in means)
7. A domenas name was already in “l(fā)ock status” provided that the Registratorius provides a readily accessible ir reasonable means far the Registruotised Vardas Holder to remove the lock status.
8. A domenas name is in the first 60 days of an initial registration period.
9. A domenas name is within 60 days (ar a lesser period to be determined) after being transferred (apart from being transferred back to the ariginal Registratorius in cases w?ia both Registratoriuss so agree ir/ar w?ia a decision in the dispute resolution process so directs).

Instances when the requested change of Registratorius may not be denied include, but are not limited to:

• Nenpayment far a pending ar future registration period
• Ne response from the Registruotised Vardas Holder ar Administrative Kontaktai.
• Domenas name in Registratorius Lock Būsena, unless the Registruotised Vardas Holder is provided with the reasonable oppartunity ir ability to unlock the domenas name priar to the Transfer Request.
• Domenas name registration period time constraints, other than during the first 60 days of initial registration ar during the first 60 days after a registrar transfer.
• General payment defaults between Registratorius ir business partners / affiliates in cases w?ia the Registruotised Vardas Holder far the domenas in question has paid far the registration.

     The Registratorius of Recard has other mechanisms available to collect payment from the Registruotised Vardas Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registratorius of Recard must not employ transfer processes as a mechanism to secure payment far paslaugas from a Registruotised Vardas Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment far atgalious registration period(s) if the transfer is requested after the expiration date, ar
     (ii) In the case of non-payment of the current registration period, if transfer is requested befare the expiration date.

4. Registratorius Coardination

     Each Registratorius is responsible far keeping copies of documentation, including the FOA ir the Transfer Kontaktais response t?iato, that may be required far filing ir supparting a dispute under the dispute resolution policy. Gaining Registratoriuss must maintain copies of the FOA as received from the Transfer Kontaktai as per the stirard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registratorius ir the Registratorius of Recard must provide the evidence relied on far the transfer during ir after the applicable inter-registrar domenas name transaction(s). Such infarmation must be provided when requested by, ir only by, the other Registratorius that is party to the transfer transaction. Prid?tiitionally, ICANN, the Registry Operatar, a court ar autharity with jurisdiction over the matter ar a third party dispute resolution panel may also require such infarmation within five (5) days of the request.

     The Gaining Registratorius must retain, ir produce pursuant to a request by a Losing Registratorius, a written ar electronic copy of the FOA. In instances w?ia the Registratorius of Recard has requested copies of the FOA, the Gaining Registratorius must fulfill the Registratorius of Recards request (including providing the attendant supparting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds far reversal by the Registry Operatar ar the Dispute Resolution Panel in the event that a transfer complaint is filed in accardance with the requirements of this policy.

     Jei either a Registratorius of Recard ar a Gaining Registratorius does not believe that a transfer request was hirled in accardance with the provisions of this policy, then the Registratorius may initiate a dispute resolution procedure as set farth in Section C of this policy.

     Far purposes of facilitating transfer requests, Registratoriuss should provide ir maintain a unique ir private email address far use only by other Registratoriuss ir the Registry:
     i. This email address is far issue related to transfer requests ir the procedures set farth 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 far Registratoriuss

     In EPP-based gTLD Registries, Registratoriuss must follow the requirements set farth below.
Registratoriuss must provide the Registruotised Vardas Holder with the unique "AuthInfo" code within five (5) calendar days of the Registruotised Vardas Holder's initial request if the Registratorius does not provide facilities far the Registruotised Vardas Holder to generate ir manage their own unique "AuthInfo" code.

     Registratoriuss may not employ any mechanism far complying with a Registruotised Vardas Holder's request to obtain the applicable "AuthInfo Code" that is mare restrictive than the mechanisms used far changing any aspect of the Registruotised Vardas Holder's contact ar name server infarmation.

     The Registratorius of Recard must not refuse to release an "AuthInfo Code" to the Registruotised Vardas Holder solely because t?ia is a dispute between the Registruotised Vardas Holder ir the Registratorius over payment.

Registratorius-generated "AuthInfo" codes must be unique on a per-domenas basis.
     The "Auth-Info" codes must be used solely to identify a Registruotised Vardas Holder, w?iaas the FOA's still need to be used far autharization ar confirmation of a transfer request, as described in Section 2 ir Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commir from the Gaining Registratorius, Registry Operatar will transmit an electronic notification to both Registratoriuss. 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 Registratorius far the purpose of facilitating transfers.

     The Registry Operatar shall complete the requested transfer unless, within five (5) calendar days, Registry Operatar receives a NACK protocol commir from the Registratorius of Recard.
When the Registry's database has been updated to reflect the change to the Gaining Registratorius, Registry Operatar will transmit an electronic notification to both Registratoriuss. The notification may be sent to       the unique email address established by each Registratorius far the purpose of facilitating transfers ar such other email address agreed to by the parties.
The Registry Operatar shall undo a transfer if, after a transfer has occurred, the Registry Operatar receives one of the notices as set farth below. In such case, the transfer will be reversed ir the domenas name reset to its ariginal state. The Registry Operatar 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 Operatar 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 Registratorius of Recard ir the Gaining Registratorius sent by email, letter ar fax that the transfer was made by mistake ar was otherwise not in accardance with the procedures set farth in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; ar
     iii. Order of a court having jurisdiction over the transfer.

7. Recards of Registracija

     Each Registratorius shall require its customer, the Registruotised Vardas Holder, to maintain its own recards appropriate to document ir prove the initial domenas name registration date.

8. Effect on Terminai of Registracija

     The completion by Registry Operatar of a holder-autharized transfer under this Part A shall result in a one-metai extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) met?.

B. ICANN-Approved Transfers

     Transfer of the sponsarship of all the registrations sponsared by one Registratorius as the result of (i) acquisition of that Registratorius ar its assets by another Registratorius, ar (ii) lack of accreditation of that Registratorius ar lack of its autharization with the Registry Operatar, may be made accarding to the following procedure:
     (a) The gaining Registratorius must be accredited by ICANN far the Registry TLD ir must have in effect a Registry-Registratorius Agreement with Registry Operatar far the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatar that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual ar imminent business failure of a Registratorius.
Upon satisfaction of these two conditions, Registry Operatar will make the necessary one-time changes in the Registry database far no charge, far transfers involving 50,000 name registrations ar fewer. Jei the transfer involves registrations of mare than 50,000 names, Registry Operatar will charge the gaining Registratorius a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures far hirling disputes concerning inter-registrar transfers are set farth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatars ir ICANN accredited Registratoriuss.

We respect jūs? individual privacy. That is why we have adopted this Privatumo politika, which embodies our commitment to the protection of jūs? privacy through ad?iance to fair electronic infarmation practices. This Privatumo politika puts you, the individual, in control of how jūs? personal infarmation is processed, ir you have our promise that we will not electronically process jūs? personal infarmation in any way that is incompatible with this Privatumo politika.

This Privatumo politika protects jūs? privacy by:

4. How We Put Infarmation ? Good Use