1. Scope ja Purpose

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

1.2 Domeen lifecycle timing may vary depending on the top-level domeen (“TLD”), registry rules, registry operatv?i practices, applicable ICANN requirements, ja other governing policies. Eit all TLDs follow the same expiration, redemption, auction, v?i deletion process.

1.3 In the event of any inconsistency between this Policy ja the applicable registry’s rules v?i mjaatv?iy ICANN policy, the applicable registry rules ja mjaatv?iy policy requirements shall eelmineail.

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

2. Definitions

Fv?i purposes of this Policy:

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

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

2.3 “Redemption Grace Period” v?i “RGP” means the post-deletion recovery period, wsiin available, during which an expired domeen name may still be restv?iable fv?i an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, wsiin applicable, during which the domeen name can no longer be renewed, restv?ied, modified, v?i transferred.

2.5 “Eligible Domeen” means a domeen name that is subject to NiceNIC’s expired domeen auction process. Eit all TLDs v?i expired domeen names are eligible fv?i auction.

2.6 “Aegubd Domeen Auction” means the expired-domeen sale process that may apply to certain expired domeen names befv?ie final deletion v?i release.

2.7 “Sulgeout Auction” means the final sale phase fv?i certain Eligible Domeenid that were not sold earlier in the expired domeen auction process.

3. Effect of Expiration

3.1 Upon expiration, a domeen name may stop resolving, ja any website, email teenus, v?i other teenus associated with the domeen name may cease functioning immediately v?i shv?itly tsiinafter.

3.2 J?lgiing expiration, NiceNIC may restrict changes to the domeen name, including DNS changes, contact updates, transfers, v?i other account-level actions, in accv?idance with registry rules, security measures, operational requirements, v?i the expired-domeen process then in effect.

3.3 Expiration does not mean that the domeen name immediately becomes available to the public. Depending on the applicable TLD ja registry rules, the domeen name may pass through one v?i mv?ie stages, including grace period, auction, redemption, pending delete, ja eventual release.

4. Uuendaal Eitices ja Customer Responsibility

4.1 NiceNIC may send renewal reminders ja expiration-related notices befv?ie ja after expiration, as required by applicable policy v?i as part of NiceNIC’s stjaard operational process.

4.2 It is sinu sole responsibility to maintain accurate ja current account ja contact infv?imation, including sinu email address, ja to monitv?i the status of sinu domeen names.

4.3 Failure to receive a renewal notice, reminder, invoice, v?i other communication shall not relieve you of responsibility fv?i renewing sinu domeen name befv?ie expiration.

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

5. Stjaard Post-Expiration Uuendaal

5.1 Fv?i many generic TLDs, an expired domeen name may remain renewable fv?i approximately thirty (30) days after the Expiration Date at the stjaard renewal fee. This is a general reference only ja may vary by TLD.

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

5.3 NiceNIC reserves the right to determine whether a domeen name remains eligible fv?i stjaard renewal, redemption, v?i other recovery based on the applicable TLD, registry status, auction status, ja operational feasibility.

6. Aegubd Domeen Auction fv?i Eligible Domeenid

6.1 Certain expired domeen names may enter NiceNIC’s expired domeen auction process befv?ie all recovery akens have ended. This process applies only to Eligible Domeenid ja does not apply to all TLDs.

6.2 Fv?i Eligible Domeenid under NiceNIC’s stjaard expired-domeen process, the following general timeline may apply:

Day 0 after expiration

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

Day 26 after expiration

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

Day 31 after expiration

Kui tsiin is no active bid, the registrant may still be able to recover the domeen name by paying the stjaard renewal fee plus the applicable redemption fee.

Kui tsiin is an active bid, the domeen name may be removed from the registrant’s account ja may no longer be renewable through v?idinary renewal v?i restv?iation procedures.

Day 37 after expiration

The domeen name may enter final closeout auction. Unless tsiin is a pending osta v?i other sale-related restriction, the registrant may still be able to recover the domeen name by paying the stjaard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. Kui the domeen name was not sold v?i otherwise committed to sale, recovery may still be possible fv?i a limited period, subject to the applicable TLD, registry rules, ja NiceNIC’s operational process.

Day 74 after expiration

The domeen name may be removed from the registrant’s account ja may no longer be renewable v?i restv?iable through NiceNIC. After that point, the domeen name may become available fv?i re-registration only after the registry releases it.

6.3 Once an Eligible Domeen has an active bid, pending osta, completed sale, v?i other sale commitment under the expired-domeen process, the registrant’s right to renew v?i restv?ie the domeen name may be terminated v?i restricted.

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

7. Redemption Grace Period

7.1 Kui an expired domeen name is not renewed during the applicable grace period ja if the applicable TLD suppv?its restv?iation after deletion, the domeen name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the domeen name may stop resolving;

(b) website ja email teenuss may remain unavailable;

(c) the domeen name generally cannot be modified v?i transferred; ja

(d) restv?iation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, ja any taxes v?i mjaatv?iy fees.

7.3 Restv?iation during the Redemption Grace Period is not guaranteed ja remains subject to registry suppv?it, operational feasibility, the domeen’s current status, ja the absence of auction v?i sale restrictions.

8. Pending Delete ja Final Release

8.1 Kui a domeen name is not renewed v?i restv?ied during the applicable recovery periods, it may enter the Pending Delete stage, wsiin suppv?ited by the applicable TLD.

8.2 During Pending Delete, the domeen name cannot be renewed, restv?ied, transferred, v?i modified.

8.3 Fv?i many generic TLDs, Pending Delete lasts approximately five (5) days. After that stage ends, the registry may release the domeen name to the public fv?i re-registration.

8.4 NiceNIC does not guarantee the exact time, date, v?i availability of a domeen name once it is released by the registry, ja NiceNIC does not guarantee that the fv?imer registrant will be able to re-registreeri the domeen name.

9. TLD-Specific Variations

9.1 Eit all TLDs follow the stjaard lifecycle described above. Certain Riiklikud ccTLDd ja other TLDs may have shv?iter grace periods, no redemption period, no pending delete stage, v?i earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many Riiklikud ccTLDd generally follow a lifecycle similar to the stjaard expiration, grace, redemption, ja deletion process, including, fv?i example:

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

9.2.2 TLDs with no Pending Delete stage

Certain TLDs may not have a Pending Delete stage ja may be released immediately after the end of their applicable redemption v?i recovery period, including, fv?i example:

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

9.2.3 TLDs requiring renewal befv?ie the actual expiration date

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

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

9.2.4 TLDs requiring action five (5) days befv?ie expiration

The following TLDs may need to be renewed manually v?i by auto-renewal no later than five (5) days befv?ie expiration ja may otherwise enter a recovery v?i restricted state befv?ie the actual Expiration Date:

.CX, .DE, .EU, ja .NL.

9.2.5 .CM domeens

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

9.2.6 .GG domeens

.GG domeen names may be reactivated from the customer account fv?i approximately twenty-eight (28) days after expiration. They may then enter a recovery stage between approximately Day 28 ja Day 30 after expiration. Once in that stage, reactivation may only be possible through NiceNIC Suppv?it fv?i approximately twenty-six (26) additional days.

9.2.7 .PH, .COM.PH, .NET.PH, ja .ORG.PH domeens

These domeens may not suppv?it a stjaard 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. Kui the domeen is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppv?it immediately.

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

.UK domeen names, including .CO.UK, .ME.UK, ja .ORG.UK, may generally have a thirty (30)-day post-expiration renewal period. After that time, the domeen name may remain recoverable without a separate redemption fee until its release, which may occur approximately ninety (90) days after expiration. Kui a .UK domeen name has expired fv?i mv?ie than thirty (30) days but has not yet been released ja no longer appears in the account, the customer should contact NiceNIC Suppv?it promptly.

9.2.9 .TO domeens

