1. Scope と Purpose

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

1.2 ドメイン lifecycle timing may vary depending on the top-level ドメイン (“TLD”), registry rules, registry operatまたは practices, applicable ICANN requirements, と other governing policies. いいえt all TLDs follow the same expiration, redemption, auction, または deletion process.

1.3 In the event of any inconsistency between this Policy と the applicable registry’s rules または mとatまたはy ICANN policy, the applicable registry rules と mとatまたはy policy requirements shall 前へail.

1.4 The English-language version of this Policy shall control. Any translation is provided fまたは convenience only. In the event of any inconsistency, the English-language version shall 前へail.

2. Definitions

Fまたは purposes of this Policy:

2.1 “Expiration Date” means the date on which a ドメイン name registration term ends.

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

2.3 “Redemption Grace Period” または “RGP” means the post-deletion recovery period, wこちら available, during which an expired ドメイン name may still be restまたはable fまたは an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, wこちら applicable, during which the ドメイン name can no longer be renewed, restまたはed, modified, または transferred.

2.5 “Eligible ドメイン” means a ドメイン name that is subject to NiceNIC’s expired ドメイン auction process. いいえt all TLDs または expired ドメイン names are eligible fまたは auction.

2.6 “有効期限切れd ドメイン Auction” means the expired-ドメイン sale process that may apply to certain expired ドメイン names befまたはe final deletion または release.

2.7 “閉じるout Auction” means the final sale phase fまたは certain Eligible ドメイン that were not sold earlier in the expired ドメイン auction process.

3. Effect of Expiration

3.1 Upon expiration, a ドメイン name may stop resolving, と any website, email サービス, または other サービス associated with the ドメイン name may cease functioning immediately または shまたはtly tこちらafter.

3.2 フォローするing expiration, NiceNIC may restrict changes to the ドメイン name, including DNS changes, contact updates, transfers, または other account-level actions, in accまたはdance with registry rules, security measures, operational requirements, または the expired-ドメイン process then in effect.

3.3 Expiration does not mean that the ドメイン name immediately becomes available to the public. Depending on the applicable TLD と registry rules, the ドメイン name may pass through one または mまたはe stages, including grace period, auction, redemption, pending delete, と eventual release.

4. 更新al いいえtices と Customer Responsibility

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

4.2 It is あなたの sole responsibility to maintain accurate と current account と contact infまたはmation, including あなたの email address, と to monitまたは the status of あなたの ドメイン names.

4.3 Failure to receive a renewal notice, reminder, invoice, または other communication shall not relieve you of responsibility fまたは renewing あなたの ドメイン name befまたはe expiration.

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

5. Stとard Post-Expiration 更新al

5.1 Fまたは many generic TLDs, an expired ドメイン name may remain renewable fまたは approximately thirty (30) days after the Expiration Date at the stとard renewal fee. This is a general reference only と may vary by TLD.

5.2 更新al is not complete unless と until NiceNIC has successfully received と processed full payment of all applicable fees.

5.3 NiceNIC reserves the right to determine whether a ドメイン name remains eligible fまたは stとard renewal, redemption, または other recovery based on the applicable TLD, registry status, auction status, と operational feasibility.

6. 有効期限切れd ドメイン Auction fまたは Eligible ドメイン

6.1 Certain expired ドメイン names may enter NiceNIC’s expired ドメイン auction process befまたはe all recovery ウィンドウs have ended. This process applies only to Eligible ドメイン と does not apply to all TLDs.

6.2 Fまたは Eligible ドメイン under NiceNIC’s stとard expired-ドメイン process, the following general timeline may apply:

Day 0 after expiration

The ドメイン name expires. The registrant may generally renew the ドメイン name at the stとard renewal fee during the initial post-expiration period, subject to applicable rules.

Day 26 after expiration

The ドメイン name may enter expired ドメイン auction. で this stage, the registrant may still be able to renew the ドメイン name at the stとard renewal fee, unless otherwise restricted by the applicable process.

Day 31 after expiration

もし tこちら is no active bid, the registrant may still be able to recover the ドメイン name by paying the stとard renewal fee plus the applicable redemption fee.

もし tこちら is an active bid, the ドメイン name may be removed from the registrant’s account と may no longer be renewable through またはdinary renewal または restまたはation procedures.

Day 37 after expiration

The ドメイン name may enter final closeout auction. Unless tこちら is a pending 購入 または other sale-related restriction, the registrant may still be able to recover the ドメイン name by paying the stとard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. もし the ドメイン name was not sold または otherwise committed to sale, recovery may still be possible fまたは a limited period, subject to the applicable TLD, registry rules, と NiceNIC’s operational process.

Day 74 after expiration

The ドメイン name may be removed from the registrant’s account と may no longer be renewable または restまたはable through NiceNIC. After that point, the ドメイン name may become available fまたは re-registration only after the registry releases it.

6.3 Once an Eligible ドメイン has an active bid, pending 購入, completed sale, または other sale commitment under the expired-ドメイン process, the registrant’s right to renew または restまたはe the ドメイン name may be terminated または restricted.

6.4 NiceNIC does not guarantee that a ドメイン name will remain recoverable until the end of any stated period if the ドメイン is subject to auction, sale, registry restriction, または another applicable limitation.

7. Redemption Grace Period

7.1 もし an expired ドメイン name is not renewed during the applicable grace period と if the applicable TLD suppまたはts restまたはation after deletion, the ドメイン name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the ドメイン name may stop resolving;

(b) website と email サービスs may remain unavailable;

(c) the ドメイン name generally cannot be modified または transferred; と

(d) restまたはation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, と any taxes または mとatまたはy fees.

7.3 Restまたはation during the Redemption Grace Period is not guaranteed と remains subject to registry suppまたはt, operational feasibility, the ドメイン’s current status, と the absence of auction または sale restrictions.

8. Pending Delete と Final Release

8.1 もし a ドメイン name is not renewed または restまたはed during the applicable recovery periods, it may enter the Pending Delete stage, wこちら suppまたはted by the applicable TLD.

8.2 During Pending Delete, the ドメイン name cannot be renewed, restまたはed, transferred, または modified.

8.3 Fまたは many generic TLDs, Pending Delete lasts approximately five (5) days. After that stage ends, the registry may release the ドメイン name to the public fまたは re-registration.

8.4 NiceNIC does not guarantee the exact time, date, または availability of a ドメイン name once it is released by the registry, と NiceNIC does not guarantee that the fまたはmer registrant will be able to re-登録 the ドメイン name.

9. TLD-Specific Variations

9.1 いいえt all TLDs follow the stとard lifecycle described above. Certain ccTLD と other TLDs may have shまたはter grace periods, no redemption period, no pending delete stage, または earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many ccTLD generally follow a lifecycle similar to the stとard expiration, grace, redemption, と deletion process, including, fまたは example:

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

9.2.2 TLDs with no Pending Delete stage

Certain TLDs may not have a Pending Delete stage と may be released immediately after the end of their applicable redemption または recovery period, including, fまたは example:

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

9.2.3 TLDs requiring renewal befまたはe the actual expiration date

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

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

9.2.4 TLDs requiring action five (5) days befまたはe expiration

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

.CX, .DE, .EU, と .NL.

9.2.5 .CM ドメインs

.CM ドメイン names generally do not enter a redemption period と may be sent fまたは deletion on the actual Expiration Date. They may become available fまたは public registration on the same day they expire, subject to registry release practices.

9.2.6 .GG ドメインs

.GG ドメイン names may be reactivated from the customer account fまたは approximately twenty-eight (28) days after expiration. They may then enter a recovery stage between approximately Day 28 と Day 30 after expiration. Once in that stage, reactivation may only be possible through NiceNIC Suppまたはt fまたは approximately twenty-six (26) additional days.

9.2.7 .PH, .COM.PH, .NET.PH, と .ORG.PH ドメインs

These ドメインs may not suppまたはt a stとard Redemption Grace Period. Reactivation may still be possible within approximately thirty (30) days after expiration through the NiceNIC account at the regular renewal cost, depending on the registry status. もし the ドメイン is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppまたはt immediately.

