1. Scope en Purpose

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

1.2 Domein lifecycle timing may vary depending on the top-level domein (“TLD”), registry rules, registry operatof practices, applicable ICANN requirements, en other governing policies. Neet all TLDs follow the same expiration, redemption, auction, of deletion process.

1.3 In the event of any inconsistency between this Policy en the applicable registry’s rules of menatofy ICANN policy, the applicable registry rules en menatofy policy requirements shall vorigeail.

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

2. Definitions

Fof purposes of this Policy:

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

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

2.3 “Redemption Grace Period” of “RGP” means the post-deletion recovery period, whier available, during which an expired domein name may still be restofable fof an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, whier applicable, during which the domein name can no longer be renewed, restofed, modified, of transferred.

2.5 “Eligible Domein” means a domein name that is subject to NiceNIC’s expired domein auction process. Neet all TLDs of expired domein names are eligible fof auction.

2.6 “Verlopend Domein Auction” means the expired-domein sale process that may apply to certain expired domein names befofe final deletion of release.

2.7 “Sluitenout Auction” means the final sale phase fof certain Eligible Domeinen that were not sold earlier in the expired domein auction process.

3. Effect of Expiration

3.1 Upon expiration, a domein name may stop resolving, en any website, email dienst, of other dienst associated with the domein name may cease functioning immediately of shoftly thierafter.

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

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

4. Verlengenal Neetices en Customer Responsibility

4.1 NiceNIC may send renewal reminders en expiration-related notices befofe en after expiration, as required by applicable policy of as part of NiceNIC’s stenard operational process.

4.2 It is jouw sole responsibility to maintain accurate en current account en contact infofmation, including jouw email address, en to monitof the status of jouw domein names.

4.3 Failure to receive a renewal notice, reminder, invoice, of other communication shall not relieve you of responsibility fof renewing jouw domein name befofe expiration.

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

5. Stenard Post-Expiration Verlengenal

5.1 Fof many generic TLDs, an expired domein name may remain renewable fof approximately thirty (30) days after the Expiration Date at the stenard renewal fee. This is a general reference only en may vary by TLD.

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

5.3 NiceNIC reserves the right to determine whether a domein name remains eligible fof stenard renewal, redemption, of other recovery based on the applicable TLD, registry status, auction status, en operational feasibility.

6. Verlopend Domein Auction fof Eligible Domeinen

6.1 Certain expired domein names may enter NiceNIC’s expired domein auction process befofe all recovery vensters have ended. This process applies only to Eligible Domeinen en does not apply to all TLDs.

6.2 Fof Eligible Domeinen under NiceNIC’s stenard expired-domein process, the following general timeline may apply:

Day 0 after expiration

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

Day 26 after expiration

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

Day 31 after expiration

Als thier is no active bid, the registrant may still be able to recover the domein name by paying the stenard renewal fee plus the applicable redemption fee.

Als thier is an active bid, the domein name may be removed from the registrant’s account en may no longer be renewable through ofdinary renewal of restofation procedures.

Day 37 after expiration

The domein name may enter final closeout auction. Unless thier is a pending kopen of other sale-related restriction, the registrant may still be able to recover the domein name by paying the stenard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. Als the domein name was not sold of otherwise committed to sale, recovery may still be possible fof a limited period, subject to the applicable TLD, registry rules, en NiceNIC’s operational process.

Day 74 after expiration

The domein name may be removed from the registrant’s account en may no longer be renewable of restofable through NiceNIC. After that point, the domein name may become available fof re-registration only after the registry releases it.

6.3 Once an Eligible Domein has an active bid, pending kopen, completed sale, of other sale commitment under the expired-domein process, the registrant’s right to renew of restofe the domein name may be terminated of restricted.

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

7. Redemption Grace Period

7.1 Als an expired domein name is not renewed during the applicable grace period en if the applicable TLD suppofts restofation after deletion, the domein name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the domein name may stop resolving;

(b) website en email diensts may remain unavailable;

(c) the domein name generally cannot be modified of transferred; en

(d) restofation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, en any taxes of menatofy fees.

7.3 Restofation during the Redemption Grace Period is not guaranteed en remains subject to registry suppoft, operational feasibility, the domein’s current status, en the absence of auction of sale restrictions.

8. Pending Delete en Final Release

8.1 Als a domein name is not renewed of restofed during the applicable recovery periods, it may enter the Pending Delete stage, whier suppofted by the applicable TLD.

8.2 During Pending Delete, the domein name cannot be renewed, restofed, transferred, of modified.

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

8.4 NiceNIC does not guarantee the exact time, date, of availability of a domein name once it is released by the registry, en NiceNIC does not guarantee that the fofmer registrant will be able to re-registreer the domein name.

9. TLD-Specific Variations

9.1 Neet all TLDs follow the stenard lifecycle described above. Certain ccTLD’s en other TLDs may have shofter grace periods, no redemption period, no pending delete stage, of earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many ccTLD’s generally follow a lifecycle similar to the stenard expiration, grace, redemption, en deletion process, including, fof example:

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

9.2.2 TLDs with no Pending Delete stage

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

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

9.2.3 TLDs requiring renewal befofe the actual expiration date

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

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

9.2.4 TLDs requiring action five (5) days befofe expiration

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

.CX, .DE, .EU, en .NL.

9.2.5 .CM domeins

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

9.2.6 .GG domeins

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

9.2.7 .PH, .COM.PH, .NET.PH, en .ORG.PH domeins

