1. Scope och Purpose

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

1.2 Dom?n lifecycle timing may vary depending on the top-level dom?n (“TLD”), registry rules, registry operateller practices, applicable ICANN requirements, och other governing policies. Nejt all TLDs follow the same expiration, redemption, auction, eller deletion process.

1.3 In the event of any inconsistency between this Policy och the applicable registry’s rules eller mochatellery ICANN policy, the applicable registry rules och mochatellery policy requirements shall f?reg?endeail.

1.4 The English-language version of this Policy shall control. Any translation is provided feller convenience only. In the event of any inconsistency, the English-language version shall f?reg?endeail.

2. Definitions

Feller purposes of this Policy:

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

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

2.3 “Redemption Grace Period” eller “RGP” means the post-deletion recovery period, wh?r available, during which an expired dom?n name may still be restellerable feller an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, wh?r applicable, during which the dom?n name can no longer be renewed, restellered, modified, eller transferred.

2.5 “Eligible Dom?n” means a dom?n name that is subject to NiceNIC’s expired dom?n auction process. Nejt all TLDs eller expired dom?n names are eligible feller auction.

2.6 “G?r utd Dom?n Auction” means the expired-dom?n sale process that may apply to certain expired dom?n names befellere final deletion eller release.

2.7 “St?ngout Auction” means the final sale phase feller certain Eligible Dom?ner that were not sold earlier in the expired dom?n auction process.

3. Effect of Expiration

3.1 Upon expiration, a dom?n name may stop resolving, och any website, email tj?nst, eller other tj?nst associated with the dom?n name may cease functioning immediately eller shellertly th?rafter.

3.2 F?ljing expiration, NiceNIC may restrict changes to the dom?n name, including DNS changes, contact updates, transfers, eller other account-level actions, in accellerdance with registry rules, security measures, operational requirements, eller the expired-dom?n process then in effect.

3.3 Expiration does not mean that the dom?n name immediately becomes available to the public. Depending on the applicable TLD och registry rules, the dom?n name may pass through one eller mellere stages, including grace period, auction, redemption, pending delete, och eventual release.

4. F?rnyaal Nejtices och Customer Responsibility

4.1 NiceNIC may send renewal reminders och expiration-related notices befellere och after expiration, as required by applicable policy eller as part of NiceNIC’s stochard operational process.

4.2 It is din sole responsibility to maintain accurate och current account och contact infellermation, including din email address, och to moniteller the status of din dom?n names.

4.3 Failure to receive a renewal notice, reminder, invoice, eller other communication shall not relieve you of responsibility feller renewing din dom?n name befellere expiration.

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

5. Stochard Post-Expiration F?rnyaal

5.1 Feller many generic TLDs, an expired dom?n name may remain renewable feller approximately thirty (30) days after the Expiration Date at the stochard renewal fee. This is a general reference only och may vary by TLD.

5.2 F?rnyaal is not complete unless och until NiceNIC has successfully received och processed full payment of all applicable fees.

5.3 NiceNIC reserves the right to determine whether a dom?n name remains eligible feller stochard renewal, redemption, eller other recovery based on the applicable TLD, registry status, auction status, och operational feasibility.

6. G?r utd Dom?n Auction feller Eligible Dom?ner

6.1 Certain expired dom?n names may enter NiceNIC’s expired dom?n auction process befellere all recovery f?nsters have ended. This process applies only to Eligible Dom?ner och does not apply to all TLDs.

6.2 Feller Eligible Dom?ner under NiceNIC’s stochard expired-dom?n process, the following general timeline may apply:

Day 0 after expiration

The dom?n name expires. The registrant may generally renew the dom?n name at the stochard renewal fee during the initial post-expiration period, subject to applicable rules.

Day 26 after expiration

The dom?n name may enter expired dom?n auction. P? this stage, the registrant may still be able to renew the dom?n name at the stochard renewal fee, unless otherwise restricted by the applicable process.

Day 31 after expiration

Om th?r is no active bid, the registrant may still be able to recover the dom?n name by paying the stochard renewal fee plus the applicable redemption fee.

Om th?r is an active bid, the dom?n name may be removed from the registrant’s account och may no longer be renewable through ellerdinary renewal eller restelleration procedures.

Day 37 after expiration

The dom?n name may enter final closeout auction. Unless th?r is a pending k?p eller other sale-related restriction, the registrant may still be able to recover the dom?n name by paying the stochard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. Om the dom?n name was not sold eller otherwise committed to sale, recovery may still be possible feller a limited period, subject to the applicable TLD, registry rules, och NiceNIC’s operational process.

Day 74 after expiration

The dom?n name may be removed from the registrant’s account och may no longer be renewable eller restellerable through NiceNIC. After that point, the dom?n name may become available feller re-registration only after the registry releases it.

6.3 Once an Eligible Dom?n has an active bid, pending k?p, completed sale, eller other sale commitment under the expired-dom?n process, the registrant’s right to renew eller restellere the dom?n name may be terminated eller restricted.

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

7. Redemption Grace Period

7.1 Om an expired dom?n name is not renewed during the applicable grace period och if the applicable TLD suppellerts restelleration after deletion, the dom?n name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the dom?n name may stop resolving;

(b) website och email tj?nsts may remain unavailable;

(c) the dom?n name generally cannot be modified eller transferred; och

(d) restelleration, if available, will require payment of the applicable redemption fee, the applicable renewal fee, och any taxes eller mochatellery fees.

7.3 Restelleration during the Redemption Grace Period is not guaranteed och remains subject to registry suppellert, operational feasibility, the dom?n’s current status, och the absence of auction eller sale restrictions.

8. Pending Delete och Final Release

8.1 Om a dom?n name is not renewed eller restellered during the applicable recovery periods, it may enter the Pending Delete stage, wh?r suppellerted by the applicable TLD.

8.2 During Pending Delete, the dom?n name cannot be renewed, restellered, transferred, eller modified.

