1. Scope dhe Purpose

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

1.2 Domain lifecycle timing may vary depending on the top-level domain (“TLD”), registry rules, registry operatose practices, applicable ICANN requirements, dhe other governing policies. Jot all TLDs follow the same expiration, redemption, auction, ose deletion process.

1.3 In the event of any inconsistency between this Policy dhe the applicable registry’s rules ose mdheatosey ICANN policy, the applicable registry rules dhe mdheatosey policy requirements shall mbrapaail.

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

2. Definitions

Fose purposes of this Policy:

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

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

2.3 “Redemption Grace Period” ose “RGP” means the post-deletion recovery period, wk?tu available, during which an expired domain name may still be restoseable fose an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, wk?tu applicable, during which the domain name can no longer be renewed, restoseed, modified, ose transferred.

2.5 “Eligible Domain” means a domain name that is subject to NiceNIC’s expired domain auction process. Jot all TLDs ose expired domain names are eligible fose auction.

2.6 “Skadond Domain Auction” means the expired-domain sale process that may apply to certain expired domain names befosee final deletion ose release.

2.7 “Mbyllout Auction” means the final sale phase fose certain Eligible Domeinet that were not sold earlier in the expired domain auction process.

3. Effect of Expiration

3.1 Upon expiration, a domain name may stop resolving, dhe any website, email sh?rbimi, ose other sh?rbimi associated with the domain name may cease functioning immediately ose shosetly tk?tuafter.

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

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

4. Rinovoal Jotices dhe Customer Responsibility

4.1 NiceNIC may send renewal reminders dhe expiration-related notices befosee dhe after expiration, as required by applicable policy ose as part of NiceNIC’s stdheard operational process.

4.2 It is t?nd sole responsibility to maintain accurate dhe current account dhe contact infosemation, including t?nd email address, dhe to monitose the status of t?nd domain names.

4.3 Failure to receive a renewal notice, reminder, invoice, ose other communication shall not relieve you of responsibility fose renewing t?nd domain name befosee expiration.

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

5. Stdheard Post-Expiration Rinovoal

5.1 Fose many generic TLDs, an expired domain name may remain renewable fose approximately thirty (30) days after the Expiration Date at the stdheard renewal fee. This is a general reference only dhe may vary by TLD.

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

5.3 NiceNIC reserves the right to determine whether a domain name remains eligible fose stdheard renewal, redemption, ose other recovery based on the applicable TLD, registry status, auction status, dhe operational feasibility.

6. Skadond Domain Auction fose Eligible Domeinet

6.1 Certain expired domain names may enter NiceNIC’s expired domain auction process befosee all recovery dritares have ended. This process applies only to Eligible Domeinet dhe does not apply to all TLDs.

6.2 Fose Eligible Domeinet under NiceNIC’s stdheard expired-domain process, the following general timeline may apply:

Day 0 after expiration

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

Day 26 after expiration

The domain name may enter expired domain auction. N? this stage, the registrant may still be able to renew the domain name at the stdheard renewal fee, unless otherwise restricted by the applicable process.

Day 31 after expiration

N?se tk?tu is no active bid, the registrant may still be able to recover the domain name by paying the stdheard renewal fee plus the applicable redemption fee.

N?se tk?tu is an active bid, the domain name may be removed from the registrant’s account dhe may no longer be renewable through osedinary renewal ose restoseation procedures.

Day 37 after expiration

The domain name may enter final closeout auction. Unless tk?tu is a pending blej ose other sale-related restriction, the registrant may still be able to recover the domain name by paying the stdheard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. N?se the domain name was not sold ose otherwise committed to sale, recovery may still be possible fose a limited period, subject to the applicable TLD, registry rules, dhe NiceNIC’s operational process.

Day 74 after expiration

The domain name may be removed from the registrant’s account dhe may no longer be renewable ose restoseable through NiceNIC. After that point, the domain name may become available fose re-registration only after the registry releases it.

6.3 Once an Eligible Domain has an active bid, pending blej, completed sale, ose other sale commitment under the expired-domain process, the registrant’s right to renew ose restosee the domain name may be terminated ose restricted.

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

7. Redemption Grace Period

7.1 N?se an expired domain name is not renewed during the applicable grace period dhe if the applicable TLD supposets restoseation after deletion, the domain name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the domain name may stop resolving;

(b) website dhe email sh?rbimis may remain unavailable;

(c) the domain name generally cannot be modified ose transferred; dhe

(d) restoseation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, dhe any taxes ose mdheatosey fees.

7.3 Restoseation during the Redemption Grace Period is not guaranteed dhe remains subject to registry supposet, operational feasibility, the domain’s current status, dhe the absence of auction ose sale restrictions.

8. Pending Delete dhe Final Release

8.1 N?se a domain name is not renewed ose restoseed during the applicable recovery periods, it may enter the Pending Delete stage, wk?tu supposeted by the applicable TLD.

8.2 During Pending Delete, the domain name cannot be renewed, restoseed, transferred, ose modified.

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

8.4 NiceNIC does not guarantee the exact time, date, ose availability of a domain name once it is released by the registry, dhe NiceNIC does not guarantee that the fosemer registrant will be able to re-regjistro the domain name.

9. TLD-Specific Variations

9.1 Jot all TLDs follow the stdheard lifecycle described above. Certain ccTLD-t? dhe other TLDs may have shoseter grace periods, no redemption period, no pending delete stage, ose earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many ccTLD-t? generally follow a lifecycle similar to the stdheard expiration, grace, redemption, dhe deletion process, including, fose example:

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

9.2.2 TLDs with no Pending Delete stage

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

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

9.2.3 TLDs requiring renewal befosee the actual expiration date

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

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

9.2.4 TLDs requiring action five (5) days befosee expiration

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

.CX, .DE, .EU, dhe .NL.

9.2.5 .CM domains

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

9.2.6 .GG domains

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

9.2.7 .PH, .COM.PH, .NET.PH, dhe .ORG.PH domains

These domains may not supposet a stdheard 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. N?se the domain is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Supposet immediately.

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

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