These domeins may not suppoft a stenard 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. Als the domein is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppoft immediately.

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

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

9.2.9 .TO domeins

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

9.2.10 .NU domeins

.NU domein names may be reactivated in the ofdinary manner within approximately seven (7) days after expiration. Als not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restofation may still be possible through NiceNIC Suppoft.

9.3 The TLD-specific infofmation above is provided fof general reference only en may change at any time based on registry policy, registry system changes, of operational requirements. Customers should contact NiceNIC Suppoft fof current TLD-specific recovery infofmation.

10. Fees en Betalenments

10.1 Stenard renewal fees, redemption fees, restofation fees, auction-related fees, en any other applicable charges shall be those listed by NiceNIC at the time of processing of otherwise communicated by NiceNIC.

10.2 Redemption of restofation requires payment in full of all applicable fees befofe processing.

10.3 Alles fees paid fof expired-domein recovery, restofation, of special processing are non-refundable once processing has begun, except whier otherwise required by applicable law.

11. Nee Guarantee of Recovery of Availability

11.1 NiceNIC does not guarantee that any expired domein name can be renewed, restofed, retained, transferred, of re-registreered after expiration.

11.2 NiceNIC does not guarantee:

(a) that a domein name will remain in a grace period fof any minimum time;

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

(c) that a domein name can be recovered after an active bid, pending kopen, of completed sale;

(d) that the registry will suppoft restofation; of

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

11.3 You acknuledge that delayed action may result in additional fees, loss of recovery rights, interruption of dienst, auction sale, of permanent loss of the domein name.

12. Limitation of Responsibility

12.1 Naar the maximum extent permitted by applicable law, NiceNIC shall not be liable fof any loss of domein name, loss of use, interruption of website of email dienst, business interruption, lost profits, loss of data, of other direct of indirect damages arising from:

(a) domein expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules of registry actions;

(e) auction placement of sale;

(f) failed restofation; of

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

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

13. Changes to This Policy

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

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

14. Contact

Als you need assistance regarding an expired domein name, renewal, redemption, of TLD-specific recovery options, please submit a suppoft ticket through jouw NiceNIC account of contact NiceNIC Suppoft through the official suppoft channels published on the NiceNIC website.

1. General

This Agreement is made between you (hierinafter referred to as “User”) en NiceNIC.NET (hierinafter referred to as “the Platfofm”). By using the Platfofm’s Kopen Neew Domein Sales dienst, you agree to be bound by the terms en conditions set fofth hierin. Als you do not agree, please do not proceed with any fixed-price domein kopen through the Platfofm.

2. Service Description

1. The Platfofm offers fixed-price domein names (“Kopen Neew Domeinen”) fof direct kopen.

2. Alles Kopen Neew Domeinen are sourced from pre-approved third-party domein providers.

3. Users may kopen these domeins at the listed price. Once payment is completed en the domein is successfully transferred, the kopener will obtain ownership of the domein.

3. Purchase Process

1. The User selects a domein labeled as “Kopen Neew” en proceeds to checkout.

2. Upon confirmation en full payment, the Platfofm initiates the transfer of delivery process.

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

4. Als, fof any reason, the selected domein becomes unavailable of undeliverable after kopen, the Platfofm will issue a full refund to the user’s account balance.

4. User Rights en Responsibilities

1. Users have the right to kopen available Kopen Neew Domeinen through the Platfofm.

2. Users must ensure that all provided account en payment infofmation is accurate en lawful.

3. Users shall not engage in malicious activity, technical disruption, of behaviof that interferes with the nofmal functioning of the Platfofm.

4. Upon acquiring a domein, the User agrees to comply with the applicable rules en policies of the cofresponding domein registry, including any legal of regulatofy obligations.

5. Platfofm Rights en Responsibilities

1. The Platfofm will provide domein transaction diensts in accofdance with this Agreement en strive to protect user interests.

2. The Platfofm reserves the right to verify user identity, payment legitimacy, en transaction authenticity.

3. The Platfofm retains the right to update, adjust, of remove Kopen Neew Domeinen from listing at its sole discretion en without priof notice.

4. Als any fraudulent of abusive behaviof is detected, the Platfofm reserves the right to suspend of terminate diensts to the user.

6. Disclaimer

1. The Platfofm does not make any guarantees regarding the future value, resale potential, of commercial use of any domein kopend.

2. The Platfofm is not liable fof delays caused by registries, third-party providers, of external systems beyond its control.

3. The Platfofm shall not be held responsible fof dienst interruptions, data loss, of failed transactions resulting from fofce majeure events of uncontrollable technical issues, though reasonable effofts will be made to assist the User in resolving any such issues.

7. Governing Law en Dispute Resolution

1. This Agreement shall be governed by en construed in accofdance with the laws of Hongkong.

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

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a Kopen Neew domein ofder.

2. The Platfofm reserves the right to amend this Agreement at any time. Bijgewerkt versions will be published on the Platfofm’s “Overeenkomsten” page en shall take immediate effect. Continued use of the dienst constitutes acceptance of the revised terms.

This Unifofm Domeinnaam Dispute Resolution Policy (the "Policy") has been adopted by the Internet Cofpofation fof Assigned Naams en Numbers ("ICANN"), is incofpofated by reference into jouw Registratie Agreement, en sets fofth the terms en conditions in connection with a dispute between you en any party other than us (the registrar) over the registration en use of an Internet domein name registreered by you. Proceedings under Paragraph 4 of this Policy will be conducted accofding to the Rules fof Unifofm Domeinnaam Dispute Resolution Policy (the "Rules of Procedure"), which are available hier, en the selected administrative-dispute-resolution dienst provider's supplemental rules.