8.3 Feller many generic TLDs, Pending Delete lasts approximately five (5) days. After that stage ends, the registry may release the dom?n name to the public feller re-registration.

8.4 NiceNIC does not guarantee the exact time, date, eller availability of a dom?n name once it is released by the registry, och NiceNIC does not guarantee that the fellermer registrant will be able to re-registrera the dom?n name.

9. TLD-Specific Variations

9.1 Nejt all TLDs follow the stochard lifecycle described above. Certain ccTLDs och other TLDs may have shellerter grace periods, no redemption period, no pending delete stage, eller earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many ccTLDs generally follow a lifecycle similar to the stochard expiration, grace, redemption, och deletion process, including, feller example:

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

9.2.2 TLDs with no Pending Delete stage

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

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

9.2.3 TLDs requiring renewal befellere the actual expiration date

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

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

9.2.4 TLDs requiring action five (5) days befellere expiration

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

.CX, .DE, .EU, och .NL.

9.2.5 .CM dom?ns

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

9.2.6 .GG dom?ns

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

9.2.7 .PH, .COM.PH, .NET.PH, och .ORG.PH dom?ns

These dom?ns may not suppellert a stochard 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. Om the dom?n is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppellert immediately.

9.2.8 .UK dom?ns, including second-level .UK dom?ns

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

9.2.9 .TO dom?ns

.TO dom?n names may only be reactivated during approximately twenty-seven (27) days after expiration. They generally do not suppellert a stochard Redemption Grace Period. After that point, they may be reserved by the registry och may no longer be recoverable.

9.2.10 .NU dom?ns

.NU dom?n names may be reactivated in the ellerdinary manner within approximately seven (7) days after expiration. Om not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restelleration may still be possible through NiceNIC Suppellert.

9.3 The TLD-specific infellermation above is provided feller general reference only och may change at any time based on registry policy, registry system changes, eller operational requirements. Customers should contact NiceNIC Suppellert feller current TLD-specific recovery infellermation.

10. Fees och Betalaments

10.1 Stochard renewal fees, redemption fees, restelleration fees, auction-related fees, och any other applicable charges shall be those listed by NiceNIC at the time of processing eller otherwise communicated by NiceNIC.

10.2 Redemption eller restelleration requires payment in full of all applicable fees befellere processing.

10.3 Alla fees paid feller expired-dom?n recovery, restelleration, eller special processing are non-refundable once processing has begun, except wh?r otherwise required by applicable law.

11. Nej Guarantee of Recovery eller Availability

11.1 NiceNIC does not guarantee that any expired dom?n name can be renewed, restellered, retained, transferred, eller re-registreraed after expiration.

11.2 NiceNIC does not guarantee:

(a) that a dom?n name will remain in a grace period feller any minimum time;

(b) that an expired dom?n name will not enter auction;

(c) that a dom?n name can be recovered after an active bid, pending k?p, eller completed sale;

(d) that the registry will suppellert restelleration; eller

(e) the exact date eller time when a deleted dom?n 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 tj?nst, auction sale, eller permanent loss of the dom?n name.

12. Limitation of Responsibility

12.1 Till the maximum extent permitted by applicable law, NiceNIC shall not be liable feller any loss of dom?n name, loss of use, interruption of website eller email tj?nst, business interruption, lost profits, loss of data, eller other direct eller indirect damages arising from:

(a) dom?n expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules eller registry actions;

(e) auction placement eller sale;

(f) failed restelleration; eller

(g) release of the dom?n name to the public.

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

13. Changes to This Policy

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

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

14. Kontakt

Om you need assistance regarding an expired dom?n name, renewal, redemption, eller TLD-specific recovery options, please submit a suppellert ticket through din NiceNIC account eller contact NiceNIC Suppellert through the official suppellert channels published on the NiceNIC website.

1. General

This Agreement is made between you (h?rinafter referred to as “User”) och NiceNIC.NET (h?rinafter referred to as “the Platfellerm”). By using the Platfellerm’s K?p Nejw Dom?n Sales tj?nst, you agree to be bound by the terms och conditions set fellerth h?rin. Om you do not agree, please do not proceed with any fixed-price dom?n k?p through the Platfellerm.

2. Service Description

1. The Platfellerm offers fixed-price dom?n names (“K?p Nejw Dom?ner”) feller direct k?p.

2. Alla K?p Nejw Dom?ner are sourced from pre-approved third-party dom?n providers.

3. Users may k?p these dom?ns at the listed price. Once payment is completed och the dom?n is successfully transferred, the k?per will obtain ownership of the dom?n.

3. Purchase Process

1. The User selects a dom?n labeled as “K?p Nejw” och proceeds to checkout.

2. Upon confirmation och full payment, the Platfellerm initiates the transfer eller delivery process.

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

4. Om, feller any reason, the selected dom?n becomes unavailable eller undeliverable after k?p, the Platfellerm will issue a full refund to the user’s account balance.

4. User Rights och Responsibilities

1. Users have the right to k?p available K?p Nejw Dom?ner through the Platfellerm.

2. Users must ensure that all provided account och payment infellermation is accurate och lawful.

3. Users shall not engage in malicious activity, technical disruption, eller behavieller that interferes with the nellermal functioning of the Platfellerm.

4. Upon acquiring a dom?n, the User agrees to comply with the applicable rules och policies of the cellerresponding dom?n registry, including any legal eller regulatellery obligations.

5. Platfellerm Rights och Responsibilities

1. The Platfellerm will provide dom?n transaction tj?nsts in accellerdance with this Agreement och strive to protect user interests.

2. The Platfellerm reserves the right to verify user identity, payment legitimacy, och transaction authenticity.

3. The Platfellerm retains the right to update, adjust, eller remove K?p Nejw Dom?ner from listing at its sole discretion och without prieller notice.

4. Om any fraudulent eller abusive behavieller is detected, the Platfellerm reserves the right to suspend eller terminate tj?nsts to the user.

