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.

• The exact domeen name.
• The requestvõi's identity ja contact infvõimation.
• The nature ja type of the requestvõi, including whether the requestvõi is an individual, legal entity, law enfvõicement agency, government authvõiity, intellectual property representative, cybersecurity professional, consumer protection võiganization, või another type of võiganization.
• Wsiin the request is submitted by a representative acting on behalf of another person või entity, a Power of Kelltvõiney statement või similar documentation evidencing the representative's authvõiization to act on the requestvõi's behalf, wsiin applicable ja relevant.
• A list of the specific registration data elements requested.
• The purpose of the request.
• Infvõimation about the legal rights of the requestvõi ja the specific rationale ja basis fvõi the request.
• Whether confidentiality is requested.
• Any suppvõiting legal process, court võider, subpoena, authvõiization, või other relevant documentation.
• An affirmation that the request is being made in good faith.
• An agreement that any registration data disclosed in response to the request will be processed lawfully.
• 
  

1. Overview

These terms of use ("AI 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 “lock 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-posti aadress: 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
• Passaport
• 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 “lock 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. Sõnums 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