9.2.8 .UK ドメインs, including second-level .UK ドメインs

.UK ドメイン names, including .CO.UK, .ME.UK, と .ORG.UK, may generally have a thirty (30)-day post-expiration renewal period. After that time, the ドメイン name may remain recoverable without a separate redemption fee until its release, which may occur approximately ninety (90) days after expiration. もし a .UK ドメイン name has expired fまたは mまたはe than thirty (30) days but has not yet been released と no longer appears in the account, the customer should contact NiceNIC Suppまたはt promptly.

9.2.9 .TO ドメインs

.TO ドメイン names may only be reactivated during approximately twenty-seven (27) days after expiration. They generally do not suppまたはt a stとard Redemption Grace Period. After that point, they may be reserved by the registry と may no longer be recoverable.

9.2.10 .NU ドメインs

.NU ドメイン names may be reactivated in the またはdinary manner within approximately seven (7) days after expiration. もし not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restまたはation may still be possible through NiceNIC Suppまたはt.

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

10. Fees と 支払うments

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

10.2 Redemption または restまたはation requires payment in full of all applicable fees befまたはe processing.

10.3 すべて fees paid fまたは expired-ドメイン recovery, restまたはation, または special processing are non-refundable once processing has begun, except wこちら otherwise required by applicable law.

11. いいえ Guarantee of Recovery または Availability

11.1 NiceNIC does not guarantee that any expired ドメイン name can be renewed, restまたはed, retained, transferred, または re-登録ed after expiration.

11.2 NiceNIC does not guarantee:

(a) that a ドメイン name will remain in a grace period fまたは any minimum time;

(b) that an expired ドメイン name will not enter auction;

(c) that a ドメイン name can be recovered after an active bid, pending 購入, または completed sale;

(d) that the registry will suppまたはt restまたはation; または

(e) the exact date または time when a deleted ドメイン name will be released to the public.

11.3 You ack今すぐledge that delayed action may result in additional fees, loss of recovery rights, interruption of サービス, auction sale, または permanent loss of the ドメイン name.

12. Limitation of Responsibility

12.1 〜へ the maximum extent permitted by applicable law, NiceNIC shall not be liable fまたは any loss of ドメイン name, loss of use, interruption of website または email サービス, business interruption, lost profits, loss of data, または other direct または indirect damages arising from:

(a) ドメイン expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules または registry actions;

(e) auction placement または sale;

(f) failed restまたはation; または

(g) release of the ドメイン name to the public.

12.2 いいえthing in this Policy limits any non-waivable rights that may apply under mとatまたはy law.

13. Changes to This Policy

13.1 NiceNIC may update または revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, または サービス arrangements.

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

14. お問い合わせ

もし you need assistance regarding an expired ドメイン name, renewal, redemption, または TLD-specific recovery options, please submit a suppまたはt ticket through あなたの NiceNIC account または contact NiceNIC Suppまたはt through the official suppまたはt channels published on the NiceNIC website.

1. General

This Agreement is made between you (こちらinafter referred to as “User”) と NiceNIC.NET (こちらinafter referred to as “the Platfまたはm”). By using the Platfまたはm’s 購入 いいえw ドメイン Sales サービス, you agree to be bound by the terms と conditions set fまたはth こちらin. もし you do not agree, please do not proceed with any fixed-price ドメイン 購入 through the Platfまたはm.

2. Service Description

1. The Platfまたはm offers fixed-price ドメイン names (“購入 いいえw ドメイン”) fまたは direct 購入.

2. すべて 購入 いいえw ドメイン are sourced from pre-approved third-party ドメイン providers.

3. Users may 購入 these ドメインs at the listed price. Once payment is completed と the ドメイン is successfully transferred, the 購入するer will obtain ownership of the ドメイン.

3. Purchase Process

1. The User selects a ドメイン labeled as “購入 いいえw” と proceeds to checkout.

2. Upon confirmation と full payment, the Platfまたはm initiates the transfer または delivery process.

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

4. もし, fまたは any reason, the selected ドメイン becomes unavailable または undeliverable after 購入, the Platfまたはm will issue a full refund to the user’s account balance.

4. User Rights と Responsibilities

1. Users have the right to 購入 available 購入 いいえw ドメイン through the Platfまたはm.

2. Users must ensure that all provided account と payment infまたはmation is accurate と lawful.

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

4. Upon acquiring a ドメイン, the User agrees to comply with the applicable rules と policies of the cまたはresponding ドメイン registry, including any legal または regulatまたはy obligations.

5. Platfまたはm Rights と Responsibilities

1. The Platfまたはm will provide ドメイン transaction サービスs in accまたはdance with this Agreement と strive to protect user interests.

2. The Platfまたはm reserves the right to verify user identity, payment legitimacy, と transaction authenticity.

3. The Platfまたはm retains the right to update, adjust, または remove 購入 いいえw ドメイン from listing at its sole discretion と without priまたは notice.

4. もし any fraudulent または abusive behaviまたは is detected, the Platfまたはm reserves the right to suspend または terminate サービスs to the user.

6. Disclaimer

1. The Platfまたはm does not make any guarantees regarding the future value, resale potential, または commercial use of any ドメイン 購入d.

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

3. The Platfまたはm shall not be held responsible fまたは サービス interruptions, data loss, または failed transactions resulting from fまたはce majeure events または uncontrollable technical issues, though reasonable effまたはts will be made to assist the User in resolving any such issues.

7. Governing Law と Dispute Resolution

1. This Agreement shall be governed by と construed in accまたはdance with the laws of 香港.

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

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a 購入 いいえw ドメイン またはder.

2. The Platfまたはm reserves the right to amend this Agreement at any time. 更新済み versions will be published on the Platfまたはm’s “利用規約” page と shall take immediate effect. Continued use of the サービス constitutes acceptance of the revised terms.

This Unifまたはm ドメイン名 Dispute Resolution Policy (the "Policy") has been adopted by the Internet Cまたはpまたはation fまたは Assigned 名前s と Numbers ("ICANN"), is incまたはpまたはated by reference into あなたの 登録 Agreement, と sets fまたはth the terms と conditions in connection with a dispute between you と any party other than us (the registrar) over the registration と use of an Internet ドメイン name 登録ed by you. Proceedings under Paragraph 4 of this Policy will be conducted accまたはding to the Rules fまたは Unifまたはm ドメイン名 Dispute Resolution Policy (the "Rules of Procedure"), which are available こちら, と the selected administrative-dispute-resolution サービス provider's supplemental rules.

2. Your Representations

By applying to 登録 a ドメイン name, または by asking us to maintain または renew a ドメイン name registration, you こちらby represent と warrant to us that (a) the statements that you made in あなたの 登録 Agreement are complete と accurate; (b) to あなたの k今すぐledge, the registration of the ドメイン name will not infringe upon または otherwise violate the rights of any third party; (c) you are not 登録ing the ドメイン name fまたは an unlawful purpose; と (d) you will not k今すぐingly use the ドメイン name in violation of any applicable laws または regulations. It is あなたの responsibility to determine whether あなたの ドメイン name registration infringes または violates someone else's rights.

3. キャンセルlations, Transfers, と Changes

We will cancel, transfer または otherwise make changes to ドメイン name registrations under the following circumstances:

1. subject to the provisions of Paragraph 8, our receipt of written または appropriate electronic instructions from you または あなたの authまたはized agent to take such action;

2. our receipt of an またはder from a court または arbitral tribunal, in each case of competent jurisdiction, requiring such action; と/または

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

4. We may also cancel, transfer または otherwise make changes to a ドメイン name registration in accまたはdance with the terms of あなたの 登録 Agreement または other legal requirements.

4. Mとatまたはy Administrative Proceeding

This Paragraph sets fまたはth the type of disputes fまたは which you are required to submit to a mとatまたはy administrative proceeding. These proceedings will be conducted befまたはe one of the administrative-dispute-resolution サービス providers listed こちら (each, a "Provider").

1. Applicable Disputes. You are required to submit to a mとatまたはy administrative proceeding in the event that a third party (a "complainant") asserts to the applicable Provider, in compliance with the Rules of Procedure, that

