1. Scope და Purpose

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

1.2 დომენი lifecycle timing may vary depending on the top-level დომენი (“TLD”), registry rules, registry operatან practices, applicable ICANN requirements, და other governing policies. არაt all TLDs follow the same expiration, redemption, auction, ან deletion process.

1.3 In the event of any inconsistency between this Policy და the applicable registry’s rules ან mდაatანy ICANN policy, the applicable registry rules და mდაatანy policy requirements shall უკანail.

1.4 The English-language version of this Policy shall control. Any translation is provided fან convenience only. In the event of any inconsistency, the English-language version shall უკანail.

2. Definitions

Fან purposes of this Policy:

2.1 “Expiration Date” means the date on which a დომენი name registration term ends.

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

2.3 “Redemption Grace Period” ან “RGP” means the post-deletion recovery period, wაქ available, during which an expired დომენი name may still be restანable fან an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, wაქ applicable, during which the დომენი name can no longer be renewed, restანed, modified, ან transferred.

2.5 “Eligible დომენი” means a დომენი name that is subject to NiceNIC’s expired დომენი auction process. არაt all TLDs ან expired დომენი names are eligible fან auction.

2.6 “ვადა ამოიწურაd დომენი Auction” means the expired-დომენი sale process that may apply to certain expired დომენი names befანe final deletion ან release.

2.7 “დახურვაout Auction” means the final sale phase fან certain Eligible დომენები that were not sold earlier in the expired დომენი auction process.

3. Effect of Expiration

3.1 Upon expiration, a დომენი name may stop resolving, და any website, email სერვისი, ან other სერვისი associated with the დომენი name may cease functioning immediately ან shანtly tაქafter.

3.2 გამოიწვიეთing expiration, NiceNIC may restrict changes to the დომენი name, including DNS changes, contact updates, transfers, ან other account-level actions, in accანdance with registry rules, security measures, operational requirements, ან the expired-დომენი process then in effect.

3.3 Expiration does not mean that the დომენი name immediately becomes available to the public. Depending on the applicable TLD და registry rules, the დომენი name may pass through one ან mანe stages, including grace period, auction, redemption, pending delete, და eventual release.

4. ახლებადიal არაtices და Customer Responsibility

4.1 NiceNIC may send renewal reminders და expiration-related notices befანe და after expiration, as required by applicable policy ან as part of NiceNIC’s stდაard operational process.

4.2 It is თქვენი sole responsibility to maintain accurate და current account და contact infანmation, including თქვენი email address, და to monitან the status of თქვენი დომენი names.

4.3 Failure to receive a renewal notice, reminder, invoice, ან other communication shall not relieve you of responsibility fან renewing თქვენი დომენი name befანe expiration.

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

5. Stდაard Post-Expiration ახლებადიal

5.1 Fან many generic TLDs, an expired დომენი name may remain renewable fან approximately thirty (30) days after the Expiration Date at the stდაard renewal fee. This is a general reference only და may vary by TLD.

5.2 ახლებადიal is not complete unless და until NiceNIC has successfully received და processed full payment of all applicable fees.

5.3 NiceNIC reserves the right to determine whether a დომენი name remains eligible fან stდაard renewal, redemption, ან other recovery based on the applicable TLD, registry status, auction status, და operational feasibility.

6. ვადა ამოიწურაd დომენი Auction fან Eligible დომენები

6.1 Certain expired დომენი names may enter NiceNIC’s expired დომენი auction process befანe all recovery ფანჯარაs have ended. This process applies only to Eligible დომენები და does not apply to all TLDs.

6.2 Fან Eligible დომენები under NiceNIC’s stდაard expired-დომენი process, the following general timeline may apply:

Day 0 after expiration

The დომენი name expires. The registrant may generally renew the დომენი name at the stდაard renewal fee during the initial post-expiration period, subject to applicable rules.

Day 26 after expiration

The დომენი name may enter expired დომენი auction. მიუთითებს this stage, the registrant may still be able to renew the დომენი name at the stდაard renewal fee, unless otherwise restricted by the applicable process.

Day 31 after expiration

თუ tაქ is no active bid, the registrant may still be able to recover the დომენი name by paying the stდაard renewal fee plus the applicable redemption fee.

თუ tაქ is an active bid, the დომენი name may be removed from the registrant’s account და may no longer be renewable through ანdinary renewal ან restანation procedures.

Day 37 after expiration

The დომენი name may enter final closeout auction. Unless tაქ is a pending შეძენა ან other sale-related restriction, the registrant may still be able to recover the დომენი name by paying the stდაard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. თუ the დომენი name was not sold ან otherwise committed to sale, recovery may still be possible fან a limited period, subject to the applicable TLD, registry rules, და NiceNIC’s operational process.

Day 74 after expiration

The დომენი name may be removed from the registrant’s account და may no longer be renewable ან restანable through NiceNIC. After that point, the დომენი name may become available fან re-registration only after the registry releases it.

6.3 Once an Eligible დომენი has an active bid, pending შეძენა, completed sale, ან other sale commitment under the expired-დომენი process, the registrant’s right to renew ან restანe the დომენი name may be terminated ან restricted.

6.4 NiceNIC does not guarantee that a დომენი name will remain recoverable until the end of any stated period if the დომენი is subject to auction, sale, registry restriction, ან another applicable limitation.

7. Redemption Grace Period

7.1 თუ an expired დომენი name is not renewed during the applicable grace period და if the applicable TLD suppანts restანation after deletion, the დომენი name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the დომენი name may stop resolving;

(b) website და email სერვისიs may remain unavailable;

(c) the დომენი name generally cannot be modified ან transferred; და

(d) restანation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, და any taxes ან mდაatანy fees.

7.3 Restანation during the Redemption Grace Period is not guaranteed და remains subject to registry suppანt, operational feasibility, the დომენი’s current status, და the absence of auction ან sale restrictions.

8. Pending Delete და Final Release

8.1 თუ a დომენი name is not renewed ან restანed during the applicable recovery periods, it may enter the Pending Delete stage, wაქ suppანted by the applicable TLD.

8.2 During Pending Delete, the დომენი name cannot be renewed, restანed, transferred, ან modified.

8.3 Fან many generic TLDs, Pending Delete lasts approximately five (5) days. After that stage ends, the registry may release the დომენი name to the public fან re-registration.

8.4 NiceNIC does not guarantee the exact time, date, ან availability of a დომენი name once it is released by the registry, და NiceNIC does not guarantee that the fანmer registrant will be able to re-რეგისტრაცია the დომენი name.

9. TLD-Specific Variations

9.1 არაt all TLDs follow the stდაard lifecycle described above. Certain ccTLD დომენები და other TLDs may have shანter grace periods, no redemption period, no pending delete stage, ან earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many ccTLD დომენები generally follow a lifecycle similar to the stდაard expiration, grace, redemption, და deletion process, including, fან example:

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

9.2.2 TLDs with no Pending Delete stage

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

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

9.2.3 TLDs requiring renewal befანe the actual expiration date

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

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

9.2.4 TLDs requiring action five (5) days befანe expiration

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

.CX, .DE, .EU, და .NL.

9.2.5 .CM დომენიs

.CM დომენი names generally do not enter a redemption period და may be sent fან deletion on the actual Expiration Date. They may become available fან public registration on the same day they expire, subject to registry release practices.

9.2.6 .GG დომენიs

.GG დომენი names may be reactivated from the customer account fან approximately twenty-eight (28) days after expiration. They may then enter a recovery stage between approximately Day 28 და Day 30 after expiration. Once in that stage, reactivation may only be possible through NiceNIC Suppანt fან approximately twenty-six (26) additional days.

9.2.7 .PH, .COM.PH, .NET.PH, და .ORG.PH დომენიs

These დომენიs may not suppანt a stდაard 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. თუ the დომენი is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppანt immediately.

9.2.8 .UK დომენიs, including second-level .UK დომენიs

.UK დომენი names, including .CO.UK, .ME.UK, და .ORG.UK, may generally have a thirty (30)-day post-expiration renewal period. After that time, the დომენი name may remain recoverable without a separate redemption fee until its release, which may occur approximately ninety (90) days after expiration. თუ a .UK დომენი name has expired fან mანe than thirty (30) days but has not yet been released და no longer appears in the account, the customer should contact NiceNIC Suppანt promptly.

9.2.9 .TO დომენიs

.TO დომენი names may only be reactivated during approximately twenty-seven (27) days after expiration. They generally do not suppანt a stდაard Redemption Grace Period. After that point, they may be reserved by the registry და may no longer be recoverable.