6. Disclaimer

1. The Platfellerm does not make any guarantees regarding the future value, resale potential, eller commercial use of any dom?n k?pd.

2. The Platfellerm is not liable feller delays caused by registries, third-party providers, eller external systems beyond its control.

3. The Platfellerm shall not be held responsible feller tj?nst interruptions, data loss, eller failed transactions resulting from fellerce majeure events eller uncontrollable technical issues, though reasonable effellerts will be made to assist the User in resolving any such issues.

7. Governing Law och Dispute Resolution

1. This Agreement shall be governed by och construed in accellerdance with the laws of Hongkong.

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

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a K?p Nejw dom?n ellerder.

2. The Platfellerm reserves the right to amend this Agreement at any time. Uppdaterad versions will be published on the Platfellerm’s “Avtal” page och shall take immediate effect. Continued use of the tj?nst constitutes acceptance of the revised terms.

This Unifellerm Dom?nnamn Dispute Resolution Policy (the "Policy") has been adopted by the Internet Cellerpelleration feller Assigned Namns och Numbers ("ICANN"), is incellerpellerated by reference into din Registrering Agreement, och sets fellerth the terms och conditions in connection with a dispute between you och any party other than us (the registrar) over the registration och use of an Internet dom?n name registreraed by you. Proceedings under Paragraph 4 of this Policy will be conducted accellerding to the Rules feller Unifellerm Dom?nnamn Dispute Resolution Policy (the "Rules of Procedure"), which are available h?r, och the selected administrative-dispute-resolution tj?nst provider's supplemental rules.

2. Your Representations

By applying to registrera a dom?n name, eller by asking us to maintain eller renew a dom?n name registration, you h?rby represent och warrant to us that (a) the statements that you made in din Registrering Agreement are complete och accurate; (b) to din knuledge, the registration of the dom?n name will not infringe upon eller otherwise violate the rights of any third party; (c) you are not registreraing the dom?n name feller an unlawful purpose; och (d) you will not knuingly use the dom?n name in violation of any applicable laws eller regulations. It is din responsibility to determine whether din dom?n name registration infringes eller violates someone else's rights.

3. Avbrytlations, Transfers, och Changes

We will cancel, transfer eller otherwise make changes to dom?n name registrations under the following circumstances:

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

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

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

4. We may also cancel, transfer eller otherwise make changes to a dom?n name registration in accellerdance with the terms of din Registrering Agreement eller other legal requirements.

4. Mochatellery Administrative Proceeding

This Paragraph sets fellerth the type of disputes feller which you are required to submit to a mochatellery administrative proceeding. These proceedings will be conducted befellere one of the administrative-dispute-resolution tj?nst providers listed h?r (each, a "Provider").

1. Applicable Disputes. You are required to submit to a mochatellery 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. din dom?n name is identical eller confusingly similar to a trademark eller tj?nst mark in which the complainant has rights; och

2. you have no rights eller legitimate interests in respect of the dom?n name; och

3. din dom?n name has been registreraed och 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 Registrering och Use in D?lig Faith. Feller 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 och use of a dom?n name in bad faith:

1. circumstances indicating that you have registreraed eller you have acquired the dom?n name primarily feller the purpose of selling, renting, eller otherwise transferring the dom?n name registration to the complainant who is the owner of the trademark eller tj?nst mark eller to a competiteller of that complainant, feller valuable consideration in excess of din documented out-of-pocket costs directly related to the dom?n name; eller

2. you have registreraed the dom?n name in ellerder to f?reg?endeent the owner of the trademark eller tj?nst mark from reflecting the mark in a cellerresponding dom?n name, provided that you have engaged in a pattern of such conduct; eller

3. you have registreraed the dom?n name primarily feller the purpose of disrupting the business of a competiteller; eller

4. by using the dom?n name, you have intentionally attempted to attract, feller commercial gain, Internet users to din web site eller other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsellership, affiliation, eller endellersement of din web site eller location eller of a product eller tj?nst on din web site eller location.

3. How to Demonstrate Your Rights to och Legitimate Interests in the Dom?nnamn in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how din 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 din rights eller legitimate interests to the dom?n name feller purposes of Paragraph 4(a)(ii):

1. befellere any notice to you of the dispute, din use of, eller demonstrable preparations to use, the dom?n name eller a name cellerresponding to the dom?n name in connection with a bona fide offering of goods eller tj?nsts; eller

2. you (as an individual, business, eller other ellerganization) have been commonly knun by the dom?n name, even if you have acquired no trademark eller tj?nst mark rights; eller

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

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

7. Fees. Alla fees charged by a Provider in connection with any dispute befellere an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wh?r you elect to expoch 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 och the complainant.

8. V?r Involvement in Administrative Proceedings. We do not, och will not, participate in the administration eller conduct of any proceeding befellere 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 befellere an Administrative Panel shall be limited to requiring the cancellation of din dom?n name eller the transfer of din dom?n name registration to the complainant.

10. Nejtification och Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a dom?n name you have registreraed with us. Alla decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact pellertions of its decision.

11. Availability of Court Proceedings. The mochatellery administrative proceeding requirements set fellerth in Paragraph 4 shall not f?reg?endeent either you eller the complainant from submitting the dispute to a court of competent jurisdiction feller independent resolution befellere such mochatellery administrative proceeding is commenced eller after such proceeding is concluded. Om an Administrative Panel decides that din dom?n name registration should be canceled eller transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are infellermed by the applicable Provider of the Administrative Panel's decision befellere 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 eller of din address as shown in our Whois database. See Paragraphs 1 och 3(b)(xiii) of the Rules of Procedure feller details.) Om we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, och we will take no further action, until we receive (i) evidence satisfactellery to us of a resolution between the parties; (ii) evidence satisfactellery to us that din lawsuit has been dismissed eller withdrawn; eller (iii) a copy of an ellerder from such court dismissing din lawsuit eller ellerdering that you do not have the right to continue to use din dom?n name.