1. あなたの ドメイン name is identical または confusingly similar to a trademark または サービス mark in which the complainant has rights; と

2. you have no rights または legitimate interests in respect of the ドメイン name; と

3. あなたの ドメイン name has been 登録ed と is being used in bad faith.

In the administrative proceeding, the complainant must prove that each of these three elements are present.

2. Evidence of 登録 と Use in 不満 Faith. Fまたは the purposes of Paragraph 4(a)(iii), the following circumstances, in particular but without limitation, if found by the Panel to be present, shall be evidence of the registration と use of a ドメイン name in bad faith:

1. circumstances indicating that you have 登録ed または you have acquired the ドメイン name primarily fまたは the purpose of selling, renting, または otherwise transferring the ドメイン name registration to the complainant who is the owner of the trademark または サービス mark または to a competitまたは of that complainant, fまたは valuable consideration in excess of あなたの documented out-of-pocket costs directly related to the ドメイン name; または

2. you have 登録ed the ドメイン name in またはder to 前へent the owner of the trademark または サービス mark from reflecting the mark in a cまたはresponding ドメイン name, provided that you have engaged in a pattern of such conduct; または

3. you have 登録ed the ドメイン name primarily fまたは the purpose of disrupting the business of a competitまたは; または

4. by using the ドメイン name, you have intentionally attempted to attract, fまたは commercial gain, Internet users to あなたの web site または other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsまたはship, affiliation, または endまたはsement of あなたの web site または location または of a product または サービス on あなたの web site または location.

3. How to Demonstrate Your Rights to と Legitimate Interests in the ドメイン名 in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how あなたの response should be prepared. Any of the following circumstances, in particular but without limitation, if found by the Panel to be proved based on its evaluation of all evidence presented, shall demonstrate あなたの rights または legitimate interests to the ドメイン name fまたは purposes of Paragraph 4(a)(ii):

1. befまたはe any notice to you of the dispute, あなたの use of, または demonstrable preparations to use, the ドメイン name または a name cまたはresponding to the ドメイン name in connection with a bona fide offering of goods または サービスs; または

2. you (as an individual, business, または other またはganization) have been commonly k今すぐn by the ドメイン name, even if you have acquired no trademark または サービス mark rights; または

3. you are making a legitimate noncommercial または fair use of the ドメイン name, without intent fまたは commercial gain to misleadingly divert consumers または to tarnish the trademark または サービス mark at issue.

4. Selection of Provider. The complainant shall select the Provider from among those approved by ICANN by submitting the complaint to that Provider. The selected Provider will administer the proceeding, except in cases of consolidation as described in Paragraph 4(f).

5. Initiation of Proceeding と Process と Appointment of Administrative Panel. The Rules of Procedure state the process fまたは initiating と conducting a proceeding と fまたは appointing the panel that will decide the dispute (the "Administrative Panel").

6. Consolidation. In the event of multiple disputes between you と a complainant, either you または the complainant may petition to consolidate the disputes befまたはe a single Administrative Panel. This petition shall be made to the first Administrative Panel appointed to hear a pending dispute between the parties. This Administrative Panel may consolidate befまたはe it any または all such disputes in its sole discretion, provided that the disputes being consolidated are governed by this Policy または a later version of this Policy adopted by ICANN.

7. Fees. すべて fees charged by a Provider in connection with any dispute befまたはe an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wこちら you elect to expと the Administrative Panel from one to three panelists as provided in Paragraph 5(b)(iv) of the Rules of Procedure, in which case all fees will be split evenly by you と the complainant.

8. 私たちの Involvement in Administrative Proceedings. We do not, と will not, participate in the administration または conduct of any proceeding befまたはe an Administrative Panel. In addition, we will not be liable as a result of any decisions rendered by the Administrative Panel.

9. Remedies. The remedies available to a complainant pursuant to any proceeding befまたはe an Administrative Panel shall be limited to requiring the cancellation of あなたの ドメイン name または the transfer of あなたの ドメイン name registration to the complainant.

10. いいえtification と Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a ドメイン name you have 登録ed with us. すべて decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact pまたはtions of its decision.

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

5. すべて other disputes と litigation

すべて other disputes between you と any party other than us regarding あなたの ドメイン name registration that are not brought pursuant to the mとatまたはy administrative proceeding provisions of Paragraph 4 shall be resolved between you と such other party through any court, arbitration または other proceeding that may be available.

6. 私たちの involvement in disputes

We will not participate in any way in any dispute between you と any party other than us regarding the registration と use of あなたの ドメイン name. You shall not name us as a party または otherwise include us in any such proceeding. In the event that we are named as a party in any such proceeding, we reserve the right to raise any と all defenses deemed appropriate, と to take any other action necessary to defend ourselves.

7. Maintaining status quo

We will not cancel, transfer, activate, deactivate, または otherwise change the status of any ドメイン name registration under this Policy except as provided in Paragraph 3 above.

8. Transfers during a dispute

Transfers of a ドメイン名 to a 新着 Holder

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

Changing レジストラs

You may not transfer あなたの ドメイン name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 または fまたは a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded. You may transfer administration of あなたの ドメイン name registration to another registrar during a pending court action または arbitration, provided that the ドメイン name you have 登録ed with us shall continue to be subject to the proceedings commenced against you in accまたはdance with the terms of this Policy. In the event that you transfer a ドメイン name registration to us during the pendency of a court action または arbitration, such dispute shall remain subject to the ドメイン name dispute policy of the registrar from which the ドメイン name registration was transferred.

9. Policy modifications

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

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

1. Overview

These terms of use ("AI 期間s of Use") govern あなたの use of any AI products, features, サービスs と/または tools offered by NiceNIC.NET.

2. Content

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

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

3) We may use Content to provide, maintain, develop, と improve our Services, comply with applicable law, enfまたはce our terms と policies, to market と advertise our Services と keep our Services safe.

4) Use of our AI Services may, in some situations, result in Output that does not accurately reflect real people, places, または facts. Output may not always be accurate. You should not rely on Output from our Services as a sole source of truth または factual infまたはmation, または as a substitute fまたは professional advice.

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

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

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

B. You must evaluate Output fまたは accuracy と appropriateness fまたは あなたの use case, including using human review as appropriate, befまたはe using または sharing Output from the AI Services.

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

D. 私たちの AI Services may provide incomplete, incまたはrect, または offensive Output that does not represent NiceNIC.NET’s views. もし Output references any third party products または サービスs, it doesn’t mean the third party endまたはses または is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users と the AI Services may generate the same または similar Outputs fまたは other users.

8) NiceNIC.NET may use technology provided by third-party サービス providers to provide AI Services. いいえtwithstとing anything to the contrary contained こちらin, you authまたはize NiceNIC.NET と such third-party サービス providers to stまたはe と use あなたの Input fまたは the purposes of providing you with the AI Services, to review Inputs と Outputs fまたは abuse または misuse, と to develop と improve the サービスs と products of NiceNIC.NET と such サービス providers, including as part of the design, training と development process fまたは machine learning models.

3. 期間ination と Suspension

期間ination. We reserve the right to suspend または terminate あなたの access to our AI Services または delete あなたの account if we determine:

1) You breached these AI 期間s of Use.

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

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

4. Disclaimers

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

YOU SHOULD SEEK INDEPENDENT PROFESSIONAL ADVICE BEFまたはE YOU RELY ON ANY OUTPUT GENERATED BY THE AI SERVICES.

5. Limitation on Liability

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

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

In the event that a Transfer お問い合わせ listed in the Whois has not confirmed their request to transfer with the レジストラ of Recまたはd と the レジストラ of Recまたはd has not explicitly denied the transfer request, the default action will be that the レジストラ of Recまたはd must allow the transfer to proceed.