2. Your Representations

By applying to registreer a domein name, of by asking us to maintain of renew a domein name registration, you hierby represent en warrant to us that (a) the statements that you made in jouw Registratie Agreement are complete en accurate; (b) to jouw knuledge, the registration of the domein name will not infringe upon of otherwise violate the rights of any third party; (c) you are not registreering the domein name fof an unlawful purpose; en (d) you will not knuingly use the domein name in violation of any applicable laws of regulations. It is jouw responsibility to determine whether jouw domein name registration infringes of violates someone else's rights.

3. Annulerenlations, Transfers, en Changes

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

1. subject to the provisions of Paragraph 8, our receipt of written of appropriate electronic instructions from you of jouw authofized agent to take such action;

2. our receipt of an ofder from a court of arbitral tribunal, in each case of competent jurisdiction, requiring such action; en/of

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

4. We may also cancel, transfer of otherwise make changes to a domein name registration in accofdance with the terms of jouw Registratie Agreement of other legal requirements.

4. Menatofy Administrative Proceeding

This Paragraph sets fofth the type of disputes fof which you are required to submit to a menatofy administrative proceeding. These proceedings will be conducted befofe one of the administrative-dispute-resolution dienst providers listed hier (each, a "Provider").

1. Applicable Disputes. You are required to submit to a menatofy 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. jouw domein name is identical of confusingly similar to a trademark of dienst mark in which the complainant has rights; en

2. you have no rights of legitimate interests in respect of the domein name; en

3. jouw domein name has been registreered en 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 Registratie en Use in Slecht Faith. Fof 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 en use of a domein name in bad faith:

1. circumstances indicating that you have registreered of you have acquired the domein name primarily fof the purpose of selling, renting, of otherwise transferring the domein name registration to the complainant who is the owner of the trademark of dienst mark of to a competitof of that complainant, fof valuable consideration in excess of jouw documented out-of-pocket costs directly related to the domein name; of

2. you have registreered the domein name in ofder to vorigeent the owner of the trademark of dienst mark from reflecting the mark in a cofresponding domein name, provided that you have engaged in a pattern of such conduct; of

3. you have registreered the domein name primarily fof the purpose of disrupting the business of a competitof; of

4. by using the domein name, you have intentionally attempted to attract, fof commercial gain, Internet users to jouw web site of other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsofship, affiliation, of endofsement of jouw web site of location of of a product of dienst on jouw web site of location.

3. How to Demonstrate Your Rights to en Legitimate Interests in the Domeinnaam in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how jouw 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 jouw rights of legitimate interests to the domein name fof purposes of Paragraph 4(a)(ii):

1. befofe any notice to you of the dispute, jouw use of, of demonstrable preparations to use, the domein name of a name cofresponding to the domein name in connection with a bona fide offering of goods of diensts; of

2. you (as an individual, business, of other ofganization) have been commonly knun by the domein name, even if you have acquired no trademark of dienst mark rights; of

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

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

7. Fees. Alles fees charged by a Provider in connection with any dispute befofe an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases whier you elect to expen 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 en the complainant.

8. Onze Involvement in Administrative Proceedings. We do not, en will not, participate in the administration of conduct of any proceeding befofe 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 befofe an Administrative Panel shall be limited to requiring the cancellation of jouw domein name of the transfer of jouw domein name registration to the complainant.

10. Neetification en Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a domein name you have registreered with us. Alles decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact poftions of its decision.

11. Availability of Court Proceedings. The menatofy administrative proceeding requirements set fofth in Paragraph 4 shall not vorigeent either you of the complainant from submitting the dispute to a court of competent jurisdiction fof independent resolution befofe such menatofy administrative proceeding is commenced of after such proceeding is concluded. Als an Administrative Panel decides that jouw domein name registration should be canceled of transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are infofmed by the applicable Provider of the Administrative Panel's decision befofe implementing that decision. We will then implement the decision unless we have received from you during that ten (10) business day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that you have commenced a lawsuit against the complainant in a jurisdiction to which the complainant has submitted under Paragraph 3(b)(xiii) of the Rules of Procedure. (In general, that jurisdiction is either the location of our principal office of of jouw address as shown in our Whois database. See Paragraphs 1 en 3(b)(xiii) of the Rules of Procedure fof details.) Als we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, en we will take no further action, until we receive (i) evidence satisfactofy to us of a resolution between the parties; (ii) evidence satisfactofy to us that jouw lawsuit has been dismissed of withdrawn; of (iii) a copy of an ofder from such court dismissing jouw lawsuit of ofdering that you do not have the right to continue to use jouw domein name.

5. Alles other disputes en litigation

Alles other disputes between you en any party other than us regarding jouw domein name registration that are not brought pursuant to the menatofy administrative proceeding provisions of Paragraph 4 shall be resolved between you en such other party through any court, arbitration of other proceeding that may be available.

6. Onze involvement in disputes

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

7. Maintaining status quo

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

8. Transfers during a dispute

Transfers of a Domeinnaam to a Nieuw Holder

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

Changing Registrars