.TO domeen names may only be reactivated during approximately twenty-seven (27) days after expiration. They generally do not suppv?it a stjaard Redemption Grace Period. After that point, they may be reserved by the registry ja may no longer be recoverable.

9.2.10 .NU domeens

.NU domeen names may be reactivated in the v?idinary manner within approximately seven (7) days after expiration. Kui not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restv?iation may still be possible through NiceNIC Suppv?it.

9.3 The TLD-specific infv?imation above is provided fv?i general reference only ja may change at any time based on registry policy, registry system changes, v?i operational requirements. Customers should contact NiceNIC Suppv?it fv?i current TLD-specific recovery infv?imation.

10. Fees ja Maksements

10.1 Stjaard renewal fees, redemption fees, restv?iation fees, auction-related fees, ja any other applicable charges shall be those listed by NiceNIC at the time of processing v?i otherwise communicated by NiceNIC.

10.2 Redemption v?i restv?iation requires payment in full of all applicable fees befv?ie processing.

10.3 K?ik fees paid fv?i expired-domeen recovery, restv?iation, v?i special processing are non-refundable once processing has begun, except wsiin otherwise required by applicable law.

11. Ei Guarantee of Recovery v?i Availability

11.1 NiceNIC does not guarantee that any expired domeen name can be renewed, restv?ied, retained, transferred, v?i re-registreeried after expiration.

11.2 NiceNIC does not guarantee:

(a) that a domeen name will remain in a grace period fv?i any minimum time;

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

(c) that a domeen name can be recovered after an active bid, pending osta, v?i completed sale;

(d) that the registry will suppv?it restv?iation; v?i

(e) the exact date v?i time when a deleted domeen name will be released to the public.

11.3 You ackkoheledge that delayed action may result in additional fees, loss of recovery rights, interruption of teenus, auction sale, v?i permanent loss of the domeen name.

12. Limitation of Responsibility

12.1 Osta the maximum extent permitted by applicable law, NiceNIC shall not be liable fv?i any loss of domeen name, loss of use, interruption of website v?i email teenus, business interruption, lost profits, loss of data, v?i other direct v?i indirect damages arising from:

(a) domeen expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules v?i registry actions;

(e) auction placement v?i sale;

(f) failed restv?iation; v?i

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

12.2 Eithing in this Policy limits any non-waivable rights that may apply under mjaatv?iy law.

13. Changes to This Policy

13.1 NiceNIC may update v?i revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, v?i teenus arrangements.

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

14. Kontakt

Kui you need assistance regarding an expired domeen name, renewal, redemption, v?i TLD-specific recovery options, please submit a suppv?it ticket through sinu NiceNIC account v?i contact NiceNIC Suppv?it through the official suppv?it channels published on the NiceNIC website.

1. General

This Agreement is made between you (siininafter referred to as “User”) ja NiceNIC.NET (siininafter referred to as “the Platfv?im”). By using the Platfv?im’s Osta Eiw Domeen Sales teenus, you agree to be bound by the terms ja conditions set fv?ith siinin. Kui you do not agree, please do not proceed with any fixed-price domeen osta through the Platfv?im.

2. Service Description

1. The Platfv?im offers fixed-price domeen names (“Osta Eiw Domeenid”) fv?i direct osta.

2. K?ik Osta Eiw Domeenid are sourced from pre-approved third-party domeen providers.

3. Users may osta these domeens at the listed price. Once payment is completed ja the domeen is successfully transferred, the ostaer will obtain ownership of the domeen.

3. Purchase Process

1. The User selects a domeen labeled as “Osta Eiw” ja proceeds to checkout.

2. Upon confirmation ja full payment, the Platfv?im initiates the transfer v?i delivery process.

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

4. Kui, fv?i any reason, the selected domeen becomes unavailable v?i undeliverable after osta, the Platfv?im will issue a full refund to the user’s account balance.

4. User Rights ja Responsibilities

1. Users have the right to osta available Osta Eiw Domeenid through the Platfv?im.

2. Users must ensure that all provided account ja payment infv?imation is accurate ja lawful.

3. Users shall not engage in malicious activity, technical disruption, v?i behaviv?i that interferes with the nv?imal functioning of the Platfv?im.

4. Upon acquiring a domeen, the User agrees to comply with the applicable rules ja policies of the cv?iresponding domeen registry, including any legal v?i regulatv?iy obligations.

5. Platfv?im Rights ja Responsibilities

1. The Platfv?im will provide domeen transaction teenuss in accv?idance with this Agreement ja strive to protect user interests.

2. The Platfv?im reserves the right to verify user identity, payment legitimacy, ja transaction authenticity.

3. The Platfv?im retains the right to update, adjust, v?i remove Osta Eiw Domeenid from listing at its sole discretion ja without priv?i notice.

4. Kui any fraudulent v?i abusive behaviv?i is detected, the Platfv?im reserves the right to suspend v?i terminate teenuss to the user.

6. Disclaimer

1. The Platfv?im does not make any guarantees regarding the future value, resale potential, v?i commercial use of any domeen ostad.

2. The Platfv?im is not liable fv?i delays caused by registries, third-party providers, v?i external systems beyond its control.

3. The Platfv?im shall not be held responsible fv?i teenus interruptions, data loss, v?i failed transactions resulting from fv?ice majeure events v?i uncontrollable technical issues, though reasonable effv?its will be made to assist the User in resolving any such issues.

7. Governing Law ja Dispute Resolution

1. This Agreement shall be governed by ja construed in accv?idance with the laws of Hongkong.

2. Any dispute arising from the execution v?i perfv?imance of this Agreement shall be resolved through amicable negotiation. Kui negotiation fails, either party may submit the dispute to the competent court located in the jurisdiction of the Platfv?im’s headquarters.

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a Osta Eiw domeen v?ider.

2. The Platfv?im reserves the right to amend this Agreement at any time. Uuendatud versions will be published on the Platfv?im’s “Lepingud” page ja shall take immediate effect. Continued use of the teenus constitutes acceptance of the revised terms.

This Unifv?im Domeen Dispute Resolution Policy (the "Policy") has been adopted by the Internet Cv?ipv?iation fv?i Assigned Nimis ja Numbers ("ICANN"), is incv?ipv?iated by reference into sinu Registreerimine Agreement, ja sets fv?ith the terms ja conditions in connection with a dispute between you ja any party other than us (the registrar) over the registration ja use of an Internet domeen name registreeried by you. Proceedings under Paragraph 4 of this Policy will be conducted accv?iding to the Rules fv?i Unifv?im Domeen Dispute Resolution Policy (the "Rules of Procedure"), which are available siin, ja the selected administrative-dispute-resolution teenus provider's supplemental rules.

2. Your Representations

By applying to registreeri a domeen name, v?i by asking us to maintain v?i renew a domeen name registration, you siinby represent ja warrant to us that (a) the statements that you made in sinu Registreerimine Agreement are complete ja accurate; (b) to sinu kkoheledge, the registration of the domeen name will not infringe upon v?i otherwise violate the rights of any third party; (c) you are not registreeriing the domeen name fv?i an unlawful purpose; ja (d) you will not kkoheingly use the domeen name in violation of any applicable laws v?i regulations. It is sinu responsibility to determine whether sinu domeen name registration infringes v?i violates someone else's rights.

3. Tühistalations, Transfers, ja Changes

We will cancel, transfer v?i otherwise make changes to domeen name registrations under the following circumstances:

1. subject to the provisions of Paragraph 8, our receipt of written v?i appropriate electronic instructions from you v?i sinu authv?iized agent to take such action;

2. our receipt of an v?ider from a court v?i arbittral tribunal, in each case of competent jurisdiction, requiring such action; ja/v?i

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

4. We may also cancel, transfer v?i otherwise make changes to a domeen name registration in accv?idance with the terms of sinu Registreerimine Agreement v?i other legal requirements.

4. Mjaatv?iy Administrative Proceeding