9.2.9 .TO domains

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

9.2.10 .NU domains

.NU domain names may be reactivated in the osedinary manner within approximately seven (7) days after expiration. N?se not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restoseation may still be possible through NiceNIC Supposet.

9.3 The TLD-specific infosemation above is provided fose general reference only dhe may change at any time based on registry policy, registry system changes, ose operational requirements. Customers should contact NiceNIC Supposet fose current TLD-specific recovery infosemation.

10. Fees dhe Paguajments

10.1 Stdheard renewal fees, redemption fees, restoseation fees, auction-related fees, dhe any other applicable charges shall be those listed by NiceNIC at the time of processing ose otherwise communicated by NiceNIC.

10.2 Redemption ose restoseation requires payment in full of all applicable fees befosee processing.

10.3 T? gjitha fees paid fose expired-domain recovery, restoseation, ose special processing are non-refundable once processing has begun, except wk?tu otherwise required by applicable law.

11. Jo Guarantee of Recovery ose Availability

11.1 NiceNIC does not guarantee that any expired domain name can be renewed, restoseed, retained, transferred, ose re-regjistroed after expiration.

11.2 NiceNIC does not guarantee:

(a) that a domain name will remain in a grace period fose any minimum time;

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

(c) that a domain name can be recovered after an active bid, pending blej, ose completed sale;

(d) that the registry will supposet restoseation; ose

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

11.3 You acktaniledge that delayed action may result in additional fees, loss of recovery rights, interruption of sh?rbimi, auction sale, ose permanent loss of the domain name.

12. Limitation of Responsibility

12.1 P?r t? the maximum extent permitted by applicable law, NiceNIC shall not be liable fose any loss of domain name, loss of use, interruption of website ose email sh?rbimi, business interruption, lost profits, loss of data, ose other direct ose indirect damages arising from:

(a) domain expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules ose registry actions;

(e) auction placement ose sale;

(f) failed restoseation; ose

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

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

13. Changes to This Policy

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

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

14. Kontakt

N?se you need assistance regarding an expired domain name, renewal, redemption, ose TLD-specific recovery options, please submit a supposet ticket through t?nd NiceNIC account ose contact NiceNIC Supposet through the official supposet channels published on the NiceNIC website.

1. General

This Agreement is made between you (k?tuinafter referred to as “User”) dhe NiceNIC.NET (k?tuinafter referred to as “the Platfosem”). By using the Platfosem’s Bli Jow Domain Sales sh?rbimi, you agree to be bound by the terms dhe conditions set foseth k?tuin. N?se you do not agree, please do not proceed with any fixed-price domain blej through the Platfosem.

2. Service Description

1. The Platfosem offers fixed-price domain names (“Bli Jow Domeinet”) fose direct blej.

2. T? gjitha Bli Jow Domeinet are sourced from pre-approved third-party domain providers.

3. Users may blej these domains at the listed price. Once payment is completed dhe the domain is successfully transferred, the bler?er will obtain ownership of the domain.

3. Purchase Process

1. The User selects a domain labeled as “Bli Jow” dhe proceeds to checkout.

2. Upon confirmation dhe full payment, the Platfosem initiates the transfer ose delivery process.

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

4. N?se, fose any reason, the selected domain becomes unavailable ose undeliverable after blej, the Platfosem will issue a full refund to the user’s account balance.

4. User Rights dhe Responsibilities

1. Users have the right to blej available Bli Jow Domeinet through the Platfosem.

2. Users must ensure that all provided account dhe payment infosemation is accurate dhe lawful.

3. Users shall not engage in malicious activity, technical disruption, ose behaviose that interferes with the nosemal functioning of the Platfosem.

4. Upon acquiring a domain, the User agrees to comply with the applicable rules dhe policies of the coseresponding domain registry, including any legal ose regulatosey obligations.

5. Platfosem Rights dhe Responsibilities

1. The Platfosem will provide domain transaction sh?rbimis in accosedance with this Agreement dhe strive to protect user interests.

2. The Platfosem reserves the right to verify user identity, payment legitimacy, dhe transaction authenticity.

3. The Platfosem retains the right to update, adjust, ose remove Bli Jow Domeinet from listing at its sole discretion dhe without priose notice.

4. N?se any fraudulent ose abusive behaviose is detected, the Platfosem reserves the right to suspend ose terminate sh?rbimis to the user.

6. Disclaimer

1. The Platfosem does not make any guarantees regarding the future value, resale potential, ose commercial use of any domain blejd.

2. The Platfosem is not liable fose delays caused by registries, third-party providers, ose external systems beyond its control.

3. The Platfosem shall not be held responsible fose sh?rbimi interruptions, data loss, ose failed transactions resulting from fosece majeure events ose uncontrollable technical issues, though reasonable effosets will be made to assist the User in resolving any such issues.

7. Governing Law dhe Dispute Resolution

1. This Agreement shall be governed by dhe construed in accosedance with the laws of Hong Kong.

2. Any dispute arising from the execution ose perfosemance of this Agreement shall be resolved through amicable negotiation. N?se negotiation fails, either party may submit the dispute to the competent court located in the jurisdiction of the Platfosem’s headquarters.

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a Bli Jow domain oseder.

2. The Platfosem reserves the right to amend this Agreement at any time. P?rdit?suar versions will be published on the Platfosem’s “Marr?veshjet” page dhe shall take immediate effect. Continued use of the sh?rbimi constitutes acceptance of the revised terms.

This Unifosem Em?r domeni Dispute Resolution Policy (the "Policy") has been adopted by the Internet Coseposeation fose Assigned Em?rs dhe Numbers ("ICANN"), is incoseposeated by reference into t?nd Regjistrim Agreement, dhe sets foseth the terms dhe conditions in connection with a dispute between you dhe any party other than us (the registrar) over the registration dhe use of an Internet domain name regjistroed by you. Proceedings under Paragraph 4 of this Policy will be conducted accoseding to the Rules fose Unifosem Em?r domeni Dispute Resolution Policy (the "Rules of Procedure"), which are available k?tu, dhe the selected administrative-dispute-resolution sh?rbimi provider's supplemental rules.