You may not transfer jouw domein name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 of fof 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 jouw domein name registration to another registrar during a pending court action of arbitration, provided that the domein name you have registreered with us shall continue to be subject to the proceedings commenced against you in accofdance with the terms of this Policy. In the event that you transfer a domein name registration to us during the pendency of a court action of arbitration, such dispute shall remain subject to the domein name dispute policy of the registrar from which the domein 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 befofe 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 domein name registration dispute, whether the dispute arose befofe, on of after the effective date of our change. In the event that you object to a change in this Policy, jouw sole remedy is to cancel jouw domein 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 jouw domein name registration.

1. Overview

These terms of use ("AI Periodes of Use") govern jouw use of any AI products, features, diensts en/of tools offered by NiceNIC.NET.

2. Content

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

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

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

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

6) By using the AI Services, you understen en agree:

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

B. You must evaluate Output fof accuracy en appropriateness fof jouw use case, including using human review as appropriate, befofe using of sharing Output from the AI Services.

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

D. Onze AI Services may provide incomplete, incofrect, of offensive Output that does not represent NiceNIC.NET’s views. Als Output references any third party products of diensts, it doesn’t mean the third party endofses of is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users en the AI Services may generate the same of similar Outputs fof other users.

8) NiceNIC.NET may use technology provided by third-party dienst providers to provide AI Services. Neetwithstening anything to the contrary contained hierin, you authofize NiceNIC.NET en such third-party dienst providers to stofe en use jouw Input fof the purposes of providing you with the AI Services, to review Inputs en Outputs fof abuse of misuse, en to develop en improve the diensts en products of NiceNIC.NET en such dienst providers, including as part of the design, training en development process fof machine learning models.

3. Periodeination en Suspension

Periodeination. We reserve the right to suspend of terminate jouw access to our AI Services of delete jouw account if we determine:

1) You breached these AI Periodes of Use.

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

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

4. Disclaimers

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

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

5. Limitation on Liability

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

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

In the event that a Transfer Contact listed in the Whois has not confirmed their request to transfer with the Registrar of Recofd en the Registrar of Recofd has not explicitly denied the transfer request, the default action will be that the Registrar of Recofd must allow the transfer to proceed.

Upon denying a transfer request fof any of the following reasons, the Registrar of Recofd must provide the Registrerened Naam Holder en the potential Gaining Registrar with the reason fof denial. The Registrar of Recofd may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court ofder by a court of competent jurisdiction
• Reasonable dispute over the identity of the Registrerened Naam Holder of Administrative Contact
• Nee payment fof vorigeious registration period (including credit card charge-backs) if the domein name is past its expiration date of fof vorigeious of current registration periods if the domein name has not yet expired. In all such cases, however, the domein name must be put into "Registrar Hold" status by the Registrar of Recofd priof to the denial of transfer.
• Express written objection to the transfer from the Transfer Contact. (e.g. - email, fax, paper document of other processes by which the Transfer Contact has expressly en voluntarily objected through opt-in means)
• A domein name was already in “l(fā)ock status” provided that the Registrar provides a readily accessible en reasonable means fof the Registrerened Naam Holder to remove the lock status.
• A domein name is in the first 60 days of an initial registration period.
• A domein name is within 60 days (of a lesser period to be determined) after being transferred (apart from being transferred back to the ofiginal Registrar in cases whier both Registrars so agree en/of whier a decision in the dispute resolution process so directs).

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

YOU ALSO AGREE THAT WE WILL NOT BE LIABLE FOF ANY INDIRECT, SPECIAL, INCIDENTAL, OF CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LBesturingssysteemT PROFITS) OF FOF ANY FINANCIAL OF ECONOMIC LBesturingssysteemS OF FOF LBesturingssysteemS OF PROFITS, LBesturingssysteemS OF BUSINESS, DEPLETION OF GOODWILL OF SIMILAR LBesturingssysteemSES, LBesturingssysteemS OF ANTICIPATED SAVINGS OF LBesturingssysteemS OF COFRUPTION OF DATA OF INFOFMATION, REGARDLESS OF THE FOFM OF ACTION WHETHER IN CONTRACT, TOFT (INCLUDING NEGLIGENCE), OF OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE PBesturingssysteemSIBILITY OF SUCH DAMAGES.

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

24. General
You may not assign any of jouw rights of privileges, of delegate any of jouw duties of obligations hierunder, in whole of in part, by operation of law of otherwise, to any third party without our priof written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon en inure to the benefit of the parties hierto en their respective permitted successofs en assigns.

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

This Agreement constitutes the entire agreement between the parties concerning the subject matter hierin en supersedes all priof understenings en agreements between the parties, whether written of ofal, regarding the subject matter hierin. Any of the provisions of this Agreement which are determined to be invalid of unenfofceable in any jurisdiction shall be ineffective to the extent of such invalidity of unenfofceability in such jurisdiction, without rendering invalid of unenfofceable the remaining provisions hierof of affecting the validity of unenfofceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach of violation of any provision of this Agreement will not constitute of be construed as a waiver of any subsequent breach of violation of that provision of as a waiver of any breach of violation of any other provision of this Agreement. The headings contained in this Agreement are fof convenience only en shall not affect meaning of interpretation of this Agreement.

25. Neetices
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 accofdance with the Account en/of WHOIS infofmation you have provided.

26. Governing Law
This Agreement en its subject matter shall be governed in accofdance with the laws of Hongkong en subject to the exclusive jurisdiction of the Hongkong courts without regard to conflict of laws en principles contained thierin with the exception of disputes related to this Agreement which fall under UDRP, URS, of similar dispute resolution process as defined by various Registry policies incofpofated of made reference to hierin.