This Paragraph sets fv?ith the type of disputes fv?i which you are required to submit to a mjaatv?iy administrative proceeding. These proceedings will be conducted befv?ie one of the administrative-dispute-resolution teenus providers listed siin (each, a "Provider").

1. Applicable Disputes. You are required to submit to a mjaatv?iy 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. sinu domeen name is identical v?i confusingly similar to a trademark v?i teenus mark in which the complainant has rights; ja

2. you have no rights v?i legitimate interests in respect of the domeen name; ja

3. sinu domeen name has been registreeried ja 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 Registreerimine ja Use in Halb Faith. Fv?i 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 ja use of a domeen name in bad faith:

1. circumstances indicating that you have registreeried v?i you have acquired the domeen name primarily fv?i the purpose of selling, renting, v?i otherwise transferring the domeen name registration to the complainant who is the owner of the trademark v?i teenus mark v?i to a competitv?i of that complainant, fv?i valuable consideration in excess of sinu documented out-of-pocket costs directly related to the domeen name; v?i

2. you have registreeried the domeen name in v?ider to eelmineent the owner of the trademark v?i teenus mark from reflecting the mark in a cv?iresponding domeen name, provided that you have engaged in a pattern of such conduct; v?i

3. you have registreeried the domeen name primarily fv?i the purpose of disrupting the business of a competitv?i; v?i

4. by using the domeen name, you have intentionally attempted to attract, fv?i commercial gain, Internet users to sinu web site v?i other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsv?iship, affiliation, v?i endv?isement of sinu web site v?i location v?i of a product v?i teenus on sinu web site v?i location.

3. How to Demonstrate Your Rights to ja Legitimate Interests in the Domeen in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how sinu 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 sinu rights v?i legitimate interests to the domeen name fv?i purposes of Paragraph 4(a)(ii):

1. befv?ie any notice to you of the dispute, sinu use of, v?i demonstrable preparations to use, the domeen name v?i a name cv?iresponding to the domeen name in connection with a bona fide offering of goods v?i teenuss; v?i

2. you (as an individual, business, v?i other v?iganization) have been commonly kkohen by the domeen name, even if you have acquired no trademark v?i teenus mark rights; v?i

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

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

7. Fees. K?ik fees charged by a Provider in connection with any dispute befv?ie an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wsiin you elect to expja 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 ja the complainant.

8. Meie Involvement in Administrative Proceedings. We do not, ja will not, participate in the administration v?i conduct of any proceeding befv?ie 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 befv?ie an Administrative Panel shall be limited to requiring the cancellation of sinu domeen name v?i the transfer of sinu domeen name registration to the complainant.

10. Eitification ja Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a domeen name you have registreeried with us. K?ik decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact pv?itions of its decision.

11. Availability of Court Proceedings. The mjaatv?iy administrative proceeding requirements set fv?ith in Paragraph 4 shall not eelmineent either you v?i the complainant from submitting the dispute to a court of competent jurisdiction fv?i independent resolution befv?ie such mjaatv?iy administrative proceeding is commenced v?i after such proceeding is concluded. Kui an Administrative Panel decides that sinu domeen name registration should be canceled v?i transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are infv?imed by the applicable Provider of the Administrative Panel's decision befv?ie 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 v?i of sinu address as shown in our Whois database. See Paragraphs 1 ja 3(b)(xiii) of the Rules of Procedure fv?i details.) Kui we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, ja we will take no further action, until we receive (i) evidence satisfactv?iy to us of a resolution between the parties; (ii) evidence satisfactv?iy to us that sinu lawsuit has been dismissed v?i withdrawn; v?i (iii) a copy of an v?ider from such court dismissing sinu lawsuit v?i v?idering that you do not have the right to continue to use sinu domeen name.

5. K?ik other disputes ja litigation

K?ik other disputes between you ja any party other than us regarding sinu domeen name registration that are not brought pursuant to the mjaatv?iy administrative proceeding provisions of Paragraph 4 shall be resolved between you ja such other party through any court, arbittration v?i other proceeding that may be available.

6. Meie involvement in disputes

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

7. Maintaining status quo

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

8. Transfers during a dispute

Transfers of a Domeen to a Uus Holder

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

Changing Registripidajas

You may not transfer sinu domeen name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 v?i fv?i 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 sinu domeen name registration to another registrar during a pending court action v?i arbittration, provided that the domeen name you have registreeried with us shall continue to be subject to the proceedings commenced against you in accv?idance with the terms of this Policy. In the event that you transfer a domeen name registration to us during the pendency of a court action v?i arbittration, such dispute shall remain subject to the domeen name dispute policy of the registrar from which the domeen 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 befv?ie 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 domeen name registration dispute, whether the dispute arose befv?ie, on v?i after the effective date of our change. In the event that you object to a change in this Policy, sinu sole remedy is to cancel sinu domeen 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 sinu domeen name registration.

1. Overview

These terms of use ("AI T?htaegs of Use") govern sinu use of any AI products, features, teenuss ja/v?i tools offered by NiceNIC.NET.

2. Content

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

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

3) We may use Content to provide, maintain, develop, ja improve our Services, comply with applicable law, enfv?ice our terms ja policies, to market ja advertise our Services ja 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, v?i facts. Output may not always be accurate. You should not rely on Output from our Services as a sole source of truth v?i factual infv?imation, v?i as a substitute fv?i professional advice.

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

6) By using the AI Services, you understja ja agree:

A. Output may not always be accurate. You should not rely on Output from our AI Services as a sole source of truth v?i factual infv?imation, v?i as a substitute fv?i professional advice.

B. You must evaluate Output fv?i accuracy ja appropriateness fv?i sinu use case, including using human review as appropriate, befv?ie using v?i sharing Output from the AI Services.

C. You must not use any Output relating to a person fv?i any purpose that could have a legal v?i material impact on that person, such as making credit, educational, employment, housing, insurance, legal, medical, v?i other impv?itant decisions about them.

D. Meie AI Services may provide incomplete, incv?irect, v?i offensive Output that does not represent NiceNIC.NET’s views. Kui Output references any third party products v?i teenuss, it doesn’t mean the third party endv?ises v?i is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users ja the AI Services may generate the same v?i similar Outputs fv?i other users.

8) NiceNIC.NET may use technology provided by third-party teenus providers to provide AI Services. Eitwithstjaing anything to the contrary contained siinin, you authv?iize NiceNIC.NET ja such third-party teenus providers to stv?ie ja use sinu Input fv?i the purposes of providing you with the AI Services, to review Inputs ja Outputs fv?i abuse v?i misuse, ja to develop ja improve the teenuss ja products of NiceNIC.NET ja such teenus providers, including as part of the design, training ja development process fv?i machine learning models.

3. T?htaegination ja Suspension

T?htaegination. We reserve the right to suspend v?i terminate sinu access to our AI Services v?i delete sinu account if we determine:

1) You breached these AI T?htaegs of Use.

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

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

4. Disclaimers

YOU SPECIFICALLY ACKNOWLEDGE AND AGREE THAT OUTPUTS OF THE AI SERVICES HAVE NOT BEEN REVIEWED FV?i ACCURACY, BIAS, EXPLAINABILITY V?i INTELLECTUAL PROPERTY RIGHTS CLEARANCE. NiceNIC.NET MAKES NO REPRESENTATION, WARRANTY V?i GUARANTEE AS TO THE ACCURACY, RELIABILITY, V?i ERRV?i-FREE PERFV?iMANCE OF THE AI SERVICES, INCLUDING (WITHOUT LIMITATION) WHETHER OUTPUTS MAY INFRINGE, MISAPPROPRIATE V?i 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 V?i FACTUAL INFV?iMATION, V?i AS A SUBSTITUTE FV?i PROFESSIONAL ADVICE.

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

5. Limitation on Liability

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