2. Your Representations

By applying to regjistro a domain name, ose by asking us to maintain ose renew a domain name registration, you k?tuby represent dhe warrant to us that (a) the statements that you made in t?nd Regjistrim Agreement are complete dhe accurate; (b) to t?nd ktaniledge, the registration of the domain name will not infringe upon ose otherwise violate the rights of any third party; (c) you are not regjistroing the domain name fose an unlawful purpose; dhe (d) you will not ktaniingly use the domain name in violation of any applicable laws ose regulations. It is t?nd responsibility to determine whether t?nd domain name registration infringes ose violates someone else's rights.

3. Anulolations, Transfers, dhe Changes

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

1. subject to the provisions of Paragraph 8, our receipt of written ose appropriate electronic instructions from you ose t?nd authoseized agent to take such action;

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

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

4. We may also cancel, transfer ose otherwise make changes to a domain name registration in accosedance with the terms of t?nd Regjistrim Agreement ose other legal requirements.

4. Mdheatosey Administrative Proceeding

This Paragraph sets foseth the type of disputes fose which you are required to submit to a mdheatosey administrative proceeding. These proceedings will be conducted befosee one of the administrative-dispute-resolution sh?rbimi providers listed k?tu (each, a "Provider").

1. Applicable Disputes. You are required to submit to a mdheatosey 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. t?nd domain name is identical ose confusingly similar to a trademark ose sh?rbimi mark in which the complainant has rights; dhe

2. you have no rights ose legitimate interests in respect of the domain name; dhe

3. t?nd domain name has been regjistroed dhe 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 Regjistrim dhe Use in Keq Faith. Fose 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 dhe use of a domain name in bad faith:

1. circumstances indicating that you have regjistroed ose you have acquired the domain name primarily fose the purpose of selling, renting, ose otherwise transferring the domain name registration to the complainant who is the owner of the trademark ose sh?rbimi mark ose to a competitose of that complainant, fose valuable consideration in excess of t?nd documented out-of-pocket costs directly related to the domain name; ose

2. you have regjistroed the domain name in oseder to mbrapaent the owner of the trademark ose sh?rbimi mark from reflecting the mark in a coseresponding domain name, provided that you have engaged in a pattern of such conduct; ose

3. you have regjistroed the domain name primarily fose the purpose of disrupting the business of a competitose; ose

4. by using the domain name, you have intentionally attempted to attract, fose commercial gain, Internet users to t?nd web site ose other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsoseship, affiliation, ose endosesement of t?nd web site ose location ose of a product ose sh?rbimi on t?nd web site ose location.

3. How to Demonstrate Your Rights to dhe Legitimate Interests in the Em?r domeni in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how t?nd 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 t?nd rights ose legitimate interests to the domain name fose purposes of Paragraph 4(a)(ii):

1. befosee any notice to you of the dispute, t?nd use of, ose demonstrable preparations to use, the domain name ose a name coseresponding to the domain name in connection with a bona fide offering of goods ose sh?rbimis; ose

2. you (as an individual, business, ose other oseganization) have been commonly ktanin by the domain name, even if you have acquired no trademark ose sh?rbimi mark rights; ose

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

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

7. Fees. T? gjitha fees charged by a Provider in connection with any dispute befosee an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wk?tu you elect to expdhe 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 dhe the complainant.

8. Yn? Involvement in Administrative Proceedings. We do not, dhe will not, participate in the administration ose conduct of any proceeding befosee 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 befosee an Administrative Panel shall be limited to requiring the cancellation of t?nd domain name ose the transfer of t?nd domain name registration to the complainant.

10. Jotification dhe Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a domain name you have regjistroed with us. T? gjitha decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact posetions of its decision.

11. Availability of Court Proceedings. The mdheatosey administrative proceeding requirements set foseth in Paragraph 4 shall not mbrapaent either you ose the complainant from submitting the dispute to a court of competent jurisdiction fose independent resolution befosee such mdheatosey administrative proceeding is commenced ose after such proceeding is concluded. N?se an Administrative Panel decides that t?nd domain name registration should be canceled ose transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are infosemed by the applicable Provider of the Administrative Panel's decision befosee 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 ose of t?nd address as shown in our Whois database. See Paragraphs 1 dhe 3(b)(xiii) of the Rules of Procedure fose details.) N?se we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, dhe we will take no further action, until we receive (i) evidence satisfactosey to us of a resolution between the parties; (ii) evidence satisfactosey to us that t?nd lawsuit has been dismissed ose withdrawn; ose (iii) a copy of an oseder from such court dismissing t?nd lawsuit ose osedering that you do not have the right to continue to use t?nd domain name.

5. T? gjitha other disputes dhe litigation

T? gjitha other disputes between you dhe any party other than us regarding t?nd domain name registration that are not brought pursuant to the mdheatosey administrative proceeding provisions of Paragraph 4 shall be resolved between you dhe such other party through any court, arbitration ose other proceeding that may be available.

6. Yn? involvement in disputes

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

7. Maintaining status quo

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

8. Transfers during a dispute

Transfers of a Em?r domeni to a I ri Holder

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

Changing Regjistruess

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

1. Overview

These terms of use ("AI Periudh?s of Use") govern t?nd use of any AI products, features, sh?rbimis dhe/ose tools offered by NiceNIC.NET.

2. Content

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

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

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

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

6) By using the AI Services, you understdhe dhe agree:

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

B. You must evaluate Output fose accuracy dhe appropriateness fose t?nd use case, including using human review as appropriate, befosee using ose sharing Output from the AI Services.

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

D. Yn? AI Services may provide incomplete, incoserect, ose offensive Output that does not represent NiceNIC.NET’s views. N?se Output references any third party products ose sh?rbimis, it doesn’t mean the third party endoseses ose is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users dhe the AI Services may generate the same ose similar Outputs fose other users.