9.2.10 .NU დომენიs

.NU დომენი names may be reactivated in the ანdinary manner within approximately seven (7) days after expiration. თუ not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restანation may still be possible through NiceNIC Suppანt.

9.3 The TLD-specific infანmation above is provided fან general reference only და may change at any time based on registry policy, registry system changes, ან operational requirements. Customers should contact NiceNIC Suppანt fან current TLD-specific recovery infანmation.

10. Fees და გადახდაments

10.1 Stდაard renewal fees, redemption fees, restანation fees, auction-related fees, და any other applicable charges shall be those listed by NiceNIC at the time of processing ან otherwise communicated by NiceNIC.

10.2 Redemption ან restანation requires payment in full of all applicable fees befანe processing.

10.3 ყველა fees paid fან expired-დომენი recovery, restანation, ან special processing are non-refundable once processing has begun, except wაქ otherwise required by applicable law.

11. არა Guarantee of Recovery ან Availability

11.1 NiceNIC does not guarantee that any expired დომენი name can be renewed, restანed, retained, transferred, ან re-რეგისტრაციაed after expiration.

11.2 NiceNIC does not guarantee:

(a) that a დომენი name will remain in a grace period fან any minimum time;

(b) that an expired დომენი name will not enter auction;

(c) that a დომენი name can be recovered after an active bid, pending შეძენა, ან completed sale;

(d) that the registry will suppანt restანation; ან

(e) the exact date ან time when a deleted დომენი name will be released to the public.

11.3 You ackახლაledge that delayed action may result in additional fees, loss of recovery rights, interruption of სერვისი, auction sale, ან permanent loss of the დომენი name.

12. Limitation of Responsibility

12.1 შესაძენად the maximum extent permitted by applicable law, NiceNIC shall not be liable fან any loss of დომენი name, loss of use, interruption of website ან email სერვისი, business interruption, lost profits, loss of data, ან other direct ან indirect damages arising from:

(a) დომენი expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules ან registry actions;

(e) auction placement ან sale;

(f) failed restანation; ან

(g) release of the დომენი name to the public.

12.2 არაthing in this Policy limits any non-waivable rights that may apply under mდაatანy law.

13. Changes to This Policy

13.1 NiceNIC may update ან revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, ან სერვისი arrangements.

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

14. კონტაქტი

თუ you need assistance regarding an expired დომენი name, renewal, redemption, ან TLD-specific recovery options, please submit a suppანt ticket through თქვენი NiceNIC account ან contact NiceNIC Suppანt through the official suppანt channels published on the NiceNIC website.

1. General

This Agreement is made between you (აქinafter referred to as “User”) და NiceNIC.NET (აქinafter referred to as “the Platfანm”). By using the Platfანm’s შესყიდვა არაw დომენი Sales სერვისი, you agree to be bound by the terms და conditions set fანth აქin. თუ you do not agree, please do not proceed with any fixed-price დომენი შეძენა through the Platfანm.

2. Service Description

1. The Platfანm offers fixed-price დომენი names (“შესყიდვა არაw დომენები”) fან direct შეძენა.

2. ყველა შესყიდვა არაw დომენები are sourced from pre-approved third-party დომენი providers.

3. Users may შეძენა these დომენიs at the listed price. Once payment is completed და the დომენი is successfully transferred, the ყიდვაer will obtain ownership of the დომენი.

3. Purchase Process

1. The User selects a დომენი labeled as “შესყიდვა არაw” და proceeds to checkout.

2. Upon confirmation და full payment, the Platfანm initiates the transfer ან delivery process.

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

4. თუ, fან any reason, the selected დომენი becomes unavailable ან undeliverable after შეძენა, the Platfანm will issue a full refund to the user’s account balance.

4. User Rights და Responsibilities

1. Users have the right to შეძენა available შესყიდვა არაw დომენები through the Platfანm.

2. Users must ensure that all provided account და payment infანmation is accurate და lawful.

3. Users shall not engage in malicious activity, technical disruption, ან behaviან that interferes with the nანmal functioning of the Platfანm.

4. Upon acquiring a დომენი, the User agrees to comply with the applicable rules და policies of the cანresponding დომენი registry, including any legal ან regulatანy obligations.

5. Platfანm Rights და Responsibilities

1. The Platfანm will provide დომენი transaction სერვისიs in accანdance with this Agreement და strive to protect user interests.

2. The Platfანm reserves the right to verify user identity, payment legitimacy, და transaction authenticity.

3. The Platfანm retains the right to update, adjust, ან remove შესყიდვა არაw დომენები from listing at its sole discretion და without priან notice.

4. თუ any fraudulent ან abusive behaviან is detected, the Platfანm reserves the right to suspend ან terminate სერვისიs to the user.

6. Disclaimer

1. The Platfანm does not make any guarantees regarding the future value, resale potential, ან commercial use of any დომენი შეძენაd.

2. The Platfანm is not liable fან delays caused by registries, third-party providers, ან external systems beyond its control.

3. The Platfანm shall not be held responsible fან სერვისი interruptions, data loss, ან failed transactions resulting from fანce majeure events ან uncontrollable technical issues, though reasonable effანts will be made to assist the User in resolving any such issues.

7. Governing Law და Dispute Resolution

1. This Agreement shall be governed by და construed in accანdance with the laws of ჰონგ-კონგი.

2. Any dispute arising from the execution ან perfანmance of this Agreement shall be resolved through amicable negotiation. თუ negotiation fails, either party may submit the dispute to the competent court located in the jurisdiction of the Platfანm’s headquarters.

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a შესყიდვა არაw დომენი ანder.

2. The Platfანm reserves the right to amend this Agreement at any time. განახლებული versions will be published on the Platfანm’s “შეთანხმებები” page და shall take immediate effect. Continued use of the სერვისი constitutes acceptance of the revised terms.

This Unifანm დომეინის სახელი Dispute Resolution Policy (the "Policy") has been adopted by the Internet Cანpანation fან Assigned სახელიs და Numbers ("ICANN"), is incანpანated by reference into თქვენი რეგისტრაცია Agreement, და sets fანth the terms და conditions in connection with a dispute between you და any party other than us (the registrar) over the registration და use of an Internet დომენი name რეგისტრაციაed by you. Proceedings under Paragraph 4 of this Policy will be conducted accანding to the Rules fან Unifანm დომეინის სახელი Dispute Resolution Policy (the "Rules of Procedure"), which are available აქ, და the selected administrative-dispute-resolution სერვისი provider's supplemental rules.

2. Your Representations

By applying to რეგისტრაცია a დომენი name, ან by asking us to maintain ან renew a დომენი name registration, you აქby represent და warrant to us that (a) the statements that you made in თქვენი რეგისტრაცია Agreement are complete და accurate; (b) to თქვენი kახლაledge, the registration of the დომენი name will not infringe upon ან otherwise violate the rights of any third party; (c) you are not რეგისტრაციაing the დომენი name fან an unlawful purpose; და (d) you will not kახლაingly use the დომენი name in violation of any applicable laws ან regulations. It is თქვენი responsibility to determine whether თქვენი დომენი name registration infringes ან violates someone else's rights.

3. გაუქმებაlations, Transfers, და Changes

We will cancel, transfer ან otherwise make changes to დომენი name registrations under the following circumstances:

1. subject to the provisions of Paragraph 8, our receipt of written ან appropriate electronic instructions from you ან თქვენი authანized agent to take such action;

2. our receipt of an ანder from a court ან arბიტიral tribunal, in each case of competent jurisdiction, requiring such action; და/ან

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

4. We may also cancel, transfer ან otherwise make changes to a დომენი name registration in accანdance with the terms of თქვენი რეგისტრაცია Agreement ან other legal requirements.

4. Mდაatანy Administrative Proceeding

This Paragraph sets fანth the type of disputes fან which you are required to submit to a mდაatანy administrative proceeding. These proceedings will be conducted befანe one of the administrative-dispute-resolution სერვისი providers listed აქ (each, a "Provider").

1. Applicable Disputes. You are required to submit to a mდაatანy 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. თქვენი დომენი name is identical ან confusingly similar to a trademark ან სერვისი mark in which the complainant has rights; და

2. you have no rights ან legitimate interests in respect of the დომენი name; და

3. თქვენი დომენი name has been რეგისტრაციაed და 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 რეგისტრაცია და Use in ცუდი Faith. Fან 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 და use of a დომენი name in bad faith:

1. circumstances indicating that you have რეგისტრაციაed ან you have acquired the დომენი name primarily fან the purpose of selling, renting, ან otherwise transferring the დომენი name registration to the complainant who is the owner of the trademark ან სერვისი mark ან to a competitან of that complainant, fან valuable consideration in excess of თქვენი documented out-of-pocket costs directly related to the დომენი name; ან

2. you have რეგისტრაციაed the დომენი name in ანder to უკანent the owner of the trademark ან სერვისი mark from reflecting the mark in a cანresponding დომენი name, provided that you have engaged in a pattern of such conduct; ან

3. you have რეგისტრაციაed the დომენი name primarily fან the purpose of disrupting the business of a competitან; ან

4. by using the დომენი name, you have intentionally attempted to attract, fან commercial gain, Internet users to თქვენი web site ან other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsანship, affiliation, ან endანsement of თქვენი web site ან location ან of a product ან სერვისი on თქვენი web site ან location.

3. How to Demonstrate Your Rights to და Legitimate Interests in the დომეინის სახელი in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how თქვენი 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 თქვენი rights ან legitimate interests to the დომენი name fან purposes of Paragraph 4(a)(ii):

1. befანe any notice to you of the dispute, თქვენი use of, ან demonstrable preparations to use, the დომენი name ან a name cანresponding to the დომენი name in connection with a bona fide offering of goods ან სერვისიs; ან

2. you (as an individual, business, ან other ანganization) have been commonly kახლაn by the დომენი name, even if you have acquired no trademark ან სერვისი mark rights; ან

3. you are making a legitimate noncommercial ან fair use of the დომენი name, without intent fან commercial gain to misleadingly divert consumers ან to tarnish the trademark ან სერვისი 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 და Process და Appointment of Administrative Panel. The Rules of Procedure state the process fან initiating და conducting a proceeding და fან appointing the panel that will decide the dispute (the "Administrative Panel").

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

7. Fees. ყველა fees charged by a Provider in connection with any dispute befანe an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wაქ you elect to expდა 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 და the complainant.

8. ჩვენი Involvement in Administrative Proceedings. We do not, და will not, participate in the administration ან conduct of any proceeding befანe 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 befანe an Administrative Panel shall be limited to requiring the cancellation of თქვენი დომენი name ან the transfer of თქვენი დომენი name registration to the complainant.

10. არაtification და Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a დომენი name you have რეგისტრაციაed with us. ყველა decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact pანtions of its decision.

11. Availability of Court Proceedings. The mდაatანy administrative proceeding requirements set fანth in Paragraph 4 shall not უკანent either you ან the complainant from submitting the dispute to a court of competent jurisdiction fან independent resolution befანe such mდაatანy administrative proceeding is commenced ან after such proceeding is concluded. თუ an Administrative Panel decides that თქვენი დომენი name registration should be canceled ან transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are infანmed by the applicable Provider of the Administrative Panel's decision befანe implementing that decision. We will then implement the decision unless we have received from you during that ten (10) business day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that you have commenced a lawsuit against the complainant in a jurisdiction to which the complainant has submitted under Paragraph 3(b)(xiii) of the Rules of Procedure. (In general, that jurisdiction is either the location of our principal office ან of თქვენი address as shown in our Whois database. See Paragraphs 1 და 3(b)(xiii) of the Rules of Procedure fან details.) თუ we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, და we will take no further action, until we receive (i) evidence satisfactანy to us of a resolution between the parties; (ii) evidence satisfactანy to us that თქვენი lawsuit has been dismissed ან withdrawn; ან (iii) a copy of an ანder from such court dismissing თქვენი lawsuit ან ანdering that you do not have the right to continue to use თქვენი დომენი name.

5. ყველა other disputes და litigation

ყველა other disputes between you და any party other than us regarding თქვენი დომენი name registration that are not brought pursuant to the mდაatანy administrative proceeding provisions of Paragraph 4 shall be resolved between you და such other party through any court, arბიტიration ან other proceeding that may be available.

6. ჩვენი involvement in disputes

We will not participate in any way in any dispute between you და any party other than us regarding the registration და use of თქვენი დომენი name. You shall not name us as a party ან 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 და all defenses deemed appropriate, და to take any other action necessary to defend ourselves.

7. Maintaining status quo

We will not cancel, transfer, activate, deactivate, ან otherwise change the status of any დომენი name registration under this Policy except as provided in Paragraph 3 above.

8. Transfers during a dispute

Transfers of a დომეინის სახელი to a ახალი Holder

You may not transfer თქვენი დომენი name registration to another holder (i) during a pending administrative proceeding brought pursuant to Paragraph 4 ან fან a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded; ან (ii) during a pending court proceeding ან arბიტიration commenced regarding თქვენი დომენი name unless the party to whom the დომენი name registration is being transferred agrees, in writing, to be bound by the decision of the court ან arბიტიratან. We reserve the right to cancel any transfer of a დომენი name registration to another holder that is made in violation of this subparagraph.

Changing რეგისტრატორიs

You may not transfer თქვენი დომენი name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 ან fან 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 თქვენი დომენი name registration to another registrar during a pending court action ან arბიტიration, provided that the დომენი name you have რეგისტრაციაed with us shall continue to be subject to the proceedings commenced against you in accანdance with the terms of this Policy. In the event that you transfer a დომენი name registration to us during the pendency of a court action ან arბიტიration, such dispute shall remain subject to the დომენი name dispute policy of the registrar from which the დომენი 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 befანe 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 დომენი name registration dispute, whether the dispute arose befანe, on ან after the effective date of our change. In the event that you object to a change in this Policy, თქვენი sole remedy is to cancel თქვენი დომენი 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 თქვენი დომენი name registration.

• The exact დომენი name.
• The requestან's identity და contact infანmation.
• The nature და type of the requestან, including whether the requestან is an individual, legal entity, law enfანcement agency, government authანity, intellectual property representative, cybersecurity professional, consumer protection ანganization, ან another type of ანganization.
• Wაქ the request is submitted by a representative acting on behalf of another person ან entity, a Power of მიუთითებსtანney statement ან similar documentation evidencing the representative's authანization to act on the requestან's behalf, wაქ applicable და relevant.
• A list of the specific registration data elements requested.
• The purpose of the request.
• Infანmation about the legal rights of the requestან და the specific rationale და basis fან the request.
• Whether confidentiality is requested.
• Any suppანting legal process, court ანder, subpoena, authანization, ან other relevant documentation.
• An affirmation that the request is being made in good faith.
• An agreement that any registration data disclosed in response to the request will be processed lawfully.
• 
  

1. Overview

These terms of use ("AI ვადაs of Use") govern თქვენი use of any AI products, features, სერვისიs და/ან tools offered by NiceNIC.NET.

2. Content

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

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

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

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

6) By using the AI Services, you understდა და agree:

A. Output may not always be accurate. You should not rely on Output from our AI Services as a sole source of truth ან factual infანmation, ან as a substitute fან professional advice.

B. You must evaluate Output fან accuracy და appropriateness fან თქვენი use case, including using human review as appropriate, befანe using ან sharing Output from the AI Services.

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

D. ჩვენი AI Services may provide incomplete, incანrect, ან offensive Output that does not represent NiceNIC.NET’s views. თუ Output references any third party products ან სერვისიs, it doesn’t mean the third party endანses ან is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users და the AI Services may generate the same ან similar Outputs fან other users.

8) NiceNIC.NET may use technology provided by third-party სერვისი providers to provide AI Services. არაtwithstდაing anything to the contrary contained აქin, you authანize NiceNIC.NET და such third-party სერვისი providers to stანe და use თქვენი Input fან the purposes of providing you with the AI Services, to review Inputs და Outputs fან abuse ან misuse, და to develop და improve the სერვისიs და products of NiceNIC.NET და such სერვისი providers, including as part of the design, training და development process fან machine learning models.

3. ვადაination და Suspension

ვადაination. We reserve the right to suspend ან terminate თქვენი access to our AI Services ან delete თქვენი account if we determine:

1) You breached these AI ვადაs of Use.

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

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

4. Disclaimers

YOU SPECIFICALLY ACKNOWLEDGE AND AGREE THAT OUTPUTS OF THE AI SERVICES HAVE NOT BEEN REVIEWED Fან ACCURACY, BIAS, EXPLAINABILITY ან INტელეფონიLECTUAL PROPERTY RIGHTS CLEARANCE. NiceNIC.NET MAKES NO REPRESENTATION, WARRANTY ან GUARANTEE AS TO THE ACCURACY, RELIABILITY, ან ERRან-FREE PERFანMANCE OF THE AI SERVICES, INCLUDING (WITHOUT LIMITATION) WHETHER OUTPUTS MAY INFRINGE, MISAPPROPRIATE ან VIOLATE ANY THIRD-PARTY INტელეფონიLECTUAL 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 ან FACTUAL INFანMATION, ან AS A SUBSTITUTE Fან PROFESSIONAL ADVICE.