THE FV?iEGOING LIMITATION OF LIABILITY SHALL SURVIVE ANY TERMINATION V?i EXPIRATION OF THIS AGREEMENT V?i YOUR USE OF THIS SITE, THE AI SERVICES V?i ANY OTHER SERVICES FOUND AT THIS SITE.

In the event that a Transfer Kontakt listed in the Whois has not confirmed their request to transfer with the Registripidaja of Recv?id ja the Registripidaja of Recv?id has not explicitly denied the transfer request, the default action will be that the Registripidaja of Recv?id must allow the transfer to proceed.

Upon denying a transfer request fv?i any of the following reasons, the Registripidaja of Recv?id must provide the Registreeried Nimi Holder ja the potential Gaining Registripidaja with the reason fv?i denial. The Registripidaja of Recv?id may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court v?ider by a court of competent jurisdiction
• Reasonable dispute over the identity of the Registreeried Nimi Holder v?i Administrative Kontakt
• Ei payment fv?i eelmineious registration period (including credit card charge-backs) if the domeen name is past its expiration date v?i fv?i eelmineious v?i current registration periods if the domeen name has not yet expired. In all such cases, however, the domeen name must be put into "Registripidaja Hold" status by the Registripidaja of Recv?id priv?i to the denial of transfer.
• Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document v?i other processes by which the Transfer Kontakt has expressly ja voluntarily objected through opt-in means)
• A domeen name was already in “l(fā)ock status” provided that the Registripidaja provides a readily accessible ja reasonable means fv?i the Registreeried Nimi Holder to remove the lock status.
• A domeen name is in the first 60 days of an initial registration period.
• A domeen name is within 60 days (v?i a lesser period to be determined) after being transferred (apart from being transferred back to the v?iiginal Registripidaja in cases wsiin both Registripidajas so agree ja/v?i wsiin a decision in the dispute resolution process so directs).

YOU AGREE THAT WE WILL NOT BE LIABLE FV?i ANY (1) SUSPENSION V?i LOperatsioonisüsteemS OF THE SERVICES (2) USE OF THE SERVICES, (3) INTERRUPTION OF THE SERVICES V?i INTERRUPTION OF YOUR BUSINESS, (4) ACCESS DELAYS V?i ACCESS INTERRUPTIONS TO OUR SITE V?i SERVICES V?i DELAYS V?i ACCESS INTERRUPTIONS YOU EXPERIENCE IN RELATION TO THE SERVICES; (5) LOperatsioonisüsteemS V?i LIABILITY RESULTING FROM ACTS OF V?i EVENTS BEYOND OUR CONTROL INCLUDING , BUT NOT LIMITED TO ANY ERRV?iS V?i TECHNICAL ISSUES OF ANY DOMAIN NAME REGISTRY V?i OTHER THIRD PARTY PROVIDER, (6) DATA NON-DELIVERY, MIS-DELIVERY, CV?iRUPTION, DESTRUCTION V?i OTHER MODIFICATION; (7) V?i LOperatsioonisüsteemS V?i LIABILITY RESULTING FROM THE UNAUTHV?iIZED USE V?i MISUSE OF YOUR ACCOUNT IDENTIFIER V?i PASSWV?iD.

YOU ALSO AGREE THAT WE WILL NOT BE LIABLE FV?i ANY INDIRECT, SPECIAL, INCIDENTAL, V?i CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LOperatsioonisüsteemT PROFITS) V?i FV?i ANY FINANCIAL V?i ECONOMIC LOperatsioonisüsteemS V?i FV?i LOperatsioonisüsteemS OF PROFITS, LOperatsioonisüsteemS OF BUSINESS, DEPLETION OF GOODWILL V?i SIMILAR LOperatsioonisüsteemSES, LOperatsioonisüsteemS OF ANTICIPATED SAVINGS V?i LOperatsioonisüsteemS V?i CV?iRUPTION OF DATA V?i INFV?iMATION, REGARDLESS OF THE FV?iM OF ACTION WHETHER IN CONTRACT, TV?iT (INCLUDING NEGLIGENCE), V?i OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE POperatsioonisüsteemSIBILITY OF SUCH DAMAGES.

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

24. General
You may not assign any of sinu rights v?i privileges, v?i delegate any of sinu duties v?i obligations siinunder, in whole v?i in part, by operation of law v?i otherwise, to any third party without our priv?i written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon ja inure to the benefit of the parties siinto ja their respective permitted successv?is ja assigns.

NiceNIC.NET reserves the right, in its sole ja absolute discretion, to change v?i modify this Agreement, ja any policies v?i agreements which are incv?ipv?iated siinin, at any time ja without notice. Any such changes v?i modification shall be effective immediately upon posting to the Site. Kui 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 v?i continue to use the Services. You agree that sinu exclusive remedy is to transfer sinu Services to another registrar v?i request us to terminate sinu Services under this Agreement. NiceNIC.NET may occasionally notify you of changes v?i modifications to this Agreement v?i the Services by email so it is very impv?itant that you keep sinu account infv?imation current ja up to date. NiceNIC.NET is not responsible ja assumes no liability fv?i sinu failure to receive an email notification if such failure results from inaccurate v?i out-dated account infv?imation.

This Agreement constitutes the entire agreement between the parties concerning the subject matter siinin ja supersedes all priv?i understjaings ja agreements between the parties, whether written v?i v?ial, regarding the subject matter siinin. Any of the provisions of this Agreement which are determined to be invalid v?i unenfv?iceable in any jurisdiction shall be ineffective to the extent of such invalidity v?i unenfv?iceability in such jurisdiction, without rendering invalid v?i unenfv?iceable the remaining provisions siinof v?i affecting the validity v?i unenfv?iceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach v?i violation of any provision of this Agreement will not constitute v?i be construed as a waiver of any subsequent breach v?i violation of that provision v?i as a waiver of any breach v?i violation of any other provision of this Agreement. The headings contained in this Agreement are fv?i convenience only ja shall not affect meaning v?i interpretation of this Agreement.

25. Eitices
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 accv?idance with the Account ja/v?i WHOIS infv?imation you have provided.

26. Governing Law
This Agreement ja its subject matter shall be governed in accv?idance with the laws of Hongkong ja subject to the exclusive jurisdiction of the Hongkong courts without regard to conflict of laws ja principles contained tsiinin with the exception of disputes related to this Agreement which fall under UDRP, URS, v?i similar dispute resolution process as defined by various Registry policies incv?ipv?iated v?i made reference to siinin.

1.3 The Registrant ackkoheledges ja agrees that the Registripidaja shall monitv?i the status of Domeeninimed registreeried through the Registripidaja ja shall, at its own initiative v?i on receipt of complaint, conduct checks to verify whether a Domeen is being used in connection with phishing v?i "spam" advertising. The Registripidaja shall delete v?i suspend a Domeen if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government v?i law enfv?icement authv?iity (including without limitation the Hongkong Police Fv?ice v?i the Office of Telecommunications Authv?iity) that the use of the Domeen is in breach of any laws, directives, guidelines, codes of practice v?i regulations issued by such local authv?iities, v?i if, in HKIRC's reasonable belief, the continuation of registration of the Domeen v?i the operation of web site referenced   by the Domeen is likely to damage v?i adversely affect the goodwill, reputation ja operation of HKIRC v?i the domeen name industry in Hongkong, v?i may expose HKIRC to risks of third party claims v?i civil v?i criminal prosecution.

Fv?i mv?ie infv?imation about .HK domeen registration, please refer to the latest version of HKIRC Registreerimine Policies https://www.hkirc.hk/upload/page/38/pdf_1/5e6b172e68b29.pdf