8) NiceNIC.NET may use technology provided by third-party sh?rbimi providers to provide AI Services. Jotwithstdheing anything to the contrary contained k?tuin, you authoseize NiceNIC.NET dhe such third-party sh?rbimi providers to stosee dhe use t?nd Input fose the purposes of providing you with the AI Services, to review Inputs dhe Outputs fose abuse ose misuse, dhe to develop dhe improve the sh?rbimis dhe products of NiceNIC.NET dhe such sh?rbimi providers, including as part of the design, training dhe development process fose machine learning models.

3. Periudh?ination dhe Suspension

Periudh?ination. We reserve the right to suspend ose terminate t?nd access to our AI Services ose delete t?nd account if we determine:

1) You breached these AI Periudh?s of Use.

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

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

4. Disclaimers

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

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

5. Limitation on Liability

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

THE FOSEEGOING LIMITATION OF LIABILITY SHALL SURVIVE ANY TERMINATION OSE EXPIRATION OF THIS AGREEMENT OSE YOUR USE OF THIS SITE, THE AI SERVICES OSE 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 Regjistrues of Recosed dhe the Regjistrues of Recosed has not explicitly denied the transfer request, the default action will be that the Regjistrues of Recosed must allow the transfer to proceed.

Upon denying a transfer request fose any of the following reasons, the Regjistrues of Recosed must provide the Regjistrohued Em?r Holder dhe the potential Gaining Regjistrues with the reason fose denial. The Regjistrues of Recosed may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court oseder by a court of competent jurisdiction
• Reasonable dispute over the identity of the Regjistrohued Em?r Holder ose Administrative Kontakt
• Jo payment fose mbrapaious registration period (including credit card charge-backs) if the domain name is past its expiration date ose fose mbrapaious ose current registration periods if the domain name has not yet expired. In all such cases, however, the domain name must be put into "Regjistrues Hold" status by the Regjistrues of Recosed priose to the denial of transfer.
• Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document ose other processes by which the Transfer Kontakt has expressly dhe voluntarily objected through opt-in means)
• A domain name was already in “l(fā)ock status” provided that the Regjistrues provides a readily accessible dhe reasonable means fose the Regjistrohued Em?r Holder to remove the lock status.
• A domain name is in the first 60 days of an initial registration period.
• A domain name is within 60 days (ose a lesser period to be determined) after being transferred (apart from being transferred back to the oseiginal Regjistrues in cases wk?tu both Regjistruess so agree dhe/ose wk?tu a decision in the dispute resolution process so directs).

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

YOU ALSO AGREE THAT WE WILL NOT BE LIABLE FOSE ANY INDIRECT, SPECIAL, INCIDENTAL, OSE CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LOST PROFITS) OSE FOSE ANY FINANCIAL OSE ECONOMIC LOSS OSE FOSE LOSS OF PROFITS, LOSS OF BUSINESS, DEPLETION OF GOODWILL OSE SIMILAR LOSSES, LOSS OF ANTICIPATED SAVINGS OSE LOSS OSE COSERUPTION OF DATA OSE INFOSEMATION, REGARDLESS OF THE FOSEM OF ACTION WHETHER IN CONTRACT, TOSET (INCLUDING NEGLIGENCE), OSE OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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

24. General
You may not assign any of t?nd rights ose privileges, ose delegate any of t?nd duties ose obligations k?tuunder, in whole ose in part, by operation of law ose otherwise, to any third party without our priose written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon dhe inure to the benefit of the parties k?tuto dhe their respective permitted successoses dhe assigns.

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

This Agreement constitutes the entire agreement between the parties concerning the subject matter k?tuin dhe supersedes all priose understdheings dhe agreements between the parties, whether written ose oseal, regarding the subject matter k?tuin. Any of the provisions of this Agreement which are determined to be invalid ose unenfoseceable in any jurisdiction shall be ineffective to the extent of such invalidity ose unenfoseceability in such jurisdiction, without rendering invalid ose unenfoseceable the remaining provisions k?tuof ose affecting the validity ose unenfoseceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach ose violation of any provision of this Agreement will not constitute ose be construed as a waiver of any subsequent breach ose violation of that provision ose as a waiver of any breach ose violation of any other provision of this Agreement. The headings contained in this Agreement are fose convenience only dhe shall not affect meaning ose interpretation of this Agreement.

25. Jotices
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 accosedance with the Account dhe/ose WHOIS infosemation you have provided.

26. Governing Law
This Agreement dhe its subject matter shall be governed in accosedance with the laws of Hong Kong dhe subject to the exclusive jurisdiction of the Hong Kong courts without regard to conflict of laws dhe principles contained tk?tuin with the exception of disputes related to this Agreement which fall under UDRP, URS, ose similar dispute resolution process as defined by various Registry policies incoseposeated ose made reference to k?tuin.

1.3 The Registrant acktaniledges dhe agrees that the Regjistrues shall monitose the status of Emrat e Domeineve regjistroed through the Regjistrues dhe shall, at its own initiative ose on receipt of complaint, conduct checks to verify whether a Em?r domeni is being used in connection with phishing ose "spam" advertising. The Regjistrues shall delete ose suspend a Em?r domeni if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government ose law enfosecement authoseity (including without limitation the Hong Kong Police Fosece ose the Office of Telecommunications Authoseity) that the use of the Em?r domeni is in breach of any laws, directives, guidelines, codes of practice ose regulations issued by such local authoseities, ose if, in HKIRC's reasonable belief, the continuation of registration of the Em?r domeni ose the operation of web site referenced   by the Em?r domeni is likely to damage ose adversely affect the goodwill, reputation dhe operation of HKIRC ose the domain name industry in Hong Kong, ose may expose HKIRC to risks of third party claims ose civil ose criminal prosecution.

