1. Scope at Purpose

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

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

1.3 In the event of any inconsistency between this Policy at the applicable registry’s rules o matatoy ICANN policy, the applicable registry rules at matatoy policy requirements shall nakaraanail.

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

2. Definitions

Fo purposes of this Policy:

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

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

2.3 “Redemption Grace Period” o “RGP” means the post-deletion recovery period, wdito available, during which an expired domain name may still be restoable fo an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, wdito applicable, during which the domain name can no longer be renewed, restoed, modified, o transferred.

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

2.6 “Magtataposd Domain Auction” means the expired-domain sale process that may apply to certain expired domain names befoe final deletion o release.

2.7 “Isaraout Auction” means the final sale phase fo certain Eligible Mga Domain that were not sold earlier in the expired domain auction process.

3. Effect of Expiration

3.1 Upon expiration, a domain name may stop resolving, at any website, email Serbisyo, o other Serbisyo associated with the domain name may cease functioning immediately o shotly tditoafter.

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

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

4. I-renewal Hinditices at Customer Responsibility

4.1 NiceNIC may send renewal reminders at expiration-related notices befoe at after expiration, as required by applicable policy o as part of NiceNIC’s statard operational process.

4.2 It is iyong sole responsibility to maintain accurate at current account at contact infomation, including iyong email address, at to monito the status of iyong domain names.

4.3 Failure to receive a renewal notice, reminder, invoice, o other communication shall not relieve you of responsibility fo renewing iyong domain name befoe expiration.

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

5. Statard Post-Expiration I-renewal

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

5.2 I-renewal is not complete unless at until NiceNIC has successfully received at processed full payment of all applicable fees.

5.3 NiceNIC reserves the right to determine whether a domain name remains eligible fo statard renewal, redemption, o other recovery based on the applicable TLD, registry status, auction status, at operational feasibility.

6. Magtataposd Domain Auction fo Eligible Mga Domain

6.1 Certain expired domain names may enter NiceNIC’s expired domain auction process befoe all recovery windows have ended. This process applies only to Eligible Mga Domain at does not apply to all TLDs.

6.2 Fo Eligible Mga Domain under NiceNIC’s statard expired-domain process, the following general timeline may apply:

Day 0 after expiration

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

Day 26 after expiration

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

Day 31 after expiration

Kung tdito is no active bid, the registrant may still be able to recover the domain name by paying the statard renewal fee plus the applicable redemption fee.

Kung tdito is an active bid, the domain name may be removed from the registrant’s account at may no longer be renewable through odinary renewal o restoation procedures.

Day 37 after expiration

The domain name may enter final closeout auction. Unless tdito is a pending bumili o other sale-related restriction, the registrant may still be able to recover the domain name by paying the statard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. Kung the domain name was not sold o otherwise committed to sale, recovery may still be possible fo a limited period, subject to the applicable TLD, registry rules, at NiceNIC’s operational process.

Day 74 after expiration

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

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

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

7. Redemption Grace Period

7.1 Kung an expired domain name is not renewed during the applicable grace period at if the applicable TLD suppots restoation after deletion, the domain name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the domain name may stop resolving;

(b) website at email Serbisyos may remain unavailable;

(c) the domain name generally cannot be modified o transferred; at

(d) restoation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, at any taxes o matatoy fees.

7.3 Restoation during the Redemption Grace Period is not guaranteed at remains subject to registry suppot, operational feasibility, the domain’s current status, at the absence of auction o sale restrictions.

8. Pending Delete at Final Release

8.1 Kung a domain name is not renewed o restoed during the applicable recovery periods, it may enter the Pending Delete stage, wdito suppoted by the applicable TLD.

8.2 During Pending Delete, the domain name cannot be renewed, restoed, transferred, o modified.

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

8.4 NiceNIC does not guarantee the exact time, date, o availability of a domain name once it is released by the registry, at NiceNIC does not guarantee that the fomer registrant will be able to re-magparehistro the domain name.

9. TLD-Specific Variations

9.1 Hindit all TLDs follow the statard lifecycle described above. Certain ccTLDs at other TLDs may have shoter grace periods, no redemption period, no pending delete stage, o earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many ccTLDs generally follow a lifecycle similar to the statard expiration, grace, redemption, at deletion process, including, fo example:

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

9.2.2 TLDs with no Pending Delete stage

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

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

9.2.3 TLDs requiring renewal befoe the actual expiration date

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

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

9.2.4 TLDs requiring action five (5) days befoe expiration

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

.CX, .DE, .EU, at .NL.

9.2.5 .CM domains

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

9.2.6 .GG domains

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

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

These domains may not suppot a statard 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. Kung the domain is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppot immediately.

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

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

9.2.9 .TO domains

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

9.2.10 .NU domains

.NU domain names may be reactivated in the odinary manner within approximately seven (7) days after expiration. Kung not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restoation may still be possible through NiceNIC Suppot.

9.3 The TLD-specific infomation above is provided fo general reference only at may change at any time based on registry policy, registry system changes, o operational requirements. Customers should contact NiceNIC Suppot fo current TLD-specific recovery infomation.

10. Fees at Magbayadments

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

10.2 Redemption o restoation requires payment in full of all applicable fees befoe processing.

10.3 Lahat fees paid fo expired-domain recovery, restoation, o special processing are non-refundable once processing has begun, except wdito otherwise required by applicable law.

11. Hindi Guarantee of Recovery o Availability

11.1 NiceNIC does not guarantee that any expired domain name can be renewed, restoed, retained, transferred, o re-magparehistroed after expiration.

11.2 NiceNIC does not guarantee:

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

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

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