5. Alla other disputes och litigation

Alla other disputes between you och any party other than us regarding din dom?n name registration that are not brought pursuant to the mochatellery administrative proceeding provisions of Paragraph 4 shall be resolved between you och such other party through any court, arbitration eller other proceeding that may be available.

6. V?r involvement in disputes

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

7. Maintaining status quo

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

8. Transfers during a dispute

Transfers of a Dom?nnamn to a Ny Holder

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

Changing Registrars

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

1. Overview

These terms of use ("AI Periods of Use") govern din use of any AI products, features, tj?nsts och/eller tools offered by NiceNIC.NET.

2. Content

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

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

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

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

6) By using the AI Services, you understoch och agree:

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

B. You must evaluate Output feller accuracy och appropriateness feller din use case, including using human review as appropriate, befellere using eller sharing Output from the AI Services.

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

D. V?r AI Services may provide incomplete, incellerrect, eller offensive Output that does not represent NiceNIC.NET’s views. Om Output references any third party products eller tj?nsts, it doesn’t mean the third party endellerses eller is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users och the AI Services may generate the same eller similar Outputs feller other users.

8) NiceNIC.NET may use technology provided by third-party tj?nst providers to provide AI Services. Nejtwithstoching anything to the contrary contained h?rin, you authellerize NiceNIC.NET och such third-party tj?nst providers to stellere och use din Input feller the purposes of providing you with the AI Services, to review Inputs och Outputs feller abuse eller misuse, och to develop och improve the tj?nsts och products of NiceNIC.NET och such tj?nst providers, including as part of the design, training och development process feller machine learning models.

3. Periodination och Suspension

Periodination. We reserve the right to suspend eller terminate din access to our AI Services eller delete din account if we determine:

1) You breached these AI Periods of Use.

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

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

4. Disclaimers

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

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

5. Limitation on Liability

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

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

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

Upon denying a transfer request feller any of the following reasons, the Registrar of Recellerd must provide the Registreraed Namn Holder och the potential Gaining Registrar with the reason feller denial. The Registrar of Recellerd may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court ellerder by a court of competent jurisdiction
• Reasonable dispute over the identity of the Registreraed Namn Holder eller Administrative Kontakt
• Nej payment feller f?reg?endeious registration period (including credit card charge-backs) if the dom?n name is past its expiration date eller feller f?reg?endeious eller current registration periods if the dom?n name has not yet expired. In all such cases, however, the dom?n name must be put into "Registrar Hold" status by the Registrar of Recellerd prieller to the denial of transfer.
• Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document eller other processes by which the Transfer Kontakt has expressly och voluntarily objected through opt-in means)
• A dom?n name was already in “l(fā)ock status” provided that the Registrar provides a readily accessible och reasonable means feller the Registreraed Namn Holder to remove the lock status.
• A dom?n name is in the first 60 days of an initial registration period.
• A dom?n name is within 60 days (eller a lesser period to be determined) after being transferred (apart from being transferred back to the elleriginal Registrar in cases wh?r both Registrars so agree och/eller wh?r a decision in the dispute resolution process so directs).

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

YOU ALSO AGREE THAT WE WILL NOT BE LIABLE FELLER ANY INDIRECT, SPECIAL, INCIDENTAL, ELLER CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LOperativsystemT PROFITS) ELLER FELLER ANY FINANCIAL ELLER ECONOMIC LOperativsystemS ELLER FELLER LOperativsystemS OF PROFITS, LOperativsystemS OF BUSINESS, DEPLETION OF GOODWILL ELLER SIMILAR LOperativsystemSES, LOperativsystemS OF ANTICIPATED SAVINGS ELLER LOperativsystemS ELLER CELLERRUPTION OF DATA ELLER INFELLERMATION, REGARDLESS OF THE FELLERM OF ACTION WHETHER IN CONTRACT, TELLERT (INCLUDING NEGLIGENCE), ELLER OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE POperativsystemSIBILITY OF SUCH DAMAGES.

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

24. General
You may not assign any of din rights eller privileges, eller delegate any of din duties eller obligations h?runder, in whole eller in part, by operation of law eller otherwise, to any third party without our prieller written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon och inure to the benefit of the parties h?rto och their respective permitted successellers och assigns.

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

This Agreement constitutes the entire agreement between the parties concerning the subject matter h?rin och supersedes all prieller understochings och agreements between the parties, whether written eller elleral, regarding the subject matter h?rin. Any of the provisions of this Agreement which are determined to be invalid eller unenfellerceable in any jurisdiction shall be ineffective to the extent of such invalidity eller unenfellerceability in such jurisdiction, without rendering invalid eller unenfellerceable the remaining provisions h?rof eller affecting the validity eller unenfellerceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach eller violation of any provision of this Agreement will not constitute eller be construed as a waiver of any subsequent breach eller violation of that provision eller as a waiver of any breach eller violation of any other provision of this Agreement. The headings contained in this Agreement are feller convenience only och shall not affect meaning eller interpretation of this Agreement.

25. Nejtices
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 accellerdance with the Account och/eller WHOIS infellermation you have provided.

26. Governing Law
This Agreement och its subject matter shall be governed in accellerdance with the laws of Hongkong och subject to the exclusive jurisdiction of the Hongkong courts without regard to conflict of laws och principles contained th?rin with the exception of disputes related to this Agreement which fall under UDRP, URS, eller similar dispute resolution process as defined by various Registry policies incellerpellerated eller made reference to h?rin.

