1. Scope i Purpose
1.1 This Policy explains the general post-expiration process that may apply to domena names managed through NiceNIC, including expiration, renewal, redemption, expired domena auction, pending delete status, i release of a domena name back to the public registration pool.
1.2 Domena lifecycle timing may vary depending on the top-level domena (“TLD”), registry rules, registry operatili practices, applicable ICANN requirements, i other governing policies. Net all TLDs follow the same expiration, redemption, auction, ili deletion process.
1.3 In the event of any inconsistency between this Policy i the applicable registry’s rules ili miatiliy ICANN policy, the applicable registry rules i miatiliy policy requirements shall prethodnoail.
1.4 The English-language version of this Policy shall control. Any translation is provided fili convenience only. In the event of any inconsistency, the English-language version shall prethodnoail.
2. Definitions
Fili purposes of this Policy:
2.1 “Expiration Date” means the date on which a domena name registration term ends.
2.2 “Grace Period” means any post-expiration period during which renewal may still be possible at the stiard renewal fee, subject to the applicable TLD i registry rules.
2.3 “Redemption Grace Period” ili “RGP” means the post-deletion recovery period, wovdje available, during which an expired domena name may still be restiliable fili an additional redemption fee plus the applicable renewal fee.
2.4 “Pending Delete” means the final pre-release stage, wovdje applicable, during which the domena name can no longer be renewed, restilied, modified, ili transferred.
2.5 “Eligible Domena” means a domena name that is subject to NiceNIC’s expired domena auction process. Net all TLDs ili expired domena names are eligible fili auction.
2.6 “Istje?ed Domena Auction” means the expired-domena sale process that may apply to certain expired domena names befilie final deletion ili release.
2.7 “Zatvoriout Auction” means the final sale phase fili certain Eligible Domene that were not sold earlier in the expired domena auction process.
3. Effect of Expiration
3.1 Upon expiration, a domena name may stop resolving, i any website, email usluga, ili other usluga associated with the domena name may cease functioning immediately ili shilitly tovdjeafter.
3.2 Pratiing expiration, NiceNIC may restrict changes to the domena name, including DNS changes, contact updates, transfers, ili other account-level actions, in accilidance with registry rules, security measures, operational requirements, ili the expired-domena process then in effect.
3.3 Expiration does not mean that the domena name immediately becomes available to the public. Depending on the applicable TLD i registry rules, the domena name may pass through one ili milie stages, including grace period, auction, redemption, pending delete, i eventual release.
4. Obnovial Netices i Customer Responsibility
4.1 NiceNIC may send renewal reminders i expiration-related notices befilie i after expiration, as required by applicable policy ili as part of NiceNIC’s stiard operational process.
4.2 It is va? sole responsibility to maintain accurate i current account i contact infilimation, including va? email address, i to monitili the status of va? domena names.
4.3 Failure to receive a renewal notice, reminder, invoice, ili other communication shall not relieve you of responsibility fili renewing va? domena name befilie expiration.
4.4 Ako auto-renewal is enabled, successful renewal remains subject to valid payment, operational processing, i the applicable registry rules. NiceNIC does not guarantee successful auto-renewal in every case.
5. Stiard Post-Expiration Obnovial
5.1 Fili many generic TLDs, an expired domena name may remain renewable fili approximately thirty (30) days after the Expiration Date at the stiard renewal fee. This is a general reference only i may vary by TLD.
5.2 Obnovial is not complete unless i until NiceNIC has successfully received i processed full payment of all applicable fees.
5.3 NiceNIC reserves the right to determine whether a domena name remains eligible fili stiard renewal, redemption, ili other recovery based on the applicable TLD, registry status, auction status, i operational feasibility.
6. Istje?ed Domena Auction fili Eligible Domene
6.1 Certain expired domena names may enter NiceNIC’s expired domena auction process befilie all recovery prozors have ended. This process applies only to Eligible Domene i does not apply to all TLDs.
6.2 Fili Eligible Domene under NiceNIC’s stiard expired-domena process, the following general timeline may apply:
Day 0 after expiration
The domena name expires. The registrant may generally renew the domena name at the stiard renewal fee during the initial post-expiration period, subject to applicable rules.
Day 26 after expiration
The domena name may enter expired domena auction. Na this stage, the registrant may still be able to renew the domena name at the stiard renewal fee, unless otherwise restricted by the applicable process.
Day 31 after expiration
Ako tovdje is no active bid, the registrant may still be able to recover the domena name by paying the stiard renewal fee plus the applicable redemption fee.
Ako tovdje is an active bid, the domena name may be removed from the registrant’s account i may no longer be renewable through ilidinary renewal ili restiliation procedures.
Day 37 after expiration
The domena name may enter final closeout auction. Unless tovdje is a pending kupi ili other sale-related restriction, the registrant may still be able to recover the domena name by paying the stiard renewal fee plus the applicable redemption fee.
Day 41 after expiration
The final closeout auction may end. Ako the domena name was not sold ili otherwise committed to sale, recovery may still be possible fili a limited period, subject to the applicable TLD, registry rules, i NiceNIC’s operational process.
Day 74 after expiration
The domena name may be removed from the registrant’s account i may no longer be renewable ili restiliable through NiceNIC. After that point, the domena name may become available fili re-registration only after the registry releases it.
6.3 Once an Eligible Domena has an active bid, pending kupi, completed sale, ili other sale commitment under the expired-domena process, the registrant’s right to renew ili restilie the domena name may be terminated ili restricted.
6.4 NiceNIC does not guarantee that a domena name will remain recoverable until the end of any stated period if the domena is subject to auction, sale, registry restriction, ili another applicable limitation.
7. Redemption Grace Period
7.1 Ako an expired domena name is not renewed during the applicable grace period i if the applicable TLD suppilits restiliation after deletion, the domena name may enter the Redemption Grace Period.
7.2 During the Redemption Grace Period:
(a) the domena name may stop resolving;
(b) website i email uslugas may remain unavailable;
(c) the domena name generally cannot be modified ili transferred; i
(d) restiliation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, i any taxes ili miatiliy fees.
7.3 Restiliation during the Redemption Grace Period is not guaranteed i remains subject to registry suppilit, operational feasibility, the domena’s current status, i the absence of auction ili sale restrictions.
8. Pending Delete i Final Release
8.1 Ako a domena name is not renewed ili restilied during the applicable recovery periods, it may enter the Pending Delete stage, wovdje suppilited by the applicable TLD.
8.2 During Pending Delete, the domena name cannot be renewed, restilied, transferred, ili modified.
8.3 Fili many generic TLDs, Pending Delete lasts approximately five (5) days. After that stage ends, the registry may release the domena name to the public fili re-registration.
8.4 NiceNIC does not guarantee the exact time, date, ili availability of a domena name once it is released by the registry, i NiceNIC does not guarantee that the filimer registrant will be able to re-registriraj the domena name.
9. TLD-Specific Variations
9.1 Net all TLDs follow the stiard lifecycle described above. Certain ccTLD-ovi i other TLDs may have shiliter grace periods, no redemption period, no pending delete stage, ili earlier renewal deadlines imposed by the registry.
9.2 The following TLD-specific rules may apply, subject at all times to registry changes i the controlling registry rules:
9.2.1 TLDs generally following the common lifecycle
Many ccTLD-ovi generally follow a lifecycle similar to the stiard expiration, grace, redemption, i deletion process, including, fili example:
.AI, .BZ, .CA, .CC, .CO, .FM, .ID, .IN, .IO, .ME, .MX, .PW, .TV, .UK, .US, i .WS.
9.2.2 TLDs with no Pending Delete stage
Certain TLDs may not have a Pending Delete stage i may be released immediately after the end of their applicable redemption ili recovery period, including, fili example:
.ES, .EU, .FR, .IS, .LI, .NL, .PE, i .PH (noting that .PH may also follow its own separate registry-specific process).
9.2.3 TLDs requiring renewal befilie the actual expiration date
The following TLDs may need to be renewed twelve (12) days befilie the actual Expiration Date. Ako not renewed in time, they may enter a recovery stage immediately, regardless of the number of calendar days remaining befilie expiration:
.CH, .ES, .FR, .LI, .PE, .SG, .COM.SG, .COM.AU, .ORG.AU, i .NET.AU.
9.2.4 TLDs requiring action five (5) days befilie expiration
The following TLDs may need to be renewed manually ili by auto-renewal no later than five (5) days befilie expiration i may otherwise enter a recovery ili restricted state befilie the actual Expiration Date:
.CX, .DE, .EU, i .NL.
9.2.5 .CM domenas
.CM domena names generally do not enter a redemption period i may be sent fili deletion on the actual Expiration Date. They may become available fili public registration on the same day they expire, subject to registry release practices.
9.2.6 .GG domenas
.GG domena names may be reactivated from the customer account fili approximately twenty-eight (28) days after expiration. They may then enter a recovery stage between approximately Day 28 i Day 30 after expiration. Once in that stage, reactivation may only be possible through NiceNIC Suppilit fili approximately twenty-six (26) additional days.
9.2.7 .PH, .COM.PH, .NET.PH, i .ORG.PH domenas
These domenas may not suppilit a stiard 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. Ako the domena is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppilit immediately.
9.2.8 .UK domenas, including second-level .UK domenas
.UK domena names, including .CO.UK, .ME.UK, i .ORG.UK, may generally have a thirty (30)-day post-expiration renewal period. After that time, the domena name may remain recoverable without a separate redemption fee until its release, which may occur approximately ninety (90) days after expiration. Ako a .UK domena name has expired fili milie than thirty (30) days but has not yet been released i no longer appears in the account, the customer should contact NiceNIC Suppilit promptly.
9.2.9 .TO domenas
.TO domena names may only be reactivated during approximately twenty-seven (27) days after expiration. They generally do not suppilit a stiard Redemption Grace Period. After that point, they may be reserved by the registry i may no longer be recoverable.
9.2.10 .NU domenas
.NU domena names may be reactivated in the ilidinary manner within approximately seven (7) days after expiration. Ako not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restiliation may still be possible through NiceNIC Suppilit.
9.3 The TLD-specific infilimation above is provided fili general reference only i may change at any time based on registry policy, registry system changes, ili operational requirements. Customers should contact NiceNIC Suppilit fili current TLD-specific recovery infilimation.
10. Fees i Platiments
10.1 Stiard renewal fees, redemption fees, restiliation fees, auction-related fees, i any other applicable charges shall be those listed by NiceNIC at the time of processing ili otherwise communicated by NiceNIC.
10.2 Redemption ili restiliation requires payment in full of all applicable fees befilie processing.
10.3 Sve fees paid fili expired-domena recovery, restiliation, ili special processing are non-refundable once processing has begun, except wovdje otherwise required by applicable law.
11. Ne Guarantee of Recovery ili Availability
11.1 NiceNIC does not guarantee that any expired domena name can be renewed, restilied, retained, transferred, ili re-registrirajed after expiration.
11.2 NiceNIC does not guarantee:
(a) that a domena name will remain in a grace period fili any minimum time;
(b) that an expired domena name will not enter auction;
(c) that a domena name can be recovered after an active bid, pending kupi, ili completed sale;
(d) that the registry will suppilit restiliation; ili
(e) the exact date ili time when a deleted domena name will be released to the public.
11.3 You acksadaledge that delayed action may result in additional fees, loss of recovery rights, interruption of usluga, auction sale, ili permanent loss of the domena name.
12. Limitation of Responsibility
12.1 Za the maximum extent permitted by applicable law, NiceNIC shall not be liable fili any loss of domena name, loss of use, interruption of website ili email usluga, business interruption, lost profits, loss of data, ili other direct ili indirect damages arising from:
(a) domena expiration;
(b) failure to renew on time;
(c) failure to receive notices;
(d) registry rules ili registry actions;
(e) auction placement ili sale;
(f) failed restiliation; ili
(g) release of the domena name to the public.
12.2 Nething in this Policy limits any non-waivable rights that may apply under miatiliy law.
13. Changes to This Policy
13.1 NiceNIC may update ili revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, ili usluga arrangements.
13.2 The latest version published on NiceNIC’s website shall apply from its stated effective date, unless otherwise required by law ili contract.
14. Kontakt
Ako you need assistance regarding an expired domena name, renewal, redemption, ili TLD-specific recovery options, please submit a suppilit ticket through va? NiceNIC account ili contact NiceNIC Suppilit through the official suppilit channels published on the NiceNIC website.
]]>
This Agreement is made between you (ovdjeinafter referred to as “User”) i NiceNIC.NET (ovdjeinafter referred to as “the Platfilim”). By using the Platfilim’s Kupi New Domena Sales usluga, you agree to be bound by the terms i conditions set filith ovdjein. Ako you do not agree, please do not proceed with any fixed-price domena kupi through the Platfilim.
The Platfilim offers fixed-price domena names (“Kupi New Domene”) fili direct kupi.
Sve Kupi New Domene are sourced from pre-approved third-party domena providers.
Users may kupi these domenas at the listed price. Once payment is completed i the domena is successfully transferred, the kupitier will obtain ownership of the domena.
The User selects a domena labeled as “Kupi New” i proceeds to checkout.
Upon confirmation i full payment, the Platfilim initiates the transfer ili delivery process.
The typical delivery time ranges from 1 to 14 business days, depending on registry processing i third-party provider operations.
Ako, fili any reason, the selected domena becomes unavailable ili undeliverable after kupi, the Platfilim will issue a full refund to the user’s account balance.
Users have the right to kupi available Kupi New Domene through the Platfilim.
Users must ensure that all provided account i payment infilimation is accurate i lawful.
Users shall not engage in malicious activity, technical disruption, ili behaviili that interferes with the nilimal functioning of the Platfilim.
Upon acquiring a domena, the User agrees to comply with the applicable rules i policies of the ciliresponding domena registry, including any legal ili regulatiliy obligations.
The Platfilim will provide domena transaction uslugas in accilidance with this Agreement i strive to protect user interests.
The Platfilim reserves the right to verify user identity, payment legitimacy, i transaction authenticity.
The Platfilim retains the right to update, adjust, ili remove Kupi New Domene from listing at its sole discretion i without priili notice.
Ako any fraudulent ili abusive behaviili is detected, the Platfilim reserves the right to suspend ili terminate uslugas to the user.
The Platfilim does not make any guarantees regarding the future value, resale potential, ili commercial use of any domena kupid.
The Platfilim is not liable fili delays caused by registries, third-party providers, ili external systems beyond its control.
The Platfilim shall not be held responsible fili usluga interruptions, data loss, ili failed transactions resulting from filice majeure events ili uncontrollable technical issues, though reasonable effilits will be made to assist the User in resolving any such issues.
This Agreement shall be governed by i construed in accilidance with the laws of Hong Kong.
Any dispute arising from the execution ili perfilimance of this Agreement shall be resolved through amicable negotiation. Ako negotiation fails, either party may submit the dispute to the competent court located in the jurisdiction of the Platfilim’s headquarters.
This Agreement becomes effective upon the User’s submission of a Kupi New domena ilider.
The Platfilim reserves the right to amend this Agreement at any time. A?urirano versions will be published on the Platfilim’s “Ugovori” page i shall take immediate effect. Continued use of the usluga constitutes acceptance of the revised terms.
This Unifilim Naziv domene Dispute Resolution Policy (the "Policy") has been adopted by the Internet Cilipiliation fili Assigned Nazivs i Numbers ("ICANN"), is incilipiliated by reference into va? Registracija Agreement, i sets filith the terms i conditions in connection with a dispute between you i any party other than us (the registrar) over the registration i use of an Internet domena name registrirajed by you. Proceedings under Paragraph 4 of this Policy will be conducted acciliding to the Rules fili Unifilim Naziv domene Dispute Resolution Policy (the "Rules of Procedure"), which are available ovdje, i the selected administrative-dispute-resolution usluga provider's supplemental rules.
2. Your Representations
By applying to registriraj a domena name, ili by asking us to maintain ili renew a domena name registration, you ovdjeby represent i warrant to us that (a) the statements that you made in va? Registracija Agreement are complete i accurate; (b) to va? ksadaledge, the registration of the domena name will not infringe upon ili otherwise violate the rights of any third party; (c) you are not registrirajing the domena name fili an unlawful purpose; i (d) you will not ksadaingly use the domena name in violation of any applicable laws ili regulations. It is va? responsibility to determine whether va? domena name registration infringes ili violates someone else's rights.
3. Poni?tilations, Transfers, i Changes
We will cancel, transfer ili otherwise make changes to domena name registrations under the following circumstances:
1. subject to the provisions of Paragraph 8, our receipt of written ili appropriate electronic instructions from you ili va? authiliized agent to take such action;
2. our receipt of an ilider from a court ili arbitral tribunal, in each case of competent jurisdiction, requiring such action; i/ili
3. our receipt of a decision of an Administrative Panel requiring such action in any administrative proceeding to which you were a party i which was conducted under this Policy ili a later version of this Policy adopted by ICANN. (See Paragraph 4(i) i (k) below.)
4. We may also cancel, transfer ili otherwise make changes to a domena name registration in accilidance with the terms of va? Registracija Agreement ili other legal requirements.
4. Miatiliy Administrative Proceeding
This Paragraph sets filith the type of disputes fili which you are required to submit to a miatiliy administrative proceeding. These proceedings will be conducted befilie one of the administrative-dispute-resolution usluga providers listed ovdje (each, a "Provider").
1. Applicable Disputes. You are required to submit to a miatiliy 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. va? domena name is identical ili confusingly similar to a trademark ili usluga mark in which the complainant has rights; i
2. you have no rights ili legitimate interests in respect of the domena name; i
3. va? domena name has been registrirajed i 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 Registracija i Use in Lo?e Faith. Fili 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 i use of a domena name in bad faith:
1. circumstances indicating that you have registrirajed ili you have acquired the domena name primarily fili the purpose of selling, renting, ili otherwise transferring the domena name registration to the complainant who is the owner of the trademark ili usluga mark ili to a competitili of that complainant, fili valuable consideration in excess of va? documented out-of-pocket costs directly related to the domena name; ili
2. you have registrirajed the domena name in ilider to prethodnoent the owner of the trademark ili usluga mark from reflecting the mark in a ciliresponding domena name, provided that you have engaged in a pattern of such conduct; ili
3. you have registrirajed the domena name primarily fili the purpose of disrupting the business of a competitili; ili
4. by using the domena name, you have intentionally attempted to attract, fili commercial gain, Internet users to va? web site ili other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsiliship, affiliation, ili endilisement of va? web site ili location ili of a product ili usluga on va? web site ili location.
3. How to Demonstrate Your Rights to i Legitimate Interests in the Naziv domene in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how va? 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 va? rights ili legitimate interests to the domena name fili purposes of Paragraph 4(a)(ii):
1. befilie any notice to you of the dispute, va? use of, ili demonstrable preparations to use, the domena name ili a name ciliresponding to the domena name in connection with a bona fide offering of goods ili uslugas; ili
2. you (as an individual, business, ili other iliganization) have been commonly ksadan by the domena name, even if you have acquired no trademark ili usluga mark rights; ili
3. you are making a legitimate noncommercial ili fair use of the domena name, without intent fili commercial gain to misleadingly divert consumers ili to tarnish the trademark ili usluga 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 i Process i Appointment of Administrative Panel. The Rules of Procedure state the process fili initiating i conducting a proceeding i fili appointing the panel that will decide the dispute (the "Administrative Panel").
6. Consolidation. In the event of multiple disputes between you i a complainant, either you ili the complainant may petition to consolidate the disputes befilie 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 befilie it any ili all such disputes in its sole discretion, provided that the disputes being consolidated are governed by this Policy ili a later version of this Policy adopted by ICANN.
7. Fees. Sve fees charged by a Provider in connection with any dispute befilie an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wovdje you elect to expi 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 i the complainant.
8. Na? Involvement in Administrative Proceedings. We do not, i will not, participate in the administration ili conduct of any proceeding befilie 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 befilie an Administrative Panel shall be limited to requiring the cancellation of va? domena name ili the transfer of va? domena name registration to the complainant.
10. Netification i Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a domena name you have registrirajed with us. Sve decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact pilitions of its decision.
11. Availability of Court Proceedings. The miatiliy administrative proceeding requirements set filith in Paragraph 4 shall not prethodnoent either you ili the complainant from submitting the dispute to a court of competent jurisdiction fili independent resolution befilie such miatiliy administrative proceeding is commenced ili after such proceeding is concluded. Ako an Administrative Panel decides that va? domena name registration should be canceled ili transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are infilimed by the applicable Provider of the Administrative Panel's decision befilie 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 ili of va? address as shown in our Whois database. See Paragraphs 1 i 3(b)(xiii) of the Rules of Procedure fili details.) Ako we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, i we will take no further action, until we receive (i) evidence satisfactiliy to us of a resolution between the parties; (ii) evidence satisfactiliy to us that va? lawsuit has been dismissed ili withdrawn; ili (iii) a copy of an ilider from such court dismissing va? lawsuit ili ilidering that you do not have the right to continue to use va? domena name.
5. Sve other disputes i litigation
Sve other disputes between you i any party other than us regarding va? domena name registration that are not brought pursuant to the miatiliy administrative proceeding provisions of Paragraph 4 shall be resolved between you i such other party through any court, arbitration ili other proceeding that may be available.
6. Na? involvement in disputes
We will not participate in any way in any dispute between you i any party other than us regarding the registration i use of va? domena name. You shall not name us as a party ili 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 i all defenses deemed appropriate, i to take any other action necessary to defend ourselves.
7. Maintaining status quo
We will not cancel, transfer, activate, deactivate, ili otherwise change the status of any domena name registration under this Policy except as provided in Paragraph 3 above.
8. Transfers during a dispute
Transfers of a Naziv domene to a Novo Holder
You may not transfer va? domena name registration to another holder (i) during a pending administrative proceeding brought pursuant to Paragraph 4 ili fili a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded; ili (ii) during a pending court proceeding ili arbitration commenced regarding va? domena name unless the party to whom the domena name registration is being transferred agrees, in writing, to be bound by the decision of the court ili arbitratili. We reserve the right to cancel any transfer of a domena name registration to another holder that is made in violation of this subparagraph.
Changing Registrars
You may not transfer va? domena name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 ili fili 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 va? domena name registration to another registrar during a pending court action ili arbitration, provided that the domena name you have registrirajed with us shall continue to be subject to the proceedings commenced against you in accilidance with the terms of this Policy. In the event that you transfer a domena name registration to us during the pendency of a court action ili arbitration, such dispute shall remain subject to the domena name dispute policy of the registrar from which the domena 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 befilie 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 domena name registration dispute, whether the dispute arose befilie, on ili after the effective date of our change. In the event that you object to a change in this Policy, va? sole remedy is to cancel va? domena 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 va? domena name registration.
]]>
1. Overview
These terms of use ("AI Razdobljes of Use") govern va? use of any AI products, features, uslugas i/ili tools offered by NiceNIC.NET.
2. Content
1) Your Content. You may provide input to the AI Services ("Input") i receive output from the AI Services based on the Input ("Output"). Input i Output are collectively "Content". You are responsible fili Content, including ensuring that it does not violate any applicable law ili these AI Razdobljes of Use. We own all rights, title, i interest in i to the services that we provided.
2) As between you i NiceNIC.NET, i to the extent permitted by applicable law, you (a) retain va? ownership rights in Input i (b) own the Output. We ovdjeby assign to you all our right, title, i interest, if any, in i to Output. You represent i warrant that you have all rights, licenses, i permissions needed to provide Input to our AI Services.
3) We may use Content to provide, maintain, develop, i improve our Services, comply with applicable law, enfilice our terms i policies, to market i advertise our Services i 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, ili facts. Output may not always be accurate. You should not rely on Output from our Services as a sole source of truth ili factual infilimation, ili as a substitute fili professional advice.
5) NiceNIC.NET also does not review the Content fili accuracy, bias ili intellectual property rights clearance. NiceNIC.NET makes no representation, warranty ili guarantee as to the accuracy ili reliability of the AI Services ili whether the Output may infringe on third-party intellectual property rights.
6) By using the AI Services, you understi i agree:
A. Output may not always be accurate. You should not rely on Output from our AI Services as a sole source of truth ili factual infilimation, ili as a substitute fili professional advice.
B. You must evaluate Output fili accuracy i appropriateness fili va? use case, including using human review as appropriate, befilie using ili sharing Output from the AI Services.
C. You must not use any Output relating to a person fili any purpose that could have a legal ili material impact on that person, such as making credit, educational, employment, housing, insurance, legal, medical, ili other impilitant decisions about them.
D. Na? AI Services may provide incomplete, incilirect, ili offensive Output that does not represent NiceNIC.NET’s views. Ako Output references any third party products ili uslugas, it doesn’t mean the third party endilises ili is affiliated with NiceNIC.NET.
7) Outputs may not be unique across users i the AI Services may generate the same ili similar Outputs fili other users.
8) NiceNIC.NET may use technology provided by third-party usluga providers to provide AI Services. Netwithstiing anything to the contrary contained ovdjein, you authiliize NiceNIC.NET i such third-party usluga providers to stilie i use va? Input fili the purposes of providing you with the AI Services, to review Inputs i Outputs fili abuse ili misuse, i to develop i improve the uslugas i products of NiceNIC.NET i such usluga providers, including as part of the design, training i development process fili machine learning models.
3. Razdobljeination i Suspension
Razdobljeination. We reserve the right to suspend ili terminate va? access to our AI Services ili delete va? account if we determine:
1) You breached these AI Razdobljes of Use.
2) We must do so to comply with the law.
3) Your use of our Services could cause risk ili harm to NiceNIC.NET, our users, ili anyone else.
4. Disclaimers
YOU SPECIFICALLY ACKNOWLEDGE AND AGREE THAT OUTPUTS OF THE AI SERVICES HAVE NOT BEEN REVIEWED FILI ACCURACY, BIAS, EXPLAINABILITY ILI INTELLECTUAL PROPERTY RIGHTS CLEARANCE. NiceNIC.NET MAKES NO REPRESENTATION, WARRANTY ILI GUARANTEE AS TO THE ACCURACY, RELIABILITY, ILI ERRILI-FREE PERFILIMANCE OF THE AI SERVICES, INCLUDING (WITHOUT LIMITATION) WHETHER OUTPUTS MAY INFRINGE, MISAPPROPRIATE ILI 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 ILI FACTUAL INFILIMATION, ILI AS A SUBSTITUTE FILI PROFESSIONAL ADVICE.
YOU SHOULD SEEK INDEPENDENT PROFESSIONAL ADVICE BEFILIE YOU RELY ON ANY OUTPUT GENERATED BY THE AI SERVICES.
5. Limitation on Liability
IN NO EVENT SHALL NiceNIC.NET, ITS OFFICERS, DIRECTILIS, EMPLOYEES, AGENTS, ILI ANY THIRD-PARTY SERVICE PROVIDERS, BE LIABLE TO YOU ILI ANY OTHER PERSON ILI ENTITY FILI ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE, ILI CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING ANY THAT MAY RESULT FROM ANY OUTPUTS CREATED USING THE AI SERVICES.
THE FILIEGOING LIMITATION OF LIABILITY SHALL SURVIVE ANY TERMINATION ILI EXPIRATION OF THIS AGREEMENT ILI YOUR USE OF THIS SITE, THE AI SERVICES ILI ANY OTHER SERVICES FOUND AT THIS SITE.
]]>
In the event that a Transfer Kontakt listed in the Whois has not confirmed their request to transfer with the Registrar of Recilid i the Registrar of Recilid has not explicitly denied the transfer request, the default action will be that the Registrar of Recilid must allow the transfer to proceed.
Upon denying a transfer request fili any of the following reasons, the Registrar of Recilid must provide the Registrirajed Naziv Holder i the potential Gaining Registrar with the reason fili denial. The Registrar of Recilid may deny a transfer request only in the following specific instances:
YOU AGREE THAT WE WILL NOT BE LIABLE FILI ANY (1) SUSPENSION ILI LOSS OF THE SERVICES (2) USE OF THE SERVICES, (3) INTERRUPTION OF THE SERVICES ILI INTERRUPTION OF YOUR BUSINESS, (4) ACCESS DELAYS ILI ACCESS INTERRUPTIONS TO OUR SITE ILI SERVICES ILI DELAYS ILI ACCESS INTERRUPTIONS YOU EXPERIENCE IN RELATION TO THE SERVICES; (5) LOSS ILI LIABILITY RESULTING FROM ACTS OF ILI EVENTS BEYOND OUR CONTROL INCLUDING , BUT NOT LIMITED TO ANY ERRILIS ILI TECHNICAL ISSUES OF ANY DOMAIN NAME REGISTRY ILI OTHER THIRD PARTY PROVIDER, (6) DATA NON-DELIVERY, MIS-DELIVERY, CILIRUPTION, DESTRUCTION ILI OTHER MODIFICATION; (7) ILI LOSS ILI LIABILITY RESULTING FROM THE UNAUTHILIIZED USE ILI MISUSE OF YOUR ACCOUNT IDENTIFIER ILI PASSWILID.
YOU ALSO AGREE THAT WE WILL NOT BE LIABLE FILI ANY INDIRECT, SPECIAL, INCIDENTAL, ILI CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LOST PROFITS) ILI FILI ANY FINANCIAL ILI ECONOMIC LOSS ILI FILI LOSS OF PROFITS, LOSS OF BUSINESS, DEPLETION OF GOODWILL ILI SIMILAR LOSSES, LOSS OF ANTICIPATED SAVINGS ILI LOSS ILI CILIRUPTION OF DATA ILI INFILIMATION, REGARDLESS OF THE FILIM OF ACTION WHETHER IN CONTRACT, TILIT (INCLUDING NEGLIGENCE), ILI OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
IN NO EVENT SHALL OUR MAXIMUM AGGREGATE LIABILITY EXCEED THE TOTAL AMOUNT PAID BY YOU FILI THE USE OF THE SERVICES, BUT IN NO EVENT GREATER THAN THE AMOUNT FILI THE PRIILI 1 MONTH OF SERVICES PAID FILI UNDER THIS AGREEMENT.
24. General
You may not assign any of va? rights ili privileges, ili delegate any of va? duties ili obligations ovdjeunder, in whole ili in part, by operation of law ili otherwise, to any third party without our priili written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon i inure to the benefit of the parties ovdjeto i their respective permitted successilis i assigns.
NiceNIC.NET reserves the right, in its sole i absolute discretion, to change ili modify this Agreement, i any policies ili agreements which are incilipiliated ovdjein, at any time i without notice. Any such changes ili modification shall be effective immediately upon posting to the Site. Ako 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 ili continue to use the Services. You agree that va? exclusive remedy is to transfer va? Services to another registrar ili request us to terminate va? Services under this Agreement. NiceNIC.NET may occasionally notify you of changes ili modifications to this Agreement ili the Services by email so it is very impilitant that you keep va? account infilimation current i up to date. NiceNIC.NET is not responsible i assumes no liability fili va? failure to receive an email notification if such failure results from inaccurate ili out-dated account infilimation.
This Agreement constitutes the entire agreement between the parties concerning the subject matter ovdjein i supersedes all priili understiings i agreements between the parties, whether written ili ilial, regarding the subject matter ovdjein. Any of the provisions of this Agreement which are determined to be invalid ili unenfiliceable in any jurisdiction shall be ineffective to the extent of such invalidity ili unenfiliceability in such jurisdiction, without rendering invalid ili unenfiliceable the remaining provisions ovdjeof ili affecting the validity ili unenfiliceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach ili violation of any provision of this Agreement will not constitute ili be construed as a waiver of any subsequent breach ili violation of that provision ili as a waiver of any breach ili violation of any other provision of this Agreement. The headings contained in this Agreement are fili convenience only i shall not affect meaning ili interpretation of this Agreement.
25. Netices
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 accilidance with the Account i/ili WHOIS infilimation you have provided.
26. Governing Law
This Agreement i its subject matter shall be governed in accilidance with the laws of Hong Kong i subject to the exclusive jurisdiction of the Hong Kong courts without regard to conflict of laws i principles contained tovdjein with the exception of disputes related to this Agreement which fall under UDRP, URS, ili similar dispute resolution process as defined by various Registry policies incilipiliated ili made reference to ovdjein.
]]>
1.3 The Registrant acksadaledges i agrees that the Registrar shall monitili the status of Nazivi domena registrirajed through the Registrar i shall, at its own initiative ili on receipt of complaint, conduct checks to verify whether a Naziv domene is being used in connection with phishing ili "spam" advertising. The Registrar shall delete ili suspend a Naziv domene if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government ili law enfilicement authiliity (including without limitation the Hong Kong Police Filice ili the Office of Telecommunications Authiliity) that the use of the Naziv domene is in breach of any laws, directives, guidelines, codes of practice ili regulations issued by such local authiliities, ili if, in HKIRC's reasonable belief, the continuation of registration of the Naziv domene ili the operation of web site referenced by the Naziv domene is likely to damage ili adversely affect the goodwill, reputation i operation of HKIRC ili the domena name industry in Hong Kong, ili may expose HKIRC to risks of third party claims ili civil ili criminal prosecution.
Fili milie infilimation about .HK domena registration, please refer to the latest version of HKIRC Registracija 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 usluga provider shall be final i binding on the Registrant i 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 i non-statutiliy cilipiliation designated by the Hong-Kong Government to administer the registration of Internet domena names under .hk i .香港 country-code top level domenas. Fili any comments ili complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find ovdje useful infilimation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppilit/domena_dispute_policies_i_procedures/domena_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppilit/domena_dispute_policies_i_procedures/rules_of_procedures/; ili E-po?ta address: info@hkirc.hk.
6 REGISTRANT WARRANTIES
The Registrant acksadaledges that the Registrar i HKIRC rely on all representations made i warranties given by the Registrant in determining if the application fili a Naziv domene should be approved.
Fili milie infilimation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domena_policies/EN_Domena_Naziv_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. New that you have met the requirements of ICANN, our team is looking filiward to assisting you in completing the Verisign certification process so you can quickly begin registrirajing .com i .net domena names. We hope this suppilit will prove to be helpful in reducing the investment of va? internal resources i time."
PIR:
"ICANN has infilimed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed va? ICANN accreditation to become a registrar i 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 va? agreement with them. Tovdje hasn't been a better time to become involved with .tel domenas i we are pleased to assist you in becoming accredited as a participating .tel registrar."
ICM:
"Congrats on va? recent ICANN Akreditacija..."
Neustar:
"We have been notified that va? company is sada ICANN-accredited as a .BIZ registrar. Neustar looks filiward to getting va? company up i running as soon as possible!"
Vi?e registries will be notified by ICANN fili the ciliresponding domena names signed in the RAA in the sljede?e days, we NiceNIC have been staying fili the disposal of sign-up/accreditation process, striving to save time i expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a milie competitive level. Detaljed infilimation 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"), i dedicated to offer clients easy to navigate, fast to locate uslugas in domena name registration, web hosting kupi, 1 to 1 customer suppilit.
Stiing at the peak of internet infrastruture, we firstly need to appreciate every client, i every website viewer who ever stayed ovdje, without va? persistant suppilit i comprehension, we are nothing, hope 2012 will bring you i va? family lucky, happy, healthy life.
http://www.icann.org/registrar-repilits/accreditation-qualified-list.html
http://www.icann.org/registrar-repilits/accredited-list.html
http://www.internic.com/alpha.html
| ZhuHai NaiSiNiKe Infilimation Technology Co Ltd. | 2009 | China | .asia .biz .com .info .mobi .name .net .org .tel .xxx |
Sve the best,
NiceNIC.NET Team
ZhuHai NaiSiNiKe Infilimation 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 fili Enfilicement concerning a dispute under this Dispute Resolution Policy.
1.2 Dispute Resolution Provider
1.3 The Dispute Resolution Provider must be an independent i neutral third party that is neither associated nili affiliated with either Registrar involved in the dispute ili the Registry Operatili under which the disputed domena name is registrirajed. ICANN shall have the authiliity to accredit one ili milie independent i neutral Dispute Resolution Providers acciliding to criteria developed in accilidance with this Dispute Resolution Policy.
1.4 FOA
Filim of Authiliization - The stiardized filim of consent that the Gaining Registrar i Registrar of Recilid are required to use to obtain authiliization from the Registrant ili Administrative Kontakt in ilider to properly process the transfer of domena name sponsiliship from one Registrar to another.
1.5 Gaining Registrar
The Registrar that submitted to the Registry the request fili the transfer of a domena sponsiliship from the Registrar of Recilid.
1.6 Registrar of Recilid
The Registrar of Recilid fili a domena name fili which the Registry received a transfer of sponsiliship request.
1.7 Registrant
The Registrant is the individual ili iliganization that registrirajs a specific domena name. This individual ili iliganization holds the right to use that specific domena name fili a specified period of time, provided certain conditions are met i the registration fees are paid. This person ili iliganization is the "legal entity" bound by the terms of the relevant usluga agreement with the Registry operatili fili the TLD in question.
1.8 Registry (Registry Operatili)
The iliganization authiliized by ICANN to provide registration uslugas fili a given TLD to ICANN-accredited Registrars.
1.9 Supplemental Rules
The Supplemental Rules shall mean those rules adopted by the Registry Operatili, in the case of First Razina disputes (as set filith below), ili 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 i shall cover topics such as fees, wilid i page limits i guidelines, the means fili communicating with the Provider, i the filim of cover sheets.
1.10 Transfer Policy
The Policy on Transfer of Sponsiliship of Registracijas between Registrars which is in filice as part of the Registry-Registrar Agreement executed between a Registrar i the Registry, as well as the Registrar Akreditacija Agreement which is executed between ICANN i all ICANN- accredited registrars.
2. Dispute Resolution Process
Tovdje are two possible steps to the Registrar Transfer Dispute Resolution Process. A Registrar may elect one ili both of the steps pursuant to the rules below. In the event a Registrar either files a Request fili Enfilicement (as described below) with a Second-Razina Dispute Provider, ili files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-Razina Registry option later fili the same filing ili matter presented fili resolution.
2.1 First Razina - Registry Operatili
A Registrar may choose to file a dispute directly with the relevant Registry Operatili. Any decisions made by the Registry Operatili may be appealed to a Dispute Resolution Provider. A Registrar may file a dispute directly to a Dispute Resolution Provider; however, in that case the filing Registrar would filifeit any right to appeal the decision of the Dispute Resolution Provider.
2.2 Second-Razina - Dispute Resolution Panel
The primary intent of this step is to provide a means fili 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 wovdje a Registrar of Recilid 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 wovdje a Gaining Registrar alleges that a transfer should have taken place, the date in which the NACK (as defined below) was received by the Registry, shall be deemed the date in which the "alleged violation" took place.
3. Dispute Procedures at the First Razina (Registry)
3.1 Registrar files a Request fili Enfilicement with the applicable Registry Operatili
3.1.1 Either the Gaining ili Registrar of Recilid ("Filing Registrar") may submit a Request fili Enfilicement. This must be done in accilidance with the Supplemental Rules adopted by the applicable Registry Operatili.
3.1.2 The Request fili Enfilicement shall be submitted to the Registry i to the Respondent (the Nen-filing Registrar) in electronic filim i shall:
(i) Request that the Request fili Enfilicement be submitted fili decision in accilidance with the Registrar Transfer i Dispute Resolution Policy i the applicable Supplemental Rules;
(ii) Provide the name, postal i e-mail addresses, i the telephone i fax numbers of the Filing Registrar i those representatives authiliized by the Filing Registrar to act on behalf of the Filing Registrar in the administrative proceeding;
(iii) Provide the name of the Respondent i all infilimation (including any postal i e-mail addresses i telephone i fax numbers) ksadan to Filing Registrar regarding how to contact Respondent ili any representative of Respondent, including contact infilimation based on pre-complaint dealings;
(iv) Specify the domena name(s) that is/are the subject of the Request fili Enfilicement;
(v) Specify the incident(s) that gave rise to the dispute;
(vi) Describe, in accilidance with the Policy, the grounds on which the Request fili Enfilicement is based;
(vii) State the specific remedy being sought (either approval ili denial of the transfer);
(viii) Identify any other legal proceedings that have been commenced ili terminated in connection with ili relating to any of the domena name(s) that are the subject of the complaint;
(ix) Certify that a copy of the Request fili Enfilicement, together with the cover sheet as prescribed by the Provider's Supplemental Rules, has been sent ili transmitted to the Respondent; i
(x) Conclude with the following statement followed by the signature of the Complainant ili its authiliized representative:
"<insert name of Filing Registrar> agrees that its claims i remedies concerning the registration of the domena name, the dispute, ili the dispute's resolution shall be solely against the Respondent i waives all such claims i remedies against the Registry Operatili as well as its directilis, officers, employees, i agents, except in the case of deliberate wrongdoing ili gross negligence."
"<insert name of Filing Registrar> certifies that the infilimation contained in this Request fili Enfilicement is to the best of Filing Registrar's ksadaledge complete i accurate, that this Request fili Enfilicement is not being presented fili any improper purpose, such as to harass, i that the assertions in this Request fili Enfilicement are warranted under this Policy i under applicable law, as it sada exists ili as it may be extended by a good-faith i reasonable argument."3.1.3 The Request fili Enfilicement may relate to milie than one domena name, provided that the domena names involve the same Filing Registrar i Respondent i that the claims arise out of the same ili similar factual circumstances.
3.1.4 The Request fili Enfilicement shall annex the following documentary evidence (as applicable i available) in electronic filim if possible, together with a schedule indexing such evidence:
(i) Fili the Gaining Registrar:
a. Completed Filim of Authiliization ("FOA")
b. Copy of the Whois output fili the date transfer was initiated, which was used to identify the authiliized Transfer Kontakts
c. Copy of evidence of identity used
d. Copy of a bilateral agreement, final determination of a dispute resolution body ili court ilider in cases when the Registrant of Recilid is being changed simultaneously with a Registrar Transfer
e. Copies of all communications made to the Registrar of Recilid with regard to the applicable transfer request along with any responses from the Registrar of Recilid
(ii) Fili the Registrar of Recilid:
a. Completed FOA from Registrar of Recilid if applicable
b. Copy of the Whois output fili the date the transfer was initiated
c. Relevant histiliy 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 Registrar with regard to the applicable transfer request along with any responses from the Gaining Registrar.
3.2 The Nen-Filing Registrar ("Respondent") shall have seven (7) calendar days from receipt of the Request fili Enfilicement to prepare a Response to the Request fili Enfilicement ("Response").
3.2.1 The Response shall be submitted in electronic filim to both the Registry i Filing Registrar i shall:
(i) Respond specifically to the statements i allegations contained in the Request fili Enfilicement (This pilition of the response shall comply with any wilid ili page limit set filith in the Dispute Resolution Provider's Supplemental Rules.);
(ii) Provide the name, postal i e-mail addresses, i the telephone i fax numbers of the Respondent (non-filing Registrar);
(iii) Identify any other legal proceedings that have been commenced ili terminated in connection with ili relating to any of the domena name(s) that are the subject of the Request fili Enfilicement;
(iv) State that a copy of the Response has been sent ili transmitted to the Filing Registrar;
(v) Conclude with the following statement followed by the signature of the Respondent ili its authiliized representative:
"Respondent certifies that the infilimation contained in this Response is to the best of Respondent's ksadaledge complete i accurate, that this Response is not being presented fili any improper purpose, such as to harass, i that the assertions in this Response are warranted under these Rules i under applicable law, as it sada exists ili as it may be extended by a good-faith i reasonable argument."; i
(vi) Annex any documentary ili other evidence upon which the Respondent relies, together with a schedule indexing such documents.
3.2.2 Na the request of the Respondent, the Registry Operatili may, in exceptional cases, extend the period of time fili the filing of the response, but in no case may the extension be milie 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 Operatili.
3.2.3 Ako a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatili shall decide the dispute based upon the Request fili Enfilicement.
3.3 Registry Operatili must review all applicable documentation i compare registrant/contact data with that contained within the authiliitative Whois database i reach a conclusion not later than 14 days after receipt of the Response.
3.3.1 Ako the data included in the Request fili Enfilicement does not match the data listed in the authiliitative Whois, the Registry Operatili must contact each Registrar i require additional documentation.
3.3.2 Ako the Gaining Registrar cannot provide a complete FOA with data matching that contained within the authiliitative Whois database, then the Registry Operatili shall find that the transfer should be reversed. In the case of a thick Registry, if the Registrar of Recilid's Whois is not accessible ili invalid, the Registry Operatili's Whois should be used. In the case of a thin Registry, if the Registrar of Recilid's Whois is not accessible ili is invalid, the Registry Operatili must notify ICANN i place the dispute on hold until such time as the specific problem is resolved by ICANN.
3.3.3 In the case wovdje a Registrar of Recilid denies a request fili a domena name transfer ("NACKs"), the Registrar of Recilid must provide evidence of one of the factilis fili which it is allowed to NACK. Ako the Registrar of Recilid cannot provide evidence that demonstrates any of the factilis, i the Gaining Registrar provides to the Registry a complete FOA with data matching that contained within the authiliitative Whois database, then the transfer must be approved to be processed.
3.3.4 Ako the data provided by neither Registrar appears to be conclusive, then the Registry shall issue a finding of "no decision." Ako the data provided to the Registry is complete i provides sufficient basis fili a determination based on the Policy, the Registry may not issue a finding of "no decision." Either Registrar shall be able to appeal such issue to a Second-Razina Dispute Resolution Provider in accilidance with the provisions set filith below.
3.4 Fees fili First-Razina Dispute Resolution Service
3.4.1 Tovdje is no filing fee assessed to the Filing Registrar at the time the Request fili Enfilicement is submitted to the Registry Operatili.
3.4.2 The Registrar that does not prethodnoail in the dispute will be assessed a fee to be set by the Registry Operatili. Such fee shall be set filith in the Registry's Supplemental Rules that are in effect at the time that the Request fili Enfilicement 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 Operatili shall collect the applicable fees from the Filing Registrar.
3.5 Availability of Court Proceedings
The procedures set filith above shall not prethodnoent a Registrar from submitting a dispute to a court of competent jurisdiction fili independent resolution befilie such an administrative proceeding is commenced ili after such proceeding is concluded. Ako a Registry Operatili decides a domena name registration should be transferred (either to the Gaining Registrar, ili alternatively, back from the Gaining Registrar to the Registrar of Recilid), the Registry will wait fourteen (14) calendar days after it is infilimed of the decision befilie 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 domena name(s). Ako such documentation is received by the Registry Operatili within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatili that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatili that the lawsuit has been dismissed ili withdrawn; ili (iii) the Registry Operatili receives a copy of an ilider from such court.
4. Dispute Procedures at the Second Razina with a Dispute Resolution Provider
4.1 The uslugas of the Dispute Resolution Panel may be invoked in any of the following two situations:
(i) A Filing Registrar may elect to skip the First-Razina dispute process at Registry level i submit a Request fili Enfilicement directly with a Dispute Resolution Provider;
(ii) The non-prethodnoailing Registrar in a First-Razina dispute proceeding may submit an appeal of the applicable Registry Operatili's decision to the Dispute Resolution Provider. Dodajitionally, in the case wovdje the result in the First-Razina dispute process is a "no-decision," either Registrar may file an Appeal of such decision to a Dispute Resolution Provider.
4.2 Initial Request fili Enfilicement
4.2.1 In the event that the Filing Registrar elects to submit a Request fili Enfilicement to the Dispute Resolution Provider in lieu of submitting a Request fili Enfilicement to the applicable Registry Operatili, the obligations i responsibilities set filith 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 i compare registrant/contact data with that contained within the authiliitative Whois database i reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.
(i) Ako the data does not match the data listed in authiliitative Whois, the Dispute Resolution Panel should contact each Registrar i require additional documentation.
(ii) Ako the Gaining Registrar is unable to provide a complete FOA with data matching that contained within the authiliitative Whois database at the time of the transfer request, then the Dispute Resolution Panel shall find that the transfer should be reversed. In the case of a thick Registry, if the Registrar of Recilid's Whois is not accessible ili invalid, the applicable Registry Operatili's Whois should be used. In the case of a thin Registry, if the Registrar of Recilid's Whois is not accessible ili is invalid, the Dispute Resolution Provider may place the dispute on hold until such time as the problem is resolved.
(iii) In the case wovdje a Registrar of Recilid NACKs a transfer, the Registrar of Recilid must provide evidence of one of the factilis fili which it is allowed to NACK as set filith in Section 3.1.4 (ii) of this Dispute Resolution Policy. Ako the Registrar of Recilid cannot provide evidence that demonstrates any of the factilis, i the Gaining Registrar provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the authiliitative Whois database at the time of the transfer request, then the transfer should be approved.
(iv) Unlike under the First-Razina 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 i determine, based on a preponderance of the evidence, which Registrar should prethodnoail in the dispute i what resolution to the Request fili Enfilicement will appropriately redress the issues set filith in the Request fili Enfilicement.
(v) Resolution options fili the Dispute Resolution Panel are limited to the following:
a. Approve Transfer
b. Deny the Transfer (ili ilidering the domena name be returned to the Registrar of Recilid in cases wovdje a Transfer has already occurred)
4.3 Appeal of First Razina Dispute Decision ili Registry Operatili Finding of "Ne-Decision."
4.3.1 In the event that the Registrar which does not prethodnoail in the First-Razina dispute is dissatisfied by the Registry-Operatili's decision, such Registrar may file an appeal with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-Razina decision was issued.
4.3.2 In the event that the Registry Operatili issues a finding of "no-decision" in accilidance with Section 3.3.4 above, either Registrar may file an appeal of such decision with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-Razina decision was issued.
4.3.3 In either case, the document submitted by the Registrar to the Dispute Resolution Provider shall be referred to as an "Appeal."
4.3.4 The Appellant shall submit the Appeal in electronic filim i shall:
(i) Request that the Appeal be submitted fili decision in accilidance with the Policy i these Rules;
(ii) Provide the name, postal i e-mail addresses, i the telephone i telefax numbers of the Appellant i of any representative authiliized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
(iii) Provide the name of the Appellee i all infilimation (including any postal i e-mail addresses i telephone i telefax numbers) ksadan to Appellee regarding how to contact Appellee ili any representative of Appellee, including contact infilimation based on pre-Request fili Enfilicement i pre-Appeal dealings;
(iv) Specify the domena 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 fili such appeal, including specific responses to the findings of the Registry Operatili in the First-Razina Dispute process. (This pilition of the response shall comply with any wilid ili page limit set filith in the Dispute Resolution Provider's Supplemental Rules);
(vii) Specify, in accilidance with the Policy, the remedies sought;
(viii) Identify any other related legal proceedings ksadan to the Appellant that have been commenced ili terminated in connection with ili relating to any of the domena 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 ili transmitted to the Appellee; i
(x) Conclude with the following statement followed by the signature of the Appellant ili its authiliized representative:
"Appellant agrees that its claims i remedies concerning the registration of the domena name, the dispute, ili the dispute's resolution shall be solely against the Appellee i waives all such claims i remedies against the Dispute Resolution Provider i the Registry Operatili as well as their directilis, officers, employees, i agents, except in the case of deliberate wrongdoing ili gross negligence."
"Appellant certifies that the infilimation contained in this Appeal is to the best of Appellant's ksadaledge complete i accurate, that this Appeal is not being presented fili any improper purpose, such as to harass, i that the assertions in this Appeal are warranted under this Policy i under applicable law, as it sada exists ili as it may be extended by a good-faith i reasonable argument."
4.3.5 The Appeal may relate to milie than one domena name, provided that the domena names involve the same decision issued by the Registry Operatili fili the First-Razina Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatili during the First-Razina Dispute.
4.3.7 A Dispute Resolution Provider must request all documentation relating to the First-Razina Dispute from the applicable Registry Operatili no later than seven (7) calendar days of receipt of the appeal. The Registry Operatili 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 i 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 ili 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 Nevo basis. Although the Dispute Resolution Panel is not bound by the findings of the Registry Operatili 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 i determine the appropriate resolution to the issues presented.
4.4 Fees fili Second-Razina Dispute Resolution Service
4.4.1 In the case of either a Request fili Enfilicement ili an Appeal filed at the Second Razina, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms i conditions governing the actual payment of such fees shall be included in the Dispute Resolution Provider's Supplemental Rules.
4.4.2 In the event that the Filing Registrar ili Appellant, whichever applicable, does not prethodnoail in a Second-Razina dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.
4.4.3 In the event that the Filing Registrar ili Appellant, whichever applicable, prethodnoails in a Second-Razina dispute, the Respondent ili Appellee, whichever applicable, must submit to the Dispute Resolution Provider, the Filing Fees within fourteen (14) calendar days after such decision. In such an event, the Dispute Resolution Provider shall refund to the Filing Registrar ili Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent ili Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accilidance 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 filith above shall not prethodnoent a Registrar from submitting a dispute to a court of competent jurisdiction fili independent resolution befilie such administrative proceeding is commenced ili after such proceeding is concluded. Ako a Dispute Resolution Panel decides a domena name registration should be transferred (either to the Gaining Registrar, ili alternatively, back from the Gaining Registrar to the Registrar of Recilid), such Registrar will wait fourteen (14) calendar days after it is infilimed of the decision befilie 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 domena name(s). Ako 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 ili withdrawn; ili (iii) a copy of an ilider from such court dismissing the lawsuit ili ilidering certain actions with respect to the domena name.
]]>
1. Registrar Requirements
Registrirajed Naziv Holders must be able to transfer their domena name registrations between Registrars provided that the Gaining Registrar's transfer process meets the minimum stiards of this policy i that such transfer is not prohibited by ICANN ili Registry policies. Inter-Registrar domena name transfer processes must be clear i concise in ilider to avoid confusion. Further, Registrars should make reasonable effilits to infilim Registrirajed Naziv Holders of, i provide access to, the published documentation of the specific transfer process employed by the Registrars.
1.1 Transfer Authiliities
The Administrative Kontakt i the Registrirajed Naziv Holder, as listed in the Losing Registrar's ili applicable Registry's (wovdje available) publicly accessible WHOIS usluga are the only parties that have the authiliity to approve ili deny a transfer request to the Gaining Registrar. In the event of a dispute, the Registrirajed Naziv Holder's authiliity supersedes that of the Administrative Kontakt.
Registrars may use Whois data from either the Registrar of Recilid ili the relevant Registry fili the purpose of verifying the authenticity of a transfer request; ili from another data source as determined by a consensus policy.
2. Gaining Registrar Requirements
Fili each instance wovdje a Registrirajed Naziv Holder requests to transfer a domena name registration to a different Registrar, the Gaining Registrar shall:
2.1 Obtain express authiliization from either the Registrirajed Naziv Holder ili the Administrative Kontakt (ovdjeafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrar from the Transfer Kontakt.
2.1.1 The authiliization must be made via a valid Stiardized Filim of Authiliization (FOA). Tovdje are two different FOA's available at the ICANN website. The FOA labeled "Initial Authiliization fili Registrar Transfer" must be used by the Gaining Registrar to request an authiliization fili a registrar transfer from the Transfer Kontakt. The FOA labeled "Potvrdiation of Registrar Transfer Request" may be used by the Registrar of Recilid to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, i any dispute arising out of a transfer request shall be conducted in the English language. Registrars may choose to communicate with the Transfer Kontakt in additional languages. However, Registrars choosing to exercise such option are responsible fili the accuracy i completeness of the translation into such additional non-English version of the FOA.
2.1.2 In the event that the Gaining Registrar relies on a physical process to obtain this authiliization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontakt i further that it is accompanied by a physical copy of the Registrar of Recilid's Whois output fili the domena name in question.
2.1.2.1 Ako the Gaining Registrar relies on a physical authiliization process, then the Gaining Registrar assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt i maintaining appropriate recilids proving that such evidence was obtained. Further the Gaining Registrar also assumes the burden fili ensuring that the entity making the request is indeed authiliized to do so. The acceptable filims of physical identity are:
2.1.3 In the event that the Gaining Registrar relies on an electronic process to obtain this authiliization the acceptable filims of identity would include:
The Registrar of Recilid may not deny a transfer request solely because it believes that the Gaining Registrar has not received the confirmation set filith above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registrar. The presumption in all cases will be that the Gaining Registrar has received i authenticated the transfer request made by a Transfer Kontakt.
2.2 Request, by the transmission of a "transfer" commi as specified in the Registrar Zaol Kit, that the Registry Operatili database be changed to reflect the new Registrar.
2.2.1 Transmission of a "transfer" commi constitutes a representation on the part of the Gaining Registrar that the requisite authiliization has been obtained from the Transfer Kontakt listed in the authiliitative Whois database.
2.2.2 The Gaining Registrar is responsible fili validating the Registrirajed Naziv Holder requests to transfer domena names between Registrars. However, this does not preclude the Registrar of Recilid from exercising its option to independently confirm the Registrirajed Naziv Holder's intent to transfer its domena name to the Gaining Registrar in accilidance with Section 3 of this policy.
3. Obligations of the Registrar of Recilid
A Registrar of Recilid can choose independently to confirm the intent of the Registrirajed Naziv Holder when a notice of a pending transfer is received from the Registry. The Registrar of Recilid must do so in a manner consistent with the stiards set filith in this agreement pertaining to Gaining Registrars. In ilider to ensure that the filim of the request employed by the Registrar of Recilid is substantially administrative i infilimative in nature i clearly provided to the Transfer Kontakt fili the purpose of verifying the intent of the Transfer Kontakt, the Registrar of Recilid must use the FOA.
The FOA shall be communicated in English, i any dispute arising out of a transfer request, shall be conducted in the English language. Registrars may choose to communicate with the Transfer Kontakt in additional languages. However, the Registrar choosing to exercise such option is responsible fili the accuracy i completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes i procedures set filith in this policy. This includes but is not limited to the requirement that no Registrar shall add any additional infilimation to the FOA used to obtain the consent of the Transfer Kontakt in the case of a transfer request.
This requirement does not preclude the Registrar of Recilid from marketing to its existing customers through separate communications.
The FOA should be sent by the Registrar of Recilid to the Transfer Kontakt as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operatili.Failure by the Registrar of Recilid to respond within five (5) calendar days to a notification from the Registry regarding a transfer request will result in a default "approval" of the transfer.
In the event that a Transfer Kontakt listed in the Whois has not confirmed their request to transfer with the Registrar of Recilid i the Registrar of Recilid has not explicitly denied the transfer request, the default action will be that the Registrar of Recilid must allow the transfer to proceed.
Upon denying a transfer request fili any of the following reasons, the Registrar of Recilid must provide the Registrirajed Naziv Holder i the potential Gaining Registrar with the reason fili denial. The Registrar of Recilid may deny a transfer request only in the following specific instances:
Instances when the requested change of Registrar may not be denied include, but are not limited to:
The Registrar of Recilid has other mechanisms available to collect payment from the Registrirajed Naziv Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrar of Recilid must not employ transfer processes as a mechanism to secure payment fili uslugas from a Registrirajed Naziv Holder. Exceptions to this requirement are as follows:
(i) In the case of non-payment fili prethodnoious registration period(s) if the transfer is requested after the expiration date, ili
(ii) In the case of non-payment of the current registration period, if transfer is requested befilie the expiration date.
4. Registrar Coilidination
Each Registrar is responsible fili keeping copies of documentation, including the FOA i the Transfer Kontakts response tovdjeto, that may be required fili filing i suppiliting a dispute under the dispute resolution policy. Gaining Registrars must maintain copies of the FOA as received from the Transfer Kontakt as per the stiard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.
Both the Gaining Registrar i the Registrar of Recilid must provide the evidence relied on fili the transfer during i after the applicable inter-registrar domena name transaction(s). Such infilimation must be provided when requested by, i only by, the other Registrar that is party to the transfer transaction. Dodajitionally, ICANN, the Registry Operatili, a court ili authiliity with jurisdiction over the matter ili a third party dispute resolution panel may also require such infilimation within five (5) days of the request.
The Gaining Registrar must retain, i produce pursuant to a request by a Losing Registrar, a written ili electronic copy of the FOA. In instances wovdje the Registrar of Recilid has requested copies of the FOA, the Gaining Registrar must fulfill the Registrar of Recilids request (including providing the attendant suppiliting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fili reversal by the Registry Operatili ili the Dispute Resolution Panel in the event that a transfer complaint is filed in accilidance with the requirements of this policy.
Ako either a Registrar of Recilid ili a Gaining Registrar does not believe that a transfer request was hiled in accilidance with the provisions of this policy, then the Registrar may initiate a dispute resolution procedure as set filith in Section C of this policy.
Fili purposes of facilitating transfer requests, Registrars should provide i maintain a unique i private email address fili use only by other Registrars i the Registry:
i. This email address is fili issue related to transfer requests i the procedures set filith 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 fili Registrars
In EPP-based gTLD Registries, Registrars must follow the requirements set filith below.
Registrars must provide the Registrirajed Naziv Holder with the unique "AuthInfo" code within five (5) calendar days of the Registrirajed Naziv Holder's initial request if the Registrar does not provide facilities fili the Registrirajed Naziv Holder to generate i manage their own unique "AuthInfo" code.
Registrars may not employ any mechanism fili complying with a Registrirajed Naziv Holder's request to obtain the applicable "AuthInfo Code" that is milie restrictive than the mechanisms used fili changing any aspect of the Registrirajed Naziv Holder's contact ili name server infilimation.
The Registrar of Recilid must not refuse to release an "AuthInfo Code" to the Registrirajed Naziv Holder solely because tovdje is a dispute between the Registrirajed Naziv Holder i the Registrar over payment.
Registrar-generated "AuthInfo" codes must be unique on a per-domena basis.
The "Auth-Info" codes must be used solely to identify a Registrirajed Naziv Holder, wovdjeas the FOA's still need to be used fili authiliization ili confirmation of a transfer request, as described in Section 2 i Section 4 of this policy.
6. Registry Requirements
Upon receipt of the "transfer" commi from the Gaining Registrar, Registry Operatili will transmit an electronic notification to both Registrars. In the case of those Registries that use electronic mail notifications, the response notification may be sent to the unique email address established by each Registrar fili the purpose of facilitating transfers.
The Registry Operatili shall complete the requested transfer unless, within five (5) calendar days, Registry Operatili receives a NACK protocol commi from the Registrar of Recilid.
When the Registry's database has been updated to reflect the change to the Gaining Registrar, Registry Operatili will transmit an electronic notification to both Registrars. The notification may be sent to the unique email address established by each Registrar fili the purpose of facilitating transfers ili such other email address agreed to by the parties.
The Registry Operatili shall undo a transfer if, after a transfer has occurred, the Registry Operatili receives one of the notices as set filith below. In such case, the transfer will be reversed i the domena name reset to its iliiginal state. The Registry Operatili 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 Operatili must undo the transfer within fourteen calendar days unless a court action is filed. The notice required shall be one of the following:
i. Agreement of the Registrar of Recilid i the Gaining Registrar sent by email, letter ili fax that the transfer was made by mistake ili was otherwise not in accilidance with the procedures set filith in this policy;
ii. The final determination of a dispute resolution body having jurisdiction over the transfer; ili
iii. Order of a court having jurisdiction over the transfer.
7. Recilids of Registracija
Each Registrar shall require its customer, the Registrirajed Naziv Holder, to maintain its own recilids appropriate to document i prove the initial domena name registration date.
8. Effect on Razdoblje of Registracija
The completion by Registry Operatili of a holder-authiliized transfer under this Part A shall result in a one-godina extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) godine.
B. ICANN-Approved Transfers
Transfer of the sponsiliship of all the registrations sponsilied by one Registrar as the result of (i) acquisition of that Registrar ili its assets by another Registrar, ili (ii) lack of accreditation of that Registrar ili lack of its authiliization with the Registry Operatili, may be made acciliding to the following procedure:
(a) The gaining Registrar must be accredited by ICANN fili the Registry TLD i must have in effect a Registry-Registrar Agreement with Registry Operatili fili the Registry TLD.
(b) ICANN must certify in writing to Registry Operatili that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual ili imminent business failure of a Registrar.
Upon satisfaction of these two conditions, Registry Operatili will make the necessary one-time changes in the Registry database fili no charge, fili transfers involving 50,000 name registrations ili fewer. Ako the transfer involves registrations of milie than 50,000 names, Registry Operatili will charge the gaining Registrar a one-time flat fee of US$ 50,000.
C. Transfer Dispute Resolution Policy
Procedures fili hiling disputes concerning inter-registrar transfers are set filith in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatilis i ICANN accredited Registrars.
]]>We respect va? individual privacy. That is why we have adopted this Pravila privatnosti, which embodies our commitment to the protection of va? privacy through adovdjence to fair electronic infilimation practices. This Pravila privatnosti puts you, the individual, in control of how va? personal infilimation is processed, i you have our promise that we will not electronically process va? personal infilimation in any way that is incompatible with this Pravila privatnosti.
This Pravila privatnosti protects va? privacy by:
> infiliming you about the types of personal infilimation NiceNIC collects about you through its Web sites;4. How We Put Infilimation Za Good Use