Fose mosee infosemation about .HK domain registration, please refer to the latest version of HKIRC Regjistrim 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 sh?rbimi provider shall be final dhe binding on the Registrant dhe 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 dhe non-statutosey coseposeation designated by the Hong-Kong Government to administer the registration of Internet domain names under .hk dhe .香港 country-code top level domains. Fose any comments ose complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find k?tu useful infosemation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_supposet/domain_dispute_policies_dhe_procedures/domain_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_supposet/domain_dispute_policies_dhe_procedures/rules_of_procedures/; ose Email address: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant acktaniledges that the Regjistrues dhe HKIRC rely on all representations made dhe warranties given by the Registrant in determining if the application fose a Em?r domeni should be approved.

    Fose mosee infosemation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domain_policies/EN_Domain_Em?r_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. Jow that you have met the requirements of ICANN, our team is looking foseward to assisting you in completing the Verisign certification process so you can quickly begin regjistroing .com dhe .net domain names. We hope this supposet will prove to be helpful in reducing the investment of t?nd internal resources dhe time."

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

ICM:
"Congrats on t?nd recent ICANN Akreditimi..."

Neustar:

"We have been notified that t?nd company is tani ICANN-accredited as a .BIZ registrar.  Neustar looks foseward to getting t?nd company up dhe running as soon as possible!"

M? shum? registries will be notified by ICANN fose the coseresponding domain names signed in the RAA in the tjet?r days, we NiceNIC have been staying fose the disposal of sign-up/accreditation process, striving to save time dhe expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mosee competitive level. Detajied infosemation 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"), dhe dedicated to offer clients easy to navigate, fast to locate sh?rbimis in domain name registration, web hosting blej, 1 to 1 customer supposet.

Stdheing at the peak of internet infrastruture, we firstly need to appreciate every client, dhe every website viewer who ever stayed k?tu, without t?nd persistant supposet dhe comprehension, we are nothing, hope 2012 will bring you dhe t?nd family lucky, happy, healthy life.

Reference links:

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

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

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

ZhuHai NaiSiNiKe Infosemation Technology Co Ltd.

2009

China

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

T? gjitha the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infosemation 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 fose Enfosecement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent dhe neutral third party that is neither associated nose affiliated with either Regjistrues involved in the dispute ose the Registry Operatose under which the disputed domain name is regjistroed. ICANN shall have the authoseity to accredit one ose mosee independent dhe neutral Dispute Resolution Providers accoseding to criteria developed in accosedance with this Dispute Resolution Policy.

1.4 FOA

     Fosem of Authoseization - The stdheardized fosem of consent that the Gaining Regjistrues dhe Regjistrues of Recosed are required to use to obtain authoseization from the Registrant ose Administrative Kontakt in oseder to properly process the transfer of domain name sponsoseship from one Regjistrues to another.

1.5 Gaining Regjistrues

     The Regjistrues that submitted to the Registry the request fose the transfer of a domain sponsoseship from the Regjistrues of Recosed.

1.6 Regjistrues of Recosed

     The Regjistrues of Recosed fose a domain name fose which the Registry received a transfer of sponsoseship request.

1.7 Registrant

     The Registrant is the individual ose oseganization that regjistros a specific domain name. This individual ose oseganization holds the right to use that specific domain name fose a specified period of time, provided certain conditions are met dhe the registration fees are paid. This person ose oseganization is the "legal entity" bound by the terms of the relevant sh?rbimi agreement with the Registry operatose fose the TLD in question.

1.8 Registry (Registry Operatose)

     The oseganization authoseized by ICANN to provide registration sh?rbimis fose a given TLD to ICANN-accredited Regjistruess.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operatose, in the case of First Niveli disputes (as set foseth below), ose 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 dhe shall cover topics such as fees, wosed dhe page limits dhe guidelines, the means fose communicating with the Provider, dhe the fosem of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponsoseship of Regjistrims between Regjistruess which is in fosece as part of the Registry-Regjistrues Agreement executed between a Regjistrues dhe the Registry, as well as the Regjistrues Akreditimi Agreement which is executed between ICANN dhe all ICANN- accredited registrars.

2. Dispute Resolution Process

     Tk?tu are two possible steps to the Regjistrues Transfer Dispute Resolution Process. A Regjistrues may elect one ose both of the steps pursuant to the rules below. In the event a Regjistrues either files a Request fose Enfosecement (as described below) with a Second-Niveli Dispute Provider, ose files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-Niveli Registry option later fose the same filing ose matter presented fose resolution.

2.1 First Niveli - Registry Operatose

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

2.2 Second-Niveli - Dispute Resolution Panel

     The primary intent of this step is to provide a means fose 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 wk?tu a Regjistrues of Recosed 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 wk?tu a Gaining Regjistrues 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 Niveli (Registry)

3.1 Regjistrues files a Request fose Enfosecement with the applicable Registry Operatose

     3.1.1 Either the Gaining ose Regjistrues of Recosed ("Filing Regjistrues") may submit a Request fose Enfosecement. This must be done in accosedance with the Supplemental Rules adopted by the applicable Registry Operatose.

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

3.1.4 The Request fose Enfosecement shall annex the following documentary evidence (as applicable dhe available) in electronic fosem if possible, together with a schedule indexing such evidence:
  (i) Fose the Gaining Regjistrues:
      a. Completed Fosem of Authoseization ("FOA")
      b. Copy of the Whois output fose the date transfer was initiated, which was used to identify the authoseized Transfer Kontakts
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body ose court oseder in cases when the Registrant of Recosed is being changed simultaneously with a Regjistrues Transfer
      e. Copies of all communications made to the Regjistrues of Recosed with regard to the applicable transfer request along with any responses from the Regjistrues of Recosed
  (ii) Fose the Regjistrues of Recosed:
      a. Completed FOA from Regjistrues of Recosed if applicable
      b. Copy of the Whois output fose the date the transfer was initiated
      c. Relevant histosey of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court oseder;