(d) that the registry will suppot restoation; o

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

11.3 You ackngayonledge that delayed action may result in additional fees, loss of recovery rights, interruption of Serbisyo, auction sale, o permanent loss of the domain name.

12. Limitation of Responsibility

12.1 Para sa the maximum extent permitted by applicable law, NiceNIC shall not be liable fo any loss of domain name, loss of use, interruption of website o email Serbisyo, business interruption, lost profits, loss of data, o other direct o indirect damages arising from:

(a) domain expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules o registry actions;

(e) auction placement o sale;

(f) failed restoation; o

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

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

13. Changes to This Policy

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

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

14. Makipag-ugnayan

Kung you need assistance regarding an expired domain name, renewal, redemption, o TLD-specific recovery options, please submit a suppot ticket through iyong NiceNIC account o contact NiceNIC Suppot through the official suppot channels published on the NiceNIC website.

1. General

This Agreement is made between you (ditoinafter referred to as “User”) at NiceNIC.NET (ditoinafter referred to as “the Platfom”). By using the Platfom’s Bumili Hindiw Domain Sales Serbisyo, you agree to be bound by the terms at conditions set foth ditoin. Kung you do not agree, please do not proceed with any fixed-price domain bumili through the Platfom.

2. Service Description

1. The Platfom offers fixed-price domain names (“Bumili Hindiw Mga Domain”) fo direct bumili.

2. Lahat Bumili Hindiw Mga Domain are sourced from pre-approved third-party domain providers.

3. Users may bumili these domains at the listed price. Once payment is completed at the domain is successfully transferred, the bumilier will obtain ownership of the domain.

3. Purchase Process

1. The User selects a domain labeled as “Bumili Hindiw” at proceeds to checkout.

2. Upon confirmation at full payment, the Platfom initiates the transfer o delivery process.

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

4. Kung, fo any reason, the selected domain becomes unavailable o undeliverable after bumili, the Platfom will issue a full refund to the user’s account balance.

4. User Rights at Responsibilities

1. Users have the right to bumili available Bumili Hindiw Mga Domain through the Platfom.

2. Users must ensure that all provided account at payment infomation is accurate at lawful.

3. Users shall not engage in malicious activity, technical disruption, o behavio that interferes with the nomal functioning of the Platfom.

4. Upon acquiring a domain, the User agrees to comply with the applicable rules at policies of the coresponding domain registry, including any legal o regulatoy obligations.

5. Platfom Rights at Responsibilities

1. The Platfom will provide domain transaction Serbisyos in accodance with this Agreement at strive to protect user interests.

2. The Platfom reserves the right to verify user identity, payment legitimacy, at transaction authenticity.

3. The Platfom retains the right to update, adjust, o remove Bumili Hindiw Mga Domain from listing at its sole discretion at without prio notice.

4. Kung any fraudulent o abusive behavio is detected, the Platfom reserves the right to suspend o terminate Serbisyos to the user.

6. Disclaimer

1. The Platfom does not make any guarantees regarding the future value, resale potential, o commercial use of any domain bumilid.

2. The Platfom is not liable fo delays caused by registries, third-party providers, o external systems beyond its control.

3. The Platfom shall not be held responsible fo Serbisyo interruptions, data loss, o failed transactions resulting from foce majeure events o uncontrollable technical issues, though reasonable effots will be made to assist the User in resolving any such issues.

7. Governing Law at Dispute Resolution

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

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

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a Bumili Hindiw domain oder.

2. The Platfom reserves the right to amend this Agreement at any time. Na-update versions will be published on the Platfom’s “Mga Kasunduan” page at shall take immediate effect. Continued use of the Serbisyo constitutes acceptance of the revised terms.

This Unifom Domain Name Dispute Resolution Policy (the "Policy") has been adopted by the Internet Copoation fo Assigned Pangalans at Numbers ("ICANN"), is incopoated by reference into iyong Pagpaparehistro Agreement, at sets foth the terms at conditions in connection with a dispute between you at any party other than us (the registrar) over the registration at use of an Internet domain name magparehistroed by you. Proceedings under Paragraph 4 of this Policy will be conducted accoding to the Rules fo Unifom Domain Name Dispute Resolution Policy (the "Rules of Procedure"), which are available dito, at the selected administrative-dispute-resolution Serbisyo provider's supplemental rules.

2. Your Representations

By applying to magparehistro a domain name, o by asking us to maintain o renew a domain name registration, you ditoby represent at warrant to us that (a) the statements that you made in iyong Pagpaparehistro Agreement are complete at accurate; (b) to iyong kngayonledge, the registration of the domain name will not infringe upon o otherwise violate the rights of any third party; (c) you are not magparehistroing the domain name fo an unlawful purpose; at (d) you will not kngayoningly use the domain name in violation of any applicable laws o regulations. It is iyong responsibility to determine whether iyong domain name registration infringes o violates someone else's rights.

3. Kanselahinlations, Transfers, at Changes

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

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

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

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

4. We may also cancel, transfer o otherwise make changes to a domain name registration in accodance with the terms of iyong Pagpaparehistro Agreement o other legal requirements.

4. Matatoy Administrative Proceeding

This Paragraph sets foth the type of disputes fo which you are required to submit to a matatoy administrative proceeding. These proceedings will be conducted befoe one of the administrative-dispute-resolution Serbisyo providers listed dito (each, a "Provider").

1. Applicable Disputes. You are required to submit to a matatoy 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. iyong domain name is identical o confusingly similar to a trademark o Serbisyo mark in which the complainant has rights; at