1.3 The Registrant acknuledges en agrees that the Registrar shall monitof the status of Domeinnamen registreered through the Registrar en shall, at its own initiative of on receipt of complaint, conduct checks to verify whether a Domeinnaam is being used in connection with phishing of "spam" advertising. The Registrar shall delete of suspend a Domeinnaam if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government of law enfofcement authofity (including without limitation the Hongkong Police Fofce of the Office of Telecommunications Authofity) that the use of the Domeinnaam is in breach of any laws, directives, guidelines, codes of practice of regulations issued by such local authofities, of if, in HKIRC's reasonable belief, the continuation of registration of the Domeinnaam of the operation of web site referenced   by the Domeinnaam is likely to damage of adversely affect the goodwill, reputation en operation of HKIRC of the domein name industry in Hongkong, of may expose HKIRC to risks of third party claims of civil of criminal prosecution.

Fof mofe infofmation about .HK domein registration, please refer to the latest version of HKIRC Registratie Policies https://www.hkirc.hk/upload/page/38/pdf_1/5e6b172e68b29.pdf

5.2 Any decision made by an arbitration panel duly appointed by a dispute resolution dienst provider shall be final en binding on the Registrant en 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 en non-statutofy cofpofation designated by the Hong-Kong Government to administer the registration of Internet domein names under .hk en .香港 country-code top level domeins. Fof any comments of complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find hier useful infofmation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppoft/domein_dispute_policies_en_procedures/domein_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppoft/domein_dispute_policies_en_procedures/rules_of_procedures/; of E-mail address: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant acknuledges that the Registrar en HKIRC rely on all representations made en warranties given by the Registrant in determining if the application fof a Domeinnaam should be approved.

    Fof mofe infofmation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domein_policies/EN_Domein_Naam_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. Neew that you have met the requirements of ICANN, our team is looking fofward to assisting you in completing the Verisign certification process so you can quickly begin registreering .com en .net domein names. We hope this suppoft will prove to be helpful in reducing the investment of jouw internal resources en time."

PIR:
"ICANN has infofmed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed jouw ICANN accreditation to become a registrar en 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 jouw agreement with them. Thier hasn't been a better time to become involved with .tel domeins en we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on jouw recent ICANN Accreditatie..."

Neustar:

"We have been notified that jouw company is nu ICANN-accredited as a .BIZ registrar.  Neustar looks fofward to getting jouw company up en running as soon as possible!"

Meer registries will be notified by ICANN fof the cofresponding domein names signed in the RAA in the volgende days, we NiceNIC have been staying fof the disposal of sign-up/accreditation process, striving to save time en expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mofe competitive level. Detailsed infofmation 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"), en dedicated to offer clients easy to navigate, fast to locate diensts in domein name registration, web hosting kopen, 1 to 1 customer suppoft.

Stening at the peak of internet infrastruture, we firstly need to appreciate every client, en every website viewer who ever stayed hier, without jouw persistant suppoft en comprehension, we are nothing, hope 2012 will bring you en jouw family lucky, happy, healthy life.

Reference links:

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

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

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

ZhuHai NaiSiNiKe Infofmation Technology Co Ltd.

2009

China

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

Alles the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infofmation 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 fof Enfofcement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent en neutral third party that is neither associated nof affiliated with either Registrar involved in the dispute of the Registry Operatof under which the disputed domein name is registreered. ICANN shall have the authofity to accredit one of mofe independent en neutral Dispute Resolution Providers accofding to criteria developed in accofdance with this Dispute Resolution Policy.

1.4 FOA

     Fofm of Authofization - The stenardized fofm of consent that the Gaining Registrar en Registrar of Recofd are required to use to obtain authofization from the Registrant of Administrative Contact in ofder to properly process the transfer of domein name sponsofship from one Registrar to another.

1.5 Gaining Registrar

     The Registrar that submitted to the Registry the request fof the transfer of a domein sponsofship from the Registrar of Recofd.

1.6 Registrar of Recofd

     The Registrar of Recofd fof a domein name fof which the Registry received a transfer of sponsofship request.

1.7 Registrant

     The Registrant is the individual of ofganization that registreers a specific domein name. This individual of ofganization holds the right to use that specific domein name fof a specified period of time, provided certain conditions are met en the registration fees are paid. This person of ofganization is the "legal entity" bound by the terms of the relevant dienst agreement with the Registry operatof fof the TLD in question.

1.8 Registry (Registry Operatof)

     The ofganization authofized by ICANN to provide registration diensts fof a given TLD to ICANN-accredited Registrars.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operatof, in the case of First Niveau disputes (as set fofth below), of 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 en shall cover topics such as fees, wofd en page limits en guidelines, the means fof communicating with the Provider, en the fofm of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponsofship of Registraties between Registrars which is in fofce as part of the Registry-Registrar Agreement executed between a Registrar en the Registry, as well as the Registrar Accreditatie Agreement which is executed between ICANN en all ICANN- accredited registrars.

2. Dispute Resolution Process

     Thier are two possible steps to the Registrar Transfer Dispute Resolution Process. A Registrar may elect one of both of the steps pursuant to the rules below. In the event a Registrar either files a Request fof Enfofcement (as described below) with a Second-Niveau Dispute Provider, of files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-Niveau Registry option later fof the same filing of matter presented fof resolution.

2.1 First Niveau - Registry Operatof

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

2.2 Second-Niveau - Dispute Resolution Panel

     The primary intent of this step is to provide a means fof 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 whier a Registrar of Recofd 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 whier a Gaining Registrar 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 Niveau (Registry)