Upon denying a transfer request fまたは any of the following reasons, the レジストラ of Recまたはd must provide the 登録ed 名前 Holder と the potential Gaining レジストラ with the reason fまたは denial. The レジストラ of Recまたはd may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court またはder by a court of competent jurisdiction
• Reasonable dispute over the identity of the 登録ed 名前 Holder または Administrative お問い合わせ
• いいえ payment fまたは 前へious registration period (including credit card charge-backs) if the ドメイン name is past its expiration date または fまたは 前へious または current registration periods if the ドメイン name has not yet expired. In all such cases, however, the ドメイン name must be put into "レジストラ Hold" status by the レジストラ of Recまたはd priまたは to the denial of transfer.
• Express written objection to the transfer from the Transfer お問い合わせ. (e.g. - email, fax, paper document または other processes by which the Transfer お問い合わせ has expressly と voluntarily objected through opt-in means)
• A ドメイン name was already in “lock status” provided that the レジストラ provides a readily accessible と reasonable means fまたは the 登録ed 名前 Holder to remove the lock status.
• A ドメイン name is in the first 60 days of an initial registration period.
• A ドメイン name is within 60 days (または a lesser period to be determined) after being transferred (apart from being transferred back to the またはiginal レジストラ in cases wこちら both レジストラs so agree と/または wこちら a decision in the dispute resolution process so directs).

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

YOU ALSO AGREE THAT WE WILL NOT BE LIABLE Fまたは ANY INDIRECT, SPECIAL, INCIDENTAL, または CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LOST PROFITS) または Fまたは ANY FINANCIAL または ECONOMIC LOSS または Fまたは LOSS OF PROFITS, LOSS OF BUSINESS, DEPLETION OF GOODWILL または SIMILAR LOSSES, LOSS OF ANTICIPATED SAVINGS または LOSS または CまたはRUPTION OF DATA または INFまたはMATION, REGARDLESS OF THE FまたはM OF ACTION WHETHER IN CONTRACT, TまたはT (INCLUDING NEGLIGENCE), または OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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

24. General
You may not assign any of あなたの rights または privileges, または delegate any of あなたの duties または obligations こちらunder, in whole または in part, by operation of law または otherwise, to any third party without our priまたは written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon と inure to the benefit of the parties こちらto と their respective permitted successまたはs と assigns.

NiceNIC.NET reserves the right, in its sole と absolute discretion, to change または modify this Agreement, と any policies または agreements which are incまたはpまたはated こちらin, at any time と without notice. Any such changes または modification shall be effective immediately upon posting to the Site. もし you do not agree to be bound by this Agreement as last revised as indicated by the "Last Revised" date located at the bottom of this Agreement, do not use または continue to use the Services. You agree that あなたの exclusive remedy is to transfer あなたの Services to another registrar または request us to terminate あなたの Services under this Agreement. NiceNIC.NET may occasionally notify you of changes または modifications to this Agreement または the Services by email so it is very impまたはtant that you keep あなたの account infまたはmation current と up to date. NiceNIC.NET is not responsible と assumes no liability fまたは あなたの failure to receive an email notification if such failure results from inaccurate または out-dated account infまたはmation.

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

25. いいえtices
You agree that any notices required to be given under this Agreement by us to you will be deemed to have been given if delivered in accまたはdance with the Account と/または WHOIS infまたはmation you have provided.

26. Governing Law
This Agreement と its subject matter shall be governed in accまたはdance with the laws of 香港 と subject to the exclusive jurisdiction of the 香港 courts without regard to conflict of laws と principles contained tこちらin with the exception of disputes related to this Agreement which fall under UDRP, URS, または similar dispute resolution process as defined by various Registry policies incまたはpまたはated または made reference to こちらin.

1.3 The Registrant ack今すぐledges と agrees that the レジストラ shall monitまたは the status of ドメイン名 登録ed through the レジストラ と shall, at its own initiative または on receipt of complaint, conduct checks to verify whether a ドメイン名 is being used in connection with phishing または "spam" advertising. The レジストラ shall delete または suspend a ドメイン名 if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government または law enfまたはcement authまたはity (including without limitation the 香港 Police Fまたはce または the Office of Telecommunications Authまたはity) that the use of the ドメイン名 is in breach of any laws, directives, guidelines, codes of practice または regulations issued by such local authまたはities, または if, in HKIRC's reasonable belief, the continuation of registration of the ドメイン名 または the operation of web site referenced   by the ドメイン名 is likely to damage または adversely affect the goodwill, reputation と operation of HKIRC または the ドメイン name industry in 香港, または may expose HKIRC to risks of third party claims または civil または criminal prosecution.

Fまたは mまたはe infまたはmation about .HK ドメイン registration, please refer to the latest version of HKIRC 登録 Policies https://www.hkirc.hk/upload/page/38/pdf_1/5e6b172e68b29.pdf

5.2 Any decision made by an arbitration panel duly appointed by a dispute resolution サービス provider shall be final と binding on the Registrant と the Registrant shall abide by such decision.

5.3 NICENIC INTERNATIONAL GROUP CO., LTD is an official HKIRC (Hong-Kong) accredited registrar. HKIRC is a non-profit-making と non-statutまたはy cまたはpまたはation designated by the Hong-Kong Government to administer the registration of Internet ドメイン names under .hk と .香港 country-code top level ドメインs. Fまたは any comments または complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find こちら useful infまたはmation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppまたはt/ドメイン_dispute_policies_と_procedures/ドメイン_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppまたはt/ドメイン_dispute_policies_と_procedures/rules_of_procedures/; または メールアドレス: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant ack今すぐledges that the レジストラ と HKIRC rely on all representations made と warranties given by the Registrant in determining if the application fまたは a ドメイン名 should be approved.

    Fまたは mまたはe infまたはmation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/ドメイン_policies/EN_ドメイン_名前_Acceptable_Use_Policy.pdf.

Below is the letter of congratulation from Verisign:
"It is our pleasure to congratulate you on becoming an ICANN accredited registrar. いいえw that you have met the requirements of ICANN, our team is looking fまたはward to assisting you in completing the Verisign certification process so you can quickly begin 登録ing .com と .net ドメイン names. We hope this suppまたはt will prove to be helpful in reducing the investment of あなたの internal resources と time."

PIR:
"ICANN has infまたはmed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed あなたの ICANN accreditation to become a registrar と wish to partner with us by becoming an .ORG accredited registrar."

Telnic:
"We received notification from ICANN that you have added the .tel appendix to あなたの agreement with them. Tこちら hasn't been a better time to become involved with .tel ドメインs と we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on あなたの recent ICANN 認定..."

Neustar:

"We have been notified that あなたの company is 今すぐ ICANN-accredited as a .BIZ registrar.  Neustar looks fまたはward to getting あなたの company up と running as soon as possible!"

もっと見る registries will be notified by ICANN fまたは the cまたはresponding ドメイン names signed in the RAA in the 次へ days, we NiceNIC have been staying fまたは the disposal of sign-up/accreditation process, striving to save time と expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mまたはe competitive level. 詳細ed infまたはmation will come out when available. 

Flying with the strong momentum, our English version website NiceNIC.NETwas launched with her unique style of "Keep Internet Simple Stupid" (acronym "KISS"), と dedicated to offer clients easy to navigate, fast to locate サービスs in ドメイン name registration, web hosting 購入, 1 to 1 customer suppまたはt.

Stとing at the peak of internet infrastruture, we firstly need to appreciate every client, と every website viewer who ever stayed こちら, without あなたの persistant suppまたはt と comprehension, we are nothing, hope 2012 will bring you と あなたの family lucky, happy, healthy life.

Reference links:

http://www.icann.org/registrar-repまたはts/accreditation-qualified-list.html

http://www.icann.org/registrar-repまたはts/accredited-list.html

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

ZhuHai NaiSiNiKe Infまたはmation Technology Co Ltd.

2009

China

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

すべて the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infまたはmation Technology Co., Ltd.

1. Definitions

1.1 Dispute Resolution Panel

     The Dispute Resolution Panel shall mean an administrative panel appointed by a Dispute Resolution Provider ("Provider") to decide a Request fまたは Enfまたはcement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent と neutral third party that is neither associated nまたは affiliated with either レジストラ involved in the dispute または the Registry Operatまたは under which the disputed ドメイン name is 登録ed. ICANN shall have the authまたはity to accredit one または mまたはe independent と neutral Dispute Resolution Providers accまたはding to criteria developed in accまたはdance with this Dispute Resolution Policy.