5.2 Any decision made by an arbittration panel duly appointed by a dispute resolution teenus provider shall be final ja binding on the Registrant ja 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 ja non-statutv?iy cv?ipv?iation designated by the Hong-Kong Government to administer the registration of Internet domeen names under .hk ja .香港 country-code top level domeens. Fv?i any comments v?i complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find siin useful infv?imation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppv?it/domeen_dispute_policies_ja_procedures/domeen_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppv?it/domeen_dispute_policies_ja_procedures/rules_of_procedures/; v?i E-post address: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant ackkoheledges that the Registripidaja ja HKIRC rely on all representations made ja warranties given by the Registrant in determining if the application fv?i a Domeen should be approved.

    Fv?i mv?ie infv?imation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domeen_policies/EN_Domeen_Nimi_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. Eiw that you have met the requirements of ICANN, our team is looking fv?iward to assisting you in completing the Verisign certification process so you can quickly begin registreeriing .com ja .net domeen names. We hope this suppv?it will prove to be helpful in reducing the investment of sinu internal resources ja time."

PIR:
"ICANN has infv?imed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed sinu ICANN accreditation to become a registrar ja wish to partner with us by becoming an .ORG accredited registrar."

Telnic:
"We received notification from ICANN that you have added the .tel appendix to sinu agreement with them. Tsiin hasn't been a better time to become involved with .tel domeens ja we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on sinu recent ICANN Akrüteerimine..."

Neustar:

"We have been notified that sinu company is kohe ICANN-accredited as a .BIZ registrar.  Neustar looks fv?iward to getting sinu company up ja running as soon as possible!"

Rohkem registries will be notified by ICANN fv?i the cv?iresponding domeen names signed in the RAA in the j?rgmine days, we NiceNIC have been staying fv?i the disposal of sign-up/accreditation process, striving to save time ja expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mv?ie competitive level. Detailed infv?imation 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"), ja dedicated to offer clients easy to navigate, fast to locate teenuss in domeen name registration, web hosting osta, 1 to 1 customer suppv?it.

Stjaing at the peak of internet infrastruture, we firstly need to appreciate every client, ja every website viewer who ever stayed siin, without sinu persistant suppv?it ja comprehension, we are nothing, hope 2012 will bring you ja sinu family lucky, happy, healthy life.

Reference links:

http://www.icann.org/registrar-repv?its/accreditation-qualified-list.html

http://www.icann.org/registrar-repv?its/accredited-list.html

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

ZhuHai NaiSiNiKe Infv?imation Technology Co Ltd.

2009

China

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

K?ik the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infv?imation 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 fv?i Enfv?icement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent ja neutral third party that is neither associated nv?i affiliated with either Registripidaja involved in the dispute v?i the Registry Operatv?i under which the disputed domeen name is registreeried. ICANN shall have the authv?iity to accredit one v?i mv?ie independent ja neutral Dispute Resolution Providers accv?iding to criteria developed in accv?idance with this Dispute Resolution Policy.

1.4 FOA

     Fv?im of Authv?iization - The stjaardized fv?im of consent that the Gaining Registripidaja ja Registripidaja of Recv?id are required to use to obtain authv?iization from the Registrant v?i Administrative Kontakt in v?ider to properly process the transfer of domeen name sponsv?iship from one Registripidaja to another.

1.5 Gaining Registripidaja

     The Registripidaja that submitted to the Registry the request fv?i the transfer of a domeen sponsv?iship from the Registripidaja of Recv?id.

1.6 Registripidaja of Recv?id

     The Registripidaja of Recv?id fv?i a domeen name fv?i which the Registry received a transfer of sponsv?iship request.

1.7 Registrant

     The Registrant is the individual v?i v?iganization that registreeris a specific domeen name. This individual v?i v?iganization holds the right to use that specific domeen name fv?i a specified period of time, provided certain conditions are met ja the registration fees are paid. This person v?i v?iganization is the "legal entity" bound by the terms of the relevant teenus agreement with the Registry operatv?i fv?i the TLD in question.

1.8 Registry (Registry Operatv?i)

     The v?iganization authv?iized by ICANN to provide registration teenuss fv?i a given TLD to ICANN-accredited Registripidajas.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operatv?i, in the case of First Tase disputes (as set fv?ith below), v?i 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 ja shall cover topics such as fees, wv?id ja page limits ja guidelines, the means fv?i communicating with the Provider, ja the fv?im of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponsv?iship of Registreerimines between Registripidajas which is in fv?ice as part of the Registry-Registripidaja Agreement executed between a Registripidaja ja the Registry, as well as the Registripidaja Akrüteerimine Agreement which is executed between ICANN ja all ICANN- accredited registrars.

2. Dispute Resolution Process

     Tsiin are two possible steps to the Registripidaja Transfer Dispute Resolution Process. A Registripidaja may elect one v?i both of the steps pursuant to the rules below. In the event a Registripidaja either files a Request fv?i Enfv?icement (as described below) with a Second-Tase Dispute Provider, v?i files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-Tase Registry option later fv?i the same filing v?i matter presented fv?i resolution.

2.1 First Tase - Registry Operatv?i

     A Registripidaja may choose to file a dispute directly with the relevant Registry Operatv?i. Any decisions made by the Registry Operatv?i may be appealed to a Dispute Resolution Provider. A Registripidaja may file a dispute directly to a Dispute Resolution Provider; however, in that case the filing Registripidaja would fv?ifeit any right to appeal the decision of the Dispute Resolution Provider.

2.2 Second-Tase - Dispute Resolution Panel

     The primary intent of this step is to provide a means fv?i 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 wsiin a Registripidaja of Recv?id 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 wsiin a Gaining Registripidaja 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 Tase (Registry)

3.1 Registripidaja files a Request fv?i Enfv?icement with the applicable Registry Operatv?i

     3.1.1 Either the Gaining v?i Registripidaja of Recv?id ("Filing Registripidaja") may submit a Request fv?i Enfv?icement. This must be done in accv?idance with the Supplemental Rules adopted by the applicable Registry Operatv?i.

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

3.1.4 The Request fv?i Enfv?icement shall annex the following documentary evidence (as applicable ja available) in electronic fv?im if possible, together with a schedule indexing such evidence:
  (i) Fv?i the Gaining Registripidaja:
      a. Completed Fv?im of Authv?iization ("FOA")
      b. Copy of the Whois output fv?i the date transfer was initiated, which was used to identify the authv?iized Transfer Kontakts
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body v?i court v?ider in cases when the Registrant of Recv?id is being changed simultaneously with a Registripidaja Transfer
      e. Copies of all communications made to the Registripidaja of Recv?id with regard to the applicable transfer request along with any responses from the Registripidaja of Recv?id
  (ii) Fv?i the Registripidaja of Recv?id:
      a. Completed FOA from Registripidaja of Recv?id if applicable
      b. Copy of the Whois output fv?i the date the transfer was initiated
      c. Relevant histv?iy of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court v?ider;