1.3 The Registrant acknuledges och agrees that the Registrar shall moniteller the status of Dom?nnamn registreraed through the Registrar och shall, at its own initiative eller on receipt of complaint, conduct checks to verify whether a Dom?nnamn is being used in connection with phishing eller "spam" advertising. The Registrar shall delete eller suspend a Dom?nnamn if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government eller law enfellercement authellerity (including without limitation the Hongkong Police Fellerce eller the Office of Telecommunications Authellerity) that the use of the Dom?nnamn is in breach of any laws, directives, guidelines, codes of practice eller regulations issued by such local authellerities, eller if, in HKIRC's reasonable belief, the continuation of registration of the Dom?nnamn eller the operation of web site referenced   by the Dom?nnamn is likely to damage eller adversely affect the goodwill, reputation och operation of HKIRC eller the dom?n name industry in Hongkong, eller may expose HKIRC to risks of third party claims eller civil eller criminal prosecution.

Feller mellere infellermation about .HK dom?n registration, please refer to the latest version of HKIRC Registrering 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 tj?nst provider shall be final och binding on the Registrant och 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 och non-statutellery cellerpelleration designated by the Hong-Kong Government to administer the registration of Internet dom?n names under .hk och .香港 country-code top level dom?ns. Feller any comments eller complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find h?r useful infellermation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppellert/dom?n_dispute_policies_och_procedures/dom?n_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppellert/dom?n_dispute_policies_och_procedures/rules_of_procedures/; eller E-post address: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant acknuledges that the Registrar och HKIRC rely on all representations made och warranties given by the Registrant in determining if the application feller a Dom?nnamn should be approved.

    Feller mellere infellermation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/dom?n_policies/EN_Dom?n_Namn_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. Nejw that you have met the requirements of ICANN, our team is looking fellerward to assisting you in completing the Verisign certification process so you can quickly begin registreraing .com och .net dom?n names. We hope this suppellert will prove to be helpful in reducing the investment of din internal resources och time."

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

ICM:
"Congrats on din recent ICANN Ackreditering..."

Neustar:

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

Mer registries will be notified by ICANN feller the cellerresponding dom?n names signed in the RAA in the n?sta days, we NiceNIC have been staying feller the disposal of sign-up/accreditation process, striving to save time och expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mellere competitive level. Detaljed infellermation 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"), och dedicated to offer clients easy to navigate, fast to locate tj?nsts in dom?n name registration, web hosting k?p, 1 to 1 customer suppellert.

Stoching at the peak of internet infrastruture, we firstly need to appreciate every client, och every website viewer who ever stayed h?r, without din persistant suppellert och comprehension, we are nothing, hope 2012 will bring you och din family lucky, happy, healthy life.

Reference links:

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

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

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

ZhuHai NaiSiNiKe Infellermation Technology Co Ltd.

2009

China

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

Alla the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infellermation 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 feller Enfellercement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent och neutral third party that is neither associated neller affiliated with either Registrar involved in the dispute eller the Registry Operateller under which the disputed dom?n name is registreraed. ICANN shall have the authellerity to accredit one eller mellere independent och neutral Dispute Resolution Providers accellerding to criteria developed in accellerdance with this Dispute Resolution Policy.

1.4 FOA

     Fellerm of Authellerization - The stochardized fellerm of consent that the Gaining Registrar och Registrar of Recellerd are required to use to obtain authellerization from the Registrant eller Administrative Kontakt in ellerder to properly process the transfer of dom?n name sponsellership from one Registrar to another.

1.5 Gaining Registrar

     The Registrar that submitted to the Registry the request feller the transfer of a dom?n sponsellership from the Registrar of Recellerd.

1.6 Registrar of Recellerd

     The Registrar of Recellerd feller a dom?n name feller which the Registry received a transfer of sponsellership request.

1.7 Registrant

     The Registrant is the individual eller ellerganization that registreras a specific dom?n name. This individual eller ellerganization holds the right to use that specific dom?n name feller a specified period of time, provided certain conditions are met och the registration fees are paid. This person eller ellerganization is the "legal entity" bound by the terms of the relevant tj?nst agreement with the Registry operateller feller the TLD in question.

1.8 Registry (Registry Operateller)

     The ellerganization authellerized by ICANN to provide registration tj?nsts feller a given TLD to ICANN-accredited Registrars.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operateller, in the case of First Niv? disputes (as set fellerth below), eller 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 och shall cover topics such as fees, wellerd och page limits och guidelines, the means feller communicating with the Provider, och the fellerm of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponsellership of Registrerings between Registrars which is in fellerce as part of the Registry-Registrar Agreement executed between a Registrar och the Registry, as well as the Registrar Ackreditering Agreement which is executed between ICANN och all ICANN- accredited registrars.

2. Dispute Resolution Process

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

2.1 First Niv? - Registry Operateller

     A Registrar may choose to file a dispute directly with the relevant Registry Operateller. Any decisions made by the Registry Operateller 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 fellerfeit any right to appeal the decision of the Dispute Resolution Provider.

2.2 Second-Niv? - Dispute Resolution Panel

     The primary intent of this step is to provide a means feller 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 wh?r a Registrar of Recellerd 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 wh?r 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 Niv? (Registry)

3.1 Registrar files a Request feller Enfellercement with the applicable Registry Operateller

     3.1.1 Either the Gaining eller Registrar of Recellerd ("Filing Registrar") may submit a Request feller Enfellercement. This must be done in accellerdance with the Supplemental Rules adopted by the applicable Registry Operateller.

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

3.1.4 The Request feller Enfellercement shall annex the following documentary evidence (as applicable och available) in electronic fellerm if possible, together with a schedule indexing such evidence:
  (i) Feller the Gaining Registrar:
      a. Completed Fellerm of Authellerization ("FOA")
      b. Copy of the Whois output feller the date transfer was initiated, which was used to identify the authellerized Transfer Kontakts
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body eller court ellerder in cases when the Registrant of Recellerd is being changed simultaneously with a Registrar Transfer
      e. Copies of all communications made to the Registrar of Recellerd with regard to the applicable transfer request along with any responses from the Registrar of Recellerd
  (ii) Feller the Registrar of Recellerd:
      a. Completed FOA from Registrar of Recellerd if applicable
      b. Copy of the Whois output feller the date the transfer was initiated
      c. Relevant histellery of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court ellerder;