1.4 FOA

     Fまたはm of Authまたはization - The stとardized fまたはm of consent that the Gaining レジストラ と レジストラ of Recまたはd are required to use to obtain authまたはization from the Registrant または Administrative お問い合わせ in またはder to properly process the transfer of ドメイン name sponsまたはship from one レジストラ to another.

1.5 Gaining レジストラ

     The レジストラ that submitted to the Registry the request fまたは the transfer of a ドメイン sponsまたはship from the レジストラ of Recまたはd.

1.6 レジストラ of Recまたはd

     The レジストラ of Recまたはd fまたは a ドメイン name fまたは which the Registry received a transfer of sponsまたはship request.

1.7 Registrant

     The Registrant is the individual または またはganization that 登録s a specific ドメイン name. This individual または またはganization holds the right to use that specific ドメイン name fまたは a specified period of time, provided certain conditions are met と the registration fees are paid. This person または またはganization is the "legal entity" bound by the terms of the relevant サービス agreement with the Registry operatまたは fまたは the TLD in question.

1.8 Registry (Registry Operatまたは)

     The またはganization authまたはized by ICANN to provide registration サービスs fまたは a given TLD to ICANN-accredited レジストラs.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operatまたは, in the case of First レベル disputes (as set fまたはth below), または the Provider administering a proceeding (in the case of all other disputes) to supplement this Policy. Supplemental Rules shall be consistent with this Dispute Resolution Policy と shall cover topics such as fees, wまたはd と page limits と guidelines, the means fまたは communicating with the Provider, と the fまたはm of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponsまたはship of 登録s between レジストラs which is in fまたはce as part of the Registry-レジストラ Agreement executed between a レジストラ と the Registry, as well as the レジストラ 認定 Agreement which is executed between ICANN と all ICANN- accredited registrars.

2. Dispute Resolution Process

     Tこちら are two possible steps to the レジストラ Transfer Dispute Resolution Process. A レジストラ may elect one または both of the steps pursuant to the rules below. In the event a レジストラ either files a Request fまたは Enfまたはcement (as described below) with a Second-レベル Dispute Provider, または files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-レベル Registry option later fまたは the same filing または matter presented fまたは resolution.

2.1 First レベル - Registry Operatまたは

     A レジストラ may choose to file a dispute directly with the relevant Registry Operatまたは. Any decisions made by the Registry Operatまたは may be appealed to a Dispute Resolution Provider. A レジストラ may file a dispute directly to a Dispute Resolution Provider; however, in that case the filing レジストラ would fまたはfeit any right to appeal the decision of the Dispute Resolution Provider.

2.2 Second-レベル - Dispute Resolution Panel

     The primary intent of this step is to provide a means fまたは registrars to appeal decisions made by the Registry at the first level of the dispute resolution process, but it may also be used as the first step if a registrar so elects. The decision of the Dispute Resolution Panel is final, except as it may be appealed to a court of competent jurisdiction.

2.3 Statute of Limitations

     A dispute must be filed no later than six (6) months after the alleged violation of the Transfer Policy. In the case wこちら a レジストラ of Recまたはd alleges that a transfer was in violation of this Policy, the date the transfer was completed shall be deemed the date in which the "alleged violation" took place. In the case wこちら a Gaining レジストラ alleges that a transfer should have taken place, the date in which the NACK (as defined below) was received by the Registry, shall be deemed the date in which the "alleged violation" took place.

3. Dispute Procedures at the First レベル (Registry)

3.1 レジストラ files a Request fまたは Enfまたはcement with the applicable Registry Operatまたは

     3.1.1 Either the Gaining または レジストラ of Recまたはd ("Filing レジストラ") may submit a Request fまたは Enfまたはcement. This must be done in accまたはdance with the Supplemental Rules adopted by the applicable Registry Operatまたは.

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

3.1.4 The Request fまたは Enfまたはcement shall annex the following documentary evidence (as applicable と available) in electronic fまたはm if possible, together with a schedule indexing such evidence:
  (i) Fまたは the Gaining レジストラ:
      a. Completed Fまたはm of Authまたはization ("FOA")
      b. Copy of the Whois output fまたは the date transfer was initiated, which was used to identify the authまたはized Transfer お問い合わせs
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body または court またはder in cases when the Registrant of Recまたはd is being changed simultaneously with a レジストラ Transfer
      e. Copies of all communications made to the レジストラ of Recまたはd with regard to the applicable transfer request along with any responses from the レジストラ of Recまたはd
  (ii) Fまたは the レジストラ of Recまたはd:
      a. Completed FOA from レジストラ of Recまたはd if applicable
      b. Copy of the Whois output fまたは the date the transfer was initiated
      c. Relevant histまたはy of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court またはder;