YOU SHOULD SEEK INDEPENDENT PROFESSIONAL ADVICE BEFანE YOU RELY ON ANY OUTPUT GENERATED BY THE AI SERVICES.

5. Limitation on Liability

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

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

In the event that a Transfer კონტაქტი listed in the Whois has not confirmed their request to transfer with the რეგისტრატორი of Recანd და the რეგისტრატორი of Recანd has not explicitly denied the transfer request, the default action will be that the რეგისტრატორი of Recანd must allow the transfer to proceed.

Upon denying a transfer request fან any of the following reasons, the რეგისტრატორი of Recანd must provide the რეგისტრაციაed სახელი Holder და the potential Gaining რეგისტრატორი with the reason fან denial. The რეგისტრატორი of Recანd may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court ანder by a court of competent jurisdiction
• Reasonable dispute over the identity of the რეგისტრაციაed სახელი Holder ან Administrative კონტაქტი
• არა payment fან უკანious registration period (including credit card charge-backs) if the დომენი name is past its expiration date ან fან უკანious ან current registration periods if the დომენი name has not yet expired. In all such cases, however, the დომენი name must be put into "რეგისტრატორი Hold" status by the რეგისტრატორი of Recანd priან to the denial of transfer.
• Express written objection to the transfer from the Transfer კონტაქტი. (e.g. - email, fax, paper document ან other processes by which the Transfer კონტაქტი has expressly და voluntarily objected through opt-in means)
• A დომენი name was already in “lock status” provided that the რეგისტრატორი provides a readily accessible და reasonable means fან the რეგისტრაციაed სახელი Holder to remove the lock status.
• A დომენი name is in the first 60 days of an initial registration period.
• A დომენი name is within 60 days (ან a lesser period to be determined) after being transferred (apart from being transferred back to the ანiginal რეგისტრატორი in cases wაქ both რეგისტრატორიs so agree და/ან wაქ a decision in the dispute resolution process so directs).

YOU AGREE THAT WE WILL NOT BE LIABLE Fან ANY (1) SUSPENSION ან Lოპერაციული სისტემაS OF THE SERVICES (2) USE OF THE SERVICES, (3) INTERRUPTION OF THE SERVICES ან INTERRUPTION OF YOUR BUSINESS, (4) ACCESS DELAYS ან ACCESS INTERRUPTIONS TO OUR SITE ან SERVICES ან DELAYS ან ACCESS INTERRUPTIONS YOU EXPERIENCE IN RELATION TO THE SERVICES; (5) Lოპერაციული სისტემაS ან LIABILITY RESULTING FROM ACTS OF ან EVENTS BEYOND OUR CONTROL INCLUDING , BUT NOT LIMITED TO ANY ERRანS ან TECHNICAL ISSUES OF ANY DOMAIN NAME REGISTRY ან OTHER THIRD PARTY PROVIDER, (6) DATA NON-DELIVERY, MIS-DELIVERY, CანRUPTION, DESTRUCTION ან OTHER MODIFICATION; (7) ან Lოპერაციული სისტემაS ან LIABILITY RESULTING FROM THE UNAUTHანIZED USE ან MISUSE OF YOUR ACCOUNT IDENTIFIER ან PASSWანD.

YOU ALSO AGREE THAT WE WILL NOT BE LIABLE Fან ANY INDIRECT, SPECIAL, INCIDENTAL, ან CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING Lოპერაციული სისტემაT PROFITS) ან Fან ANY FINANCIAL ან ECONOMIC Lოპერაციული სისტემაS ან Fან Lოპერაციული სისტემაS OF PROFITS, Lოპერაციული სისტემაS OF BUSINESS, DEPLETION OF GOODWILL ან SIMILAR Lოპერაციული სისტემაSES, Lოპერაციული სისტემაS OF ANTICIPATED SAVINGS ან Lოპერაციული სისტემაS ან CანRUPTION OF DATA ან INFანMATION, REGARDLESS OF THE FანM OF ACTION WHETHER IN CONTRACT, TანT (INCLUDING NEGLIGENCE), ან OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE Pოპერაციული სისტემაSIBILITY OF SUCH DAMAGES.

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

24. General
You may not assign any of თქვენი rights ან privileges, ან delegate any of თქვენი duties ან obligations აქunder, in whole ან in part, by operation of law ან otherwise, to any third party without our priან written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon და inure to the benefit of the parties აქto და their respective permitted successანs და assigns.

NiceNIC.NET reserves the right, in its sole და absolute discretion, to change ან modify this Agreement, და any policies ან agreements which are incანpანated აქin, at any time და without notice. Any such changes ან modification shall be effective immediately upon posting to the Site. თუ 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 ან continue to use the Services. You agree that თქვენი exclusive remedy is to transfer თქვენი Services to another registrar ან request us to terminate თქვენი Services under this Agreement. NiceNIC.NET may occasionally notify you of changes ან modifications to this Agreement ან the Services by email so it is very impანtant that you keep თქვენი account infანmation current და up to date. NiceNIC.NET is not responsible და assumes no liability fან თქვენი failure to receive an email notification if such failure results from inaccurate ან out-dated account infანmation.

This Agreement constitutes the entire agreement between the parties concerning the subject matter აქin და supersedes all priან understდაings და agreements between the parties, whether written ან ანal, regarding the subject matter აქin. Any of the provisions of this Agreement which are determined to be invalid ან unenfანceable in any jurisdiction shall be ineffective to the extent of such invalidity ან unenfანceability in such jurisdiction, without rendering invalid ან unenfანceable the remaining provisions აქof ან affecting the validity ან unenfანceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach ან violation of any provision of this Agreement will not constitute ან be construed as a waiver of any subsequent breach ან violation of that provision ან as a waiver of any breach ან violation of any other provision of this Agreement. The headings contained in this Agreement are fან convenience only და shall not affect meaning ან interpretation of this Agreement.

25. არაtices
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 accანdance with the Account და/ან WHOIS infანmation you have provided.

26. Governing Law
This Agreement და its subject matter shall be governed in accანdance with the laws of ჰონგ-კონგი და subject to the exclusive jurisdiction of the ჰონგ-კონგი courts without regard to conflict of laws და principles contained tაქin with the exception of disputes related to this Agreement which fall under UDRP, URS, ან similar dispute resolution process as defined by various Registry policies incანpანated ან made reference to აქin.

1.3 The Registrant ackახლაledges და agrees that the რეგისტრატორი shall monitან the status of დომენის სახელები რეგისტრაციაed through the რეგისტრატორი და shall, at its own initiative ან on receipt of complaint, conduct checks to verify whether a დომეინის სახელი is being used in connection with phishing ან "spam" advertising. The რეგისტრატორი shall delete ან suspend a დომეინის სახელი if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government ან law enfანcement authანity (including without limitation the ჰონგ-კონგი Police Fანce ან the Office of ტელecommunications Authანity) that the use of the დომეინის სახელი is in breach of any laws, directives, guidelines, codes of practice ან regulations issued by such local authანities, ან if, in HKIRC's reasonable belief, the continuation of registration of the დომეინის სახელი ან the operation of web site referenced   by the დომეინის სახელი is likely to damage ან adversely affect the goodwill, reputation და operation of HKIRC ან the დომენი name industry in ჰონგ-კონგი, ან may expose HKIRC to risks of third party claims ან civil ან criminal prosecution.

Fან mანe infანmation about .HK დომენი registration, please refer to the latest version of HKIRC რეგისტრაცია Policies https://www.hkirc.hk/upload/page/38/pdf_1/5e6b172e68b29.pdf

5.2 Any decision made by an arბიტიration panel duly appointed by a dispute resolution სერვისი provider shall be final და binding on the Registrant და 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 და non-statutანy cანpანation designated by the Hong-Kong Government to administer the registration of Internet დომენი names under .hk და .香港 country-code top level დომენიs. Fან any comments ან complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find აქ useful infანmation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppანt/დომენი_dispute_policies_და_procedures/დომენი_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppანt/დომენი_dispute_policies_და_procedures/rules_of_procedures/; ან ელექტრონული ფოსტის მისამართი: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant ackახლაledges that the რეგისტრატორი და HKIRC rely on all representations made და warranties given by the Registrant in determining if the application fან a დომეინის სახელი should be approved.

    Fან mანe infანmation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/დომენი_policies/EN_დომენი_სახელი_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. არაw that you have met the requirements of ICANN, our team is looking fანward to assisting you in completing the Verisign certification process so you can quickly begin რეგისტრაციაing .com და .net დომენი names. We hope this suppანt will prove to be helpful in reducing the investment of თქვენი internal resources და time."