2. you have no rights o legitimate interests in respect of the domain name; at

3. iyong domain name has been magparehistroed at 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 Pagpaparehistro at Use in Mababa Faith. Fo 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 at use of a domain name in bad faith:

1. circumstances indicating that you have magparehistroed o you have acquired the domain name primarily fo the purpose of selling, renting, o otherwise transferring the domain name registration to the complainant who is the owner of the trademark o Serbisyo mark o to a competito of that complainant, fo valuable consideration in excess of iyong documented out-of-pocket costs directly related to the domain name; o

2. you have magparehistroed the domain name in oder to nakaraanent the owner of the trademark o Serbisyo mark from reflecting the mark in a coresponding domain name, provided that you have engaged in a pattern of such conduct; o

3. you have magparehistroed the domain name primarily fo the purpose of disrupting the business of a competito; o

4. by using the domain name, you have intentionally attempted to attract, fo commercial gain, Internet users to iyong web site o other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsoship, affiliation, o endosement of iyong web site o location o of a product o Serbisyo on iyong web site o location.

3. How to Demonstrate Your Rights to at Legitimate Interests in the Domain Name in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how iyong 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 iyong rights o legitimate interests to the domain name fo purposes of Paragraph 4(a)(ii):

1. befoe any notice to you of the dispute, iyong use of, o demonstrable preparations to use, the domain name o a name coresponding to the domain name in connection with a bona fide offering of goods o Serbisyos; o

2. you (as an individual, business, o other oganization) have been commonly kngayonn by the domain name, even if you have acquired no trademark o Serbisyo mark rights; o

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

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

7. Fees. Lahat fees charged by a Provider in connection with any dispute befoe an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wdito you elect to expat 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 at the complainant.

8. Aming Involvement in Administrative Proceedings. We do not, at will not, participate in the administration o conduct of any proceeding befoe 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 befoe an Administrative Panel shall be limited to requiring the cancellation of iyong domain name o the transfer of iyong domain name registration to the complainant.

10. Hinditification at Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a domain name you have magparehistroed with us. Lahat decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact potions of its decision.

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

5. Lahat other disputes at litigation

Lahat other disputes between you at any party other than us regarding iyong domain name registration that are not brought pursuant to the matatoy administrative proceeding provisions of Paragraph 4 shall be resolved between you at such other party through any court, arbitration o other proceeding that may be available.

6. Aming involvement in disputes

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

7. Maintaining status quo

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

8. Transfers during a dispute

Transfers of a Domain Name to a Bago Holder

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

Changing Registrars

You may not transfer iyong domain name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 o fo 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 iyong domain name registration to another registrar during a pending court action o arbitration, provided that the domain name you have magparehistroed with us shall continue to be subject to the proceedings commenced against you in accodance with the terms of this Policy. In the event that you transfer a domain name registration to us during the pendency of a court action o arbitration, such dispute shall remain subject to the domain name dispute policy of the registrar from which the domain name registration was transferred.

9. Policy modifications

We reserve the right to modify this Policy at any time with the permission of ICANN. We will post our revised Policy at this location at least thirty (30) calendar days befoe it becomes effective. Unless this Policy has already been invoked by the submission of a complaint to a Provider, in which event the version of the Policy in effect at the time it was invoked will apply to you until the dispute is over, all such changes will be binding upon you with respect to any domain name registration dispute, whether the dispute arose befoe, on o after the effective date of our change. In the event that you object to a change in this Policy, iyong sole remedy is to cancel iyong domain name registration with us, provided that you will not be entitled to a refund of any fees you paid to us. The revised Policy will apply to you until you cancel iyong domain name registration.

• The exact domain name.
• The requesto's identity at contact infomation.
• The nature at type of the requesto, including whether the requesto is an individual, legal entity, law enfocement agency, government authoity, intellectual property representative, cybersecurity professional, consumer protection oganization, o another type of oganization.
• Wdito the request is submitted by a representative acting on behalf of another person o entity, a Power of Satoney statement o similar documentation evidencing the representative's authoization to act on the requesto's behalf, wdito applicable at relevant.
• A list of the specific registration data elements requested.
• The purpose of the request.
• Infomation about the legal rights of the requesto at the specific rationale at basis fo the request.
• Whether confidentiality is requested.
• Any suppoting legal process, court oder, subpoena, authoization, o 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 Terminos of Use") govern iyong use of any AI products, features, Serbisyos at/o tools offered by NiceNIC.NET.

2. Content

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

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

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

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

6) By using the AI Services, you understat at agree:

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

B. You must evaluate Output fo accuracy at appropriateness fo iyong use case, including using human review as appropriate, befoe using o sharing Output from the AI Services.

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

D. Aming AI Services may provide incomplete, incorect, o offensive Output that does not represent NiceNIC.NET’s views. Kung Output references any third party products o Serbisyos, it doesn’t mean the third party endoses o is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users at the AI Services may generate the same o similar Outputs fo other users.

8) NiceNIC.NET may use technology provided by third-party Serbisyo providers to provide AI Services. Hinditwithstating anything to the contrary contained ditoin, you authoize NiceNIC.NET at such third-party Serbisyo providers to stoe at use iyong Input fo the purposes of providing you with the AI Services, to review Inputs at Outputs fo abuse o misuse, at to develop at improve the Serbisyos at products of NiceNIC.NET at such Serbisyo providers, including as part of the design, training at development process fo machine learning models.

3. Terminoination at Suspension

Terminoination. We reserve the right to suspend o terminate iyong access to our AI Services o delete iyong account if we determine:

1) You breached these AI Terminos of Use.

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

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

4. Disclaimers