• Registrant ose administrative contact identity dispute in accosedance with Section 4 [Regjistrues of Recosed Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the Regjistrohued Em?r Holder ose Administrative Kontakt;
• LOCK status along with proof of a reasonable means fose the registrant to remove LOCK status as per Section __of Exhibit __ to this Agreement;
• domain name within 60 days of initial registration; ose
• domain name within 60 days of a priose transfer.

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

3.2 The Jon-Filing Regjistrues ("Respondent") shall have seven (7) calendar days from receipt of the Request fose Enfosecement to prepare a Response to the Request fose Enfosecement ("Response").

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

3.2.2 N? the request of the Respondent, the Registry Operatose may, in exceptional cases, extend the period of time fose the filing of the response, but in no case may the extension be mosee 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 Operatose.

3.2.3 N?se a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatose shall decide the dispute based upon the Request fose Enfosecement.

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

3.3.1 N?se the data included in the Request fose Enfosecement does not match the data listed in the authoseitative Whois, the Registry Operatose must contact each Regjistrues dhe require additional documentation.

3.3.2 N?se the Gaining Regjistrues cannot provide a complete FOA with data matching that contained within the authoseitative Whois database, then the Registry Operatose shall find that the transfer should be reversed. In the case of a thick Registry, if the Regjistrues of Recosed's Whois is not accessible ose invalid, the Registry Operatose's Whois should be used. In the case of a thin Registry, if the Regjistrues of Recosed's Whois is not accessible ose is invalid, the Registry Operatose must notify ICANN dhe place the dispute on hold until such time as the specific problem is resolved by ICANN.

3.3.3 In the case wk?tu a Regjistrues of Recosed denies a request fose a domain name transfer ("NACKs"), the Regjistrues of Recosed must provide evidence of one of the factoses fose which it is allowed to NACK. N?se the Regjistrues of Recosed cannot provide evidence that demonstrates any of the factoses, dhe the Gaining Regjistrues provides to the Registry a complete FOA with data matching that contained within the authoseitative Whois database, then the transfer must be approved to be processed.

3.3.4 N?se the data provided by neither Regjistrues appears to be conclusive, then the Registry shall issue a finding of "no decision." N?se the data provided to the Registry is complete dhe provides sufficient basis fose a determination based on the Policy, the Registry may not issue a finding of "no decision." Either Regjistrues shall be able to appeal such issue to a Second-Niveli Dispute Resolution Provider in accosedance with the provisions set foseth below.

3.4 Fees fose First-Niveli Dispute Resolution Service

3.4.1 Tk?tu is no filing fee assessed to the Filing Regjistrues at the time the Request fose Enfosecement is submitted to the Registry Operatose.

3.4.2 The Regjistrues that does not mbrapaail in the dispute will be assessed a fee to be set by the Registry Operatose. Such fee shall be set foseth in the Registry's Supplemental Rules that are in effect at the time that the Request fose Enfosecement 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 Operatose shall collect the applicable fees from the Filing Regjistrues.

3.5 Availability of Court Proceedings

      The procedures set foseth above shall not mbrapaent a Regjistrues from submitting a dispute to a court of competent jurisdiction fose independent resolution befosee such an administrative proceeding is commenced ose after such proceeding is concluded. N?se a Registry Operatose decides a domain name registration should be transferred (either to the Gaining Regjistrues, ose alternatively, back from the Gaining Regjistrues to the Regjistrues of Recosed), the Registry will wait fourteen (14) calendar days after it is infosemed of the decision befosee 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 domain name(s). N?se such documentation is received by the Registry Operatose within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatose that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatose that the lawsuit has been dismissed ose withdrawn; ose (iii) the Registry Operatose receives a copy of an oseder from such court.

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

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

      (i) A Filing Regjistrues may elect to skip the First-Niveli dispute process at Registry level dhe submit a Request fose Enfosecement directly with a Dispute Resolution Provider;
      (ii) The non-mbrapaailing Regjistrues in a First-Niveli dispute proceeding may submit an appeal of the applicable Registry Operatose's decision to the Dispute Resolution Provider. Shtoitionally, in the case wk?tu the result in the First-Niveli dispute process is a "no-decision," either Regjistrues may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request fose Enfosecement

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

4.3 Appeal of First Niveli Dispute Decision ose Registry Operatose Finding of "Jo-Decision."

4.3.1 In the event that the Regjistrues which does not mbrapaail in the First-Niveli dispute is dissatisfied by the Registry-Operatose's decision, such Regjistrues 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-Niveli decision was issued.

4.3.2 In the event that the Registry Operatose issues a finding of "no-decision" in accosedance with Section 3.3.4 above, either Regjistrues 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-Niveli decision was issued.

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

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

4.3.5 The Appeal may relate to mosee than one domain name, provided that the domain names involve the same decision issued by the Registry Operatose fose the First-Niveli Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatose during the First-Niveli Dispute.

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

• Approval of a Transfer
• Denial of the Transfer (ose osedering the domain name be returned to the Regjistrues of Recosed in cases wk?tu a Transfer has already occurred)

4.4 Fees fose Second-Niveli Dispute Resolution Service

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

4.4.3 In the event that the Filing Regjistrues ose Appellant, whichever applicable, mbrapaails in a Second-Niveli dispute, the Respondent ose 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 Regjistrues ose Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent ose Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accosedance 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 foseth above shall not mbrapaent a Regjistrues from submitting a dispute to a court of competent jurisdiction fose independent resolution befosee such administrative proceeding is commenced ose after such proceeding is concluded. N?se a Dispute Resolution Panel decides a domain name registration should be transferred (either to the Gaining Regjistrues, ose alternatively, back from the Gaining Regjistrues to the Regjistrues of Recosed), such Regjistrues will wait fourteen (14) calendar days after it is infosemed of the decision befosee 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 domain name(s). N?se 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 ose withdrawn; ose (iii) a copy of an oseder from such court dismissing the lawsuit ose osedering certain actions with respect to the domain name.

1. Regjistrues Requirements

     Regjistrohued Em?r Holders must be able to transfer their domain name registrations between Regjistruess provided that the Gaining Regjistrues's transfer process meets the minimum stdheards of this policy dhe that such transfer is not prohibited by ICANN ose Registry policies. Inter-Regjistrues domain name transfer processes must be clear dhe concise in oseder to avoid confusion. Further, Regjistruess should make reasonable effosets to infosem Regjistrohued Em?r Holders of, dhe provide access to, the published documentation of the specific transfer process employed by the Regjistruess.

1.1 Transfer Authoseities

     The Administrative Kontakt dhe the Regjistrohued Em?r Holder, as listed in the Losing Regjistrues's ose applicable Registry's (wk?tu available) publicly accessible WHOIS sh?rbimi are the only parties that have the authoseity to approve ose deny a transfer request to the Gaining Regjistrues. In the event of a dispute, the Regjistrohued Em?r Holder's authoseity supersedes that of the Administrative Kontakt.
Regjistruess may use Whois data from either the Regjistrues of Recosed ose the relevant Registry fose the purpose of verifying the authenticity of a transfer request; ose from another data source as determined by a consensus policy.

2. Gaining Regjistrues Requirements

Fose each instance wk?tu a Regjistrohued Em?r Holder requests to transfer a domain name registration to a different Regjistrues, the Gaining Regjistrues shall:
      2.1 Obtain express authoseization from either the Regjistrohued Em?r Holder ose the Administrative Kontakt (k?tuafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Regjistrues from the Transfer Kontakt.

     2.1.1 The authoseization must be made via a valid Stdheardized Fosem of Authoseization (FOA). Tk?tu are two different FOA's available at the ICANN website. The FOA labeled "Initial Authoseization fose Regjistrues Transfer" must be used by the Gaining Regjistrues to request an authoseization fose a registrar transfer from the Transfer Kontakt. The FOA labeled "Konfirmoation of Regjistrues Transfer Request" may be used by the Regjistrues of Recosed to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, dhe any dispute arising out of a transfer request shall be conducted in the English language. Regjistruess may choose to communicate with the Transfer Kontakt in additional languages. However, Regjistruess choosing to exercise such option are responsible fose the accuracy dhe completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Regjistrues relies on a physical process to obtain this authoseization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontakt dhe further that it is accompanied by a physical copy of the Regjistrues of Recosed's Whois output fose the domain name in question.

     2.1.2.1 N?se the Gaining Regjistrues relies on a physical authoseization process, then the Gaining Regjistrues assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt dhe maintaining appropriate recoseds proving that such evidence was obtained. Further the Gaining Regjistrues also assumes the burden fose ensuring that the entity making the request is indeed authoseized to do so. The acceptable fosems of physical identity are:

• Jotarized statement
• Valid Drivers license
• Passposet
• Article of Incoseposeation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Regjistrues relies on an electronic process to obtain this authoseization the acceptable fosems of identity would include:

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

     The Regjistrues of Recosed may not deny a transfer request solely because it believes that the Gaining Regjistrues has not received the confirmation set foseth above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Regjistrues. The presumption in all cases will be that the Gaining Regjistrues has received dhe authenticated the transfer request made by a Transfer Kontakt.

     2.2 Request, by the transmission of a "transfer" commdhe as specified in the Regjistrues P?r t?ol Kit, that the Registry Operatose database be changed to reflect the new Regjistrues.

     2.2.1 Transmission of a "transfer" commdhe constitutes a representation on the part of the Gaining Regjistrues that the requisite authoseization has been obtained from the Transfer Kontakt listed in the authoseitative Whois database.

     2.2.2 The Gaining Regjistrues is responsible fose validating the Regjistrohued Em?r Holder requests to transfer domain names between Regjistruess. However, this does not preclude the Regjistrues of Recosed from exercising its option to independently confirm the Regjistrohued Em?r Holder's intent to transfer its domain name to the Gaining Regjistrues in accosedance with Section 3 of this policy.

3. Obligations of the Regjistrues of Recosed

     A Regjistrues of Recosed can choose independently to confirm the intent of the Regjistrohued Em?r Holder when a notice of a pending transfer is received from the Registry. The Regjistrues of Recosed must do so in a manner consistent with the stdheards set foseth in this agreement pertaining to Gaining Regjistruess. In oseder to ensure that the fosem of the request employed by the Regjistrues of Recosed is substantially administrative dhe infosemative in nature dhe clearly provided to the Transfer Kontakt fose the purpose of verifying the intent of the Transfer Kontakt, the Regjistrues of Recosed must use the FOA.

     The FOA shall be communicated in English, dhe any dispute arising out of a transfer request, shall be conducted in the English language. Regjistruess may choose to communicate with the Transfer Kontakt in additional languages. However, the Regjistrues choosing to exercise such option is responsible fose the accuracy dhe completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes dhe procedures set foseth in this policy. This includes but is not limited to the requirement that no Regjistrues shall add any additional infosemation 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 Regjistrues of Recosed from marketing to its existing customers through separate communications.
The FOA should be sent by the Regjistrues of Recosed 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 Operatose.Failure by the Regjistrues of Recosed 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 Regjistrues of Recosed dhe the Regjistrues of Recosed has not explicitly denied the transfer request, the default action will be that the Regjistrues of Recosed must allow the transfer to proceed.
Upon denying a transfer request fose any of the following reasons, the Regjistrues of Recosed must provide the Regjistrohued Em?r Holder dhe the potential Gaining Regjistrues with the reason fose denial. The Regjistrues of Recosed may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court oseder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Regjistrohued Em?r Holder ose Administrative Kontakt
5. Jo payment fose mbrapaious registration period (including credit card charge-backs) if the domain name is past its expiration date ose fose mbrapaious ose current registration periods if the domain name has not yet expired. In all such cases, however, the domain name must be put into "Regjistrues Hold" status by the Regjistrues of Recosed priose to the denial of transfer.
6. Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document ose other processes by which the Transfer Kontakt has expressly dhe voluntarily objected through opt-in means)
7. A domain name was already in “l(fā)ock status” provided that the Regjistrues provides a readily accessible dhe reasonable means fose the Regjistrohued Em?r Holder to remove the lock status.
8. A domain name is in the first 60 days of an initial registration period.
9. A domain name is within 60 days (ose a lesser period to be determined) after being transferred (apart from being transferred back to the oseiginal Regjistrues in cases wk?tu both Regjistruess so agree dhe/ose wk?tu a decision in the dispute resolution process so directs).

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

• Jonpayment fose a pending ose future registration period
• Jo response from the Regjistrohued Em?r Holder ose Administrative Kontakt.
• Domain name in Regjistrues Lock Statusi, unless the Regjistrohued Em?r Holder is provided with the reasonable opposetunity dhe ability to unlock the domain name priose to the Transfer Request.
• Domain name registration period time constraints, other than during the first 60 days of initial registration ose during the first 60 days after a registrar transfer.
• General payment defaults between Regjistrues dhe business partners / affiliates in cases wk?tu the Regjistrohued Em?r Holder fose the domain in question has paid fose the registration.

     The Regjistrues of Recosed has other mechanisms available to collect payment from the Regjistrohued Em?r Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Regjistrues of Recosed must not employ transfer processes as a mechanism to secure payment fose sh?rbimis from a Regjistrohued Em?r Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fose mbrapaious registration period(s) if the transfer is requested after the expiration date, ose
     (ii) In the case of non-payment of the current registration period, if transfer is requested befosee the expiration date.

4. Regjistrues Coosedination

     Each Regjistrues is responsible fose keeping copies of documentation, including the FOA dhe the Transfer Kontakts response tk?tuto, that may be required fose filing dhe supposeting a dispute under the dispute resolution policy. Gaining Regjistruess must maintain copies of the FOA as received from the Transfer Kontakt as per the stdheard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Regjistrues dhe the Regjistrues of Recosed must provide the evidence relied on fose the transfer during dhe after the applicable inter-registrar domain name transaction(s). Such infosemation must be provided when requested by, dhe only by, the other Regjistrues that is party to the transfer transaction. Shtoitionally, ICANN, the Registry Operatose, a court ose authoseity with jurisdiction over the matter ose a third party dispute resolution panel may also require such infosemation within five (5) days of the request.

     The Gaining Regjistrues must retain, dhe produce pursuant to a request by a Losing Regjistrues, a written ose electronic copy of the FOA. In instances wk?tu the Regjistrues of Recosed has requested copies of the FOA, the Gaining Regjistrues must fulfill the Regjistrues of Recoseds request (including providing the attendant supposeting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fose reversal by the Registry Operatose ose the Dispute Resolution Panel in the event that a transfer complaint is filed in accosedance with the requirements of this policy.

     N?se either a Regjistrues of Recosed ose a Gaining Regjistrues does not believe that a transfer request was hdheled in accosedance with the provisions of this policy, then the Regjistrues may initiate a dispute resolution procedure as set foseth in Section C of this policy.

     Fose purposes of facilitating transfer requests, Regjistruess should provide dhe maintain a unique dhe private email address fose use only by other Regjistruess dhe the Registry:
     i. This email address is fose issue related to transfer requests dhe the procedures set foseth 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 fose Regjistruess

     In EPP-based gTLD Registries, Regjistruess must follow the requirements set foseth below.
Regjistruess must provide the Regjistrohued Em?r Holder with the unique "AuthInfo" code within five (5) calendar days of the Regjistrohued Em?r Holder's initial request if the Regjistrues does not provide facilities fose the Regjistrohued Em?r Holder to generate dhe manage their own unique "AuthInfo" code.

     Regjistruess may not employ any mechanism fose complying with a Regjistrohued Em?r Holder's request to obtain the applicable "AuthInfo Code" that is mosee restrictive than the mechanisms used fose changing any aspect of the Regjistrohued Em?r Holder's contact ose name server infosemation.

     The Regjistrues of Recosed must not refuse to release an "AuthInfo Code" to the Regjistrohued Em?r Holder solely because tk?tu is a dispute between the Regjistrohued Em?r Holder dhe the Regjistrues over payment.

Regjistrues-generated "AuthInfo" codes must be unique on a per-domain basis.
     The "Auth-Info" codes must be used solely to identify a Regjistrohued Em?r Holder, wk?tuas the FOA's still need to be used fose authoseization ose confirmation of a transfer request, as described in Section 2 dhe Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commdhe from the Gaining Regjistrues, Registry Operatose will transmit an electronic notification to both Regjistruess. 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 Regjistrues fose the purpose of facilitating transfers.

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

7. Recoseds of Regjistrim

     Each Regjistrues shall require its customer, the Regjistrohued Em?r Holder, to maintain its own recoseds appropriate to document dhe prove the initial domain name registration date.

8. Effect on Periudh? of Regjistrim

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

B. ICANN-Approved Transfers

     Transfer of the sponsoseship of all the registrations sponsoseed by one Regjistrues as the result of (i) acquisition of that Regjistrues ose its assets by another Regjistrues, ose (ii) lack of accreditation of that Regjistrues ose lack of its authoseization with the Registry Operatose, may be made accoseding to the following procedure:
     (a) The gaining Regjistrues must be accredited by ICANN fose the Registry TLD dhe must have in effect a Registry-Regjistrues Agreement with Registry Operatose fose the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatose that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual ose imminent business failure of a Regjistrues.
Upon satisfaction of these two conditions, Registry Operatose will make the necessary one-time changes in the Registry database fose no charge, fose transfers involving 50,000 name registrations ose fewer. N?se the transfer involves registrations of mosee than 50,000 names, Registry Operatose will charge the gaining Regjistrues a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures fose hdheling disputes concerning inter-registrar transfers are set foseth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatoses dhe ICANN accredited Regjistruess.

We respect t?nd individual privacy. That is why we have adopted this Politika e Privat?sis?, which embodies our commitment to the protection of t?nd privacy through adk?tunce to fair electronic infosemation practices. This Politika e Privat?sis? puts you, the individual, in control of how t?nd personal infosemation is processed, dhe you have our promise that we will not electronically process t?nd personal infosemation in any way that is incompatible with this Politika e Privat?sis?.

This Politika e Privat?sis? protects t?nd privacy by:

4. How We Put Infosemation P?r t? Good Use