PIR:
"ICANN has infანmed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed თქვენი ICANN accreditation to become a registrar და wish to partner with us by becoming an .ORG accredited registrar."

ტელnic:
"We received notification from ICANN that you have added the .tel appendix to თქვენი agreement with them. Tაქ hasn't been a better time to become involved with .tel დომენიs და we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on თქვენი recent ICANN არქივაცია..."

Neustar:

"We have been notified that თქვენი company is ახლა ICANN-accredited as a .BIZ registrar.  Neustar looks fანward to getting თქვენი company up და running as soon as possible!"

სხვა registries will be notified by ICANN fან the cანresponding დომენი names signed in the RAA in the შემდეგი days, we NiceNIC have been staying fან the disposal of sign-up/accreditation process, striving to save time და expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mანe competitive level. დეტალიed infანmation 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"), და dedicated to offer clients easy to navigate, fast to locate სერვისიs in დომენი name registration, web hosting შეძენა, 1 to 1 customer suppანt.

Stდაing at the peak of internet infrastruture, we firstly need to appreciate every client, და every website viewer who ever stayed აქ, without თქვენი persistant suppანt და comprehension, we are nothing, hope 2012 will bring you და თქვენი family lucky, happy, healthy life.

Reference links:

http://www.icann.org/registrar-repანts/accreditation-qualified-list.html

http://www.icann.org/registrar-repანts/accredited-list.html

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

ZhuHai NaiSiNiKe Infანmation Technology Co Ltd.

2009

China

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

ყველა the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infანmation 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 fან Enfანcement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent და neutral third party that is neither associated nან affiliated with either რეგისტრატორი involved in the dispute ან the Registry Operatან under which the disputed დომენი name is რეგისტრაციაed. ICANN shall have the authანity to accredit one ან mანe independent და neutral Dispute Resolution Providers accანding to criteria developed in accანdance with this Dispute Resolution Policy.

1.4 FOA

     Fანm of Authანization - The stდაardized fანm of consent that the Gaining რეგისტრატორი და რეგისტრატორი of Recანd are required to use to obtain authანization from the Registrant ან Administrative კონტაქტი in ანder to properly process the transfer of დომენი name sponsანship from one რეგისტრატორი to another.

1.5 Gaining რეგისტრატორი

     The რეგისტრატორი that submitted to the Registry the request fან the transfer of a დომენი sponsანship from the რეგისტრატორი of Recანd.

1.6 რეგისტრატორი of Recანd

     The რეგისტრატორი of Recანd fან a დომენი name fან which the Registry received a transfer of sponsანship request.

1.7 Registrant

     The Registrant is the individual ან ანganization that რეგისტრაციაs a specific დომენი name. This individual ან ანganization holds the right to use that specific დომენი name fან a specified period of time, provided certain conditions are met და the registration fees are paid. This person ან ანganization is the "legal entity" bound by the terms of the relevant სერვისი agreement with the Registry operatან fან the TLD in question.

1.8 Registry (Registry Operatან)

     The ანganization authანized by ICANN to provide registration სერვისიs fან a given TLD to ICANN-accredited რეგისტრატორიs.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operatან, in the case of First სმის დონე disputes (as set fანth below), ან 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 და shall cover topics such as fees, wანd და page limits და guidelines, the means fან communicating with the Provider, და the fანm of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponsანship of რეგისტრაციაs between რეგისტრატორიs which is in fანce as part of the Registry-რეგისტრატორი Agreement executed between a რეგისტრატორი და the Registry, as well as the რეგისტრატორი არქივაცია Agreement which is executed between ICANN და all ICANN- accredited registrars.

2. Dispute Resolution Process

     Tაქ are two possible steps to the რეგისტრატორი Transfer Dispute Resolution Process. A რეგისტრატორი may elect one ან both of the steps pursuant to the rules below. In the event a რეგისტრატორი either files a Request fან Enfანcement (as described below) with a Second-სმის დონე Dispute Provider, ან files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-სმის დონე Registry option later fან the same filing ან matter presented fან resolution.

2.1 First სმის დონე - Registry Operatან

     A რეგისტრატორი may choose to file a dispute directly with the relevant Registry Operatან. Any decisions made by the Registry Operatან may be appealed to a Dispute Resolution Provider. A რეგისტრატორი may file a dispute directly to a Dispute Resolution Provider; however, in that case the filing რეგისტრატორი would fანfeit any right to appeal the decision of the Dispute Resolution Provider.

2.2 Second-სმის დონე - Dispute Resolution Panel

     The primary intent of this step is to provide a means fან 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 wაქ a რეგისტრატორი of Recანd 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 wაქ a Gaining რეგისტრატორი 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 სმის დონე (Registry)

3.1 რეგისტრატორი files a Request fან Enfანcement with the applicable Registry Operatან

     3.1.1 Either the Gaining ან რეგისტრატორი of Recანd ("Filing რეგისტრატორი") may submit a Request fან Enfანcement. This must be done in accანdance with the Supplemental Rules adopted by the applicable Registry Operatან.

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

3.1.4 The Request fან Enfანcement shall annex the following documentary evidence (as applicable და available) in electronic fანm if possible, together with a schedule indexing such evidence:
  (i) Fან the Gaining რეგისტრატორი:
      a. Completed Fანm of Authანization ("FOA")
      b. Copy of the Whois output fან the date transfer was initiated, which was used to identify the authანized Transfer კონტაქტიs
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body ან court ანder in cases when the Registrant of Recანd is being changed simultaneously with a რეგისტრატორი Transfer
      e. Copies of all communications made to the რეგისტრატორი of Recანd with regard to the applicable transfer request along with any responses from the რეგისტრატორი of Recანd
  (ii) Fან the რეგისტრატორი of Recანd:
      a. Completed FOA from რეგისტრატორი of Recანd if applicable
      b. Copy of the Whois output fან the date the transfer was initiated
      c. Relevant histანy of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court ანder;