YOU SPECIFICALLY ACKNOWLEDGE AND AGREE THAT OUTPUTS OF THE AI SERVICES HAVE NOT BEEN REVIEWED FO ACCURACY, BIAS, EXPLAINABILITY O INTELLECTUAL PROPERTY RIGHTS CLEARANCE. NiceNIC.NET MAKES NO REPRESENTATION, WARRANTY O GUARANTEE AS TO THE ACCURACY, RELIABILITY, O ERRO-FREE PERFOMANCE OF THE AI SERVICES, INCLUDING (WITHOUT LIMITATION) WHETHER OUTPUTS MAY INFRINGE, MISAPPROPRIATE O VIOLATE ANY THIRD-PARTY INTELLECTUAL PROPERTY RIGHTS.

YOU ACCEPT AND AGREE THAT ANY USE OF OUTPUTS FROM OUR AI SERVICE IS AT YOUR SOLE RISK AND YOU WILL NOT RELY ON OUTPUT AS A SOLE SOURCE OF TRUTH O FACTUAL INFOMATION, O AS A SUBSTITUTE FO PROFESSIONAL ADVICE.

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

5. Limitation on Liability

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

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

In the event that a Transfer Makipag-ugnayan listed in the Whois has not confirmed their request to transfer with the Registrar of Recod at the Registrar of Recod has not explicitly denied the transfer request, the default action will be that the Registrar of Recod must allow the transfer to proceed.

Upon denying a transfer request fo any of the following reasons, the Registrar of Recod must provide the Magrehistroed Pangalan Holder at the potential Gaining Registrar with the reason fo denial. The Registrar of Recod may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court oder by a court of competent jurisdiction
• Reasonable dispute over the identity of the Magrehistroed Pangalan Holder o Administrative Makipag-ugnayan
• Hindi payment fo nakaraanious registration period (including credit card charge-backs) if the domain name is past its expiration date o fo nakaraanious o current registration periods if the domain name has not yet expired. In all such cases, however, the domain name must be put into "Registrar Hold" status by the Registrar of Recod prio to the denial of transfer.
• Express written objection to the transfer from the Transfer Makipag-ugnayan. (e.g. - email, fax, paper document o other processes by which the Transfer Makipag-ugnayan has expressly at voluntarily objected through opt-in means)
• A domain name was already in “lock status” provided that the Registrar provides a readily accessible at reasonable means fo the Magrehistroed Pangalan Holder to remove the lock status.
• A domain name is in the first 60 days of an initial registration period.
• A domain name is within 60 days (o a lesser period to be determined) after being transferred (apart from being transferred back to the oiginal Registrar in cases wdito both Registrars so agree at/o wdito a decision in the dispute resolution process so directs).

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

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

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

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

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

This Agreement constitutes the entire agreement between the parties concerning the subject matter ditoin at supersedes all prio understatings at agreements between the parties, whether written o oal, regarding the subject matter ditoin. Any of the provisions of this Agreement which are determined to be invalid o unenfoceable in any jurisdiction shall be ineffective to the extent of such invalidity o unenfoceability in such jurisdiction, without rendering invalid o unenfoceable the remaining provisions ditoof o affecting the validity o unenfoceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach o violation of any provision of this Agreement will not constitute o be construed as a waiver of any subsequent breach o violation of that provision o as a waiver of any breach o violation of any other provision of this Agreement. The headings contained in this Agreement are fo convenience only at shall not affect meaning o interpretation of this Agreement.

25. Hinditices
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 accodance with the Account at/o WHOIS infomation you have provided.

26. Governing Law
This Agreement at its subject matter shall be governed in accodance with the laws of Hong Kong at subject to the exclusive jurisdiction of the Hong Kong courts without regard to conflict of laws at principles contained tditoin with the exception of disputes related to this Agreement which fall under UDRP, URS, o similar dispute resolution process as defined by various Registry policies incopoated o made reference to ditoin.

1.3 The Registrant ackngayonledges at agrees that the Registrar shall monito the status of Mga Domain Name magparehistroed through the Registrar at shall, at its own initiative o on receipt of complaint, conduct checks to verify whether a Domain Name is being used in connection with phishing o "spam" advertising. The Registrar shall delete o suspend a Domain Name if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government o law enfocement authoity (including without limitation the Hong Kong Police Foce o the Office of Telecommunications Authoity) that the use of the Domain Name is in breach of any laws, directives, guidelines, codes of practice o regulations issued by such local authoities, o if, in HKIRC's reasonable belief, the continuation of registration of the Domain Name o the operation of web site referenced   by the Domain Name is likely to damage o adversely affect the goodwill, reputation at operation of HKIRC o the domain name industry in Hong Kong, o may expose HKIRC to risks of third party claims o civil o criminal prosecution.

Fo moe infomation about .HK domain registration, please refer to the latest version of HKIRC Pagpaparehistro Policies https://www.hkirc.hk/upload/page/38/pdf_1/5e6b172e68b29.pdf

5.2 Any decision made by an arbitration panel duly appointed by a dispute resolution Serbisyo provider shall be final at binding on the Registrant at 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 at non-statutoy copoation designated by the Hong-Kong Government to administer the registration of Internet domain names under .hk at .香港 country-code top level domains. Fo any comments o complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find dito useful infomation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppot/domain_dispute_policies_at_procedures/domain_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppot/domain_dispute_policies_at_procedures/rules_of_procedures/; o Email address: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant ackngayonledges that the Registrar at HKIRC rely on all representations made at warranties given by the Registrant in determining if the application fo a Domain Name should be approved.

    Fo moe infomation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domain_policies/EN_Domain_Pangalan_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. Hindiw that you have met the requirements of ICANN, our team is looking foward to assisting you in completing the Verisign certification process so you can quickly begin magparehistroing .com at .net domain names. We hope this suppot will prove to be helpful in reducing the investment of iyong internal resources at time."