• Registrant eller administrative contact identity dispute in accellerdance with Section 4 [Registrar of Recellerd Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the Registreraed Namn Holder eller Administrative Kontakt;
• LOCK status along with proof of a reasonable means feller the registrant to remove LOCK status as per Section __of Exhibit __ to this Agreement;
• dom?n name within 60 days of initial registration; eller
• dom?n name within 60 days of a prieller 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 Nejn-Filing Registrar ("Respondent") shall have seven (7) calendar days from receipt of the Request feller Enfellercement to prepare a Response to the Request feller Enfellercement ("Response").

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

3.2.2 P? the request of the Respondent, the Registry Operateller may, in exceptional cases, extend the period of time feller the filing of the response, but in no case may the extension be mellere 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 Operateller.

3.2.3 Om a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operateller shall decide the dispute based upon the Request feller Enfellercement.

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

3.3.1 Om the data included in the Request feller Enfellercement does not match the data listed in the authelleritative Whois, the Registry Operateller must contact each Registrar och require additional documentation.

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

3.3.3 In the case wh?r a Registrar of Recellerd denies a request feller a dom?n name transfer ("NACKs"), the Registrar of Recellerd must provide evidence of one of the factellers feller which it is allowed to NACK. Om the Registrar of Recellerd cannot provide evidence that demonstrates any of the factellers, och the Gaining Registrar provides to the Registry a complete FOA with data matching that contained within the authelleritative Whois database, then the transfer must be approved to be processed.

3.3.4 Om the data provided by neither Registrar appears to be conclusive, then the Registry shall issue a finding of "no decision." Om the data provided to the Registry is complete och provides sufficient basis feller 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-Niv? Dispute Resolution Provider in accellerdance with the provisions set fellerth below.

3.4 Fees feller First-Niv? Dispute Resolution Service

3.4.1 Th?r is no filing fee assessed to the Filing Registrar at the time the Request feller Enfellercement is submitted to the Registry Operateller.

3.4.2 The Registrar that does not f?reg?endeail in the dispute will be assessed a fee to be set by the Registry Operateller. Such fee shall be set fellerth in the Registry's Supplemental Rules that are in effect at the time that the Request feller Enfellercement 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 Operateller shall collect the applicable fees from the Filing Registrar.

3.5 Availability of Court Proceedings

      The procedures set fellerth above shall not f?reg?endeent a Registrar from submitting a dispute to a court of competent jurisdiction feller independent resolution befellere such an administrative proceeding is commenced eller after such proceeding is concluded. Om a Registry Operateller decides a dom?n name registration should be transferred (either to the Gaining Registrar, eller alternatively, back from the Gaining Registrar to the Registrar of Recellerd), the Registry will wait fourteen (14) calendar days after it is infellermed of the decision befellere 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 dom?n name(s). Om such documentation is received by the Registry Operateller within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operateller that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operateller that the lawsuit has been dismissed eller withdrawn; eller (iii) the Registry Operateller receives a copy of an ellerder from such court.

4. Dispute Procedures at the Second Niv? with a Dispute Resolution Provider

4.1 The tj?nsts 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-Niv? dispute process at Registry level och submit a Request feller Enfellercement directly with a Dispute Resolution Provider;
      (ii) The non-f?reg?endeailing Registrar in a First-Niv? dispute proceeding may submit an appeal of the applicable Registry Operateller's decision to the Dispute Resolution Provider. L?gg tillitionally, in the case wh?r the result in the First-Niv? dispute process is a "no-decision," either Registrar may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request feller Enfellercement

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

4.3 Appeal of First Niv? Dispute Decision eller Registry Operateller Finding of "Nej-Decision."

4.3.1 In the event that the Registrar which does not f?reg?endeail in the First-Niv? dispute is dissatisfied by the Registry-Operateller'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-Niv? decision was issued.

4.3.2 In the event that the Registry Operateller issues a finding of "no-decision" in accellerdance 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-Niv? 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 fellerm och shall:
     (i) Request that the Appeal be submitted feller decision in accellerdance with the Policy och these Rules;
     (ii) Provide the name, postal och e-mail addresses, och the telephone och telefax numbers of the Appellant och of any representative authellerized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
     (iii) Provide the name of the Appellee och all infellermation (including any postal och e-mail addresses och telephone och telefax numbers) knun to Appellee regarding how to contact Appellee eller any representative of Appellee, including contact infellermation based on pre-Request feller Enfellercement och pre-Appeal dealings;
     (iv) Specify the dom?n 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 feller such appeal, including specific responses to the findings of the Registry Operateller in the First-Niv? Dispute process. (This pellertion of the response shall comply with any wellerd eller page limit set fellerth in the Dispute Resolution Provider's Supplemental Rules);
     (vii) Specify, in accellerdance with the Policy, the remedies sought;
     (viii) Identify any other related legal proceedings knun to the Appellant that have been commenced eller terminated in connection with eller relating to any of the dom?n 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 eller transmitted to the Appellee; och
      (x) Conclude with the following statement followed by the signature of the Appellant eller its authellerized representative:
  "Appellant agrees that its claims och remedies concerning the registration of the dom?n name, the dispute, eller the dispute's resolution shall be solely against the Appellee och waives all such claims och remedies against the Dispute Resolution Provider och the Registry Operateller as well as their directellers, officers, employees, och agents, except in the case of deliberate wrongdoing eller gross negligence."
  "Appellant certifies that the infellermation contained in this Appeal is to the best of Appellant's knuledge complete och accurate, that this Appeal is not being presented feller any improper purpose, such as to harass, och that the assertions in this Appeal are warranted under this Policy och under applicable law, as it nu exists eller as it may be extended by a good-faith och reasonable argument."

4.3.5 The Appeal may relate to mellere than one dom?n name, provided that the dom?n names involve the same decision issued by the Registry Operateller feller the First-Niv? Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operateller during the First-Niv? Dispute.

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

• Approval of a Transfer
• Denial of the Transfer (eller ellerdering the dom?n name be returned to the Registrar of Recellerd in cases wh?r a Transfer has already occurred)

4.4 Fees feller Second-Niv? Dispute Resolution Service

4.4.1 In the case of either a Request feller Enfellercement eller an Appeal filed at the Second Niv?, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms och 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 eller Appellant, whichever applicable, does not f?reg?endeail in a Second-Niv? dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

4.4.3 In the event that the Filing Registrar eller Appellant, whichever applicable, f?reg?endeails in a Second-Niv? dispute, the Respondent eller 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 eller Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent eller Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accellerdance 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 fellerth above shall not f?reg?endeent a Registrar from submitting a dispute to a court of competent jurisdiction feller independent resolution befellere such administrative proceeding is commenced eller after such proceeding is concluded. Om a Dispute Resolution Panel decides a dom?n name registration should be transferred (either to the Gaining Registrar, eller alternatively, back from the Gaining Registrar to the Registrar of Recellerd), such Registrar will wait fourteen (14) calendar days after it is infellermed of the decision befellere 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 dom?n name(s). Om 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 eller withdrawn; eller (iii) a copy of an ellerder from such court dismissing the lawsuit eller ellerdering certain actions with respect to the dom?n name.

1. Registrar Requirements

     Registreraed Namn Holders must be able to transfer their dom?n name registrations between Registrars provided that the Gaining Registrar's transfer process meets the minimum stochards of this policy och that such transfer is not prohibited by ICANN eller Registry policies. Inter-Registrar dom?n name transfer processes must be clear och concise in ellerder to avoid confusion. Further, Registrars should make reasonable effellerts to infellerm Registreraed Namn Holders of, och provide access to, the published documentation of the specific transfer process employed by the Registrars.

1.1 Transfer Authellerities

     The Administrative Kontakt och the Registreraed Namn Holder, as listed in the Losing Registrar's eller applicable Registry's (wh?r available) publicly accessible WHOIS tj?nst are the only parties that have the authellerity to approve eller deny a transfer request to the Gaining Registrar. In the event of a dispute, the Registreraed Namn Holder's authellerity supersedes that of the Administrative Kontakt.
Registrars may use Whois data from either the Registrar of Recellerd eller the relevant Registry feller the purpose of verifying the authenticity of a transfer request; eller from another data source as determined by a consensus policy.

2. Gaining Registrar Requirements

Feller each instance wh?r a Registreraed Namn Holder requests to transfer a dom?n name registration to a different Registrar, the Gaining Registrar shall:
      2.1 Obtain express authellerization from either the Registreraed Namn Holder eller the Administrative Kontakt (h?rafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrar from the Transfer Kontakt.

     2.1.1 The authellerization must be made via a valid Stochardized Fellerm of Authellerization (FOA). Th?r are two different FOA's available at the ICANN website. The FOA labeled "Initial Authellerization feller Registrar Transfer" must be used by the Gaining Registrar to request an authellerization feller a registrar transfer from the Transfer Kontakt. The FOA labeled "Bekr?ftaation of Registrar Transfer Request" may be used by the Registrar of Recellerd to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, och any dispute arising out of a transfer request shall be conducted in the English language. Registrars may choose to communicate with the Transfer Kontakt in additional languages. However, Registrars choosing to exercise such option are responsible feller the accuracy och 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 authellerization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontakt och further that it is accompanied by a physical copy of the Registrar of Recellerd's Whois output feller the dom?n name in question.

     2.1.2.1 Om the Gaining Registrar relies on a physical authellerization process, then the Gaining Registrar assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt och maintaining appropriate recellerds proving that such evidence was obtained. Further the Gaining Registrar also assumes the burden feller ensuring that the entity making the request is indeed authellerized to do so. The acceptable fellerms of physical identity are:

• Nejtarized statement
• Valid Drivers license
• Passpellert
• Article of Incellerpelleration
• 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 authellerization the acceptable fellerms of identity would include:

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

     The Registrar of Recellerd may not deny a transfer request solely because it believes that the Gaining Registrar has not received the confirmation set fellerth 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 och authenticated the transfer request made by a Transfer Kontakt.

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

     2.2.1 Transmission of a "transfer" commoch constitutes a representation on the part of the Gaining Registrar that the requisite authellerization has been obtained from the Transfer Kontakt listed in the authelleritative Whois database.

     2.2.2 The Gaining Registrar is responsible feller validating the Registreraed Namn Holder requests to transfer dom?n names between Registrars. However, this does not preclude the Registrar of Recellerd from exercising its option to independently confirm the Registreraed Namn Holder's intent to transfer its dom?n name to the Gaining Registrar in accellerdance with Section 3 of this policy.

3. Obligations of the Registrar of Recellerd

     A Registrar of Recellerd can choose independently to confirm the intent of the Registreraed Namn Holder when a notice of a pending transfer is received from the Registry. The Registrar of Recellerd must do so in a manner consistent with the stochards set fellerth in this agreement pertaining to Gaining Registrars. In ellerder to ensure that the fellerm of the request employed by the Registrar of Recellerd is substantially administrative och infellermative in nature och clearly provided to the Transfer Kontakt feller the purpose of verifying the intent of the Transfer Kontakt, the Registrar of Recellerd must use the FOA.

     The FOA shall be communicated in English, och any dispute arising out of a transfer request, shall be conducted in the English language. Registrars may choose to communicate with the Transfer Kontakt in additional languages. However, the Registrar choosing to exercise such option is responsible feller the accuracy och completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes och procedures set fellerth in this policy. This includes but is not limited to the requirement that no Registrar shall add any additional infellermation to the FOA used to obtain the consent of the Transfer Kontakt in the case of a transfer request.
This requirement does not preclude the Registrar of Recellerd from marketing to its existing customers through separate communications.
The FOA should be sent by the Registrar of Recellerd to the Transfer Kontakt as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operateller.Failure by the Registrar of Recellerd to respond within five (5) calendar days to a notification from the Registry regarding a transfer request will result in a default "approval" of the transfer.

     In the event that a Transfer Kontakt listed in the Whois has not confirmed their request to transfer with the Registrar of Recellerd och the Registrar of Recellerd has not explicitly denied the transfer request, the default action will be that the Registrar of Recellerd must allow the transfer to proceed.
Upon denying a transfer request feller any of the following reasons, the Registrar of Recellerd must provide the Registreraed Namn Holder och the potential Gaining Registrar with the reason feller denial. The Registrar of Recellerd may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court ellerder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Registreraed Namn Holder eller Administrative Kontakt
5. Nej payment feller f?reg?endeious registration period (including credit card charge-backs) if the dom?n name is past its expiration date eller feller f?reg?endeious eller current registration periods if the dom?n name has not yet expired. In all such cases, however, the dom?n name must be put into "Registrar Hold" status by the Registrar of Recellerd prieller to the denial of transfer.
6. Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document eller other processes by which the Transfer Kontakt has expressly och voluntarily objected through opt-in means)
7. A dom?n name was already in “l(fā)ock status” provided that the Registrar provides a readily accessible och reasonable means feller the Registreraed Namn Holder to remove the lock status.
8. A dom?n name is in the first 60 days of an initial registration period.
9. A dom?n name is within 60 days (eller a lesser period to be determined) after being transferred (apart from being transferred back to the elleriginal Registrar in cases wh?r both Registrars so agree och/eller wh?r 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:

• Nejnpayment feller a pending eller future registration period
• Nej response from the Registreraed Namn Holder eller Administrative Kontakt.
• Dom?n name in Registrar Lock Status, unless the Registreraed Namn Holder is provided with the reasonable oppellertunity och ability to unlock the dom?n name prieller to the Transfer Request.
• Dom?n name registration period time constraints, other than during the first 60 days of initial registration eller during the first 60 days after a registrar transfer.
• General payment defaults between Registrar och business partners / affiliates in cases wh?r the Registreraed Namn Holder feller the dom?n in question has paid feller the registration.

     The Registrar of Recellerd has other mechanisms available to collect payment from the Registreraed Namn Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrar of Recellerd must not employ transfer processes as a mechanism to secure payment feller tj?nsts from a Registreraed Namn Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment feller f?reg?endeious registration period(s) if the transfer is requested after the expiration date, eller
     (ii) In the case of non-payment of the current registration period, if transfer is requested befellere the expiration date.

4. Registrar Coellerdination

     Each Registrar is responsible feller keeping copies of documentation, including the FOA och the Transfer Kontakts response th?rto, that may be required feller filing och suppellerting a dispute under the dispute resolution policy. Gaining Registrars must maintain copies of the FOA as received from the Transfer Kontakt as per the stochard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registrar och the Registrar of Recellerd must provide the evidence relied on feller the transfer during och after the applicable inter-registrar dom?n name transaction(s). Such infellermation must be provided when requested by, och only by, the other Registrar that is party to the transfer transaction. L?gg tillitionally, ICANN, the Registry Operateller, a court eller authellerity with jurisdiction over the matter eller a third party dispute resolution panel may also require such infellermation within five (5) days of the request.

     The Gaining Registrar must retain, och produce pursuant to a request by a Losing Registrar, a written eller electronic copy of the FOA. In instances wh?r the Registrar of Recellerd has requested copies of the FOA, the Gaining Registrar must fulfill the Registrar of Recellerds request (including providing the attendant suppellerting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds feller reversal by the Registry Operateller eller the Dispute Resolution Panel in the event that a transfer complaint is filed in accellerdance with the requirements of this policy.

     Om either a Registrar of Recellerd eller a Gaining Registrar does not believe that a transfer request was hochled in accellerdance with the provisions of this policy, then the Registrar may initiate a dispute resolution procedure as set fellerth in Section C of this policy.

     Feller purposes of facilitating transfer requests, Registrars should provide och maintain a unique och private email address feller use only by other Registrars och the Registry:
     i. This email address is feller issue related to transfer requests och the procedures set fellerth 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 feller Registrars

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

     Registrars may not employ any mechanism feller complying with a Registreraed Namn Holder's request to obtain the applicable "AuthInfo Code" that is mellere restrictive than the mechanisms used feller changing any aspect of the Registreraed Namn Holder's contact eller name server infellermation.

     The Registrar of Recellerd must not refuse to release an "AuthInfo Code" to the Registreraed Namn Holder solely because th?r is a dispute between the Registreraed Namn Holder och the Registrar over payment.

Registrar-generated "AuthInfo" codes must be unique on a per-dom?n basis.
     The "Auth-Info" codes must be used solely to identify a Registreraed Namn Holder, wh?ras the FOA's still need to be used feller authellerization eller confirmation of a transfer request, as described in Section 2 och Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commoch from the Gaining Registrar, Registry Operateller 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 feller the purpose of facilitating transfers.

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

7. Recellerds of Registrering

     Each Registrar shall require its customer, the Registreraed Namn Holder, to maintain its own recellerds appropriate to document och prove the initial dom?n name registration date.

8. Effect on Period of Registrering

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

B. ICANN-Approved Transfers

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

C. Transfer Dispute Resolution Policy

     Procedures feller hochling disputes concerning inter-registrar transfers are set fellerth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatellers och ICANN accredited Registrars.

We respect din individual privacy. That is why we have adopted this Integritetspolicy, which embodies our commitment to the protection of din privacy through adh?rnce to fair electronic infellermation practices. This Integritetspolicy puts you, the individual, in control of how din personal infellermation is processed, och you have our promise that we will not electronically process din personal infellermation in any way that is incompatible with this Integritetspolicy.

This Integritetspolicy protects din privacy by:

4. How We Put Infellermation Till Good Use