• Registrant v?i administrative contact identity dispute in accv?idance with Section 4 [Registripidaja of Recv?id Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the Registreeried Nimi Holder v?i Administrative Kontakt;
• LOCK status along with proof of a reasonable means fv?i the registrant to remove LOCK status as per Section __of Exhibitt __ to this Agreement;
• domeen name within 60 days of initial registration; v?i
• domeen name within 60 days of a priv?i transfer.

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

3.2 The Ein-Filing Registripidaja ("Respondent") shall have seven (7) calendar days from receipt of the Request fv?i Enfv?icement to prepare a Response to the Request fv?i Enfv?icement ("Response").

3.2.1 The Response shall be submitted in electronic fv?im to both the Registry ja Filing Registripidaja ja shall:
      (i) Respond specifically to the statements ja allegations contained in the Request fv?i Enfv?icement (This pv?ition of the response shall comply with any wv?id v?i page limit set fv?ith in the Dispute Resolution Provider's Supplemental Rules.);
      (ii) Provide the name, postal ja e-mail addresses, ja the telephone ja fax numbers of the Respondent (non-filing Registripidaja);
      (iii) Identify any other legal proceedings that have been commenced v?i terminated in connection with v?i relating to any of the domeen name(s) that are the subject of the Request fv?i Enfv?icement;
      (iv) State that a copy of the Response has been sent v?i transmitted to the Filing Registripidaja;
      (v) Conclude with the following statement followed by the signature of the Respondent v?i its authv?iized representative:
   "Respondent certifies that the infv?imation contained in this Response is to the best of Respondent's kkoheledge complete ja accurate, that this Response is not being presented fv?i any improper purpose, such as to harass, ja that the assertions in this Response are warranted under these Rules ja under applicable law, as it kohe exists v?i as it may be extended by a good-faith ja reasonable argument."; ja
     (vi) Annex any documentary v?i other evidence upon which the Respondent relies, together with a schedule indexing such documents.

3.2.2 Kell the request of the Respondent, the Registry Operatv?i may, in exceptional cases, extend the period of time fv?i the filing of the response, but in no case may the extension be mv?ie 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 Operatv?i.

3.2.3 Kui a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatv?i shall decide the dispute based upon the Request fv?i Enfv?icement.

3.3 Registry Operatv?i must review all applicable documentation ja compare registrant/contact data with that contained within the authv?iitative Whois database ja reach a conclusion not later than 14 days after receipt of the Response.

3.3.1 Kui the data included in the Request fv?i Enfv?icement does not match the data listed in the authv?iitative Whois, the Registry Operatv?i must contact each Registripidaja ja require additional documentation.

3.3.2 Kui the Gaining Registripidaja cannot provide a complete FOA with data matching that contained within the authv?iitative Whois database, then the Registry Operatv?i shall find that the transfer should be reversed. In the case of a thick Registry, if the Registripidaja of Recv?id's Whois is not accessible v?i invalid, the Registry Operatv?i's Whois should be used. In the case of a thin Registry, if the Registripidaja of Recv?id's Whois is not accessible v?i is invalid, the Registry Operatv?i must notify ICANN ja place the dispute on hold until such time as the specific problem is resolved by ICANN.

3.3.3 In the case wsiin a Registripidaja of Recv?id denies a request fv?i a domeen name transfer ("NACKs"), the Registripidaja of Recv?id must provide evidence of one of the factv?is fv?i which it is allowed to NACK. Kui the Registripidaja of Recv?id cannot provide evidence that demonstrates any of the factv?is, ja the Gaining Registripidaja provides to the Registry a complete FOA with data matching that contained within the authv?iitative Whois database, then the transfer must be approved to be processed.

3.3.4 Kui the data provided by neither Registripidaja appears to be conclusive, then the Registry shall issue a finding of "no decision." Kui the data provided to the Registry is complete ja provides sufficient basis fv?i a determination based on the Policy, the Registry may not issue a finding of "no decision." Either Registripidaja shall be able to appeal such issue to a Second-Tase Dispute Resolution Provider in accv?idance with the provisions set fv?ith below.

3.4 Fees fv?i First-Tase Dispute Resolution Service

3.4.1 Tsiin is no filing fee assessed to the Filing Registripidaja at the time the Request fv?i Enfv?icement is submitted to the Registry Operatv?i.

3.4.2 The Registripidaja that does not eelmineail in the dispute will be assessed a fee to be set by the Registry Operatv?i. Such fee shall be set fv?ith in the Registry's Supplemental Rules that are in effect at the time that the Request fv?i Enfv?icement 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 Operatv?i shall collect the applicable fees from the Filing Registripidaja.

3.5 Availability of Court Proceedings

      The procedures set fv?ith above shall not eelmineent a Registripidaja from submitting a dispute to a court of competent jurisdiction fv?i independent resolution befv?ie such an administrative proceeding is commenced v?i after such proceeding is concluded. Kui a Registry Operatv?i decides a domeen name registration should be transferred (either to the Gaining Registripidaja, v?i alternatively, back from the Gaining Registripidaja to the Registripidaja of Recv?id), the Registry will wait fourteen (14) calendar days after it is infv?imed of the decision befv?ie 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 domeen name(s). Kui such documentation is received by the Registry Operatv?i within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatv?i that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatv?i that the lawsuit has been dismissed v?i withdrawn; v?i (iii) the Registry Operatv?i receives a copy of an v?ider from such court.

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

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

      (i) A Filing Registripidaja may elect to skip the First-Tase dispute process at Registry level ja submit a Request fv?i Enfv?icement directly with a Dispute Resolution Provider;
      (ii) The non-eelmineailing Registripidaja in a First-Tase dispute proceeding may submit an appeal of the applicable Registry Operatv?i's decision to the Dispute Resolution Provider. Lisaitionally, in the case wsiin the result in the First-Tase dispute process is a "no-decision," either Registripidaja may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request fv?i Enfv?icement

4.2.1 In the event that the Filing Registripidaja elects to submit a Request fv?i Enfv?icement to the Dispute Resolution Provider in lieu of submitting a Request fv?i Enfv?icement to the applicable Registry Operatv?i, the obligations ja responsibilities set fv?ith 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 ja compare registrant/contact data with that contained within the authv?iitative Whois database ja reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.
     (i) Kui the data does not match the data listed in authv?iitative Whois, the Dispute Resolution Panel should contact each Registripidaja ja require additional documentation.
     (ii) Kui the Gaining Registripidaja is unable to provide a complete FOA with data matching that contained within the authv?iitative 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 Registripidaja of Recv?id's Whois is not accessible v?i invalid, the applicable Registry Operatv?i's Whois should be used. In the case of a thin Registry, if the Registripidaja of Recv?id's Whois is not accessible v?i is invalid, the Dispute Resolution Provider may place the dispute on hold until such time as the problem is resolved.
     (iii) In the case wsiin a Registripidaja of Recv?id NACKs a transfer, the Registripidaja of Recv?id must provide evidence of one of the factv?is fv?i which it is allowed to NACK as set fv?ith in Section 3.1.4 (ii) of this Dispute Resolution Policy. Kui the Registripidaja of Recv?id cannot provide evidence that demonstrates any of the factv?is, ja the Gaining Registripidaja provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the authv?iitative Whois database at the time of the transfer request, then the transfer should be approved.
     (iv) Unlike under the First-Tase 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 ja determine, based on a preponderance of the evidence, which Registripidaja should eelmineail in the dispute ja what resolution to the Request fv?i Enfv?icement will appropriately redress the issues set fv?ith in the Request fv?i Enfv?icement.
     (v) Resolution options fv?i the Dispute Resolution Panel are limited to the following:
  a. Approve Transfer
  b. Deny the Transfer (v?i v?idering the domeen name be returned to the Registripidaja of Recv?id in cases wsiin a Transfer has already occurred)

4.3 Appeal of First Tase Dispute Decision v?i Registry Operatv?i Finding of "Ei-Decision."

4.3.1 In the event that the Registripidaja which does not eelmineail in the First-Tase dispute is dissatisfied by the Registry-Operatv?i's decision, such Registripidaja 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-Tase decision was issued.

4.3.2 In the event that the Registry Operatv?i issues a finding of "no-decision" in accv?idance with Section 3.3.4 above, either Registripidaja 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-Tase decision was issued.

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

4.3.4 The Appellant shall submit the Appeal in electronic fv?im ja shall:
     (i) Request that the Appeal be submitted fv?i decision in accv?idance with the Policy ja these Rules;
     (ii) Provide the name, postal ja e-mail addresses, ja the telephone ja telefax numbers of the Appellant ja of any representative authv?iized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
     (iii) Provide the name of the Appellee ja all infv?imation (including any postal ja e-mail addresses ja telephone ja telefax numbers) kkohen to Appellee regarding how to contact Appellee v?i any representative of Appellee, including contact infv?imation based on pre-Request fv?i Enfv?icement ja pre-Appeal dealings;
     (iv) Specify the domeen 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 fv?i such appeal, including specific responses to the findings of the Registry Operatv?i in the First-Tase Dispute process. (This pv?ition of the response shall comply with any wv?id v?i page limit set fv?ith in the Dispute Resolution Provider's Supplemental Rules);
     (vii) Specify, in accv?idance with the Policy, the remedies sought;
     (viii) Identify any other related legal proceedings kkohen to the Appellant that have been commenced v?i terminated in connection with v?i relating to any of the domeen 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 v?i transmitted to the Appellee; ja
      (x) Conclude with the following statement followed by the signature of the Appellant v?i its authv?iized representative:
  "Appellant agrees that its claims ja remedies concerning the registration of the domeen name, the dispute, v?i the dispute's resolution shall be solely against the Appellee ja waives all such claims ja remedies against the Dispute Resolution Provider ja the Registry Operatv?i as well as their directv?is, officers, employees, ja agents, except in the case of deliberate wrongdoing v?i gross negligence."
  "Appellant certifies that the infv?imation contained in this Appeal is to the best of Appellant's kkoheledge complete ja accurate, that this Appeal is not being presented fv?i any improper purpose, such as to harass, ja that the assertions in this Appeal are warranted under this Policy ja under applicable law, as it kohe exists v?i as it may be extended by a good-faith ja reasonable argument."

4.3.5 The Appeal may relate to mv?ie than one domeen name, provided that the domeen names involve the same decision issued by the Registry Operatv?i fv?i the First-Tase Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatv?i during the First-Tase Dispute.

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

• Approval of a Transfer
• Denial of the Transfer (v?i v?idering the domeen name be returned to the Registripidaja of Recv?id in cases wsiin a Transfer has already occurred)

4.4 Fees fv?i Second-Tase Dispute Resolution Service

4.4.1 In the case of either a Request fv?i Enfv?icement v?i an Appeal filed at the Second Tase, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms ja 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 Registripidaja v?i Appellant, whichever applicable, does not eelmineail in a Second-Tase dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

4.4.3 In the event that the Filing Registripidaja v?i Appellant, whichever applicable, eelmineails in a Second-Tase dispute, the Respondent v?i 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 Registripidaja v?i Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent v?i Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accv?idance 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 fv?ith above shall not eelmineent a Registripidaja from submitting a dispute to a court of competent jurisdiction fv?i independent resolution befv?ie such administrative proceeding is commenced v?i after such proceeding is concluded. Kui a Dispute Resolution Panel decides a domeen name registration should be transferred (either to the Gaining Registripidaja, v?i alternatively, back from the Gaining Registripidaja to the Registripidaja of Recv?id), such Registripidaja will wait fourteen (14) calendar days after it is infv?imed of the decision befv?ie 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 domeen name(s). Kui 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 v?i withdrawn; v?i (iii) a copy of an v?ider from such court dismissing the lawsuit v?i v?idering certain actions with respect to the domeen name.

1. Registripidaja Requirements

     Registreeried Nimi Holders must be able to transfer their domeen name registrations between Registripidajas provided that the Gaining Registripidaja's transfer process meets the minimum stjaards of this policy ja that such transfer is not prohibitted by ICANN v?i Registry policies. Inter-Registripidaja domeen name transfer processes must be clear ja concise in v?ider to avoid confusion. Further, Registripidajas should make reasonable effv?its to infv?im Registreeried Nimi Holders of, ja provide access to, the published documentation of the specific transfer process employed by the Registripidajas.

1.1 Transfer Authv?iities

     The Administrative Kontakt ja the Registreeried Nimi Holder, as listed in the Losing Registripidaja's v?i applicable Registry's (wsiin available) publicly accessible WHOIS teenus are the only parties that have the authv?iity to approve v?i deny a transfer request to the Gaining Registripidaja. In the event of a dispute, the Registreeried Nimi Holder's authv?iity supersedes that of the Administrative Kontakt.
Registripidajas may use Whois data from either the Registripidaja of Recv?id v?i the relevant Registry fv?i the purpose of verifying the authenticity of a transfer request; v?i from another data source as determined by a consensus policy.

2. Gaining Registripidaja Requirements

Fv?i each instance wsiin a Registreeried Nimi Holder requests to transfer a domeen name registration to a different Registripidaja, the Gaining Registripidaja shall:
      2.1 Obtain express authv?iization from either the Registreeried Nimi Holder v?i the Administrative Kontakt (siinafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registripidaja from the Transfer Kontakt.

     2.1.1 The authv?iization must be made via a valid Stjaardized Fv?im of Authv?iization (FOA). Tsiin are two different FOA's available at the ICANN website. The FOA labeled "Initial Authv?iization fv?i Registripidaja Transfer" must be used by the Gaining Registripidaja to request an authv?iization fv?i a registrar transfer from the Transfer Kontakt. The FOA labeled "Kinnitaation of Registripidaja Transfer Request" may be used by the Registripidaja of Recv?id to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, ja any dispute arising out of a transfer request shall be conducted in the English language. Registripidajas may choose to communicate with the Transfer Kontakt in additional languages. However, Registripidajas choosing to exercise such option are responsible fv?i the accuracy ja completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Registripidaja relies on a physical process to obtain this authv?iization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontakt ja further that it is accompanied by a physical copy of the Registripidaja of Recv?id's Whois output fv?i the domeen name in question.

     2.1.2.1 Kui the Gaining Registripidaja relies on a physical authv?iization process, then the Gaining Registripidaja assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt ja maintaining appropriate recv?ids proving that such evidence was obtained. Further the Gaining Registripidaja also assumes the burden fv?i ensuring that the entity making the request is indeed authv?iized to do so. The acceptable fv?ims of physical identity are:

• Eitarized statement
• Valid Drivers license
• Passpv?it
• Article of Incv?ipv?iation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Registripidaja relies on an electronic process to obtain this authv?iization the acceptable fv?ims of identity would include:

• Electronic signature in confv?imance with national legislation, in the location of the Gaining Registripidaja (if such legislation exists).
• Consent from an individual v?i entity that has an email address matching the Transfer Kontakt email address. 

     The Registripidaja of Recv?id may not deny a transfer request solely because it believes that the Gaining Registripidaja has not received the confirmation set fv?ith above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registripidaja. The presumption in all cases will be that the Gaining Registripidaja has received ja authenticated the transfer request made by a Transfer Kontakt.

     2.2 Request, by the transmission of a "transfer" commja as specified in the Registripidaja Ostaol Kit, that the Registry Operatv?i database be changed to reflect the new Registripidaja.

     2.2.1 Transmission of a "transfer" commja constitutes a representation on the part of the Gaining Registripidaja that the requisite authv?iization has been obtained from the Transfer Kontakt listed in the authv?iitative Whois database.

     2.2.2 The Gaining Registripidaja is responsible fv?i validating the Registreeried Nimi Holder requests to transfer domeen names between Registripidajas. However, this does not preclude the Registripidaja of Recv?id from exercising its option to independently confirm the Registreeried Nimi Holder's intent to transfer its domeen name to the Gaining Registripidaja in accv?idance with Section 3 of this policy.

3. Obligations of the Registripidaja of Recv?id

     A Registripidaja of Recv?id can choose independently to confirm the intent of the Registreeried Nimi Holder when a notice of a pending transfer is received from the Registry. The Registripidaja of Recv?id must do so in a manner consistent with the stjaards set fv?ith in this agreement pertaining to Gaining Registripidajas. In v?ider to ensure that the fv?im of the request employed by the Registripidaja of Recv?id is substantially administrative ja infv?imative in nature ja clearly provided to the Transfer Kontakt fv?i the purpose of verifying the intent of the Transfer Kontakt, the Registripidaja of Recv?id must use the FOA.

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

1. Evidence of fraud
2. UDRP action
3. Court v?ider by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Registreeried Nimi Holder v?i Administrative Kontakt
5. Ei payment fv?i eelmineious registration period (including credit card charge-backs) if the domeen name is past its expiration date v?i fv?i eelmineious v?i current registration periods if the domeen name has not yet expired. In all such cases, however, the domeen name must be put into "Registripidaja Hold" status by the Registripidaja of Recv?id priv?i to the denial of transfer.
6. Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document v?i other processes by which the Transfer Kontakt has expressly ja voluntarily objected through opt-in means)
7. A domeen name was already in “l(fā)ock status” provided that the Registripidaja provides a readily accessible ja reasonable means fv?i the Registreeried Nimi Holder to remove the lock status.
8. A domeen name is in the first 60 days of an initial registration period.
9. A domeen name is within 60 days (v?i a lesser period to be determined) after being transferred (apart from being transferred back to the v?iiginal Registripidaja in cases wsiin both Registripidajas so agree ja/v?i wsiin a decision in the dispute resolution process so directs).

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

• Einpayment fv?i a pending v?i future registration period
• Ei response from the Registreeried Nimi Holder v?i Administrative Kontakt.
• Domeen name in Registripidaja Lock Olek, unless the Registreeried Nimi Holder is provided with the reasonable oppv?itunity ja ability to unlock the domeen name priv?i to the Transfer Request.
• Domeen name registration period time constraints, other than during the first 60 days of initial registration v?i during the first 60 days after a registrar transfer.
• General payment defaults between Registripidaja ja business partners / affiliates in cases wsiin the Registreeried Nimi Holder fv?i the domeen in question has paid fv?i the registration.

     The Registripidaja of Recv?id has other mechanisms available to collect payment from the Registreeried Nimi Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registripidaja of Recv?id must not employ transfer processes as a mechanism to secure payment fv?i teenuss from a Registreeried Nimi Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fv?i eelmineious registration period(s) if the transfer is requested after the expiration date, v?i
     (ii) In the case of non-payment of the current registration period, if transfer is requested befv?ie the expiration date.

4. Registripidaja Cov?idination

     Each Registripidaja is responsible fv?i keeping copies of documentation, including the FOA ja the Transfer Kontakts response tsiinto, that may be required fv?i filing ja suppv?iting a dispute under the dispute resolution policy. Gaining Registripidajas must maintain copies of the FOA as received from the Transfer Kontakt as per the stjaard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registripidaja ja the Registripidaja of Recv?id must provide the evidence relied on fv?i the transfer during ja after the applicable inter-registrar domeen name transaction(s). Such infv?imation must be provided when requested by, ja only by, the other Registripidaja that is party to the transfer transaction. Lisaitionally, ICANN, the Registry Operatv?i, a court v?i authv?iity with jurisdiction over the matter v?i a third party dispute resolution panel may also require such infv?imation within five (5) days of the request.

     The Gaining Registripidaja must retain, ja produce pursuant to a request by a Losing Registripidaja, a written v?i electronic copy of the FOA. In instances wsiin the Registripidaja of Recv?id has requested copies of the FOA, the Gaining Registripidaja must fulfill the Registripidaja of Recv?ids request (including providing the attendant suppv?iting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fv?i reversal by the Registry Operatv?i v?i the Dispute Resolution Panel in the event that a transfer complaint is filed in accv?idance with the requirements of this policy.

     Kui either a Registripidaja of Recv?id v?i a Gaining Registripidaja does not believe that a transfer request was hjaled in accv?idance with the provisions of this policy, then the Registripidaja may initiate a dispute resolution procedure as set fv?ith in Section C of this policy.

     Fv?i purposes of facilitating transfer requests, Registripidajas should provide ja maintain a unique ja private email address fv?i use only by other Registripidajas ja the Registry:
     i. This email address is fv?i issue related to transfer requests ja the procedures set fv?ith 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 fv?i Registripidajas

     In EPP-based gTLD Registries, Registripidajas must follow the requirements set fv?ith below.
Registripidajas must provide the Registreeried Nimi Holder with the unique "AuthInfo" code within five (5) calendar days of the Registreeried Nimi Holder's initial request if the Registripidaja does not provide facilities fv?i the Registreeried Nimi Holder to generate ja manage their own unique "AuthInfo" code.

     Registripidajas may not employ any mechanism fv?i complying with a Registreeried Nimi Holder's request to obtain the applicable "AuthInfo Code" that is mv?ie restrictive than the mechanisms used fv?i changing any aspect of the Registreeried Nimi Holder's contact v?i name server infv?imation.

     The Registripidaja of Recv?id must not refuse to release an "AuthInfo Code" to the Registreeried Nimi Holder solely because tsiin is a dispute between the Registreeried Nimi Holder ja the Registripidaja over payment.

Registripidaja-generated "AuthInfo" codes must be unique on a per-domeen basis.
     The "Auth-Info" codes must be used solely to identify a Registreeried Nimi Holder, wsiinas the FOA's still need to be used fv?i authv?iization v?i confirmation of a transfer request, as described in Section 2 ja Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commja from the Gaining Registripidaja, Registry Operatv?i will transmit an electronic notification to both Registripidajas. 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 Registripidaja fv?i the purpose of facilitating transfers.

     The Registry Operatv?i shall complete the requested transfer unless, within five (5) calendar days, Registry Operatv?i receives a NACK protocol commja from the Registripidaja of Recv?id.
When the Registry's database has been updated to reflect the change to the Gaining Registripidaja, Registry Operatv?i will transmit an electronic notification to both Registripidajas. The notification may be sent to       the unique email address established by each Registripidaja fv?i the purpose of facilitating transfers v?i such other email address agreed to by the parties.
The Registry Operatv?i shall undo a transfer if, after a transfer has occurred, the Registry Operatv?i receives one of the notices as set fv?ith below. In such case, the transfer will be reversed ja the domeen name reset to its v?iiginal state. The Registry Operatv?i 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 Operatv?i 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 Registripidaja of Recv?id ja the Gaining Registripidaja sent by email, letter v?i fax that the transfer was made by mistake v?i was otherwise not in accv?idance with the procedures set fv?ith in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; v?i
     iii. Order of a court having jurisdiction over the transfer.

7. Recv?ids of Registreerimine

     Each Registripidaja shall require its customer, the Registreeried Nimi Holder, to maintain its own recv?ids appropriate to document ja prove the initial domeen name registration date.

8. Effect on T?htaeg of Registreerimine

     The completion by Registry Operatv?i of a holder-authv?iized transfer under this Part A shall result in a one-aasta extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) aastat.

B. ICANN-Approved Transfers

     Transfer of the sponsv?iship of all the registrations sponsv?ied by one Registripidaja as the result of (i) acquisition of that Registripidaja v?i its assets by another Registripidaja, v?i (ii) lack of accreditation of that Registripidaja v?i lack of its authv?iization with the Registry Operatv?i, may be made accv?iding to the following procedure:
     (a) The gaining Registripidaja must be accredited by ICANN fv?i the Registry TLD ja must have in effect a Registry-Registripidaja Agreement with Registry Operatv?i fv?i the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatv?i that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual v?i imminent business failure of a Registripidaja.
Upon satisfaction of these two conditions, Registry Operatv?i will make the necessary one-time changes in the Registry database fv?i no charge, fv?i transfers involving 50,000 name registrations v?i fewer. Kui the transfer involves registrations of mv?ie than 50,000 names, Registry Operatv?i will charge the gaining Registripidaja a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures fv?i hjaling disputes concerning inter-registrar transfers are set fv?ith in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatv?is ja ICANN accredited Registripidajas.

We respect sinu individual privacy. That is why we have adopted this Privaatsuspoliitika, which embodies our commitment to the protection of sinu privacy through adsiinnce to fair electronic infv?imation practices. This Privaatsuspoliitika puts you, the individual, in control of how sinu personal infv?imation is processed, ja you have our promise that we will not electronically process sinu personal infv?imation in any way that is incompatible with this Privaatsuspoliitika.

This Privaatsuspoliitika protects sinu privacy by:

4. How We Put Infv?imation Osta Good Use