PIR:
"ICANN has infomed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed iyong ICANN accreditation to become a registrar at wish to partner with us by becoming an .ORG accredited registrar."

Telnic:
"We received notification from ICANN that you have added the .tel appendix to iyong agreement with them. Tdito hasn't been a better time to become involved with .tel domains at we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on iyong recent ICANN Akreditasyon..."

Neustar:

"We have been notified that iyong company is ngayon ICANN-accredited as a .BIZ registrar.  Neustar looks foward to getting iyong company up at running as soon as possible!"

Higit Pa registries will be notified by ICANN fo the coresponding domain names signed in the RAA in the susunod days, we NiceNIC have been staying fo the disposal of sign-up/accreditation process, striving to save time at expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a moe competitive level. Detalyeed infomation 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"), at dedicated to offer clients easy to navigate, fast to locate Serbisyos in domain name registration, web hosting bumili, 1 to 1 customer suppot.

Stating at the peak of internet infrastruture, we firstly need to appreciate every client, at every website viewer who ever stayed dito, without iyong persistant suppot at comprehension, we are nothing, hope 2012 will bring you at iyong family lucky, happy, healthy life.

Reference links:

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

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

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

ZhuHai NaiSiNiKe Infomation Technology Co Ltd.

2009

China

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

Lahat the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infomation 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 fo Enfocement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent at neutral third party that is neither associated no affiliated with either Registrar involved in the dispute o the Registry Operato under which the disputed domain name is magparehistroed. ICANN shall have the authoity to accredit one o moe independent at neutral Dispute Resolution Providers accoding to criteria developed in accodance with this Dispute Resolution Policy.

1.4 FOA

     Fom of Authoization - The statardized fom of consent that the Gaining Registrar at Registrar of Recod are required to use to obtain authoization from the Registrant o Administrative Makipag-ugnayan in oder to properly process the transfer of domain name sponsoship from one Registrar to another.

1.5 Gaining Registrar

     The Registrar that submitted to the Registry the request fo the transfer of a domain sponsoship from the Registrar of Recod.

1.6 Registrar of Recod

     The Registrar of Recod fo a domain name fo which the Registry received a transfer of sponsoship request.

1.7 Registrant

     The Registrant is the individual o oganization that magparehistros a specific domain name. This individual o oganization holds the right to use that specific domain name fo a specified period of time, provided certain conditions are met at the registration fees are paid. This person o oganization is the "legal entity" bound by the terms of the relevant Serbisyo agreement with the Registry operato fo the TLD in question.

1.8 Registry (Registry Operato)

     The oganization authoized by ICANN to provide registration Serbisyos fo a given TLD to ICANN-accredited Registrars.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operato, in the case of First Antas disputes (as set foth below), o 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 at shall cover topics such as fees, wod at page limits at guidelines, the means fo communicating with the Provider, at the fom of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponsoship of Pagpaparehistros between Registrars which is in foce as part of the Registry-Registrar Agreement executed between a Registrar at the Registry, as well as the Registrar Akreditasyon Agreement which is executed between ICANN at all ICANN- accredited registrars.

2. Dispute Resolution Process

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

2.1 First Antas - Registry Operato

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

2.2 Second-Antas - Dispute Resolution Panel

     The primary intent of this step is to provide a means fo 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 wdito a Registrar of Recod 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 wdito a Gaining Registrar alleges that a transfer should have taken place, the date in which the NACK (as defined below) was received by the Registry, shall be deemed the date in which the "alleged violation" took place.

3. Dispute Procedures at the First Antas (Registry)

3.1 Registrar files a Request fo Enfocement with the applicable Registry Operato

     3.1.1 Either the Gaining o Registrar of Recod ("Filing Registrar") may submit a Request fo Enfocement. This must be done in accodance with the Supplemental Rules adopted by the applicable Registry Operato.

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

3.1.4 The Request fo Enfocement shall annex the following documentary evidence (as applicable at available) in electronic fom if possible, together with a schedule indexing such evidence:
  (i) Fo the Gaining Registrar:
      a. Completed Fom of Authoization ("FOA")
      b. Copy of the Whois output fo the date transfer was initiated, which was used to identify the authoized Transfer Makipag-ugnayans
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body o court oder in cases when the Registrant of Recod is being changed simultaneously with a Registrar Transfer
      e. Copies of all communications made to the Registrar of Recod with regard to the applicable transfer request along with any responses from the Registrar of Recod
  (ii) Fo the Registrar of Recod:
      a. Completed FOA from Registrar of Recod if applicable
      b. Copy of the Whois output fo the date the transfer was initiated
      c. Relevant histoy of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court oder;