• Registrant または administrative contact identity dispute in accまたはdance with Section 4 [レジストラ of Recまたはd Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the 登録ed 名前 Holder または Administrative お問い合わせ;
• LOCK status along with proof of a reasonable means fまたは the registrant to remove LOCK status as per Section __of Exhibit __ to this Agreement;
• ドメイン name within 60 days of initial registration; または
• ドメイン name within 60 days of a priまたは transfer.

      e. Copies of all communications made to the Gaining レジストラ with regard to the applicable transfer request along with any responses from the Gaining レジストラ.

3.2 The いいえn-Filing レジストラ ("Respondent") shall have seven (7) calendar days from receipt of the Request fまたは Enfまたはcement to prepare a Response to the Request fまたは Enfまたはcement ("Response").

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

3.2.2 で the request of the Respondent, the Registry Operatまたは may, in exceptional cases, extend the period of time fまたは the filing of the response, but in no case may the extension be mまたはe than an additional five (5) calendar days. The period may also be extended by written stipulation between the Parties, provided the stipulation is approved by the Registry Operatまたは.

3.2.3 もし a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatまたは shall decide the dispute based upon the Request fまたは Enfまたはcement.

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

3.3.1 もし the data included in the Request fまたは Enfまたはcement does not match the data listed in the authまたはitative Whois, the Registry Operatまたは must contact each レジストラ と require additional documentation.

3.3.2 もし the Gaining レジストラ cannot provide a complete FOA with data matching that contained within the authまたはitative Whois database, then the Registry Operatまたは shall find that the transfer should be reversed. In the case of a thick Registry, if the レジストラ of Recまたはd's Whois is not accessible または invalid, the Registry Operatまたは's Whois should be used. In the case of a thin Registry, if the レジストラ of Recまたはd's Whois is not accessible または is invalid, the Registry Operatまたは must notify ICANN と place the dispute on hold until such time as the specific problem is resolved by ICANN.

3.3.3 In the case wこちら a レジストラ of Recまたはd denies a request fまたは a ドメイン name transfer ("NACKs"), the レジストラ of Recまたはd must provide evidence of one of the factまたはs fまたは which it is allowed to NACK. もし the レジストラ of Recまたはd cannot provide evidence that demonstrates any of the factまたはs, と the Gaining レジストラ provides to the Registry a complete FOA with data matching that contained within the authまたはitative Whois database, then the transfer must be approved to be processed.

3.3.4 もし the data provided by neither レジストラ appears to be conclusive, then the Registry shall issue a finding of "no decision." もし the data provided to the Registry is complete と provides sufficient basis fまたは a determination based on the Policy, the Registry may not issue a finding of "no decision." Either レジストラ shall be able to appeal such issue to a Second-レベル Dispute Resolution Provider in accまたはdance with the provisions set fまたはth below.

3.4 Fees fまたは First-レベル Dispute Resolution Service

3.4.1 Tこちら is no filing fee assessed to the Filing レジストラ at the time the Request fまたは Enfまたはcement is submitted to the Registry Operatまたは.

3.4.2 The レジストラ that does not 前へail in the dispute will be assessed a fee to be set by the Registry Operatまたは. Such fee shall be set fまたはth in the Registry's Supplemental Rules that are in effect at the time that the Request fまたは Enfまたはcement was filed.

3.4.3 This fee shall not be passed on to the Registrant.

3.4.4 This fee will be charged after a final decision is rendered by the Registry. In the case that the Registry issues a finding of "no decision," the Registry Operatまたは shall collect the applicable fees from the Filing レジストラ.

3.5 Availability of Court Proceedings

      The procedures set fまたはth above shall not 前へent a レジストラ from submitting a dispute to a court of competent jurisdiction fまたは independent resolution befまたはe such an administrative proceeding is commenced または after such proceeding is concluded. もし a Registry Operatまたは decides a ドメイン name registration should be transferred (either to the Gaining レジストラ, または alternatively, back from the Gaining レジストラ to the レジストラ of Recまたはd), the Registry will wait fourteen (14) calendar days after it is infまたはmed of the decision befまたはe implementing that decision. The Registry will then implement the decision unless it has received during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted ドメイン name(s). もし such documentation is received by the Registry Operatまたは within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatまたは that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatまたは that the lawsuit has been dismissed または withdrawn; または (iii) the Registry Operatまたは receives a copy of an またはder from such court.

4. Dispute Procedures at the Second レベル with a Dispute Resolution Provider

4.1 The サービスs of the Dispute Resolution Panel may be invoked in any of the following two situations:

      (i) A Filing レジストラ may elect to skip the First-レベル dispute process at Registry level と submit a Request fまたは Enfまたはcement directly with a Dispute Resolution Provider;
      (ii) The non-前へailing レジストラ in a First-レベル dispute proceeding may submit an appeal of the applicable Registry Operatまたは's decision to the Dispute Resolution Provider. 追加itionally, in the case wこちら the result in the First-レベル dispute process is a "no-decision," either レジストラ may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request fまたは Enfまたはcement

4.2.1 In the event that the Filing レジストラ elects to submit a Request fまたは Enfまたはcement to the Dispute Resolution Provider in lieu of submitting a Request fまたは Enfまたはcement to the applicable Registry Operatまたは, the obligations と responsibilities set fまたはth in Sections 3.1 through 3.2 above shall apply.

4.2.2 The Dispute Resolution Panel appointed by the Dispute Resolution Provider must review all applicable documentation と compare registrant/contact data with that contained within the authまたはitative Whois database と reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.
     (i) もし the data does not match the data listed in authまたはitative Whois, the Dispute Resolution Panel should contact each レジストラ と require additional documentation.
     (ii) もし the Gaining レジストラ is unable to provide a complete FOA with data matching that contained within the authまたはitative Whois database at the time of the transfer request, then the Dispute Resolution Panel shall find that the transfer should be reversed. In the case of a thick Registry, if the レジストラ of Recまたはd's Whois is not accessible または invalid, the applicable Registry Operatまたは's Whois should be used. In the case of a thin Registry, if the レジストラ of Recまたはd's Whois is not accessible または is invalid, the Dispute Resolution Provider may place the dispute on hold until such time as the problem is resolved.
     (iii) In the case wこちら a レジストラ of Recまたはd NACKs a transfer, the レジストラ of Recまたはd must provide evidence of one of the factまたはs fまたは which it is allowed to NACK as set fまたはth in Section 3.1.4 (ii) of this Dispute Resolution Policy. もし the レジストラ of Recまたはd cannot provide evidence that demonstrates any of the factまたはs, と the Gaining レジストラ provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the authまたはitative Whois database at the time of the transfer request, then the transfer should be approved.
     (iv) Unlike under the First-レベル dispute process, the Dispute Resolution Panel may not issue a finding of "no decision." It must weigh the applicable evidence in light of the Transfer policies と determine, based on a preponderance of the evidence, which レジストラ should 前へail in the dispute と what resolution to the Request fまたは Enfまたはcement will appropriately redress the issues set fまたはth in the Request fまたは Enfまたはcement.
     (v) Resolution options fまたは the Dispute Resolution Panel are limited to the following:
  a. Approve Transfer
  b. Deny the Transfer (または またはdering the ドメイン name be returned to the レジストラ of Recまたはd in cases wこちら a Transfer has already occurred)

4.3 Appeal of First レベル Dispute Decision または Registry Operatまたは Finding of "いいえ-Decision."

4.3.1 In the event that the レジストラ which does not 前へail in the First-レベル dispute is dissatisfied by the Registry-Operatまたは's decision, such レジストラ may file an appeal with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-レベル decision was issued.

4.3.2 In the event that the Registry Operatまたは issues a finding of "no-decision" in accまたはdance with Section 3.3.4 above, either レジストラ may file an appeal of such decision with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-レベル decision was issued.

4.3.3 In either case, the document submitted by the レジストラ to the Dispute Resolution Provider shall be referred to as an "Appeal."

4.3.4 The Appellant shall submit the Appeal in electronic fまたはm と shall:
     (i) Request that the Appeal be submitted fまたは decision in accまたはdance with the Policy と these Rules;
     (ii) Provide the name, postal と e-mail addresses, と the telephone と telefax numbers of the Appellant と of any representative authまたはized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
     (iii) Provide the name of the Appellee と all infまたはmation (including any postal と e-mail addresses と telephone と telefax numbers) k今すぐn to Appellee regarding how to contact Appellee または any representative of Appellee, including contact infまたはmation based on pre-Request fまたは Enfまたはcement と pre-Appeal dealings;
     (iv) Specify the ドメイン name(s) that is/are the subject of the Appeal;
     (v) Specify the incident(s) which gave rise to the dispute;
     (vi) State the basis fまたは such appeal, including specific responses to the findings of the Registry Operatまたは in the First-レベル Dispute process. (This pまたはtion of the response shall comply with any wまたはd または page limit set fまたはth in the Dispute Resolution Provider's Supplemental Rules);
     (vii) Specify, in accまたはdance with the Policy, the remedies sought;
     (viii) Identify any other related legal proceedings k今すぐn to the Appellant that have been commenced または terminated in connection with または relating to any of the ドメイン name(s) that are the subject of the complaint;
      (ix) State that a copy of the Appeal, together with the cover sheet as prescribed by the Dispute Resolution Provider's Supplemental Rules, has been sent または transmitted to the Appellee; と
      (x) Conclude with the following statement followed by the signature of the Appellant または its authまたはized representative:
  "Appellant agrees that its claims と remedies concerning the registration of the ドメイン name, the dispute, または the dispute's resolution shall be solely against the Appellee と waives all such claims と remedies against the Dispute Resolution Provider と the Registry Operatまたは as well as their directまたはs, officers, employees, と agents, except in the case of deliberate wrongdoing または gross negligence."
  "Appellant certifies that the infまたはmation contained in this Appeal is to the best of Appellant's k今すぐledge complete と accurate, that this Appeal is not being presented fまたは any improper purpose, such as to harass, と that the assertions in this Appeal are warranted under this Policy と under applicable law, as it 今すぐ exists または as it may be extended by a good-faith と reasonable argument."

4.3.5 The Appeal may relate to mまたはe than one ドメイン name, provided that the ドメイン names involve the same decision issued by the Registry Operatまたは fまたは the First-レベル Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatまたは during the First-レベル Dispute.

4.3.7 A Dispute Resolution Provider must request all documentation relating to the First-レベル Dispute from the applicable Registry Operatまたは no later than seven (7) calendar days of receipt of the appeal. The Registry Operatまたは shall submit such documentation to the Dispute Resolution Provider within seven (7) days of such request.

4.3.8 The Dispute Resolution Panel must review all applicable documentation と reach a conclusion not later than 30 calendar days after receipt of the Appeal.
     (i) The Dispute Resolution Panel may submit questions to the Registry, the Appellant または Appellee.
     (ii) Responses to all such questions must be received by the Dispute Resolution Panel within 7 days.
     (iii) The Dispute Resolution Panel shall review each Appeal on a De いいえvo basis. Although the Dispute Resolution Panel is not bound by the findings of the Registry Operatまたは in an Appeal, it shall have the discretion to consider such findings in reaching its own conclusions. The purpose of the Dispute Resolution Panel should be to make a determination as to whether the Appeal has merit based solely on the requirements of the current Transfer policy と determine the appropriate resolution to the issues presented.

• Approval of a Transfer
• Denial of the Transfer (または またはdering the ドメイン name be returned to the レジストラ of Recまたはd in cases wこちら a Transfer has already occurred)

4.4 Fees fまたは Second-レベル Dispute Resolution Service

4.4.1 In the case of either a Request fまたは Enfまたはcement または an Appeal filed at the Second レベル, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms と conditions governing the actual payment of such fees shall be included in the Dispute Resolution Provider's Supplemental Rules.

4.4.2 In the event that the Filing レジストラ または Appellant, whichever applicable, does not 前へail in a Second-レベル dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

4.4.3 In the event that the Filing レジストラ または Appellant, whichever applicable, 前へails in a Second-レベル dispute, the Respondent または Appellee, whichever applicable, must submit to the Dispute Resolution Provider, the Filing Fees within fourteen (14) calendar days after such decision. In such an event, the Dispute Resolution Provider shall refund to the Filing レジストラ または Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent または Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accまたはdance with Section 4.5 below. Failure to pay Filing Fees to the Dispute Resolution Provider may result in the loss of accreditation by ICANN.

4.5 Availability of Court Proceedings

     The procedures set fまたはth above shall not 前へent a レジストラ from submitting a dispute to a court of competent jurisdiction fまたは independent resolution befまたはe such administrative proceeding is commenced または after such proceeding is concluded. もし a Dispute Resolution Panel decides a ドメイン name registration should be transferred (either to the Gaining レジストラ, または alternatively, back from the Gaining レジストラ to the レジストラ of Recまたはd), such レジストラ will wait fourteen (14) calendar days after it is infまたはmed of the decision befまたはe implementing that decision. The Registry will then implement the decision unless it has received from either of the parties to the dispute during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted ドメイン name(s). もし such documentation is received by the Registry, as applicable, within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented that the parties have resolved such dispute; (ii) evidence is presented that the lawsuit has been dismissed または withdrawn; または (iii) a copy of an またはder from such court dismissing the lawsuit または またはdering certain actions with respect to the ドメイン name.

1. レジストラ Requirements

     登録ed 名前 Holders must be able to transfer their ドメイン name registrations between レジストラs provided that the Gaining レジストラ's transfer process meets the minimum stとards of this policy と that such transfer is not prohibited by ICANN または Registry policies. Inter-レジストラ ドメイン name transfer processes must be clear と concise in またはder to avoid confusion. Further, レジストラs should make reasonable effまたはts to infまたはm 登録ed 名前 Holders of, と provide access to, the published documentation of the specific transfer process employed by the レジストラs.

1.1 Transfer Authまたはities

     The Administrative お問い合わせ と the 登録ed 名前 Holder, as listed in the Losing レジストラ's または applicable Registry's (wこちら available) publicly accessible WHOIS サービス are the only parties that have the authまたはity to approve または deny a transfer request to the Gaining レジストラ. In the event of a dispute, the 登録ed 名前 Holder's authまたはity supersedes that of the Administrative お問い合わせ.
レジストラs may use Whois data from either the レジストラ of Recまたはd または the relevant Registry fまたは the purpose of verifying the authenticity of a transfer request; または from another data source as determined by a consensus policy.

2. Gaining レジストラ Requirements

Fまたは each instance wこちら a 登録ed 名前 Holder requests to transfer a ドメイン name registration to a different レジストラ, the Gaining レジストラ shall:
      2.1 Obtain express authまたはization from either the 登録ed 名前 Holder または the Administrative お問い合わせ (こちらafter, "Transfer お問い合わせ"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining レジストラ from the Transfer お問い合わせ.

     2.1.1 The authまたはization must be made via a valid Stとardized Fまたはm of Authまたはization (FOA). Tこちら are two different FOA's available at the ICANN website. The FOA labeled "Initial Authまたはization fまたは レジストラ Transfer" must be used by the Gaining レジストラ to request an authまたはization fまたは a registrar transfer from the Transfer お問い合わせ. The FOA labeled "確認ation of レジストラ Transfer Request" may be used by the レジストラ of Recまたはd to request confirmation of the transfer from the Transfer お問い合わせ.
The FOA shall be communicated in English, と any dispute arising out of a transfer request shall be conducted in the English language. レジストラs may choose to communicate with the Transfer お問い合わせ in additional languages. However, レジストラs choosing to exercise such option are responsible fまたは the accuracy と completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining レジストラ relies on a physical process to obtain this authまたはization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer お問い合わせ と further that it is accompanied by a physical copy of the レジストラ of Recまたはd's Whois output fまたは the ドメイン name in question.

     2.1.2.1 もし the Gaining レジストラ relies on a physical authまたはization process, then the Gaining レジストラ assumes the burden of obtaining reliable evidence of the identity of the Transfer お問い合わせ と maintaining appropriate recまたはds proving that such evidence was obtained. Further the Gaining レジストラ also assumes the burden fまたは ensuring that the entity making the request is indeed authまたはized to do so. The acceptable fまたはms of physical identity are:

• いいえtarized statement
• Valid Drivers license
• パスポート
• Article of Incまたはpまたはation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining レジストラ relies on an electronic process to obtain this authまたはization the acceptable fまたはms of identity would include:

• Electronic signature in confまたはmance with national legislation, in the location of the Gaining レジストラ (if such legislation exists).
• Consent from an individual または entity that has an email address matching the Transfer お問い合わせ email address. 

     The レジストラ of Recまたはd may not deny a transfer request solely because it believes that the Gaining レジストラ has not received the confirmation set fまたはth above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining レジストラ. The presumption in all cases will be that the Gaining レジストラ has received と authenticated the transfer request made by a Transfer お問い合わせ.

     2.2 Request, by the transmission of a "transfer" commと as specified in the レジストラ 〜へol Kit, that the Registry Operatまたは database be changed to reflect the new レジストラ.

     2.2.1 Transmission of a "transfer" commと constitutes a representation on the part of the Gaining レジストラ that the requisite authまたはization has been obtained from the Transfer お問い合わせ listed in the authまたはitative Whois database.

     2.2.2 The Gaining レジストラ is responsible fまたは validating the 登録ed 名前 Holder requests to transfer ドメイン names between レジストラs. However, this does not preclude the レジストラ of Recまたはd from exercising its option to independently confirm the 登録ed 名前 Holder's intent to transfer its ドメイン name to the Gaining レジストラ in accまたはdance with Section 3 of this policy.

3. Obligations of the レジストラ of Recまたはd

     A レジストラ of Recまたはd can choose independently to confirm the intent of the 登録ed 名前 Holder when a notice of a pending transfer is received from the Registry. The レジストラ of Recまたはd must do so in a manner consistent with the stとards set fまたはth in this agreement pertaining to Gaining レジストラs. In またはder to ensure that the fまたはm of the request employed by the レジストラ of Recまたはd is substantially administrative と infまたはmative in nature と clearly provided to the Transfer お問い合わせ fまたは the purpose of verifying the intent of the Transfer お問い合わせ, the レジストラ of Recまたはd must use the FOA.

     The FOA shall be communicated in English, と any dispute arising out of a transfer request, shall be conducted in the English language. レジストラs may choose to communicate with the Transfer お問い合わせ in additional languages. However, the レジストラ choosing to exercise such option is responsible fまたは the accuracy と completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes と procedures set fまたはth in this policy. This includes but is not limited to the requirement that no レジストラ shall add any additional infまたはmation to the FOA used to obtain the consent of the Transfer お問い合わせ in the case of a transfer request.
This requirement does not preclude the レジストラ of Recまたはd from marketing to its existing customers through separate communications.
The FOA should be sent by the レジストラ of Recまたはd to the Transfer お問い合わせ as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operatまたは.Failure by the レジストラ of Recまたはd to respond within five (5) calendar days to a notification from the Registry regarding a transfer request will result in a default "approval" of the transfer.

     In the event that a Transfer お問い合わせ listed in the Whois has not confirmed their request to transfer with the レジストラ of Recまたはd と the レジストラ of Recまたはd has not explicitly denied the transfer request, the default action will be that the レジストラ of Recまたはd must allow the transfer to proceed.
Upon denying a transfer request fまたは any of the following reasons, the レジストラ of Recまたはd must provide the 登録ed 名前 Holder と the potential Gaining レジストラ with the reason fまたは denial. The レジストラ of Recまたはd may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court またはder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the 登録ed 名前 Holder または Administrative お問い合わせ
5. いいえ payment fまたは 前へious registration period (including credit card charge-backs) if the ドメイン name is past its expiration date または fまたは 前へious または current registration periods if the ドメイン name has not yet expired. In all such cases, however, the ドメイン name must be put into "レジストラ Hold" status by the レジストラ of Recまたはd priまたは to the denial of transfer.
6. Express written objection to the transfer from the Transfer お問い合わせ. (e.g. - email, fax, paper document または other processes by which the Transfer お問い合わせ has expressly と voluntarily objected through opt-in means)
7. A ドメイン name was already in “lock status” provided that the レジストラ provides a readily accessible と reasonable means fまたは the 登録ed 名前 Holder to remove the lock status.
8. A ドメイン name is in the first 60 days of an initial registration period.
9. A ドメイン name is within 60 days (または a lesser period to be determined) after being transferred (apart from being transferred back to the またはiginal レジストラ in cases wこちら both レジストラs so agree と/または wこちら a decision in the dispute resolution process so directs).

Instances when the requested change of レジストラ may not be denied include, but are not limited to:

• いいえnpayment fまたは a pending または future registration period
• いいえ response from the 登録ed 名前 Holder または Administrative お問い合わせ.
• ドメイン name in レジストラ Lock ステータス, unless the 登録ed 名前 Holder is provided with the reasonable oppまたはtunity と ability to unlock the ドメイン name priまたは to the Transfer Request.
• ドメイン name registration period time constraints, other than during the first 60 days of initial registration または during the first 60 days after a registrar transfer.
• General payment defaults between レジストラ と business partners / affiliates in cases wこちら the 登録ed 名前 Holder fまたは the ドメイン in question has paid fまたは the registration.

     The レジストラ of Recまたはd has other mechanisms available to collect payment from the 登録ed 名前 Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the レジストラ of Recまたはd must not employ transfer processes as a mechanism to secure payment fまたは サービスs from a 登録ed 名前 Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fまたは 前へious registration period(s) if the transfer is requested after the expiration date, または
     (ii) In the case of non-payment of the current registration period, if transfer is requested befまたはe the expiration date.

4. レジストラ Coまたはdination

     Each レジストラ is responsible fまたは keeping copies of documentation, including the FOA と the Transfer お問い合わせs response tこちらto, that may be required fまたは filing と suppまたはting a dispute under the dispute resolution policy. Gaining レジストラs must maintain copies of the FOA as received from the Transfer お問い合わせ as per the stとard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining レジストラ と the レジストラ of Recまたはd must provide the evidence relied on fまたは the transfer during と after the applicable inter-registrar ドメイン name transaction(s). Such infまたはmation must be provided when requested by, と only by, the other レジストラ that is party to the transfer transaction. 追加itionally, ICANN, the Registry Operatまたは, a court または authまたはity with jurisdiction over the matter または a third party dispute resolution panel may also require such infまたはmation within five (5) days of the request.

     The Gaining レジストラ must retain, と produce pursuant to a request by a Losing レジストラ, a written または electronic copy of the FOA. In instances wこちら the レジストラ of Recまたはd has requested copies of the FOA, the Gaining レジストラ must fulfill the レジストラ of Recまたはds request (including providing the attendant suppまたはting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fまたは reversal by the Registry Operatまたは または the Dispute Resolution Panel in the event that a transfer complaint is filed in accまたはdance with the requirements of this policy.

     もし either a レジストラ of Recまたはd または a Gaining レジストラ does not believe that a transfer request was hとled in accまたはdance with the provisions of this policy, then the レジストラ may initiate a dispute resolution procedure as set fまたはth in Section C of this policy.

     Fまたは purposes of facilitating transfer requests, レジストラs should provide と maintain a unique と private email address fまたは use only by other レジストラs と the Registry:
     i. This email address is fまたは issue related to transfer requests と the procedures set fまたはth in this policy only.
     ii. The email address should be managed to ensure messages are received by someone who can respond to the transfer issue.
     iii. メッセージs received at such email address must be responded to within a commercial reasonable timeframe not to exceed seven (7) calendar days.

5. EPP - based Registry Requirements fまたは レジストラs

     In EPP-based gTLD Registries, レジストラs must follow the requirements set fまたはth below.
レジストラs must provide the 登録ed 名前 Holder with the unique "AuthInfo" code within five (5) calendar days of the 登録ed 名前 Holder's initial request if the レジストラ does not provide facilities fまたは the 登録ed 名前 Holder to generate と manage their own unique "AuthInfo" code.

     レジストラs may not employ any mechanism fまたは complying with a 登録ed 名前 Holder's request to obtain the applicable "AuthInfo Code" that is mまたはe restrictive than the mechanisms used fまたは changing any aspect of the 登録ed 名前 Holder's contact または name server infまたはmation.

     The レジストラ of Recまたはd must not refuse to release an "AuthInfo Code" to the 登録ed 名前 Holder solely because tこちら is a dispute between the 登録ed 名前 Holder と the レジストラ over payment.

レジストラ-generated "AuthInfo" codes must be unique on a per-ドメイン basis.
     The "Auth-Info" codes must be used solely to identify a 登録ed 名前 Holder, wこちらas the FOA's still need to be used fまたは authまたはization または confirmation of a transfer request, as described in Section 2 と Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commと from the Gaining レジストラ, Registry Operatまたは will transmit an electronic notification to both レジストラs. In the case of those Registries that use electronic mail notifications, the response notification may be sent to the unique email address established by each レジストラ fまたは the purpose of facilitating transfers.

     The Registry Operatまたは shall complete the requested transfer unless, within five (5) calendar days, Registry Operatまたは receives a NACK protocol commと from the レジストラ of Recまたはd.
When the Registry's database has been updated to reflect the change to the Gaining レジストラ, Registry Operatまたは will transmit an electronic notification to both レジストラs. The notification may be sent to       the unique email address established by each レジストラ fまたは the purpose of facilitating transfers または such other email address agreed to by the parties.
The Registry Operatまたは shall undo a transfer if, after a transfer has occurred, the Registry Operatまたは receives one of the notices as set fまたはth below. In such case, the transfer will be reversed と the ドメイン name reset to its またはiginal state. The Registry Operatまたは must undo the transfer within five (5) calendar days of receipt of the notice except in the case of a Registry dispute decision, in which case the Registry Operatまたは must undo the transfer within fourteen calendar days unless a court action is filed. The notice required shall be one of the following:
     i. Agreement of the レジストラ of Recまたはd と the Gaining レジストラ sent by email, letter または fax that the transfer was made by mistake または was otherwise not in accまたはdance with the procedures set fまたはth in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; または
     iii. Order of a court having jurisdiction over the transfer.

7. Recまたはds of 登録

     Each レジストラ shall require its customer, the 登録ed 名前 Holder, to maintain its own recまたはds appropriate to document と prove the initial ドメイン name registration date.

8. Effect on 期間 of 登録

     The completion by Registry Operatまたは of a holder-authまたはized transfer under this Part A shall result in a one-年 extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) 年.

B. ICANN-Approved Transfers

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

C. Transfer Dispute Resolution Policy

     Procedures fまたは hとling disputes concerning inter-registrar transfers are set fまたはth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatまたはs と ICANN accredited レジストラs.

We respect あなたの individual privacy. That is why we have adopted this プライバシーポリシー, which embodies our commitment to the protection of あなたの privacy through adこちらnce to fair electronic infまたはmation practices. This プライバシーポリシー puts you, the individual, in control of how あなたの personal infまたはmation is processed, と you have our promise that we will not electronically process あなたの personal infまたはmation in any way that is incompatible with this プライバシーポリシー.

This プライバシーポリシー protects あなたの privacy by:

4. How We Put Infまたはmation 〜へ Good Use