3.1 Registrar files a Request fof Enfofcement with the applicable Registry Operatof

     3.1.1 Either the Gaining of Registrar of Recofd ("Filing Registrar") may submit a Request fof Enfofcement. This must be done in accofdance with the Supplemental Rules adopted by the applicable Registry Operatof.

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

3.1.4 The Request fof Enfofcement shall annex the following documentary evidence (as applicable en available) in electronic fofm if possible, together with a schedule indexing such evidence:
  (i) Fof the Gaining Registrar:
      a. Completed Fofm of Authofization ("FOA")
      b. Copy of the Whois output fof the date transfer was initiated, which was used to identify the authofized Transfer Contacts
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body of court ofder in cases when the Registrant of Recofd is being changed simultaneously with a Registrar Transfer
      e. Copies of all communications made to the Registrar of Recofd with regard to the applicable transfer request along with any responses from the Registrar of Recofd
  (ii) Fof the Registrar of Recofd:
      a. Completed FOA from Registrar of Recofd if applicable
      b. Copy of the Whois output fof the date the transfer was initiated
      c. Relevant histofy of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court ofder;
• Registrant of administrative contact identity dispute in accofdance with Section 4 [Registrar of Recofd Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the Registrerened Naam Holder of Administrative Contact;
• LOCK status along with proof of a reasonable means fof the registrant to remove LOCK status as per Section __of Exhibit __ to this Agreement;
• domein name within 60 days of initial registration; of
• domein name within 60 days of a priof transfer.

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

3.2 The Neen-Filing Registrar ("Respondent") shall have seven (7) calendar days from receipt of the Request fof Enfofcement to prepare a Response to the Request fof Enfofcement ("Response").

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

3.2.2 Bij the request of the Respondent, the Registry Operatof may, in exceptional cases, extend the period of time fof the filing of the response, but in no case may the extension be mofe 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 Operatof.

3.2.3 Als a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatof shall decide the dispute based upon the Request fof Enfofcement.

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

3.3.1 Als the data included in the Request fof Enfofcement does not match the data listed in the authofitative Whois, the Registry Operatof must contact each Registrar en require additional documentation.

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

3.3.3 In the case whier a Registrar of Recofd denies a request fof a domein name transfer ("NACKs"), the Registrar of Recofd must provide evidence of one of the factofs fof which it is allowed to NACK. Als the Registrar of Recofd cannot provide evidence that demonstrates any of the factofs, en the Gaining Registrar provides to the Registry a complete FOA with data matching that contained within the authofitative Whois database, then the transfer must be approved to be processed.

3.3.4 Als the data provided by neither Registrar appears to be conclusive, then the Registry shall issue a finding of "no decision." Als the data provided to the Registry is complete en provides sufficient basis fof a determination based on the Policy, the Registry may not issue a finding of "no decision." Either Registrar shall be able to appeal such issue to a Second-Niveau Dispute Resolution Provider in accofdance with the provisions set fofth below.

3.4 Fees fof First-Niveau Dispute Resolution Service

3.4.1 Thier is no filing fee assessed to the Filing Registrar at the time the Request fof Enfofcement is submitted to the Registry Operatof.

3.4.2 The Registrar that does not vorigeail in the dispute will be assessed a fee to be set by the Registry Operatof. Such fee shall be set fofth in the Registry's Supplemental Rules that are in effect at the time that the Request fof Enfofcement 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 Operatof shall collect the applicable fees from the Filing Registrar.

3.5 Availability of Court Proceedings

      The procedures set fofth above shall not vorigeent a Registrar from submitting a dispute to a court of competent jurisdiction fof independent resolution befofe such an administrative proceeding is commenced of after such proceeding is concluded. Als a Registry Operatof decides a domein name registration should be transferred (either to the Gaining Registrar, of alternatively, back from the Gaining Registrar to the Registrar of Recofd), the Registry will wait fourteen (14) calendar days after it is infofmed of the decision befofe 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 domein name(s). Als such documentation is received by the Registry Operatof within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatof that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatof that the lawsuit has been dismissed of withdrawn; of (iii) the Registry Operatof receives a copy of an ofder from such court.

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

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

      (i) A Filing Registrar may elect to skip the First-Niveau dispute process at Registry level en submit a Request fof Enfofcement directly with a Dispute Resolution Provider;
      (ii) The non-vorigeailing Registrar in a First-Niveau dispute proceeding may submit an appeal of the applicable Registry Operatof's decision to the Dispute Resolution Provider. Toevoegenitionally, in the case whier the result in the First-Niveau dispute process is a "no-decision," either Registrar may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request fof Enfofcement

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

4.3 Appeal of First Niveau Dispute Decision of Registry Operatof Finding of "Nee-Decision."

4.3.1 In the event that the Registrar which does not vorigeail in the First-Niveau dispute is dissatisfied by the Registry-Operatof's decision, such Registrar 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-Niveau decision was issued.

4.3.2 In the event that the Registry Operatof issues a finding of "no-decision" in accofdance with Section 3.3.4 above, either Registrar 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-Niveau decision was issued.

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

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

4.3.5 The Appeal may relate to mofe than one domein name, provided that the domein names involve the same decision issued by the Registry Operatof fof the First-Niveau Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatof during the First-Niveau Dispute.

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

• Approval of a Transfer
• Denial of the Transfer (of ofdering the domein name be returned to the Registrar of Recofd in cases whier a Transfer has already occurred)

4.4 Fees fof Second-Niveau Dispute Resolution Service

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

4.4.3 In the event that the Filing Registrar of Appellant, whichever applicable, vorigeails in a Second-Niveau dispute, the Respondent of 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 Registrar of Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent of Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accofdance 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 fofth above shall not vorigeent a Registrar from submitting a dispute to a court of competent jurisdiction fof independent resolution befofe such administrative proceeding is commenced of after such proceeding is concluded. Als a Dispute Resolution Panel decides a domein name registration should be transferred (either to the Gaining Registrar, of alternatively, back from the Gaining Registrar to the Registrar of Recofd), such Registrar will wait fourteen (14) calendar days after it is infofmed of the decision befofe 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 domein name(s). Als 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 of withdrawn; of (iii) a copy of an ofder from such court dismissing the lawsuit of ofdering certain actions with respect to the domein name.

1. Registrar Requirements

     Registrerened Naam Holders must be able to transfer their domein name registrations between Registrars provided that the Gaining Registrar's transfer process meets the minimum stenards of this policy en that such transfer is not prohibited by ICANN of Registry policies. Inter-Registrar domein name transfer processes must be clear en concise in ofder to avoid confusion. Further, Registrars should make reasonable effofts to infofm Registrerened Naam Holders of, en provide access to, the published documentation of the specific transfer process employed by the Registrars.

1.1 Transfer Authofities

     The Administrative Contact en the Registrerened Naam Holder, as listed in the Losing Registrar's of applicable Registry's (whier available) publicly accessible WHOIS dienst are the only parties that have the authofity to approve of deny a transfer request to the Gaining Registrar. In the event of a dispute, the Registrerened Naam Holder's authofity supersedes that of the Administrative Contact.
Registrars may use Whois data from either the Registrar of Recofd of the relevant Registry fof the purpose of verifying the authenticity of a transfer request; of from another data source as determined by a consensus policy.

2. Gaining Registrar Requirements

Fof each instance whier a Registrerened Naam Holder requests to transfer a domein name registration to a different Registrar, the Gaining Registrar shall:
      2.1 Obtain express authofization from either the Registrerened Naam Holder of the Administrative Contact (hierafter, "Transfer Contact"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrar from the Transfer Contact.

     2.1.1 The authofization must be made via a valid Stenardized Fofm of Authofization (FOA). Thier are two different FOA's available at the ICANN website. The FOA labeled "Initial Authofization fof Registrar Transfer" must be used by the Gaining Registrar to request an authofization fof a registrar transfer from the Transfer Contact. The FOA labeled "Bevestigenation of Registrar Transfer Request" may be used by the Registrar of Recofd to request confirmation of the transfer from the Transfer Contact.
The FOA shall be communicated in English, en any dispute arising out of a transfer request shall be conducted in the English language. Registrars may choose to communicate with the Transfer Contact in additional languages. However, Registrars choosing to exercise such option are responsible fof the accuracy en completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Registrar relies on a physical process to obtain this authofization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Contact en further that it is accompanied by a physical copy of the Registrar of Recofd's Whois output fof the domein name in question.

     2.1.2.1 Als the Gaining Registrar relies on a physical authofization process, then the Gaining Registrar assumes the burden of obtaining reliable evidence of the identity of the Transfer Contact en maintaining appropriate recofds proving that such evidence was obtained. Further the Gaining Registrar also assumes the burden fof ensuring that the entity making the request is indeed authofized to do so. The acceptable fofms of physical identity are:

• Neetarized statement
• Valid Drivers license
• Passpoft
• Article of Incofpofation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Registrar relies on an electronic process to obtain this authofization the acceptable fofms of identity would include:

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

     The Registrar of Recofd may not deny a transfer request solely because it believes that the Gaining Registrar has not received the confirmation set fofth above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registrar. The presumption in all cases will be that the Gaining Registrar has received en authenticated the transfer request made by a Transfer Contact.

     2.2 Request, by the transmission of a "transfer" commen as specified in the Registrar Naarol Kit, that the Registry Operatof database be changed to reflect the new Registrar.

     2.2.1 Transmission of a "transfer" commen constitutes a representation on the part of the Gaining Registrar that the requisite authofization has been obtained from the Transfer Contact listed in the authofitative Whois database.

     2.2.2 The Gaining Registrar is responsible fof validating the Registrerened Naam Holder requests to transfer domein names between Registrars. However, this does not preclude the Registrar of Recofd from exercising its option to independently confirm the Registrerened Naam Holder's intent to transfer its domein name to the Gaining Registrar in accofdance with Section 3 of this policy.

3. Obligations of the Registrar of Recofd

     A Registrar of Recofd can choose independently to confirm the intent of the Registrerened Naam Holder when a notice of a pending transfer is received from the Registry. The Registrar of Recofd must do so in a manner consistent with the stenards set fofth in this agreement pertaining to Gaining Registrars. In ofder to ensure that the fofm of the request employed by the Registrar of Recofd is substantially administrative en infofmative in nature en clearly provided to the Transfer Contact fof the purpose of verifying the intent of the Transfer Contact, the Registrar of Recofd must use the FOA.

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

1. Evidence of fraud
2. UDRP action
3. Court ofder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Registrerened Naam Holder of Administrative Contact
5. Nee payment fof vorigeious registration period (including credit card charge-backs) if the domein name is past its expiration date of fof vorigeious of current registration periods if the domein name has not yet expired. In all such cases, however, the domein name must be put into "Registrar Hold" status by the Registrar of Recofd priof to the denial of transfer.
6. Express written objection to the transfer from the Transfer Contact. (e.g. - email, fax, paper document of other processes by which the Transfer Contact has expressly en voluntarily objected through opt-in means)
7. A domein name was already in “l(fā)ock status” provided that the Registrar provides a readily accessible en reasonable means fof the Registrerened Naam Holder to remove the lock status.
8. A domein name is in the first 60 days of an initial registration period.
9. A domein name is within 60 days (of a lesser period to be determined) after being transferred (apart from being transferred back to the ofiginal Registrar in cases whier both Registrars so agree en/of whier a decision in the dispute resolution process so directs).

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

• Neenpayment fof a pending of future registration period
• Nee response from the Registrerened Naam Holder of Administrative Contact.
• Domein name in Registrar Lock Status, unless the Registrerened Naam Holder is provided with the reasonable oppoftunity en ability to unlock the domein name priof to the Transfer Request.
• Domein name registration period time constraints, other than during the first 60 days of initial registration of during the first 60 days after a registrar transfer.
• General payment defaults between Registrar en business partners / affiliates in cases whier the Registrerened Naam Holder fof the domein in question has paid fof the registration.

     The Registrar of Recofd has other mechanisms available to collect payment from the Registrerened Naam Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrar of Recofd must not employ transfer processes as a mechanism to secure payment fof diensts from a Registrerened Naam Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fof vorigeious registration period(s) if the transfer is requested after the expiration date, of
     (ii) In the case of non-payment of the current registration period, if transfer is requested befofe the expiration date.

4. Registrar Coofdination

     Each Registrar is responsible fof keeping copies of documentation, including the FOA en the Transfer Contacts response thierto, that may be required fof filing en suppofting a dispute under the dispute resolution policy. Gaining Registrars must maintain copies of the FOA as received from the Transfer Contact as per the stenard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registrar en the Registrar of Recofd must provide the evidence relied on fof the transfer during en after the applicable inter-registrar domein name transaction(s). Such infofmation must be provided when requested by, en only by, the other Registrar that is party to the transfer transaction. Toevoegenitionally, ICANN, the Registry Operatof, a court of authofity with jurisdiction over the matter of a third party dispute resolution panel may also require such infofmation within five (5) days of the request.

     The Gaining Registrar must retain, en produce pursuant to a request by a Losing Registrar, a written of electronic copy of the FOA. In instances whier the Registrar of Recofd has requested copies of the FOA, the Gaining Registrar must fulfill the Registrar of Recofds request (including providing the attendant suppofting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fof reversal by the Registry Operatof of the Dispute Resolution Panel in the event that a transfer complaint is filed in accofdance with the requirements of this policy.

     Als either a Registrar of Recofd of a Gaining Registrar does not believe that a transfer request was henled in accofdance with the provisions of this policy, then the Registrar may initiate a dispute resolution procedure as set fofth in Section C of this policy.

     Fof purposes of facilitating transfer requests, Registrars should provide en maintain a unique en private email address fof use only by other Registrars en the Registry:
     i. This email address is fof issue related to transfer requests en the procedures set fofth in this policy only.
     ii. The email address should be managed to ensure messages are received by someone who can respond to the transfer issue.
     iii. Messages received at such email address must be responded to within a commercial reasonable timeframe not to exceed seven (7) calendar days.

5. EPP - based Registry Requirements fof Registrars

     In EPP-based gTLD Registries, Registrars must follow the requirements set fofth below.
Registrars must provide the Registrerened Naam Holder with the unique "AuthInfo" code within five (5) calendar days of the Registrerened Naam Holder's initial request if the Registrar does not provide facilities fof the Registrerened Naam Holder to generate en manage their own unique "AuthInfo" code.

     Registrars may not employ any mechanism fof complying with a Registrerened Naam Holder's request to obtain the applicable "AuthInfo Code" that is mofe restrictive than the mechanisms used fof changing any aspect of the Registrerened Naam Holder's contact of name server infofmation.

     The Registrar of Recofd must not refuse to release an "AuthInfo Code" to the Registrerened Naam Holder solely because thier is a dispute between the Registrerened Naam Holder en the Registrar over payment.

Registrar-generated "AuthInfo" codes must be unique on a per-domein basis.
     The "Auth-Info" codes must be used solely to identify a Registrerened Naam Holder, whieras the FOA's still need to be used fof authofization of confirmation of a transfer request, as described in Section 2 en Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commen from the Gaining Registrar, Registry Operatof will transmit an electronic notification to both Registrars. 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 Registrar fof the purpose of facilitating transfers.

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

7. Recofds of Registratie

     Each Registrar shall require its customer, the Registrerened Naam Holder, to maintain its own recofds appropriate to document en prove the initial domein name registration date.

8. Effect on Periode of Registratie

     The completion by Registry Operatof of a holder-authofized transfer under this Part A shall result in a one-jaar extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) jaren.

B. ICANN-Approved Transfers

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

C. Transfer Dispute Resolution Policy

     Procedures fof henling disputes concerning inter-registrar transfers are set fofth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatofs en ICANN accredited Registrars.

We respect jouw individual privacy. That is why we have adopted this Privacybeleid, which embodies our commitment to the protection of jouw privacy through adhiernce to fair electronic infofmation practices. This Privacybeleid puts you, the individual, in control of how jouw personal infofmation is processed, en you have our promise that we will not electronically process jouw personal infofmation in any way that is incompatible with this Privacybeleid.

This Privacybeleid protects jouw privacy by:

4. How We Put Infofmation Naar Good Use