• Registrant o administrative contact identity dispute in accodance with Section 4 [Registrar of Recod Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the Magrehistroed Pangalan Holder o Administrative Makipag-ugnayan;
• LOCK status along with proof of a reasonable means fo the registrant to remove LOCK status as per Section __of Exhibit __ to this Agreement;
• domain name within 60 days of initial registration; o
• domain name within 60 days of a prio transfer.

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

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

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

3.2.2 Sa the request of the Respondent, the Registry Operato may, in exceptional cases, extend the period of time fo the filing of the response, but in no case may the extension be moe 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 Operato.

3.2.3 Kung a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operato shall decide the dispute based upon the Request fo Enfocement.

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

3.3.1 Kung the data included in the Request fo Enfocement does not match the data listed in the authoitative Whois, the Registry Operato must contact each Registrar at require additional documentation.

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

3.3.3 In the case wdito a Registrar of Recod denies a request fo a domain name transfer ("NACKs"), the Registrar of Recod must provide evidence of one of the factos fo which it is allowed to NACK. Kung the Registrar of Recod cannot provide evidence that demonstrates any of the factos, at the Gaining Registrar provides to the Registry a complete FOA with data matching that contained within the authoitative Whois database, then the transfer must be approved to be processed.

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

3.4 Fees fo First-Antas Dispute Resolution Service

3.4.1 Tdito is no filing fee assessed to the Filing Registrar at the time the Request fo Enfocement is submitted to the Registry Operato.

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

3.5 Availability of Court Proceedings

      The procedures set foth above shall not nakaraanent a Registrar from submitting a dispute to a court of competent jurisdiction fo independent resolution befoe such an administrative proceeding is commenced o after such proceeding is concluded. Kung a Registry Operato decides a domain name registration should be transferred (either to the Gaining Registrar, o alternatively, back from the Gaining Registrar to the Registrar of Recod), the Registry will wait fourteen (14) calendar days after it is infomed of the decision befoe implementing that decision. The Registry will then implement the decision unless it has received during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted domain name(s). Kung such documentation is received by the Registry Operato within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operato that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operato that the lawsuit has been dismissed o withdrawn; o (iii) the Registry Operato receives a copy of an oder from such court.

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

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

      (i) A Filing Registrar may elect to skip the First-Antas dispute process at Registry level at submit a Request fo Enfocement directly with a Dispute Resolution Provider;
      (ii) The non-nakaraanailing Registrar in a First-Antas dispute proceeding may submit an appeal of the applicable Registry Operato's decision to the Dispute Resolution Provider. Magdagdagitionally, in the case wdito the result in the First-Antas dispute process is a "no-decision," either Registrar may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request fo Enfocement

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

4.3 Appeal of First Antas Dispute Decision o Registry Operato Finding of "Hindi-Decision."

4.3.1 In the event that the Registrar which does not nakaraanail in the First-Antas dispute is dissatisfied by the Registry-Operato's decision, such Registrar may file an appeal with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-Antas decision was issued.

4.3.2 In the event that the Registry Operato issues a finding of "no-decision" in accodance with Section 3.3.4 above, either Registrar may file an appeal of such decision with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-Antas decision was issued.

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

4.3.4 The Appellant shall submit the Appeal in electronic fom at shall:
     (i) Request that the Appeal be submitted fo decision in accodance with the Policy at these Rules;
     (ii) Provide the name, postal at e-mail addresses, at the telephone at telefax numbers of the Appellant at of any representative authoized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
     (iii) Provide the name of the Appellee at all infomation (including any postal at e-mail addresses at telephone at telefax numbers) kngayonn to Appellee regarding how to contact Appellee o any representative of Appellee, including contact infomation based on pre-Request fo Enfocement at pre-Appeal dealings;
     (iv) Specify the domain name(s) that is/are the subject of the Appeal;
     (v) Specify the incident(s) which gave rise to the dispute;
     (vi) State the basis fo such appeal, including specific responses to the findings of the Registry Operato in the First-Antas Dispute process. (This potion of the response shall comply with any wod o page limit set foth in the Dispute Resolution Provider's Supplemental Rules);
     (vii) Specify, in accodance with the Policy, the remedies sought;
     (viii) Identify any other related legal proceedings kngayonn to the Appellant that have been commenced o terminated in connection with o relating to any of the domain name(s) that are the subject of the complaint;
      (ix) State that a copy of the Appeal, together with the cover sheet as prescribed by the Dispute Resolution Provider's Supplemental Rules, has been sent o transmitted to the Appellee; at
      (x) Conclude with the following statement followed by the signature of the Appellant o its authoized representative:
  "Appellant agrees that its claims at remedies concerning the registration of the domain name, the dispute, o the dispute's resolution shall be solely against the Appellee at waives all such claims at remedies against the Dispute Resolution Provider at the Registry Operato as well as their directos, officers, employees, at agents, except in the case of deliberate wrongdoing o gross negligence."
  "Appellant certifies that the infomation contained in this Appeal is to the best of Appellant's kngayonledge complete at accurate, that this Appeal is not being presented fo any improper purpose, such as to harass, at that the assertions in this Appeal are warranted under this Policy at under applicable law, as it ngayon exists o as it may be extended by a good-faith at reasonable argument."

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

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

• Approval of a Transfer
• Denial of the Transfer (o odering the domain name be returned to the Registrar of Recod in cases wdito a Transfer has already occurred)

4.4 Fees fo Second-Antas Dispute Resolution Service

4.4.1 In the case of either a Request fo Enfocement o an Appeal filed at the Second Antas, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms at conditions governing the actual payment of such fees shall be included in the Dispute Resolution Provider's Supplemental Rules.

4.4.2 In the event that the Filing Registrar o Appellant, whichever applicable, does not nakaraanail in a Second-Antas dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

4.4.3 In the event that the Filing Registrar o Appellant, whichever applicable, nakaraanails in a Second-Antas dispute, the Respondent o Appellee, whichever applicable, must submit to the Dispute Resolution Provider, the Filing Fees within fourteen (14) calendar days after such decision. In such an event, the Dispute Resolution Provider shall refund to the Filing Registrar o Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent o Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accodance 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 foth above shall not nakaraanent a Registrar from submitting a dispute to a court of competent jurisdiction fo independent resolution befoe such administrative proceeding is commenced o after such proceeding is concluded. Kung a Dispute Resolution Panel decides a domain name registration should be transferred (either to the Gaining Registrar, o alternatively, back from the Gaining Registrar to the Registrar of Recod), such Registrar will wait fourteen (14) calendar days after it is infomed of the decision befoe implementing that decision. The Registry will then implement the decision unless it has received from either of the parties to the dispute during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted domain name(s). Kung 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 o withdrawn; o (iii) a copy of an oder from such court dismissing the lawsuit o odering certain actions with respect to the domain name.

1. Registrar Requirements

     Magrehistroed Pangalan Holders must be able to transfer their domain name registrations between Registrars provided that the Gaining Registrar's transfer process meets the minimum statards of this policy at that such transfer is not prohibited by ICANN o Registry policies. Inter-Registrar domain name transfer processes must be clear at concise in oder to avoid confusion. Further, Registrars should make reasonable effots to infom Magrehistroed Pangalan Holders of, at provide access to, the published documentation of the specific transfer process employed by the Registrars.

1.1 Transfer Authoities

     The Administrative Makipag-ugnayan at the Magrehistroed Pangalan Holder, as listed in the Losing Registrar's o applicable Registry's (wdito available) publicly accessible WHOIS Serbisyo are the only parties that have the authoity to approve o deny a transfer request to the Gaining Registrar. In the event of a dispute, the Magrehistroed Pangalan Holder's authoity supersedes that of the Administrative Makipag-ugnayan.
Registrars may use Whois data from either the Registrar of Recod o the relevant Registry fo the purpose of verifying the authenticity of a transfer request; o from another data source as determined by a consensus policy.

2. Gaining Registrar Requirements

Fo each instance wdito a Magrehistroed Pangalan Holder requests to transfer a domain name registration to a different Registrar, the Gaining Registrar shall:
      2.1 Obtain express authoization from either the Magrehistroed Pangalan Holder o the Administrative Makipag-ugnayan (ditoafter, "Transfer Makipag-ugnayan"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrar from the Transfer Makipag-ugnayan.

     2.1.1 The authoization must be made via a valid Statardized Fom of Authoization (FOA). Tdito are two different FOA's available at the ICANN website. The FOA labeled "Initial Authoization fo Registrar Transfer" must be used by the Gaining Registrar to request an authoization fo a registrar transfer from the Transfer Makipag-ugnayan. The FOA labeled "Kumpirmahination of Registrar Transfer Request" may be used by the Registrar of Recod to request confirmation of the transfer from the Transfer Makipag-ugnayan.
The FOA shall be communicated in English, at any dispute arising out of a transfer request shall be conducted in the English language. Registrars may choose to communicate with the Transfer Makipag-ugnayan in additional languages. However, Registrars choosing to exercise such option are responsible fo the accuracy at completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Registrar relies on a physical process to obtain this authoization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Makipag-ugnayan at further that it is accompanied by a physical copy of the Registrar of Recod's Whois output fo the domain name in question.

     2.1.2.1 Kung the Gaining Registrar relies on a physical authoization process, then the Gaining Registrar assumes the burden of obtaining reliable evidence of the identity of the Transfer Makipag-ugnayan at maintaining appropriate recods proving that such evidence was obtained. Further the Gaining Registrar also assumes the burden fo ensuring that the entity making the request is indeed authoized to do so. The acceptable foms of physical identity are:

• Hinditarized statement
• Valid Drivers license
• Pasaporte
• Article of Incopoation
• Military ID
• State/Government issued ID
• Birth Certificate

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

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

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

     2.2 Request, by the transmission of a "transfer" commat as specified in the Registrar Para saol Kit, that the Registry Operato database be changed to reflect the new Registrar.

     2.2.1 Transmission of a "transfer" commat constitutes a representation on the part of the Gaining Registrar that the requisite authoization has been obtained from the Transfer Makipag-ugnayan listed in the authoitative Whois database.

     2.2.2 The Gaining Registrar is responsible fo validating the Magrehistroed Pangalan Holder requests to transfer domain names between Registrars. However, this does not preclude the Registrar of Recod from exercising its option to independently confirm the Magrehistroed Pangalan Holder's intent to transfer its domain name to the Gaining Registrar in accodance with Section 3 of this policy.

3. Obligations of the Registrar of Recod

     A Registrar of Recod can choose independently to confirm the intent of the Magrehistroed Pangalan Holder when a notice of a pending transfer is received from the Registry. The Registrar of Recod must do so in a manner consistent with the statards set foth in this agreement pertaining to Gaining Registrars. In oder to ensure that the fom of the request employed by the Registrar of Recod is substantially administrative at infomative in nature at clearly provided to the Transfer Makipag-ugnayan fo the purpose of verifying the intent of the Transfer Makipag-ugnayan, the Registrar of Recod must use the FOA.

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

1. Evidence of fraud
2. UDRP action
3. Court oder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Magrehistroed Pangalan Holder o Administrative Makipag-ugnayan
5. Hindi payment fo nakaraanious registration period (including credit card charge-backs) if the domain name is past its expiration date o fo nakaraanious o current registration periods if the domain name has not yet expired. In all such cases, however, the domain name must be put into "Registrar Hold" status by the Registrar of Recod prio to the denial of transfer.
6. Express written objection to the transfer from the Transfer Makipag-ugnayan. (e.g. - email, fax, paper document o other processes by which the Transfer Makipag-ugnayan has expressly at voluntarily objected through opt-in means)
7. A domain name was already in “lock status” provided that the Registrar provides a readily accessible at reasonable means fo the Magrehistroed Pangalan Holder to remove the lock status.
8. A domain name is in the first 60 days of an initial registration period.
9. A domain name is within 60 days (o a lesser period to be determined) after being transferred (apart from being transferred back to the oiginal Registrar in cases wdito both Registrars so agree at/o wdito a decision in the dispute resolution process so directs).

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

• Hindinpayment fo a pending o future registration period
• Hindi response from the Magrehistroed Pangalan Holder o Administrative Makipag-ugnayan.
• Domain name in Registrar Lock Status, unless the Magrehistroed Pangalan Holder is provided with the reasonable oppotunity at ability to unlock the domain name prio to the Transfer Request.
• Domain name registration period time constraints, other than during the first 60 days of initial registration o during the first 60 days after a registrar transfer.
• General payment defaults between Registrar at business partners / affiliates in cases wdito the Magrehistroed Pangalan Holder fo the domain in question has paid fo the registration.

     The Registrar of Recod has other mechanisms available to collect payment from the Magrehistroed Pangalan Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrar of Recod must not employ transfer processes as a mechanism to secure payment fo Serbisyos from a Magrehistroed Pangalan Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fo nakaraanious registration period(s) if the transfer is requested after the expiration date, o
     (ii) In the case of non-payment of the current registration period, if transfer is requested befoe the expiration date.

4. Registrar Coodination

     Each Registrar is responsible fo keeping copies of documentation, including the FOA at the Transfer Makipag-ugnayans response tditoto, that may be required fo filing at suppoting a dispute under the dispute resolution policy. Gaining Registrars must maintain copies of the FOA as received from the Transfer Makipag-ugnayan as per the statard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registrar at the Registrar of Recod must provide the evidence relied on fo the transfer during at after the applicable inter-registrar domain name transaction(s). Such infomation must be provided when requested by, at only by, the other Registrar that is party to the transfer transaction. Magdagdagitionally, ICANN, the Registry Operato, a court o authoity with jurisdiction over the matter o a third party dispute resolution panel may also require such infomation within five (5) days of the request.

     The Gaining Registrar must retain, at produce pursuant to a request by a Losing Registrar, a written o electronic copy of the FOA. In instances wdito the Registrar of Recod has requested copies of the FOA, the Gaining Registrar must fulfill the Registrar of Recods request (including providing the attendant suppoting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fo reversal by the Registry Operato o the Dispute Resolution Panel in the event that a transfer complaint is filed in accodance with the requirements of this policy.

     Kung either a Registrar of Recod o a Gaining Registrar does not believe that a transfer request was hatled in accodance with the provisions of this policy, then the Registrar may initiate a dispute resolution procedure as set foth in Section C of this policy.

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

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

     Registrars may not employ any mechanism fo complying with a Magrehistroed Pangalan Holder's request to obtain the applicable "AuthInfo Code" that is moe restrictive than the mechanisms used fo changing any aspect of the Magrehistroed Pangalan Holder's contact o name server infomation.

     The Registrar of Recod must not refuse to release an "AuthInfo Code" to the Magrehistroed Pangalan Holder solely because tdito is a dispute between the Magrehistroed Pangalan Holder at the Registrar over payment.

Registrar-generated "AuthInfo" codes must be unique on a per-domain basis.
     The "Auth-Info" codes must be used solely to identify a Magrehistroed Pangalan Holder, wditoas the FOA's still need to be used fo authoization o confirmation of a transfer request, as described in Section 2 at Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commat from the Gaining Registrar, Registry Operato will transmit an electronic notification to both Registrars. In the case of those Registries that use electronic mail notifications, the response notification may be sent to the unique email address established by each Registrar fo the purpose of facilitating transfers.

     The Registry Operato shall complete the requested transfer unless, within five (5) calendar days, Registry Operato receives a NACK protocol commat from the Registrar of Recod.
When the Registry's database has been updated to reflect the change to the Gaining Registrar, Registry Operato will transmit an electronic notification to both Registrars. The notification may be sent to       the unique email address established by each Registrar fo the purpose of facilitating transfers o such other email address agreed to by the parties.
The Registry Operato shall undo a transfer if, after a transfer has occurred, the Registry Operato receives one of the notices as set foth below. In such case, the transfer will be reversed at the domain name reset to its oiginal state. The Registry Operato 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 Operato must undo the transfer within fourteen calendar days unless a court action is filed. The notice required shall be one of the following:
     i. Agreement of the Registrar of Recod at the Gaining Registrar sent by email, letter o fax that the transfer was made by mistake o was otherwise not in accodance with the procedures set foth in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; o
     iii. Order of a court having jurisdiction over the transfer.

7. Recods of Pagpaparehistro

     Each Registrar shall require its customer, the Magrehistroed Pangalan Holder, to maintain its own recods appropriate to document at prove the initial domain name registration date.

8. Effect on Termino of Pagpaparehistro

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

B. ICANN-Approved Transfers

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

C. Transfer Dispute Resolution Policy

     Procedures fo hatling disputes concerning inter-registrar transfers are set foth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatos at ICANN accredited Registrars.

We respect iyong individual privacy. That is why we have adopted this Patakaran sa Privacy, which embodies our commitment to the protection of iyong privacy through additonce to fair electronic infomation practices. This Patakaran sa Privacy puts you, the individual, in control of how iyong personal infomation is processed, at you have our promise that we will not electronically process iyong personal infomation in any way that is incompatible with this Patakaran sa Privacy.

This Patakaran sa Privacy protects iyong privacy by:

4. How We Put Infomation Para sa Good Use