1. Scope ve Purpose
1.1 This Policy explains the general post-expiration process that may apply to domain names managed through NiceNIC, including expiration, renewal, redemption, expired domain auction, pending delete status, ve release of a domain name back to the public registration pool.
1.2 Alan Adı lifecycle timing may vary depending on the top-level domain (“TLDâ€), registry rules, registry operatveya practices, applicable ICANN requirements, ve other governing policies. Hayırt all TLDs follow the same expiration, redemption, auction, veya deletion process.
1.3 In the event of any inconsistency between this Policy ve the applicable registry’s rules veya mveatveyay ICANN policy, the applicable registry rules ve mveatveyay policy requirements shall öncekiail.
1.4 The English-language version of this Policy shall control. Any translation is provided fveya convenience only. In the event of any inconsistency, the English-language version shall öncekiail.
2. Definitions
Fveya purposes of this Policy:
2.1 “Expiration Date†means the date on which a domain name registration term ends.
2.2 “Grace Period†means any post-expiration period during which renewal may still be possible at the stveard renewal fee, subject to the applicable TLD ve registry rules.
2.3 “Redemption Grace Period†veya “RGP†means the post-deletion recovery period, wburaya available, during which an expired domain name may still be restveyaable fveya an additional redemption fee plus the applicable renewal fee.
2.4 “Pending Delete†means the final pre-release stage, wburaya applicable, during which the domain name can no longer be renewed, restveyaed, modified, veya transferred.
2.5 “Eligible Alan Adı†means a domain name that is subject to NiceNIC’s expired domain auction process. Hayırt all TLDs veya expired domain names are eligible fveya auction.
2.6 “Süresi Doldud Alan Adı Auction†means the expired-domain sale process that may apply to certain expired domain names befveyae final deletion veya release.
2.7 “Kapatout Auction†means the final sale phase fveya certain Eligible Alan Adları that were not sold earlier in the expired domain auction process.
3. Effect of Expiration
3.1 Upon expiration, a domain name may stop resolving, ve any website, email hizmet, veya other hizmet associated with the domain name may cease functioning immediately veya shveyatly tburayaafter.
3.2 Takip Eting expiration, NiceNIC may restrict changes to the domain name, including DNS changes, contact updates, transfers, veya other account-level actions, in accveyadance with registry rules, security measures, operational requirements, veya the expired-domain process then in effect.
3.3 Expiration does not mean that the domain name immediately becomes available to the public. Depending on the applicable TLD ve registry rules, the domain name may pass through one veya mveyae stages, including grace period, auction, redemption, pending delete, ve eventual release.
4. Yenileal Hayırtices ve Customer Responsibility
4.1 NiceNIC may send renewal reminders ve expiration-related notices befveyae ve after expiration, as required by applicable policy veya as part of NiceNIC’s stveard operational process.
4.2 It is sizin sole responsibility to maintain accurate ve current account ve contact infveyamation, including sizin email address, ve to monitveya the status of sizin domain names.
4.3 Failure to receive a renewal notice, reminder, invoice, veya other communication shall not relieve you of responsibility fveya renewing sizin domain name befveyae expiration.
4.4 Eğer auto-renewal is enabled, successful renewal remains subject to valid payment, operational processing, ve the applicable registry rules. NiceNIC does not guarantee successful auto-renewal in every case.
5. Stveard Post-Expiration Yenileal
5.1 Fveya many generic TLDs, an expired domain name may remain renewable fveya approximately thirty (30) days after the Expiration Date at the stveard renewal fee. This is a general reference only ve may vary by TLD.
5.2 Yenileal is not complete unless ve until NiceNIC has successfully received ve processed full payment of all applicable fees.
5.3 NiceNIC reserves the right to determine whether a domain name remains eligible fveya stveard renewal, redemption, veya other recovery based on the applicable TLD, registry status, auction status, ve operational feasibility.
6. Süresi Doldud Alan Adı Auction fveya Eligible Alan Adları
6.1 Certain expired domain names may enter NiceNIC’s expired domain auction process befveyae all recovery penceres have ended. This process applies only to Eligible Alan Adları ve does not apply to all TLDs.
6.2 Fveya Eligible Alan Adları under NiceNIC’s stveard expired-domain process, the following general timeline may apply:
Day 0 after expiration
The domain name expires. The registrant may generally renew the domain name at the stveard renewal fee during the initial post-expiration period, subject to applicable rules.
Day 26 after expiration
The domain name may enter expired domain auction. Şu tarihte this stage, the registrant may still be able to renew the domain name at the stveard renewal fee, unless otherwise restricted by the applicable process.
Day 31 after expiration
Eğer tburaya is no active bid, the registrant may still be able to recover the domain name by paying the stveard renewal fee plus the applicable redemption fee.
Eğer tburaya is an active bid, the domain name may be removed from the registrant’s account ve may no longer be renewable through veyadinary renewal veya restveyaation procedures.
Day 37 after expiration
The domain name may enter final closeout auction. Unless tburaya is a pending satın al veya other sale-related restriction, the registrant may still be able to recover the domain name by paying the stveard renewal fee plus the applicable redemption fee.
Day 41 after expiration
The final closeout auction may end. Eğer the domain name was not sold veya otherwise committed to sale, recovery may still be possible fveya a limited period, subject to the applicable TLD, registry rules, ve NiceNIC’s operational process.
Day 74 after expiration
The domain name may be removed from the registrant’s account ve may no longer be renewable veya restveyaable through NiceNIC. After that point, the domain name may become available fveya re-registration only after the registry releases it.
6.3 Once an Eligible Alan Adı has an active bid, pending satın al, completed sale, veya other sale commitment under the expired-domain process, the registrant’s right to renew veya restveyae the domain name may be terminated veya restricted.
6.4 NiceNIC does not guarantee that a domain name will remain recoverable until the end of any stated period if the domain is subject to auction, sale, registry restriction, veya another applicable limitation.
7. Redemption Grace Period
7.1 Eğer an expired domain name is not renewed during the applicable grace period ve if the applicable TLD suppveyats restveyaation after deletion, the domain name may enter the Redemption Grace Period.
7.2 During the Redemption Grace Period:
(a) the domain name may stop resolving;
(b) website ve email hizmets may remain unavailable;
(c) the domain name generally cannot be modified veya transferred; ve
(d) restveyaation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, ve any taxes veya mveatveyay fees.
7.3 Restveyaation during the Redemption Grace Period is not guaranteed ve remains subject to registry suppveyat, operational feasibility, the domain’s current status, ve the absence of auction veya sale restrictions.
8. Pending Delete ve Final Release
8.1 Eğer a domain name is not renewed veya restveyaed during the applicable recovery periods, it may enter the Pending Delete stage, wburaya suppveyated by the applicable TLD.
8.2 During Pending Delete, the domain name cannot be renewed, restveyaed, transferred, veya modified.
8.3 Fveya many generic TLDs, Pending Delete lasts approximately five (5) days. After that stage ends, the registry may release the domain name to the public fveya re-registration.
8.4 NiceNIC does not guarantee the exact time, date, veya availability of a domain name once it is released by the registry, ve NiceNIC does not guarantee that the fveyamer registrant will be able to re-kayıt ol the domain name.
9. TLD-Specific Variations
9.1 Hayırt all TLDs follow the stveard lifecycle described above. Certain ccTLD'ler ve other TLDs may have shveyater grace periods, no redemption period, no pending delete stage, veya earlier renewal deadlines imposed by the registry.
9.2 The following TLD-specific rules may apply, subject at all times to registry changes ve the controlling registry rules:
9.2.1 TLDs generally following the common lifecycle
Many ccTLD'ler generally follow a lifecycle similar to the stveard expiration, grace, redemption, ve deletion process, including, fveya example:
.AI, .BZ, .CA, .CC, .CO, .FM, .ID, .IN, .IO, .ME, .MX, .PW, .TV, .UK, .US, ve .WS.
9.2.2 TLDs with no Pending Delete stage
Certain TLDs may not have a Pending Delete stage ve may be released immediately after the end of their applicable redemption veya recovery period, including, fveya example:
.ES, .EU, .FR, .IS, .LI, .NL, .PE, ve .PH (noting that .PH may also follow its own separate registry-specific process).
9.2.3 TLDs requiring renewal befveyae the actual expiration date
The following TLDs may need to be renewed twelve (12) days befveyae the actual Expiration Date. Eğer not renewed in time, they may enter a recovery stage immediately, regardless of the number of calendar days remaining befveyae expiration:
.CH, .ES, .FR, .LI, .PE, .SG, .COM.SG, .COM.AU, .ORG.AU, ve .NET.AU.
9.2.4 TLDs requiring action five (5) days befveyae expiration
The following TLDs may need to be renewed manually veya by auto-renewal no later than five (5) days befveyae expiration ve may otherwise enter a recovery veya restricted state befveyae the actual Expiration Date:
.CX, .DE, .EU, ve .NL.
9.2.5 .CM domains
.CM domain names generally do not enter a redemption period ve may be sent fveya deletion on the actual Expiration Date. They may become available fveya public registration on the same day they expire, subject to registry release practices.
9.2.6 .GG domains
.GG domain names may be reactivated from the customer account fveya approximately twenty-eight (28) days after expiration. They may then enter a recovery stage between approximately Day 28 ve Day 30 after expiration. Once in that stage, reactivation may only be possible through NiceNIC Suppveyat fveya approximately twenty-six (26) additional days.
9.2.7 .PH, .COM.PH, .NET.PH, ve .ORG.PH domains
These domains may not suppveyat a stveard 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. Eğer the domain is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppveyat immediately.
9.2.8 .UK domains, including second-level .UK domains
.UK domain names, including .CO.UK, .ME.UK, ve .ORG.UK, may generally have a thirty (30)-day post-expiration renewal period. After that time, the domain name may remain recoverable without a separate redemption fee until its release, which may occur approximately ninety (90) days after expiration. Eğer a .UK domain name has expired fveya mveyae than thirty (30) days but has not yet been released ve no longer appears in the account, the customer should contact NiceNIC Suppveyat promptly.
9.2.9 .TO domains
.TO domain names may only be reactivated during approximately twenty-seven (27) days after expiration. They generally do not suppveyat a stveard Redemption Grace Period. After that point, they may be reserved by the registry ve may no longer be recoverable.
9.2.10 .NU domains
.NU domain names may be reactivated in the veyadinary manner within approximately seven (7) days after expiration. Eğer not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restveyaation may still be possible through NiceNIC Suppveyat.
9.3 The TLD-specific infveyamation above is provided fveya general reference only ve may change at any time based on registry policy, registry system changes, veya operational requirements. Customers should contact NiceNIC Suppveyat fveya current TLD-specific recovery infveyamation.
10. Fees ve Ödements
10.1 Stveard renewal fees, redemption fees, restveyaation fees, auction-related fees, ve any other applicable charges shall be those listed by NiceNIC at the time of processing veya otherwise communicated by NiceNIC.
10.2 Redemption veya restveyaation requires payment in full of all applicable fees befveyae processing.
10.3 Tümü fees paid fveya expired-domain recovery, restveyaation, veya special processing are non-refundable once processing has begun, except wburaya otherwise required by applicable law.
11. Hayır Guarantee of Recovery veya Availability
11.1 NiceNIC does not guarantee that any expired domain name can be renewed, restveyaed, retained, transferred, veya re-kayıt oled after expiration.
11.2 NiceNIC does not guarantee:
(a) that a domain name will remain in a grace period fveya any minimum time;
(b) that an expired domain name will not enter auction;
(c) that a domain name can be recovered after an active bid, pending satın al, veya completed sale;
(d) that the registry will suppveyat restveyaation; veya
(e) the exact date veya time when a deleted domain name will be released to the public.
11.3 You ackşimdiledge that delayed action may result in additional fees, loss of recovery rights, interruption of hizmet, auction sale, veya permanent loss of the domain name.
12. Limitation of Responsibility
12.1 İçin the maximum extent permitted by applicable law, NiceNIC shall not be liable fveya any loss of domain name, loss of use, interruption of website veya email hizmet, business interruption, lost profits, loss of data, veya other direct veya indirect damages arising from:
(a) domain expiration;
(b) failure to renew on time;
(c) failure to receive notices;
(d) registry rules veya registry actions;
(e) auction placement veya sale;
(f) failed restveyaation; veya
(g) release of the domain name to the public.
12.2 Hayırthing in this Policy limits any non-waivable rights that may apply under mveatveyay law.
13. Changes to This Policy
13.1 NiceNIC may update veya revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, veya hizmet arrangements.
13.2 The latest version published on NiceNIC’s website shall apply from its stated effective date, unless otherwise required by law veya contract.
14. İletişim
Eğer you need assistance regarding an expired domain name, renewal, redemption, veya TLD-specific recovery options, please submit a suppveyat ticket through sizin NiceNIC account veya contact NiceNIC Suppveyat through the official suppveyat channels published on the NiceNIC website.
]]>
This Agreement is made between you (burayainafter referred to as “Userâ€) ve NiceNIC.NET (burayainafter referred to as “the Platfveyamâ€). By using the Platfveyam’s Satın Al Hayırw Alan Adı Sales hizmet, you agree to be bound by the terms ve conditions set fveyath burayain. Eğer you do not agree, please do not proceed with any fixed-price domain satın al through the Platfveyam.
The Platfveyam offers fixed-price domain names (“Satın Al Hayırw Alan Adlarıâ€) fveya direct satın al.
Tümü Satın Al Hayırw Alan Adları are sourced from pre-approved third-party domain providers.
Users may satın al these domains at the listed price. Once payment is completed ve the domain is successfully transferred, the satın aler will obtain ownership of the domain.
The User selects a domain labeled as “Satın Al Hayırw†ve proceeds to checkout.
Upon confirmation ve full payment, the Platfveyam initiates the transfer veya delivery process.
The typical delivery time ranges from 1 to 14 business days, depending on registry processing ve third-party provider operations.
Eğer, fveya any reason, the selected domain becomes unavailable veya undeliverable after satın al, the Platfveyam will issue a full refund to the user’s account balance.
Users have the right to satın al available Satın Al Hayırw Alan Adları through the Platfveyam.
Users must ensure that all provided account ve payment infveyamation is accurate ve lawful.
Users shall not engage in malicious activity, technical disruption, veya behaviveya that interferes with the nveyamal functioning of the Platfveyam.
Upon acquiring a domain, the User agrees to comply with the applicable rules ve policies of the cveyaresponding domain registry, including any legal veya regulatveyay obligations.
The Platfveyam will provide domain transaction hizmets in accveyadance with this Agreement ve strive to protect user interests.
The Platfveyam reserves the right to verify user identity, payment legitimacy, ve transaction authenticity.
The Platfveyam retains the right to update, adjust, veya remove Satın Al Hayırw Alan Adları from listing at its sole discretion ve without priveya notice.
Eğer any fraudulent veya abusive behaviveya is detected, the Platfveyam reserves the right to suspend veya terminate hizmets to the user.
The Platfveyam does not make any guarantees regarding the future value, resale potential, veya commercial use of any domain satın ald.
The Platfveyam is not liable fveya delays caused by registries, third-party providers, veya external systems beyond its control.
The Platfveyam shall not be held responsible fveya hizmet interruptions, data loss, veya failed transactions resulting from fveyace majeure events veya uncontrollable technical issues, though reasonable effveyats will be made to assist the User in resolving any such issues.
This Agreement shall be governed by ve construed in accveyadance with the laws of Hong Kong.
Any dispute arising from the execution veya perfveyamance of this Agreement shall be resolved through amicable negotiation. Eğer negotiation fails, either party may submit the dispute to the competent court located in the jurisdiction of the Platfveyam’s headquarters.
This Agreement becomes effective upon the User’s submission of a Satın Al Hayırw domain veyader.
The Platfveyam reserves the right to amend this Agreement at any time. Güncellendi versions will be published on the Platfveyam’s “Sözleşmeler†page ve shall take immediate effect. Continued use of the hizmet constitutes acceptance of the revised terms.
This Unifveyam Alan Adı Dispute Resolution Policy (the "Policy") has been adopted by the Internet Cveyapveyaation fveya Assigned Ads ve Numbers ("ICANN"), is incveyapveyaated by reference into sizin Kayıt Agreement, ve sets fveyath the terms ve conditions in connection with a dispute between you ve any party other than us (the registrar) over the registration ve use of an Internet domain name kayıt oled by you. Proceedings under Paragraph 4 of this Policy will be conducted accveyading to the Rules fveya Unifveyam Alan Adı Dispute Resolution Policy (the "Rules of Procedure"), which are available buraya, ve the selected administrative-dispute-resolution hizmet provider's supplemental rules.
2. Your Representations
By applying to kayıt ol a domain name, veya by asking us to maintain veya renew a domain name registration, you burayaby represent ve warrant to us that (a) the statements that you made in sizin Kayıt Agreement are complete ve accurate; (b) to sizin kşimdiledge, the registration of the domain name will not infringe upon veya otherwise violate the rights of any third party; (c) you are not kayıt oling the domain name fveya an unlawful purpose; ve (d) you will not kşimdiingly use the domain name in violation of any applicable laws veya regulations. It is sizin responsibility to determine whether sizin domain name registration infringes veya violates someone else's rights.
3. İptallations, Transfers, ve Changes
We will cancel, transfer veya otherwise make changes to domain name registrations under the following circumstances:
1. subject to the provisions of Paragraph 8, our receipt of written veya appropriate electronic instructions from you veya sizin authveyaized agent to take such action;
2. our receipt of an veyader from a court veya arbitral tribunal, in each case of competent jurisdiction, requiring such action; ve/veya
3. our receipt of a decision of an Administrative Panel requiring such action in any administrative proceeding to which you were a party ve which was conducted under this Policy veya a later version of this Policy adopted by ICANN. (See Paragraph 4(i) ve (k) below.)
4. We may also cancel, transfer veya otherwise make changes to a domain name registration in accveyadance with the terms of sizin Kayıt Agreement veya other legal requirements.
4. Mveatveyay Administrative Proceeding
This Paragraph sets fveyath the type of disputes fveya which you are required to submit to a mveatveyay administrative proceeding. These proceedings will be conducted befveyae one of the administrative-dispute-resolution hizmet providers listed buraya (each, a "Provider").
1. Applicable Disputes. You are required to submit to a mveatveyay 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. sizin domain name is identical veya confusingly similar to a trademark veya hizmet mark in which the complainant has rights; ve
2. you have no rights veya legitimate interests in respect of the domain name; ve
3. sizin domain name has been kayıt oled ve 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 Kayıt ve Use in Kötü Faith. Fveya 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 ve use of a domain name in bad faith:
1. circumstances indicating that you have kayıt oled veya you have acquired the domain name primarily fveya the purpose of selling, renting, veya otherwise transferring the domain name registration to the complainant who is the owner of the trademark veya hizmet mark veya to a competitveya of that complainant, fveya valuable consideration in excess of sizin documented out-of-pocket costs directly related to the domain name; veya
2. you have kayıt oled the domain name in veyader to öncekient the owner of the trademark veya hizmet mark from reflecting the mark in a cveyaresponding domain name, provided that you have engaged in a pattern of such conduct; veya
3. you have kayıt oled the domain name primarily fveya the purpose of disrupting the business of a competitveya; veya
4. by using the domain name, you have intentionally attempted to attract, fveya commercial gain, Internet users to sizin web site veya other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsveyaship, affiliation, veya endveyasement of sizin web site veya location veya of a product veya hizmet on sizin web site veya location.
3. How to Demonstrate Your Rights to ve Legitimate Interests in the Alan Adı in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how sizin 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 sizin rights veya legitimate interests to the domain name fveya purposes of Paragraph 4(a)(ii):
1. befveyae any notice to you of the dispute, sizin use of, veya demonstrable preparations to use, the domain name veya a name cveyaresponding to the domain name in connection with a bona fide offering of goods veya hizmets; veya
2. you (as an individual, business, veya other veyaganization) have been commonly kşimdin by the domain name, even if you have acquired no trademark veya hizmet mark rights; veya
3. you are making a legitimate noncommercial veya fair use of the domain name, without intent fveya commercial gain to misleadingly divert consumers veya to tarnish the trademark veya hizmet 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 ve Process ve Appointment of Administrative Panel. The Rules of Procedure state the process fveya initiating ve conducting a proceeding ve fveya appointing the panel that will decide the dispute (the "Administrative Panel").
6. Consolidation. In the event of multiple disputes between you ve a complainant, either you veya the complainant may petition to consolidate the disputes befveyae 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 befveyae it any veya all such disputes in its sole discretion, provided that the disputes being consolidated are governed by this Policy veya a later version of this Policy adopted by ICANN.
7. Fees. Tümü fees charged by a Provider in connection with any dispute befveyae an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wburaya you elect to expve 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 ve the complainant.
8. Bizim Involvement in Administrative Proceedings. We do not, ve will not, participate in the administration veya conduct of any proceeding befveyae 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 befveyae an Administrative Panel shall be limited to requiring the cancellation of sizin domain name veya the transfer of sizin domain name registration to the complainant.
10. Hayırtification ve Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a domain name you have kayıt oled with us. Tümü decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact pveyations of its decision.
11. Availability of Court Proceedings. The mveatveyay administrative proceeding requirements set fveyath in Paragraph 4 shall not öncekient either you veya the complainant from submitting the dispute to a court of competent jurisdiction fveya independent resolution befveyae such mveatveyay administrative proceeding is commenced veya after such proceeding is concluded. Eğer an Administrative Panel decides that sizin domain name registration should be canceled veya transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are infveyamed by the applicable Provider of the Administrative Panel's decision befveyae 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 veya of sizin address as shown in our Whois database. See Paragraphs 1 ve 3(b)(xiii) of the Rules of Procedure fveya details.) Eğer we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, ve we will take no further action, until we receive (i) evidence satisfactveyay to us of a resolution between the parties; (ii) evidence satisfactveyay to us that sizin lawsuit has been dismissed veya withdrawn; veya (iii) a copy of an veyader from such court dismissing sizin lawsuit veya veyadering that you do not have the right to continue to use sizin domain name.
5. Tümü other disputes ve litigation
Tümü other disputes between you ve any party other than us regarding sizin domain name registration that are not brought pursuant to the mveatveyay administrative proceeding provisions of Paragraph 4 shall be resolved between you ve such other party through any court, arbitration veya other proceeding that may be available.
6. Bizim involvement in disputes
We will not participate in any way in any dispute between you ve any party other than us regarding the registration ve use of sizin domain name. You shall not name us as a party veya 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 ve all defenses deemed appropriate, ve to take any other action necessary to defend ourselves.
7. Maintaining status quo
We will not cancel, transfer, activate, deactivate, veya otherwise change the status of any domain name registration under this Policy except as provided in Paragraph 3 above.
8. Transfers during a dispute
Transfers of a Alan Adı to a Yeni Holder
You may not transfer sizin domain name registration to another holder (i) during a pending administrative proceeding brought pursuant to Paragraph 4 veya fveya a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded; veya (ii) during a pending court proceeding veya arbitration commenced regarding sizin domain name unless the party to whom the domain name registration is being transferred agrees, in writing, to be bound by the decision of the court veya arbitratveya. We reserve the right to cancel any transfer of a domain name registration to another holder that is made in violation of this subparagraph.
Changing Kayıt Kuruluşus
You may not transfer sizin domain name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 veya fveya 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 sizin domain name registration to another registrar during a pending court action veya arbitration, provided that the domain name you have kayıt oled with us shall continue to be subject to the proceedings commenced against you in accveyadance with the terms of this Policy. In the event that you transfer a domain name registration to us during the pendency of a court action veya arbitration, such dispute shall remain subject to the domain name dispute policy of the registrar from which the domain name registration was transferred.
9. Policy modifications
We reserve the right to modify this Policy at any time with the permission of ICANN. We will post our revised Policy at this location at least thirty (30) calendar days befveyae it becomes effective. Unless this Policy has already been invoked by the submission of a complaint to a Provider, in which event the version of the Policy in effect at the time it was invoked will apply to you until the dispute is over, all such changes will be binding upon you with respect to any domain name registration dispute, whether the dispute arose befveyae, on veya after the effective date of our change. In the event that you object to a change in this Policy, sizin sole remedy is to cancel sizin domain name registration with us, provided that you will not be entitled to a refund of any fees you paid to us. The revised Policy will apply to you until you cancel sizin domain name registration.
]]>
1. Overview
These terms of use ("AI Süres of Use") govern sizin use of any AI products, features, hizmets ve/veya tools offered by NiceNIC.NET.
2. Content
1) Your Content. You may provide input to the AI Services ("Input") ve receive output from the AI Services based on the Input ("Output"). Input ve Output are collectively "Content". You are responsible fveya Content, including ensuring that it does not violate any applicable law veya these AI Süres of Use. We own all rights, title, ve interest in ve to the services that we provided.
2) As between you ve NiceNIC.NET, ve to the extent permitted by applicable law, you (a) retain sizin ownership rights in Input ve (b) own the Output. We burayaby assign to you all our right, title, ve interest, if any, in ve to Output. You represent ve warrant that you have all rights, licenses, ve permissions needed to provide Input to our AI Services.
3) We may use Content to provide, maintain, develop, ve improve our Services, comply with applicable law, enfveyace our terms ve policies, to market ve advertise our Services ve 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, veya facts. Output may not always be accurate. You should not rely on Output from our Services as a sole source of truth veya factual infveyamation, veya as a substitute fveya professional advice.
5) NiceNIC.NET also does not review the Content fveya accuracy, bias veya intellectual property rights clearance. NiceNIC.NET makes no representation, warranty veya guarantee as to the accuracy veya reliability of the AI Services veya whether the Output may infringe on third-party intellectual property rights.
6) By using the AI Services, you understve ve agree:
A. Output may not always be accurate. You should not rely on Output from our AI Services as a sole source of truth veya factual infveyamation, veya as a substitute fveya professional advice.
B. You must evaluate Output fveya accuracy ve appropriateness fveya sizin use case, including using human review as appropriate, befveyae using veya sharing Output from the AI Services.
C. You must not use any Output relating to a person fveya any purpose that could have a legal veya material impact on that person, such as making credit, educational, employment, housing, insurance, legal, medical, veya other impveyatant decisions about them.
D. Bizim AI Services may provide incomplete, incveyarect, veya offensive Output that does not represent NiceNIC.NET’s views. Eğer Output references any third party products veya hizmets, it doesn’t mean the third party endveyases veya is affiliated with NiceNIC.NET.
7) Outputs may not be unique across users ve the AI Services may generate the same veya similar Outputs fveya other users.
8) NiceNIC.NET may use technology provided by third-party hizmet providers to provide AI Services. Hayırtwithstveing anything to the contrary contained burayain, you authveyaize NiceNIC.NET ve such third-party hizmet providers to stveyae ve use sizin Input fveya the purposes of providing you with the AI Services, to review Inputs ve Outputs fveya abuse veya misuse, ve to develop ve improve the hizmets ve products of NiceNIC.NET ve such hizmet providers, including as part of the design, training ve development process fveya machine learning models.
3. Süreination ve Suspension
Süreination. We reserve the right to suspend veya terminate sizin access to our AI Services veya delete sizin account if we determine:
1) You breached these AI Süres of Use.
2) We must do so to comply with the law.
3) Your use of our Services could cause risk veya harm to NiceNIC.NET, our users, veya anyone else.
4. Disclaimers
YOU SPECIFICALLY ACKNOWLEDGE AND AGREE THAT OUTPUTS OF THE AI SERVICES HAVE NOT BEEN REVIEWED FVEYA ACCURACY, BIAS, EXPLAINABILITY VEYA INTELLECTUAL PROPERTY RIGHTS CLEARANCE. NiceNIC.NET MAKES NO REPRESENTATION, WARRANTY VEYA GUARANTEE AS TO THE ACCURACY, RELIABILITY, VEYA ERRVEYA-FREE PERFVEYAMANCE OF THE AI SERVICES, INCLUDING (WITHOUT LIMITATION) WHETHER OUTPUTS MAY INFRINGE, MISAPPROPRIATE VEYA 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 VEYA FACTUAL INFVEYAMATION, VEYA AS A SUBSTITUTE FVEYA PROFESSIONAL ADVICE.
YOU SHOULD SEEK INDEPENDENT PROFESSIONAL ADVICE BEFVEYAE YOU RELY ON ANY OUTPUT GENERATED BY THE AI SERVICES.
5. Limitation on Liability
IN NO EVENT SHALL NiceNIC.NET, ITS OFFICERS, DIRECTVEYAS, EMPLOYEES, AGENTS, VEYA ANY THIRD-PARTY SERVICE PROVIDERS, BE LIABLE TO YOU VEYA ANY OTHER PERSON VEYA ENTITY FVEYA ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE, VEYA CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING ANY THAT MAY RESULT FROM ANY OUTPUTS CREATED USING THE AI SERVICES.
THE FVEYAEGOING LIMITATION OF LIABILITY SHALL SURVIVE ANY TERMINATION VEYA EXPIRATION OF THIS AGREEMENT VEYA YOUR USE OF THIS SITE, THE AI SERVICES VEYA ANY OTHER SERVICES FOUND AT THIS SITE.
]]>
In the event that a Transfer İletişim listed in the Whois has not confirmed their request to transfer with the Kayıt Kuruluşu of Recveyad ve the Kayıt Kuruluşu of Recveyad has not explicitly denied the transfer request, the default action will be that the Kayıt Kuruluşu of Recveyad must allow the transfer to proceed.
Upon denying a transfer request fveya any of the following reasons, the Kayıt Kuruluşu of Recveyad must provide the Kayıt Oled Ad Holder ve the potential Gaining Kayıt Kuruluşu with the reason fveya denial. The Kayıt Kuruluşu of Recveyad may deny a transfer request only in the following specific instances:
YOU AGREE THAT WE WILL NOT BE LIABLE FVEYA ANY (1) SUSPENSION VEYA Lİşletim SistemiS OF THE SERVICES (2) USE OF THE SERVICES, (3) INTERRUPTION OF THE SERVICES VEYA INTERRUPTION OF YOUR BUSINESS, (4) ACCESS DELAYS VEYA ACCESS INTERRUPTIONS TO OUR SITE VEYA SERVICES VEYA DELAYS VEYA ACCESS INTERRUPTIONS YOU EXPERIENCE IN RELATION TO THE SERVICES; (5) Lİşletim SistemiS VEYA LIABILITY RESULTING FROM ACTS OF VEYA EVENTS BEYOND OUR CONTROL INCLUDING , BUT NOT LIMITED TO ANY ERRVEYAS VEYA TECHNICAL ISSUES OF ANY DOMAIN NAME REGISTRY VEYA OTHER THIRD PARTY PROVIDER, (6) DATA NON-DELIVERY, MIS-DELIVERY, CVEYARUPTION, DESTRUCTION VEYA OTHER MODIFICATION; (7) VEYA Lİşletim SistemiS VEYA LIABILITY RESULTING FROM THE UNAUTHVEYAIZED USE VEYA MISUSE OF YOUR ACCOUNT IDENTIFIER VEYA PASSWVEYAD.
YOU ALSO AGREE THAT WE WILL NOT BE LIABLE FVEYA ANY INDIRECT, SPECIAL, INCIDENTAL, VEYA CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING Lİşletim SistemiT PROFITS) VEYA FVEYA ANY FINANCIAL VEYA ECONOMIC Lİşletim SistemiS VEYA FVEYA Lİşletim SistemiS OF PROFITS, Lİşletim SistemiS OF BUSINESS, DEPLETION OF GOODWILL VEYA SIMILAR Lİşletim SistemiSES, Lİşletim SistemiS OF ANTICIPATED SAVINGS VEYA Lİşletim SistemiS VEYA CVEYARUPTION OF DATA VEYA INFVEYAMATION, REGARDLESS OF THE FVEYAM OF ACTION WHETHER IN CONTRACT, TVEYAT (INCLUDING NEGLIGENCE), VEYA OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE Pİşletim SistemiSIBILITY OF SUCH DAMAGES.
IN NO EVENT SHALL OUR MAXIMUM AGGREGATE LIABILITY EXCEED THE TOTAL AMOUNT PAID BY YOU FVEYA THE USE OF THE SERVICES, BUT IN NO EVENT GREATER THAN THE AMOUNT FVEYA THE PRIVEYA 1 MONTH OF SERVICES PAID FVEYA UNDER THIS AGREEMENT.
24. General
You may not assign any of sizin rights veya privileges, veya delegate any of sizin duties veya obligations burayaunder, in whole veya in part, by operation of law veya otherwise, to any third party without our priveya written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon ve inure to the benefit of the parties burayato ve their respective permitted successveyas ve assigns.
NiceNIC.NET reserves the right, in its sole ve absolute discretion, to change veya modify this Agreement, ve any policies veya agreements which are incveyapveyaated burayain, at any time ve without notice. Any such changes veya modification shall be effective immediately upon posting to the Site. Eğer 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 veya continue to use the Services. You agree that sizin exclusive remedy is to transfer sizin Services to another registrar veya request us to terminate sizin Services under this Agreement. NiceNIC.NET may occasionally notify you of changes veya modifications to this Agreement veya the Services by email so it is very impveyatant that you keep sizin account infveyamation current ve up to date. NiceNIC.NET is not responsible ve assumes no liability fveya sizin failure to receive an email notification if such failure results from inaccurate veya out-dated account infveyamation.
This Agreement constitutes the entire agreement between the parties concerning the subject matter burayain ve supersedes all priveya understveings ve agreements between the parties, whether written veya veyaal, regarding the subject matter burayain. Any of the provisions of this Agreement which are determined to be invalid veya unenfveyaceable in any jurisdiction shall be ineffective to the extent of such invalidity veya unenfveyaceability in such jurisdiction, without rendering invalid veya unenfveyaceable the remaining provisions burayaof veya affecting the validity veya unenfveyaceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach veya violation of any provision of this Agreement will not constitute veya be construed as a waiver of any subsequent breach veya violation of that provision veya as a waiver of any breach veya violation of any other provision of this Agreement. The headings contained in this Agreement are fveya convenience only ve shall not affect meaning veya interpretation of this Agreement.
25. Hayırtices
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 accveyadance with the Account ve/veya WHOIS infveyamation you have provided.
26. Governing Law
This Agreement ve its subject matter shall be governed in accveyadance with the laws of Hong Kong ve subject to the exclusive jurisdiction of the Hong Kong courts without regard to conflict of laws ve principles contained tburayain with the exception of disputes related to this Agreement which fall under UDRP, URS, veya similar dispute resolution process as defined by various Registry policies incveyapveyaated veya made reference to burayain.
]]>
1.3 The Registrant ackşimdiledges ve agrees that the Kayıt Kuruluşu shall monitveya the status of Alan Adları kayıt oled through the Kayıt Kuruluşu ve shall, at its own initiative veya on receipt of complaint, conduct checks to verify whether a Alan Adı is being used in connection with phishing veya "spam" advertising. The Kayıt Kuruluşu shall delete veya suspend a Alan Adı if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government veya law enfveyacement authveyaity (including without limitation the Hong Kong Police Fveyace veya the Office of Telecommunications Authveyaity) that the use of the Alan Adı is in breach of any laws, directives, guidelines, codes of practice veya regulations issued by such local authveyaities, veya if, in HKIRC's reasonable belief, the continuation of registration of the Alan Adı veya the operation of web site referenced by the Alan Adı is likely to damage veya adversely affect the goodwill, reputation ve operation of HKIRC veya the domain name industry in Hong Kong, veya may expose HKIRC to risks of third party claims veya civil veya criminal prosecution.
Fveya mveyae infveyamation about .HK domain registration, please refer to the latest version of HKIRC Kayıt 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 hizmet provider shall be final ve binding on the Registrant ve 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 ve non-statutveyay cveyapveyaation designated by the Hong-Kong Government to administer the registration of Internet domain names under .hk ve .香港 country-code top level domains. Fveya any comments veya complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find buraya useful infveyamation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppveyat/domain_dispute_policies_ve_procedures/domain_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppveyat/domain_dispute_policies_ve_procedures/rules_of_procedures/; veya E-posta address: info@hkirc.hk.
6 REGISTRANT WARRANTIES
The Registrant ackşimdiledges that the Kayıt Kuruluşu ve HKIRC rely on all representations made ve warranties given by the Registrant in determining if the application fveya a Alan Adı should be approved.
Fveya mveyae infveyamation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domain_policies/EN_Alan Adı_Ad_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. Hayırw that you have met the requirements of ICANN, our team is looking fveyaward to assisting you in completing the Verisign certification process so you can quickly begin kayıt oling .com ve .net domain names. We hope this suppveyat will prove to be helpful in reducing the investment of sizin internal resources ve time."
PIR:
"ICANN has infveyamed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed sizin ICANN accreditation to become a registrar ve 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 sizin agreement with them. Tburaya hasn't been a better time to become involved with .tel domains ve we are pleased to assist you in becoming accredited as a participating .tel registrar."
ICM:
"Congrats on sizin recent ICANN Akreditasyon..."
Neustar:
"We have been notified that sizin company is şimdi ICANN-accredited as a .BIZ registrar. Neustar looks fveyaward to getting sizin company up ve running as soon as possible!"
Daha Fazla registries will be notified by ICANN fveya the cveyaresponding domain names signed in the RAA in the sonraki days, we NiceNIC have been staying fveya the disposal of sign-up/accreditation process, striving to save time ve expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mveyae competitive level. Detayed infveyamation 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"), ve dedicated to offer clients easy to navigate, fast to locate hizmets in domain name registration, web hosting satın al, 1 to 1 customer suppveyat.
Stveing at the peak of internet infrastruture, we firstly need to appreciate every client, ve every website viewer who ever stayed buraya, without sizin persistant suppveyat ve comprehension, we are nothing, hope 2012 will bring you ve sizin family lucky, happy, healthy life.
http://www.icann.org/registrar-repveyats/accreditation-qualified-list.html
http://www.icann.org/registrar-repveyats/accredited-list.html
http://www.internic.com/alpha.html
| ZhuHai NaiSiNiKe Infveyamation Technology Co Ltd. | 2009 | China | .asia .biz .com .info .mobi .name .net .org .tel .xxx |
Tümü the best,
NiceNIC.NET Team
ZhuHai NaiSiNiKe Infveyamation 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 fveya Enfveyacement concerning a dispute under this Dispute Resolution Policy.
1.2 Dispute Resolution Provider
1.3 The Dispute Resolution Provider must be an independent ve neutral third party that is neither associated nveya affiliated with either Kayıt Kuruluşu involved in the dispute veya the Registry Operatveya under which the disputed domain name is kayıt oled. ICANN shall have the authveyaity to accredit one veya mveyae independent ve neutral Dispute Resolution Providers accveyading to criteria developed in accveyadance with this Dispute Resolution Policy.
1.4 FOA
Fveyam of Authveyaization - The stveardized fveyam of consent that the Gaining Kayıt Kuruluşu ve Kayıt Kuruluşu of Recveyad are required to use to obtain authveyaization from the Registrant veya Administrative İletişim in veyader to properly process the transfer of domain name sponsveyaship from one Kayıt Kuruluşu to another.
1.5 Gaining Kayıt Kuruluşu
The Kayıt Kuruluşu that submitted to the Registry the request fveya the transfer of a domain sponsveyaship from the Kayıt Kuruluşu of Recveyad.
1.6 Kayıt Kuruluşu of Recveyad
The Kayıt Kuruluşu of Recveyad fveya a domain name fveya which the Registry received a transfer of sponsveyaship request.
1.7 Registrant
The Registrant is the individual veya veyaganization that kayıt ols a specific domain name. This individual veya veyaganization holds the right to use that specific domain name fveya a specified period of time, provided certain conditions are met ve the registration fees are paid. This person veya veyaganization is the "legal entity" bound by the terms of the relevant hizmet agreement with the Registry operatveya fveya the TLD in question.
1.8 Registry (Registry Operatveya)
The veyaganization authveyaized by ICANN to provide registration hizmets fveya a given TLD to ICANN-accredited Kayıt Kuruluşus.
1.9 Supplemental Rules
The Supplemental Rules shall mean those rules adopted by the Registry Operatveya, in the case of First Seviye disputes (as set fveyath below), veya 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 ve shall cover topics such as fees, wveyad ve page limits ve guidelines, the means fveya communicating with the Provider, ve the fveyam of cover sheets.
1.10 Transfer Policy
The Policy on Transfer of Sponsveyaship of Kayıts between Kayıt Kuruluşus which is in fveyace as part of the Registry-Kayıt Kuruluşu Agreement executed between a Kayıt Kuruluşu ve the Registry, as well as the Kayıt Kuruluşu Akreditasyon Agreement which is executed between ICANN ve all ICANN- accredited registrars.
2. Dispute Resolution Process
Tburaya are two possible steps to the Kayıt Kuruluşu Transfer Dispute Resolution Process. A Kayıt Kuruluşu may elect one veya both of the steps pursuant to the rules below. In the event a Kayıt Kuruluşu either files a Request fveya Enfveyacement (as described below) with a Second-Seviye Dispute Provider, veya files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-Seviye Registry option later fveya the same filing veya matter presented fveya resolution.
2.1 First Seviye - Registry Operatveya
A Kayıt Kuruluşu may choose to file a dispute directly with the relevant Registry Operatveya. Any decisions made by the Registry Operatveya may be appealed to a Dispute Resolution Provider. A Kayıt Kuruluşu may file a dispute directly to a Dispute Resolution Provider; however, in that case the filing Kayıt Kuruluşu would fveyafeit any right to appeal the decision of the Dispute Resolution Provider.
2.2 Second-Seviye - Dispute Resolution Panel
The primary intent of this step is to provide a means fveya 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 wburaya a Kayıt Kuruluşu of Recveyad 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 wburaya a Gaining Kayıt Kuruluşu 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 Seviye (Registry)
3.1 Kayıt Kuruluşu files a Request fveya Enfveyacement with the applicable Registry Operatveya
3.1.1 Either the Gaining veya Kayıt Kuruluşu of Recveyad ("Filing Kayıt Kuruluşu") may submit a Request fveya Enfveyacement. This must be done in accveyadance with the Supplemental Rules adopted by the applicable Registry Operatveya.
3.1.2 The Request fveya Enfveyacement shall be submitted to the Registry ve to the Respondent (the Hayırn-filing Kayıt Kuruluşu) in electronic fveyam ve shall:
(i) Request that the Request fveya Enfveyacement be submitted fveya decision in accveyadance with the Kayıt Kuruluşu Transfer ve Dispute Resolution Policy ve the applicable Supplemental Rules;
(ii) Provide the name, postal ve e-mail addresses, ve the telephone ve fax numbers of the Filing Kayıt Kuruluşu ve those representatives authveyaized by the Filing Kayıt Kuruluşu to act on behalf of the Filing Kayıt Kuruluşu in the administrative proceeding;
(iii) Provide the name of the Respondent ve all infveyamation (including any postal ve e-mail addresses ve telephone ve fax numbers) kşimdin to Filing Kayıt Kuruluşu regarding how to contact Respondent veya any representative of Respondent, including contact infveyamation based on pre-complaint dealings;
(iv) Specify the domain name(s) that is/are the subject of the Request fveya Enfveyacement;
(v) Specify the incident(s) that gave rise to the dispute;
(vi) Describe, in accveyadance with the Policy, the grounds on which the Request fveya Enfveyacement is based;
(vii) State the specific remedy being sought (either approval veya denial of the transfer);
(viii) Identify any other legal proceedings that have been commenced veya terminated in connection with veya relating to any of the domain name(s) that are the subject of the complaint;
(ix) Certify that a copy of the Request fveya Enfveyacement, together with the cover sheet as prescribed by the Provider's Supplemental Rules, has been sent veya transmitted to the Respondent; ve
(x) Conclude with the following statement followed by the signature of the Complainant veya its authveyaized representative:
"<insert name of Filing Kayıt Kuruluşu> agrees that its claims ve remedies concerning the registration of the domain name, the dispute, veya the dispute's resolution shall be solely against the Respondent ve waives all such claims ve remedies against the Registry Operatveya as well as its directveyas, officers, employees, ve agents, except in the case of deliberate wrongdoing veya gross negligence."
"<insert name of Filing Kayıt Kuruluşu> certifies that the infveyamation contained in this Request fveya Enfveyacement is to the best of Filing Kayıt Kuruluşu's kşimdiledge complete ve accurate, that this Request fveya Enfveyacement is not being presented fveya any improper purpose, such as to harass, ve that the assertions in this Request fveya Enfveyacement are warranted under this Policy ve under applicable law, as it şimdi exists veya as it may be extended by a good-faith ve reasonable argument."3.1.3 The Request fveya Enfveyacement may relate to mveyae than one domain name, provided that the domain names involve the same Filing Kayıt Kuruluşu ve Respondent ve that the claims arise out of the same veya similar factual circumstances.
3.1.4 The Request fveya Enfveyacement shall annex the following documentary evidence (as applicable ve available) in electronic fveyam if possible, together with a schedule indexing such evidence:
(i) Fveya the Gaining Kayıt Kuruluşu:
a. Completed Fveyam of Authveyaization ("FOA")
b. Copy of the Whois output fveya the date transfer was initiated, which was used to identify the authveyaized Transfer İletişims
c. Copy of evidence of identity used
d. Copy of a bilateral agreement, final determination of a dispute resolution body veya court veyader in cases when the Registrant of Recveyad is being changed simultaneously with a Kayıt Kuruluşu Transfer
e. Copies of all communications made to the Kayıt Kuruluşu of Recveyad with regard to the applicable transfer request along with any responses from the Kayıt Kuruluşu of Recveyad
(ii) Fveya the Kayıt Kuruluşu of Recveyad:
a. Completed FOA from Kayıt Kuruluşu of Recveyad if applicable
b. Copy of the Whois output fveya the date the transfer was initiated
c. Relevant histveyay of Whois modifications made to the applicable registration
d. Evidence of one of the following if a transfer was denied:
e. Copies of all communications made to the Gaining Kayıt Kuruluşu with regard to the applicable transfer request along with any responses from the Gaining Kayıt Kuruluşu.
3.2 The Hayırn-Filing Kayıt Kuruluşu ("Respondent") shall have seven (7) calendar days from receipt of the Request fveya Enfveyacement to prepare a Response to the Request fveya Enfveyacement ("Response").
3.2.1 The Response shall be submitted in electronic fveyam to both the Registry ve Filing Kayıt Kuruluşu ve shall:
(i) Respond specifically to the statements ve allegations contained in the Request fveya Enfveyacement (This pveyation of the response shall comply with any wveyad veya page limit set fveyath in the Dispute Resolution Provider's Supplemental Rules.);
(ii) Provide the name, postal ve e-mail addresses, ve the telephone ve fax numbers of the Respondent (non-filing Kayıt Kuruluşu);
(iii) Identify any other legal proceedings that have been commenced veya terminated in connection with veya relating to any of the domain name(s) that are the subject of the Request fveya Enfveyacement;
(iv) State that a copy of the Response has been sent veya transmitted to the Filing Kayıt Kuruluşu;
(v) Conclude with the following statement followed by the signature of the Respondent veya its authveyaized representative:
"Respondent certifies that the infveyamation contained in this Response is to the best of Respondent's kşimdiledge complete ve accurate, that this Response is not being presented fveya any improper purpose, such as to harass, ve that the assertions in this Response are warranted under these Rules ve under applicable law, as it şimdi exists veya as it may be extended by a good-faith ve reasonable argument."; ve
(vi) Annex any documentary veya other evidence upon which the Respondent relies, together with a schedule indexing such documents.
3.2.2 Şu tarihte the request of the Respondent, the Registry Operatveya may, in exceptional cases, extend the period of time fveya the filing of the response, but in no case may the extension be mveyae 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 Operatveya.
3.2.3 Eğer a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatveya shall decide the dispute based upon the Request fveya Enfveyacement.
3.3 Registry Operatveya must review all applicable documentation ve compare registrant/contact data with that contained within the authveyaitative Whois database ve reach a conclusion not later than 14 days after receipt of the Response.
3.3.1 Eğer the data included in the Request fveya Enfveyacement does not match the data listed in the authveyaitative Whois, the Registry Operatveya must contact each Kayıt Kuruluşu ve require additional documentation.
3.3.2 Eğer the Gaining Kayıt Kuruluşu cannot provide a complete FOA with data matching that contained within the authveyaitative Whois database, then the Registry Operatveya shall find that the transfer should be reversed. In the case of a thick Registry, if the Kayıt Kuruluşu of Recveyad's Whois is not accessible veya invalid, the Registry Operatveya's Whois should be used. In the case of a thin Registry, if the Kayıt Kuruluşu of Recveyad's Whois is not accessible veya is invalid, the Registry Operatveya must notify ICANN ve place the dispute on hold until such time as the specific problem is resolved by ICANN.
3.3.3 In the case wburaya a Kayıt Kuruluşu of Recveyad denies a request fveya a domain name transfer ("NACKs"), the Kayıt Kuruluşu of Recveyad must provide evidence of one of the factveyas fveya which it is allowed to NACK. Eğer the Kayıt Kuruluşu of Recveyad cannot provide evidence that demonstrates any of the factveyas, ve the Gaining Kayıt Kuruluşu provides to the Registry a complete FOA with data matching that contained within the authveyaitative Whois database, then the transfer must be approved to be processed.
3.3.4 Eğer the data provided by neither Kayıt Kuruluşu appears to be conclusive, then the Registry shall issue a finding of "no decision." Eğer the data provided to the Registry is complete ve provides sufficient basis fveya a determination based on the Policy, the Registry may not issue a finding of "no decision." Either Kayıt Kuruluşu shall be able to appeal such issue to a Second-Seviye Dispute Resolution Provider in accveyadance with the provisions set fveyath below.
3.4 Fees fveya First-Seviye Dispute Resolution Service
3.4.1 Tburaya is no filing fee assessed to the Filing Kayıt Kuruluşu at the time the Request fveya Enfveyacement is submitted to the Registry Operatveya.
3.4.2 The Kayıt Kuruluşu that does not öncekiail in the dispute will be assessed a fee to be set by the Registry Operatveya. Such fee shall be set fveyath in the Registry's Supplemental Rules that are in effect at the time that the Request fveya Enfveyacement 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 Operatveya shall collect the applicable fees from the Filing Kayıt Kuruluşu.
3.5 Availability of Court Proceedings
The procedures set fveyath above shall not öncekient a Kayıt Kuruluşu from submitting a dispute to a court of competent jurisdiction fveya independent resolution befveyae such an administrative proceeding is commenced veya after such proceeding is concluded. Eğer a Registry Operatveya decides a domain name registration should be transferred (either to the Gaining Kayıt Kuruluşu, veya alternatively, back from the Gaining Kayıt Kuruluşu to the Kayıt Kuruluşu of Recveyad), the Registry will wait fourteen (14) calendar days after it is infveyamed of the decision befveyae implementing that decision. The Registry will then implement the decision unless it has received during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted domain name(s). Eğer such documentation is received by the Registry Operatveya within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatveya that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatveya that the lawsuit has been dismissed veya withdrawn; veya (iii) the Registry Operatveya receives a copy of an veyader from such court.
4. Dispute Procedures at the Second Seviye with a Dispute Resolution Provider
4.1 The hizmets of the Dispute Resolution Panel may be invoked in any of the following two situations:
(i) A Filing Kayıt Kuruluşu may elect to skip the First-Seviye dispute process at Registry level ve submit a Request fveya Enfveyacement directly with a Dispute Resolution Provider;
(ii) The non-öncekiailing Kayıt Kuruluşu in a First-Seviye dispute proceeding may submit an appeal of the applicable Registry Operatveya's decision to the Dispute Resolution Provider. Ekleitionally, in the case wburaya the result in the First-Seviye dispute process is a "no-decision," either Kayıt Kuruluşu may file an Appeal of such decision to a Dispute Resolution Provider.
4.2 Initial Request fveya Enfveyacement
4.2.1 In the event that the Filing Kayıt Kuruluşu elects to submit a Request fveya Enfveyacement to the Dispute Resolution Provider in lieu of submitting a Request fveya Enfveyacement to the applicable Registry Operatveya, the obligations ve responsibilities set fveyath 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 ve compare registrant/contact data with that contained within the authveyaitative Whois database ve reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.
(i) Eğer the data does not match the data listed in authveyaitative Whois, the Dispute Resolution Panel should contact each Kayıt Kuruluşu ve require additional documentation.
(ii) Eğer the Gaining Kayıt Kuruluşu is unable to provide a complete FOA with data matching that contained within the authveyaitative 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 Kayıt Kuruluşu of Recveyad's Whois is not accessible veya invalid, the applicable Registry Operatveya's Whois should be used. In the case of a thin Registry, if the Kayıt Kuruluşu of Recveyad's Whois is not accessible veya is invalid, the Dispute Resolution Provider may place the dispute on hold until such time as the problem is resolved.
(iii) In the case wburaya a Kayıt Kuruluşu of Recveyad NACKs a transfer, the Kayıt Kuruluşu of Recveyad must provide evidence of one of the factveyas fveya which it is allowed to NACK as set fveyath in Section 3.1.4 (ii) of this Dispute Resolution Policy. Eğer the Kayıt Kuruluşu of Recveyad cannot provide evidence that demonstrates any of the factveyas, ve the Gaining Kayıt Kuruluşu provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the authveyaitative Whois database at the time of the transfer request, then the transfer should be approved.
(iv) Unlike under the First-Seviye 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 ve determine, based on a preponderance of the evidence, which Kayıt Kuruluşu should öncekiail in the dispute ve what resolution to the Request fveya Enfveyacement will appropriately redress the issues set fveyath in the Request fveya Enfveyacement.
(v) Resolution options fveya the Dispute Resolution Panel are limited to the following:
a. Approve Transfer
b. Deny the Transfer (veya veyadering the domain name be returned to the Kayıt Kuruluşu of Recveyad in cases wburaya a Transfer has already occurred)
4.3 Appeal of First Seviye Dispute Decision veya Registry Operatveya Finding of "Hayır-Decision."
4.3.1 In the event that the Kayıt Kuruluşu which does not öncekiail in the First-Seviye dispute is dissatisfied by the Registry-Operatveya's decision, such Kayıt Kuruluşu 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-Seviye decision was issued.
4.3.2 In the event that the Registry Operatveya issues a finding of "no-decision" in accveyadance with Section 3.3.4 above, either Kayıt Kuruluşu 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-Seviye decision was issued.
4.3.3 In either case, the document submitted by the Kayıt Kuruluşu to the Dispute Resolution Provider shall be referred to as an "Appeal."
4.3.4 The Appellant shall submit the Appeal in electronic fveyam ve shall:
(i) Request that the Appeal be submitted fveya decision in accveyadance with the Policy ve these Rules;
(ii) Provide the name, postal ve e-mail addresses, ve the telephone ve telefax numbers of the Appellant ve of any representative authveyaized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
(iii) Provide the name of the Appellee ve all infveyamation (including any postal ve e-mail addresses ve telephone ve telefax numbers) kşimdin to Appellee regarding how to contact Appellee veya any representative of Appellee, including contact infveyamation based on pre-Request fveya Enfveyacement ve pre-Appeal dealings;
(iv) Specify the domain name(s) that is/are the subject of the Appeal;
(v) Specify the incident(s) which gave rise to the dispute;
(vi) State the basis fveya such appeal, including specific responses to the findings of the Registry Operatveya in the First-Seviye Dispute process. (This pveyation of the response shall comply with any wveyad veya page limit set fveyath in the Dispute Resolution Provider's Supplemental Rules);
(vii) Specify, in accveyadance with the Policy, the remedies sought;
(viii) Identify any other related legal proceedings kşimdin to the Appellant that have been commenced veya terminated in connection with veya relating to any of the domain name(s) that are the subject of the complaint;
(ix) State that a copy of the Appeal, together with the cover sheet as prescribed by the Dispute Resolution Provider's Supplemental Rules, has been sent veya transmitted to the Appellee; ve
(x) Conclude with the following statement followed by the signature of the Appellant veya its authveyaized representative:
"Appellant agrees that its claims ve remedies concerning the registration of the domain name, the dispute, veya the dispute's resolution shall be solely against the Appellee ve waives all such claims ve remedies against the Dispute Resolution Provider ve the Registry Operatveya as well as their directveyas, officers, employees, ve agents, except in the case of deliberate wrongdoing veya gross negligence."
"Appellant certifies that the infveyamation contained in this Appeal is to the best of Appellant's kşimdiledge complete ve accurate, that this Appeal is not being presented fveya any improper purpose, such as to harass, ve that the assertions in this Appeal are warranted under this Policy ve under applicable law, as it şimdi exists veya as it may be extended by a good-faith ve reasonable argument."
4.3.5 The Appeal may relate to mveyae than one domain name, provided that the domain names involve the same decision issued by the Registry Operatveya fveya the First-Seviye Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatveya during the First-Seviye Dispute.
4.3.7 A Dispute Resolution Provider must request all documentation relating to the First-Seviye Dispute from the applicable Registry Operatveya no later than seven (7) calendar days of receipt of the appeal. The Registry Operatveya 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 ve 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 veya 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 Hayırvo basis. Although the Dispute Resolution Panel is not bound by the findings of the Registry Operatveya 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 ve determine the appropriate resolution to the issues presented.
4.4 Fees fveya Second-Seviye Dispute Resolution Service
4.4.1 In the case of either a Request fveya Enfveyacement veya an Appeal filed at the Second Seviye, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms ve 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 Kayıt Kuruluşu veya Appellant, whichever applicable, does not öncekiail in a Second-Seviye dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.
4.4.3 In the event that the Filing Kayıt Kuruluşu veya Appellant, whichever applicable, öncekiails in a Second-Seviye dispute, the Respondent veya 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 Kayıt Kuruluşu veya Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent veya Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accveyadance 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 fveyath above shall not öncekient a Kayıt Kuruluşu from submitting a dispute to a court of competent jurisdiction fveya independent resolution befveyae such administrative proceeding is commenced veya after such proceeding is concluded. Eğer a Dispute Resolution Panel decides a domain name registration should be transferred (either to the Gaining Kayıt Kuruluşu, veya alternatively, back from the Gaining Kayıt Kuruluşu to the Kayıt Kuruluşu of Recveyad), such Kayıt Kuruluşu will wait fourteen (14) calendar days after it is infveyamed of the decision befveyae implementing that decision. The Registry will then implement the decision unless it has received from either of the parties to the dispute during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted domain name(s). Eğer 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 veya withdrawn; veya (iii) a copy of an veyader from such court dismissing the lawsuit veya veyadering certain actions with respect to the domain name.
]]>
1. Kayıt Kuruluşu Requirements
Kayıt Oled Ad Holders must be able to transfer their domain name registrations between Kayıt Kuruluşus provided that the Gaining Kayıt Kuruluşu's transfer process meets the minimum stveards of this policy ve that such transfer is not prohibited by ICANN veya Registry policies. Inter-Kayıt Kuruluşu domain name transfer processes must be clear ve concise in veyader to avoid confusion. Further, Kayıt Kuruluşus should make reasonable effveyats to infveyam Kayıt Oled Ad Holders of, ve provide access to, the published documentation of the specific transfer process employed by the Kayıt Kuruluşus.
1.1 Transfer Authveyaities
The Administrative İletişim ve the Kayıt Oled Ad Holder, as listed in the Losing Kayıt Kuruluşu's veya applicable Registry's (wburaya available) publicly accessible WHOIS hizmet are the only parties that have the authveyaity to approve veya deny a transfer request to the Gaining Kayıt Kuruluşu. In the event of a dispute, the Kayıt Oled Ad Holder's authveyaity supersedes that of the Administrative İletişim.
Kayıt Kuruluşus may use Whois data from either the Kayıt Kuruluşu of Recveyad veya the relevant Registry fveya the purpose of verifying the authenticity of a transfer request; veya from another data source as determined by a consensus policy.
2. Gaining Kayıt Kuruluşu Requirements
Fveya each instance wburaya a Kayıt Oled Ad Holder requests to transfer a domain name registration to a different Kayıt Kuruluşu, the Gaining Kayıt Kuruluşu shall:
2.1 Obtain express authveyaization from either the Kayıt Oled Ad Holder veya the Administrative İletişim (burayaafter, "Transfer İletişim"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Kayıt Kuruluşu from the Transfer İletişim.
2.1.1 The authveyaization must be made via a valid Stveardized Fveyam of Authveyaization (FOA). Tburaya are two different FOA's available at the ICANN website. The FOA labeled "Initial Authveyaization fveya Kayıt Kuruluşu Transfer" must be used by the Gaining Kayıt Kuruluşu to request an authveyaization fveya a registrar transfer from the Transfer İletişim. The FOA labeled "Onaylaation of Kayıt Kuruluşu Transfer Request" may be used by the Kayıt Kuruluşu of Recveyad to request confirmation of the transfer from the Transfer İletişim.
The FOA shall be communicated in English, ve any dispute arising out of a transfer request shall be conducted in the English language. Kayıt Kuruluşus may choose to communicate with the Transfer İletişim in additional languages. However, Kayıt Kuruluşus choosing to exercise such option are responsible fveya the accuracy ve completeness of the translation into such additional non-English version of the FOA.
2.1.2 In the event that the Gaining Kayıt Kuruluşu relies on a physical process to obtain this authveyaization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer İletişim ve further that it is accompanied by a physical copy of the Kayıt Kuruluşu of Recveyad's Whois output fveya the domain name in question.
2.1.2.1 Eğer the Gaining Kayıt Kuruluşu relies on a physical authveyaization process, then the Gaining Kayıt Kuruluşu assumes the burden of obtaining reliable evidence of the identity of the Transfer İletişim ve maintaining appropriate recveyads proving that such evidence was obtained. Further the Gaining Kayıt Kuruluşu also assumes the burden fveya ensuring that the entity making the request is indeed authveyaized to do so. The acceptable fveyams of physical identity are:
2.1.3 In the event that the Gaining Kayıt Kuruluşu relies on an electronic process to obtain this authveyaization the acceptable fveyams of identity would include:
The Kayıt Kuruluşu of Recveyad may not deny a transfer request solely because it believes that the Gaining Kayıt Kuruluşu has not received the confirmation set fveyath above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Kayıt Kuruluşu. The presumption in all cases will be that the Gaining Kayıt Kuruluşu has received ve authenticated the transfer request made by a Transfer İletişim.
2.2 Request, by the transmission of a "transfer" commve as specified in the Kayıt Kuruluşu İçinol Kit, that the Registry Operatveya database be changed to reflect the new Kayıt Kuruluşu.
2.2.1 Transmission of a "transfer" commve constitutes a representation on the part of the Gaining Kayıt Kuruluşu that the requisite authveyaization has been obtained from the Transfer İletişim listed in the authveyaitative Whois database.
2.2.2 The Gaining Kayıt Kuruluşu is responsible fveya validating the Kayıt Oled Ad Holder requests to transfer domain names between Kayıt Kuruluşus. However, this does not preclude the Kayıt Kuruluşu of Recveyad from exercising its option to independently confirm the Kayıt Oled Ad Holder's intent to transfer its domain name to the Gaining Kayıt Kuruluşu in accveyadance with Section 3 of this policy.
3. Obligations of the Kayıt Kuruluşu of Recveyad
A Kayıt Kuruluşu of Recveyad can choose independently to confirm the intent of the Kayıt Oled Ad Holder when a notice of a pending transfer is received from the Registry. The Kayıt Kuruluşu of Recveyad must do so in a manner consistent with the stveards set fveyath in this agreement pertaining to Gaining Kayıt Kuruluşus. In veyader to ensure that the fveyam of the request employed by the Kayıt Kuruluşu of Recveyad is substantially administrative ve infveyamative in nature ve clearly provided to the Transfer İletişim fveya the purpose of verifying the intent of the Transfer İletişim, the Kayıt Kuruluşu of Recveyad must use the FOA.
The FOA shall be communicated in English, ve any dispute arising out of a transfer request, shall be conducted in the English language. Kayıt Kuruluşus may choose to communicate with the Transfer İletişim in additional languages. However, the Kayıt Kuruluşu choosing to exercise such option is responsible fveya the accuracy ve completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes ve procedures set fveyath in this policy. This includes but is not limited to the requirement that no Kayıt Kuruluşu shall add any additional infveyamation to the FOA used to obtain the consent of the Transfer İletişim in the case of a transfer request.
This requirement does not preclude the Kayıt Kuruluşu of Recveyad from marketing to its existing customers through separate communications.
The FOA should be sent by the Kayıt Kuruluşu of Recveyad to the Transfer İletişim as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operatveya.Failure by the Kayıt Kuruluşu of Recveyad 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 İletişim listed in the Whois has not confirmed their request to transfer with the Kayıt Kuruluşu of Recveyad ve the Kayıt Kuruluşu of Recveyad has not explicitly denied the transfer request, the default action will be that the Kayıt Kuruluşu of Recveyad must allow the transfer to proceed.
Upon denying a transfer request fveya any of the following reasons, the Kayıt Kuruluşu of Recveyad must provide the Kayıt Oled Ad Holder ve the potential Gaining Kayıt Kuruluşu with the reason fveya denial. The Kayıt Kuruluşu of Recveyad may deny a transfer request only in the following specific instances:
Instances when the requested change of Kayıt Kuruluşu may not be denied include, but are not limited to:
The Kayıt Kuruluşu of Recveyad has other mechanisms available to collect payment from the Kayıt Oled Ad Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Kayıt Kuruluşu of Recveyad must not employ transfer processes as a mechanism to secure payment fveya hizmets from a Kayıt Oled Ad Holder. Exceptions to this requirement are as follows:
(i) In the case of non-payment fveya öncekiious registration period(s) if the transfer is requested after the expiration date, veya
(ii) In the case of non-payment of the current registration period, if transfer is requested befveyae the expiration date.
4. Kayıt Kuruluşu Coveyadination
Each Kayıt Kuruluşu is responsible fveya keeping copies of documentation, including the FOA ve the Transfer İletişims response tburayato, that may be required fveya filing ve suppveyating a dispute under the dispute resolution policy. Gaining Kayıt Kuruluşus must maintain copies of the FOA as received from the Transfer İletişim as per the stveard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.
Both the Gaining Kayıt Kuruluşu ve the Kayıt Kuruluşu of Recveyad must provide the evidence relied on fveya the transfer during ve after the applicable inter-registrar domain name transaction(s). Such infveyamation must be provided when requested by, ve only by, the other Kayıt Kuruluşu that is party to the transfer transaction. Ekleitionally, ICANN, the Registry Operatveya, a court veya authveyaity with jurisdiction over the matter veya a third party dispute resolution panel may also require such infveyamation within five (5) days of the request.
The Gaining Kayıt Kuruluşu must retain, ve produce pursuant to a request by a Losing Kayıt Kuruluşu, a written veya electronic copy of the FOA. In instances wburaya the Kayıt Kuruluşu of Recveyad has requested copies of the FOA, the Gaining Kayıt Kuruluşu must fulfill the Kayıt Kuruluşu of Recveyads request (including providing the attendant suppveyating documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fveya reversal by the Registry Operatveya veya the Dispute Resolution Panel in the event that a transfer complaint is filed in accveyadance with the requirements of this policy.
Eğer either a Kayıt Kuruluşu of Recveyad veya a Gaining Kayıt Kuruluşu does not believe that a transfer request was hveled in accveyadance with the provisions of this policy, then the Kayıt Kuruluşu may initiate a dispute resolution procedure as set fveyath in Section C of this policy.
Fveya purposes of facilitating transfer requests, Kayıt Kuruluşus should provide ve maintain a unique ve private email address fveya use only by other Kayıt Kuruluşus ve the Registry:
i. This email address is fveya issue related to transfer requests ve the procedures set fveyath in this policy only.
ii. The email address should be managed to ensure messages are received by someone who can respond to the transfer issue.
iii. Messages received at such email address must be responded to within a commercial reasonable timeframe not to exceed seven (7) calendar days.
5. EPP - based Registry Requirements fveya Kayıt Kuruluşus
In EPP-based gTLD Registries, Kayıt Kuruluşus must follow the requirements set fveyath below.
Kayıt Kuruluşus must provide the Kayıt Oled Ad Holder with the unique "AuthInfo" code within five (5) calendar days of the Kayıt Oled Ad Holder's initial request if the Kayıt Kuruluşu does not provide facilities fveya the Kayıt Oled Ad Holder to generate ve manage their own unique "AuthInfo" code.
Kayıt Kuruluşus may not employ any mechanism fveya complying with a Kayıt Oled Ad Holder's request to obtain the applicable "AuthInfo Code" that is mveyae restrictive than the mechanisms used fveya changing any aspect of the Kayıt Oled Ad Holder's contact veya name server infveyamation.
The Kayıt Kuruluşu of Recveyad must not refuse to release an "AuthInfo Code" to the Kayıt Oled Ad Holder solely because tburaya is a dispute between the Kayıt Oled Ad Holder ve the Kayıt Kuruluşu over payment.
Kayıt Kuruluşu-generated "AuthInfo" codes must be unique on a per-domain basis.
The "Auth-Info" codes must be used solely to identify a Kayıt Oled Ad Holder, wburayaas the FOA's still need to be used fveya authveyaization veya confirmation of a transfer request, as described in Section 2 ve Section 4 of this policy.
6. Registry Requirements
Upon receipt of the "transfer" commve from the Gaining Kayıt Kuruluşu, Registry Operatveya will transmit an electronic notification to both Kayıt Kuruluşus. 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 Kayıt Kuruluşu fveya the purpose of facilitating transfers.
The Registry Operatveya shall complete the requested transfer unless, within five (5) calendar days, Registry Operatveya receives a NACK protocol commve from the Kayıt Kuruluşu of Recveyad.
When the Registry's database has been updated to reflect the change to the Gaining Kayıt Kuruluşu, Registry Operatveya will transmit an electronic notification to both Kayıt Kuruluşus. The notification may be sent to the unique email address established by each Kayıt Kuruluşu fveya the purpose of facilitating transfers veya such other email address agreed to by the parties.
The Registry Operatveya shall undo a transfer if, after a transfer has occurred, the Registry Operatveya receives one of the notices as set fveyath below. In such case, the transfer will be reversed ve the domain name reset to its veyaiginal state. The Registry Operatveya 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 Operatveya 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 Kayıt Kuruluşu of Recveyad ve the Gaining Kayıt Kuruluşu sent by email, letter veya fax that the transfer was made by mistake veya was otherwise not in accveyadance with the procedures set fveyath in this policy;
ii. The final determination of a dispute resolution body having jurisdiction over the transfer; veya
iii. Order of a court having jurisdiction over the transfer.
7. Recveyads of Kayıt
Each Kayıt Kuruluşu shall require its customer, the Kayıt Oled Ad Holder, to maintain its own recveyads appropriate to document ve prove the initial domain name registration date.
8. Effect on Süre of Kayıt
The completion by Registry Operatveya of a holder-authveyaized transfer under this Part A shall result in a one-yıl extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) yıl.
B. ICANN-Approved Transfers
Transfer of the sponsveyaship of all the registrations sponsveyaed by one Kayıt Kuruluşu as the result of (i) acquisition of that Kayıt Kuruluşu veya its assets by another Kayıt Kuruluşu, veya (ii) lack of accreditation of that Kayıt Kuruluşu veya lack of its authveyaization with the Registry Operatveya, may be made accveyading to the following procedure:
(a) The gaining Kayıt Kuruluşu must be accredited by ICANN fveya the Registry TLD ve must have in effect a Registry-Kayıt Kuruluşu Agreement with Registry Operatveya fveya the Registry TLD.
(b) ICANN must certify in writing to Registry Operatveya that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual veya imminent business failure of a Kayıt Kuruluşu.
Upon satisfaction of these two conditions, Registry Operatveya will make the necessary one-time changes in the Registry database fveya no charge, fveya transfers involving 50,000 name registrations veya fewer. Eğer the transfer involves registrations of mveyae than 50,000 names, Registry Operatveya will charge the gaining Kayıt Kuruluşu a one-time flat fee of US$ 50,000.
C. Transfer Dispute Resolution Policy
Procedures fveya hveling disputes concerning inter-registrar transfers are set fveyath in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatveyas ve ICANN accredited Kayıt Kuruluşus.
]]>We respect sizin individual privacy. That is why we have adopted this Gizlilik Politikası, which embodies our commitment to the protection of sizin privacy through adburayance to fair electronic infveyamation practices. This Gizlilik Politikası puts you, the individual, in control of how sizin personal infveyamation is processed, ve you have our promise that we will not electronically process sizin personal infveyamation in any way that is incompatible with this Gizlilik Politikası.
This Gizlilik Politikası protects sizin privacy by:
> infveyaming you about the types of personal infveyamation NiceNIC collects about you through its Web sites;4. How We Put Infveyamation İçin Good Use