• Registrant ან administrative contact identity dispute in accანdance with Section 4 [რეგისტრატორი of Recანd Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the რეგისტრაციაed სახელი Holder ან Administrative კონტაქტი;
• LOCK status along with proof of a reasonable means fან the registrant to remove LOCK status as per Section __of Exhiბიტი __ to this Agreement;
• დომენი name within 60 days of initial registration; ან
• დომენი name within 60 days of a priან transfer.

      e. Copies of all communications made to the Gaining რეგისტრატორი with regard to the applicable transfer request along with any responses from the Gaining რეგისტრატორი.

3.2 The არაn-Filing რეგისტრატორი ("Respondent") shall have seven (7) calendar days from receipt of the Request fან Enfანcement to prepare a Response to the Request fან Enfანcement ("Response").

3.2.1 The Response shall be submitted in electronic fანm to both the Registry და Filing რეგისტრატორი და shall:
      (i) Respond specifically to the statements და allegations contained in the Request fან Enfანcement (This pანtion of the response shall comply with any wანd ან page limit set fანth in the Dispute Resolution Provider's Supplemental Rules.);
      (ii) Provide the name, postal და e-mail addresses, და the telephone და fax numbers of the Respondent (non-filing რეგისტრატორი);
      (iii) Identify any other legal proceedings that have been commenced ან terminated in connection with ან relating to any of the დომენი name(s) that are the subject of the Request fან Enfანcement;
      (iv) State that a copy of the Response has been sent ან transmitted to the Filing რეგისტრატორი;
      (v) Conclude with the following statement followed by the signature of the Respondent ან its authანized representative:
   "Respondent certifies that the infანmation contained in this Response is to the best of Respondent's kახლაledge complete და accurate, that this Response is not being presented fან any improper purpose, such as to harass, და that the assertions in this Response are warranted under these Rules და under applicable law, as it ახლა exists ან as it may be extended by a good-faith და reasonable argument."; და
     (vi) Annex any documentary ან other evidence upon which the Respondent relies, together with a schedule indexing such documents.

3.2.2 მიუთითებს the request of the Respondent, the Registry Operatან may, in exceptional cases, extend the period of time fან the filing of the response, but in no case may the extension be mანe 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 Operatან.

3.2.3 თუ a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatან shall decide the dispute based upon the Request fან Enfანcement.

3.3 Registry Operatან must review all applicable documentation და compare registrant/contact data with that contained within the authანitative Whois database და reach a conclusion not later than 14 days after receipt of the Response.

3.3.1 თუ the data included in the Request fან Enfანcement does not match the data listed in the authანitative Whois, the Registry Operatან must contact each რეგისტრატორი და require additional documentation.

3.3.2 თუ the Gaining რეგისტრატორი cannot provide a complete FOA with data matching that contained within the authანitative Whois database, then the Registry Operatან shall find that the transfer should be reversed. In the case of a thick Registry, if the რეგისტრატორი of Recანd's Whois is not accessible ან invalid, the Registry Operatან's Whois should be used. In the case of a thin Registry, if the რეგისტრატორი of Recანd's Whois is not accessible ან is invalid, the Registry Operatან must notify ICANN და place the dispute on hold until such time as the specific problem is resolved by ICANN.

3.3.3 In the case wაქ a რეგისტრატორი of Recანd denies a request fან a დომენი name transfer ("NACKs"), the რეგისტრატორი of Recანd must provide evidence of one of the factანs fან which it is allowed to NACK. თუ the რეგისტრატორი of Recანd cannot provide evidence that demonstrates any of the factანs, და the Gaining რეგისტრატორი provides to the Registry a complete FOA with data matching that contained within the authანitative Whois database, then the transfer must be approved to be processed.

3.3.4 თუ the data provided by neither რეგისტრატორი appears to be conclusive, then the Registry shall issue a finding of "no decision." თუ the data provided to the Registry is complete და provides sufficient basis fან a determination based on the Policy, the Registry may not issue a finding of "no decision." Either რეგისტრატორი shall be able to appeal such issue to a Second-სმის დონე Dispute Resolution Provider in accანdance with the provisions set fანth below.

3.4 Fees fან First-სმის დონე Dispute Resolution Service

3.4.1 Tაქ is no filing fee assessed to the Filing რეგისტრატორი at the time the Request fან Enfანcement is submitted to the Registry Operatან.

3.4.2 The რეგისტრატორი that does not უკანail in the dispute will be assessed a fee to be set by the Registry Operatან. Such fee shall be set fანth in the Registry's Supplemental Rules that are in effect at the time that the Request fან Enfანcement 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 Operatან shall collect the applicable fees from the Filing რეგისტრატორი.

3.5 Availability of Court Proceedings

      The procedures set fანth above shall not უკანent a რეგისტრატორი from submitting a dispute to a court of competent jurisdiction fან independent resolution befანe such an administrative proceeding is commenced ან after such proceeding is concluded. თუ a Registry Operatან decides a დომენი name registration should be transferred (either to the Gaining რეგისტრატორი, ან alternatively, back from the Gaining რეგისტრატორი to the რეგისტრატორი of Recანd), the Registry will wait fourteen (14) calendar days after it is infანmed of the decision befანe 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 დომენი name(s). თუ such documentation is received by the Registry Operatან within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatან that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatან that the lawsuit has been dismissed ან withdrawn; ან (iii) the Registry Operatან receives a copy of an ანder from such court.

4. Dispute Procedures at the Second სმის დონე with a Dispute Resolution Provider

4.1 The სერვისიs of the Dispute Resolution Panel may be invoked in any of the following two situations:

      (i) A Filing რეგისტრატორი may elect to skip the First-სმის დონე dispute process at Registry level და submit a Request fან Enfანcement directly with a Dispute Resolution Provider;
      (ii) The non-უკანailing რეგისტრატორი in a First-სმის დონე dispute proceeding may submit an appeal of the applicable Registry Operatან's decision to the Dispute Resolution Provider. დამატებაitionally, in the case wაქ the result in the First-სმის დონე dispute process is a "no-decision," either რეგისტრატორი may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request fან Enfანcement

4.2.1 In the event that the Filing რეგისტრატორი elects to submit a Request fან Enfანcement to the Dispute Resolution Provider in lieu of submitting a Request fან Enfანcement to the applicable Registry Operatან, the obligations და responsibilities set fანth 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 და compare registrant/contact data with that contained within the authანitative Whois database და reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.
     (i) თუ the data does not match the data listed in authანitative Whois, the Dispute Resolution Panel should contact each რეგისტრატორი და require additional documentation.
     (ii) თუ the Gaining რეგისტრატორი is unable to provide a complete FOA with data matching that contained within the authანitative 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 რეგისტრატორი of Recანd's Whois is not accessible ან invalid, the applicable Registry Operatან's Whois should be used. In the case of a thin Registry, if the რეგისტრატორი of Recანd's Whois is not accessible ან is invalid, the Dispute Resolution Provider may place the dispute on hold until such time as the problem is resolved.
     (iii) In the case wაქ a რეგისტრატორი of Recანd NACKs a transfer, the რეგისტრატორი of Recანd must provide evidence of one of the factანs fან which it is allowed to NACK as set fანth in Section 3.1.4 (ii) of this Dispute Resolution Policy. თუ the რეგისტრატორი of Recანd cannot provide evidence that demonstrates any of the factანs, და the Gaining რეგისტრატორი provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the authანitative Whois database at the time of the transfer request, then the transfer should be approved.
     (iv) Unlike under the First-სმის დონე 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 და determine, based on a preponderance of the evidence, which რეგისტრატორი should უკანail in the dispute და what resolution to the Request fან Enfანcement will appropriately redress the issues set fანth in the Request fან Enfანcement.
     (v) Resolution options fან the Dispute Resolution Panel are limited to the following:
  a. Approve Transfer
  b. Deny the Transfer (ან ანdering the დომენი name be returned to the რეგისტრატორი of Recანd in cases wაქ a Transfer has already occurred)

4.3 Appeal of First სმის დონე Dispute Decision ან Registry Operatან Finding of "არა-Decision."

4.3.1 In the event that the რეგისტრატორი which does not უკანail in the First-სმის დონე dispute is dissatisfied by the Registry-Operatან's decision, such რეგისტრატორი 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-სმის დონე decision was issued.

4.3.2 In the event that the Registry Operatან issues a finding of "no-decision" in accანdance with Section 3.3.4 above, either რეგისტრატორი 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-სმის დონე decision was issued.

4.3.3 In either case, the document submitted by the რეგისტრატორი to the Dispute Resolution Provider shall be referred to as an "Appeal."

4.3.4 The Appellant shall submit the Appeal in electronic fანm და shall:
     (i) Request that the Appeal be submitted fან decision in accანdance with the Policy და these Rules;
     (ii) Provide the name, postal და e-mail addresses, და the telephone და telefax numbers of the Appellant და of any representative authანized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
     (iii) Provide the name of the Appellee და all infანmation (including any postal და e-mail addresses და telephone და telefax numbers) kახლაn to Appellee regarding how to contact Appellee ან any representative of Appellee, including contact infანmation based on pre-Request fან Enfანcement და pre-Appeal dealings;
     (iv) Specify the დომენი 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 fან such appeal, including specific responses to the findings of the Registry Operatან in the First-სმის დონე Dispute process. (This pანtion of the response shall comply with any wანd ან page limit set fანth in the Dispute Resolution Provider's Supplemental Rules);
     (vii) Specify, in accანdance with the Policy, the remedies sought;
     (viii) Identify any other related legal proceedings kახლაn to the Appellant that have been commenced ან terminated in connection with ან relating to any of the დომენი 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 ან transmitted to the Appellee; და
      (x) Conclude with the following statement followed by the signature of the Appellant ან its authანized representative:
  "Appellant agrees that its claims და remedies concerning the registration of the დომენი name, the dispute, ან the dispute's resolution shall be solely against the Appellee და waives all such claims და remedies against the Dispute Resolution Provider და the Registry Operatან as well as their directანs, officers, employees, და agents, except in the case of deliberate wrongdoing ან gross negligence."
  "Appellant certifies that the infანmation contained in this Appeal is to the best of Appellant's kახლაledge complete და accurate, that this Appeal is not being presented fან any improper purpose, such as to harass, და that the assertions in this Appeal are warranted under this Policy და under applicable law, as it ახლა exists ან as it may be extended by a good-faith და reasonable argument."

4.3.5 The Appeal may relate to mანe than one დომენი name, provided that the დომენი names involve the same decision issued by the Registry Operatან fან the First-სმის დონე Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatან during the First-სმის დონე Dispute.

4.3.7 A Dispute Resolution Provider must request all documentation relating to the First-სმის დონე Dispute from the applicable Registry Operatან no later than seven (7) calendar days of receipt of the appeal. The Registry Operatან 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 და 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 ან 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 არაvo basis. Although the Dispute Resolution Panel is not bound by the findings of the Registry Operatან 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 და determine the appropriate resolution to the issues presented.

• Approval of a Transfer
• Denial of the Transfer (ან ანdering the დომენი name be returned to the რეგისტრატორი of Recანd in cases wაქ a Transfer has already occurred)

4.4 Fees fან Second-სმის დონე Dispute Resolution Service

4.4.1 In the case of either a Request fან Enfანcement ან an Appeal filed at the Second სმის დონე, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms და 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 რეგისტრატორი ან Appellant, whichever applicable, does not უკანail in a Second-სმის დონე dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

4.4.3 In the event that the Filing რეგისტრატორი ან Appellant, whichever applicable, უკანails in a Second-სმის დონე dispute, the Respondent ან 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 რეგისტრატორი ან Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent ან Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accანdance 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 fანth above shall not უკანent a რეგისტრატორი from submitting a dispute to a court of competent jurisdiction fან independent resolution befანe such administrative proceeding is commenced ან after such proceeding is concluded. თუ a Dispute Resolution Panel decides a დომენი name registration should be transferred (either to the Gaining რეგისტრატორი, ან alternatively, back from the Gaining რეგისტრატორი to the რეგისტრატორი of Recანd), such რეგისტრატორი will wait fourteen (14) calendar days after it is infანmed of the decision befანe 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 დომენი name(s). თუ 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 ან withdrawn; ან (iii) a copy of an ანder from such court dismissing the lawsuit ან ანdering certain actions with respect to the დომენი name.

1. რეგისტრატორი Requirements

     რეგისტრაციაed სახელი Holders must be able to transfer their დომენი name registrations between რეგისტრატორიs provided that the Gaining რეგისტრატორი's transfer process meets the minimum stდაards of this policy და that such transfer is not prohiბიტიed by ICANN ან Registry policies. Inter-რეგისტრატორი დომენი name transfer processes must be clear და concise in ანder to avoid confusion. Further, რეგისტრატორიs should make reasonable effანts to infანm რეგისტრაციაed სახელი Holders of, და provide access to, the published documentation of the specific transfer process employed by the რეგისტრატორიs.

1.1 Transfer Authანities

     The Administrative კონტაქტი და the რეგისტრაციაed სახელი Holder, as listed in the Losing რეგისტრატორი's ან applicable Registry's (wაქ available) publicly accessible WHOIS სერვისი are the only parties that have the authანity to approve ან deny a transfer request to the Gaining რეგისტრატორი. In the event of a dispute, the რეგისტრაციაed სახელი Holder's authანity supersedes that of the Administrative კონტაქტი.
რეგისტრატორიs may use Whois data from either the რეგისტრატორი of Recანd ან the relevant Registry fან the purpose of verifying the authenticity of a transfer request; ან from another data source as determined by a consensus policy.

2. Gaining რეგისტრატორი Requirements

Fან each instance wაქ a რეგისტრაციაed სახელი Holder requests to transfer a დომენი name registration to a different რეგისტრატორი, the Gaining რეგისტრატორი shall:
      2.1 Obtain express authანization from either the რეგისტრაციაed სახელი Holder ან the Administrative კონტაქტი (აქafter, "Transfer კონტაქტი"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining რეგისტრატორი from the Transfer კონტაქტი.

     2.1.1 The authანization must be made via a valid Stდაardized Fანm of Authანization (FOA). Tაქ are two different FOA's available at the ICANN website. The FOA labeled "Initial Authანization fან რეგისტრატორი Transfer" must be used by the Gaining რეგისტრატორი to request an authანization fან a registrar transfer from the Transfer კონტაქტი. The FOA labeled "დადასტურებაation of რეგისტრატორი Transfer Request" may be used by the რეგისტრატორი of Recანd to request confirmation of the transfer from the Transfer კონტაქტი.
The FOA shall be communicated in English, და any dispute arising out of a transfer request shall be conducted in the English language. რეგისტრატორიs may choose to communicate with the Transfer კონტაქტი in additional languages. However, რეგისტრატორიs choosing to exercise such option are responsible fან the accuracy და completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining რეგისტრატორი relies on a physical process to obtain this authანization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer კონტაქტი და further that it is accompanied by a physical copy of the რეგისტრატორი of Recანd's Whois output fან the დომენი name in question.

     2.1.2.1 თუ the Gaining რეგისტრატორი relies on a physical authანization process, then the Gaining რეგისტრატორი assumes the burden of obtaining reliable evidence of the identity of the Transfer კონტაქტი და maintaining appropriate recანds proving that such evidence was obtained. Further the Gaining რეგისტრატორი also assumes the burden fან ensuring that the entity making the request is indeed authანized to do so. The acceptable fანms of physical identity are:

• არაtarized statement
• Valid Drivers license
• პასპორტი
• Article of Incანpანation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining რეგისტრატორი relies on an electronic process to obtain this authანization the acceptable fანms of identity would include:

• Electronic signature in confანmance with national legislation, in the location of the Gaining რეგისტრატორი (if such legislation exists).
• Consent from an individual ან entity that has an email address matching the Transfer კონტაქტი email address. 

     The რეგისტრატორი of Recანd may not deny a transfer request solely because it believes that the Gaining რეგისტრატორი has not received the confirmation set fანth above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining რეგისტრატორი. The presumption in all cases will be that the Gaining რეგისტრატორი has received და authenticated the transfer request made by a Transfer კონტაქტი.

     2.2 Request, by the transmission of a "transfer" commდა as specified in the რეგისტრატორი შესაძენადol Kit, that the Registry Operatან database be changed to reflect the new რეგისტრატორი.

     2.2.1 Transmission of a "transfer" commდა constitutes a representation on the part of the Gaining რეგისტრატორი that the requisite authანization has been obtained from the Transfer კონტაქტი listed in the authანitative Whois database.

     2.2.2 The Gaining რეგისტრატორი is responsible fან validating the რეგისტრაციაed სახელი Holder requests to transfer დომენი names between რეგისტრატორიs. However, this does not preclude the რეგისტრატორი of Recანd from exercising its option to independently confirm the რეგისტრაციაed სახელი Holder's intent to transfer its დომენი name to the Gaining რეგისტრატორი in accანdance with Section 3 of this policy.

3. Obligations of the რეგისტრატორი of Recანd

     A რეგისტრატორი of Recანd can choose independently to confirm the intent of the რეგისტრაციაed სახელი Holder when a notice of a pending transfer is received from the Registry. The რეგისტრატორი of Recანd must do so in a manner consistent with the stდაards set fანth in this agreement pertaining to Gaining რეგისტრატორიs. In ანder to ensure that the fანm of the request employed by the რეგისტრატორი of Recანd is substantially administrative და infანmative in nature და clearly provided to the Transfer კონტაქტი fან the purpose of verifying the intent of the Transfer კონტაქტი, the რეგისტრატორი of Recანd must use the FOA.

     The FOA shall be communicated in English, და any dispute arising out of a transfer request, shall be conducted in the English language. რეგისტრატორიs may choose to communicate with the Transfer კონტაქტი in additional languages. However, the რეგისტრატორი choosing to exercise such option is responsible fან the accuracy და completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes და procedures set fანth in this policy. This includes but is not limited to the requirement that no რეგისტრატორი shall add any additional infანmation to the FOA used to obtain the consent of the Transfer კონტაქტი in the case of a transfer request.
This requirement does not preclude the რეგისტრატორი of Recანd from marketing to its existing customers through separate communications.
The FOA should be sent by the რეგისტრატორი of Recანd to the Transfer კონტაქტი as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operatან.Failure by the რეგისტრატორი of Recანd 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 კონტაქტი listed in the Whois has not confirmed their request to transfer with the რეგისტრატორი of Recანd და the რეგისტრატორი of Recანd has not explicitly denied the transfer request, the default action will be that the რეგისტრატორი of Recანd must allow the transfer to proceed.
Upon denying a transfer request fან any of the following reasons, the რეგისტრატორი of Recანd must provide the რეგისტრაციაed სახელი Holder და the potential Gaining რეგისტრატორი with the reason fან denial. The რეგისტრატორი of Recანd may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court ანder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the რეგისტრაციაed სახელი Holder ან Administrative კონტაქტი
5. არა payment fან უკანious registration period (including credit card charge-backs) if the დომენი name is past its expiration date ან fან უკანious ან current registration periods if the დომენი name has not yet expired. In all such cases, however, the დომენი name must be put into "რეგისტრატორი Hold" status by the რეგისტრატორი of Recანd priან to the denial of transfer.
6. Express written objection to the transfer from the Transfer კონტაქტი. (e.g. - email, fax, paper document ან other processes by which the Transfer კონტაქტი has expressly და voluntarily objected through opt-in means)
7. A დომენი name was already in “lock status” provided that the რეგისტრატორი provides a readily accessible და reasonable means fან the რეგისტრაციაed სახელი Holder to remove the lock status.
8. A დომენი name is in the first 60 days of an initial registration period.
9. A დომენი name is within 60 days (ან a lesser period to be determined) after being transferred (apart from being transferred back to the ანiginal რეგისტრატორი in cases wაქ both რეგისტრატორიs so agree და/ან wაქ a decision in the dispute resolution process so directs).

Instances when the requested change of რეგისტრატორი may not be denied include, but are not limited to:

• არაnpayment fან a pending ან future registration period
• არა response from the რეგისტრაციაed სახელი Holder ან Administrative კონტაქტი.
• დომენი name in რეგისტრატორი Lock სტატუსი, unless the რეგისტრაციაed სახელი Holder is provided with the reasonable oppანtunity და ability to unlock the დომენი name priან to the Transfer Request.
• დომენი name registration period time constraints, other than during the first 60 days of initial registration ან during the first 60 days after a registrar transfer.
• General payment defaults between რეგისტრატორი და business partners / affiliates in cases wაქ the რეგისტრაციაed სახელი Holder fან the დომენი in question has paid fან the registration.

     The რეგისტრატორი of Recანd has other mechanisms available to collect payment from the რეგისტრაციაed სახელი Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the რეგისტრატორი of Recანd must not employ transfer processes as a mechanism to secure payment fან სერვისიs from a რეგისტრაციაed სახელი Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fან უკანious registration period(s) if the transfer is requested after the expiration date, ან
     (ii) In the case of non-payment of the current registration period, if transfer is requested befანe the expiration date.

4. რეგისტრატორი Coანdination

     Each რეგისტრატორი is responsible fან keeping copies of documentation, including the FOA და the Transfer კონტაქტიs response tაქto, that may be required fან filing და suppანting a dispute under the dispute resolution policy. Gaining რეგისტრატორიs must maintain copies of the FOA as received from the Transfer კონტაქტი as per the stდაard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining რეგისტრატორი და the რეგისტრატორი of Recანd must provide the evidence relied on fან the transfer during და after the applicable inter-registrar დომენი name transaction(s). Such infანmation must be provided when requested by, და only by, the other რეგისტრატორი that is party to the transfer transaction. დამატებაitionally, ICANN, the Registry Operatან, a court ან authანity with jurisdiction over the matter ან a third party dispute resolution panel may also require such infანmation within five (5) days of the request.

     The Gaining რეგისტრატორი must retain, და produce pursuant to a request by a Losing რეგისტრატორი, a written ან electronic copy of the FOA. In instances wაქ the რეგისტრატორი of Recანd has requested copies of the FOA, the Gaining რეგისტრატორი must fulfill the რეგისტრატორი of Recანds request (including providing the attendant suppანting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fან reversal by the Registry Operatან ან the Dispute Resolution Panel in the event that a transfer complaint is filed in accანdance with the requirements of this policy.

     თუ either a რეგისტრატორი of Recანd ან a Gaining რეგისტრატორი does not believe that a transfer request was hდაled in accანdance with the provisions of this policy, then the რეგისტრატორი may initiate a dispute resolution procedure as set fანth in Section C of this policy.

     Fან purposes of facilitating transfer requests, რეგისტრატორიs should provide და maintain a unique და private email address fან use only by other რეგისტრატორიs და the Registry:
     i. This email address is fან issue related to transfer requests და the procedures set fანth in this policy only.
     ii. The email address should be managed to ensure messages are received by someone who can respond to the transfer issue.
     iii. მესიჯიs 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 fან რეგისტრატორიs

     In EPP-based gTLD Registries, რეგისტრატორიs must follow the requirements set fანth below.
რეგისტრატორიs must provide the რეგისტრაციაed სახელი Holder with the unique "AuthInfo" code within five (5) calendar days of the რეგისტრაციაed სახელი Holder's initial request if the რეგისტრატორი does not provide facilities fან the რეგისტრაციაed სახელი Holder to generate და manage their own unique "AuthInfo" code.

     რეგისტრატორიs may not employ any mechanism fან complying with a რეგისტრაციაed სახელი Holder's request to obtain the applicable "AuthInfo Code" that is mანe restrictive than the mechanisms used fან changing any aspect of the რეგისტრაციაed სახელი Holder's contact ან name server infანmation.

     The რეგისტრატორი of Recანd must not refuse to release an "AuthInfo Code" to the რეგისტრაციაed სახელი Holder solely because tაქ is a dispute between the რეგისტრაციაed სახელი Holder და the რეგისტრატორი over payment.

რეგისტრატორი-generated "AuthInfo" codes must be unique on a per-დომენი basis.
     The "Auth-Info" codes must be used solely to identify a რეგისტრაციაed სახელი Holder, wაქas the FOA's still need to be used fან authანization ან confirmation of a transfer request, as described in Section 2 და Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commდა from the Gaining რეგისტრატორი, Registry Operatან will transmit an electronic notification to both რეგისტრატორიs. 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 რეგისტრატორი fან the purpose of facilitating transfers.

     The Registry Operatან shall complete the requested transfer unless, within five (5) calendar days, Registry Operatან receives a NACK protocol commდა from the რეგისტრატორი of Recანd.
When the Registry's database has been updated to reflect the change to the Gaining რეგისტრატორი, Registry Operatან will transmit an electronic notification to both რეგისტრატორიs. The notification may be sent to       the unique email address established by each რეგისტრატორი fან the purpose of facilitating transfers ან such other email address agreed to by the parties.
The Registry Operatან shall undo a transfer if, after a transfer has occurred, the Registry Operatან receives one of the notices as set fანth below. In such case, the transfer will be reversed და the დომენი name reset to its ანiginal state. The Registry Operatან 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 Operatან 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 რეგისტრატორი of Recანd და the Gaining რეგისტრატორი sent by email, letter ან fax that the transfer was made by mistake ან was otherwise not in accანdance with the procedures set fანth in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; ან
     iii. Order of a court having jurisdiction over the transfer.

7. Recანds of რეგისტრაცია

     Each რეგისტრატორი shall require its customer, the რეგისტრაციაed სახელი Holder, to maintain its own recანds appropriate to document და prove the initial დომენი name registration date.

8. Effect on ვადა of რეგისტრაცია

     The completion by Registry Operatან of a holder-authანized transfer under this Part A shall result in a one-წელი extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) წელი.

B. ICANN-Approved Transfers

     Transfer of the sponsანship of all the registrations sponsანed by one რეგისტრატორი as the result of (i) acquisition of that რეგისტრატორი ან its assets by another რეგისტრატორი, ან (ii) lack of accreditation of that რეგისტრატორი ან lack of its authანization with the Registry Operatან, may be made accანding to the following procedure:
     (a) The gaining რეგისტრატორი must be accredited by ICANN fან the Registry TLD და must have in effect a Registry-რეგისტრატორი Agreement with Registry Operatან fან the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatან that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual ან imminent business failure of a რეგისტრატორი.
Upon satisfaction of these two conditions, Registry Operatან will make the necessary one-time changes in the Registry database fან no charge, fან transfers involving 50,000 name registrations ან fewer. თუ the transfer involves registrations of mანe than 50,000 names, Registry Operatან will charge the gaining რეგისტრატორი a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures fან hდაling disputes concerning inter-registrar transfers are set fანth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatანs და ICANN accredited რეგისტრატორიs.

We respect თქვენი individual privacy. That is why we have adopted this კონფიდენციალურობის პოლიტიკა, which embodies our commitment to the protection of თქვენი privacy through adაქnce to fair electronic infანmation practices. This კონფიდენციალურობის პოლიტიკა puts you, the individual, in control of how თქვენი personal infანmation is processed, და you have our promise that we will not electronically process თქვენი personal infანmation in any way that is incompatible with this კონფიდენციალურობის პოლიტიკა.

This კონფიდენციალურობის პოლიტიკა protects თქვენი privacy by:

4. How We Put Infანmation შესაძენად Good Use