.com.ee Domain Registration

Estonia Domain - .com.ee Domain Registration

Top Selling Estonian Domains



.com.ee Registry logo

Registration Pricing

  • 1 Year 52.00 USD

Application Fee

Registration Time Frame

3 Weeks


Requirements

Yes Details Are Individual .com.ee domain registrations allowed?

Yes Details Company or legal entities registrations allowed for .com.ee?

Yes Details Are there requirements, documents, or information needed for .com.ee?

Yes Details Are some .com.ee domain names restricted?

No Details Does .com.ee domain have a special use?

No Details Other information I need to know about .com.ee?

Yes Details Are there any additional fees for .com.ee?

No Details Do I need a trademark/brand name to register .com.ee?

No Details WHOIS Privacy service available?

Trustee / Proxy service offered? Fees? Yes Details


.com.ee Domain FAQ

.com.ee General FAQ
Estonia is a state in the Baltic Region of Northern Europe. The country shares borders with Latvia and the Russian Federation and has coastlines on the Gulf of Finland, the Baltic Sea and Lake Peipsi. It has an estimated population of 1.34 million people, and the official language is Estonian, which is closely related to Finnish.

The Estonian economy is supported largely by oil shale energy, telecommunications, textiles, cpr144449003101 chemical services, banking products and food and fishing, among other sectors.

Why should I buy a .com.ee domain name?
Having a .com.ee domain extension will allow you to market your business in this cpr144449003101 stable economy by showing your commitment to the region and lending credibility to your site.
What name can I register?
Certain domains are reserved and these can only be registered as Domain Names under special conditions. The list of reserved domains and the special conditions for their registration are published on the EIF website.

Certain domains are blocked and these cannot be registered as a Domain Name. The list of blocked domains is published on the EIF website.

A Domain Name is not registered if it is identical to a Domain Name with a valid registration.

The Registrant undertakes in good faith before EIF to fulfil the Domain Regulation and instructions published by EIF, and agrees and confirms that:

  • The information in the application cpr144449003101 submitted by the Registrant is correct;
  • The Registrant has the desire and the Registrant also has the right to use the Domain Name marked in the application;
  • The registration and use of the Domain Name does not, to the knowledge of the Registrant, violate any valid legal acts or third party rights;

For complete regulation see here: http://www.internet.ee/eng/domain-regulation/domain-regulation

What is the registration term allowed for .com.ee domain names?
The minimum term for .com.ee cpr144449003101 domain names is 1 year(s).
Can anyone register a .com.ee domain name?

YesAre Individual .com.ee domain registrations allowed?

YesCompany or legal entities registrations allowed for .com.ee?

YesAre there requirements, documents, or information needed for .com.ee?

Organizations: Government issued company business registration number from any country. Individuals: provide your birth date. Trustee service is required and must be selected at checkout for you to manage your domain through our services.

YesAre some .com.ee domain names restricted?

Names identical to another registration, violating rights to third parties, names contrary to the laws of Estonia. See FAQs for complete restrictions.

NoDoes .com.ee domain have a special use?

NoOther information I need cpr144449003101 to know about .com.ee?

YesAre there any additional fees for .com.ee?

Ownership update is considered a new registration and price of new registration will be charged.

NoDo I need a trademark/brand name to register .com.ee?

NoWHOIS Privacy service available?

Yes.com.ee Trustee / Proxy service offered? Fees?

How long does it take to register my .com.ee domain name?
The domain registration time frame for .com.ee during general availability is 3 Weeks. .com.ee is not cpr144449003101 expected to launch until 3 Weeks. Once launched, a registration time frame will be available.
What are the characters and valid character lengths for .com.ee domain names?
Domain Names must:
  • have minimum of 2 and a maximum of 63 characters;
  • begin with a letter or a number and end with a letter or a number;
  • use the English character set and may contain letters (i.e., a-z, A-Z),numbers (i.e. 0-9) and dashes (-) or a combination of these;
  • neither begin with, nor cpr144449003101 end with a dash;
  • not contain a dash in the third and fourth positions (e.g. www.ab- -cd.com.ee); and
  • not include a space (e.g. www.ab cd.com.ee).
Trustee Service for .com.ee

Trustee Service helps you satisfy most local presence requirements when there are restrictions on registering a domain name.

cpr144449003101

Trustee Service Is Available for this extension

How do I host my .com.ee domain name?
bluesit.com offers hosting and email service for .com.ee. You can order hosting, email service and SSL certificates at checkout or you can contact sales.cpr144449003101
How do I transfer my .com.ee domain name?

To transfer your .com.ee domain name to bluesit.com, submit your domain name transfer or contact sales.

To transfer your .com.ee domain cpr144449003101 name out of bluesit.com, contact sales.

Can I transfer out my domain if I’m using your Trustee Service?
Trustee service is non-transferable. If you are using our Trustee Service, you cpr144449003101 must update ownership according to .com.ee requirements before transfer out can be started.
Can I hide my registration information (Private WHOIS)?
No. At present the .com.ee domain zone does not provide means to hide the information cpr144449003101 of the domain owner. All information (name, address, email, etc.) will be displayed in WHOIS.
Can I register my .com.ee domain name in different languages (Internationalized Domain Name)?

Yes, You can register IDNs in the following languages

Grace period for .com.ee domain name?
Grace periods vary for country code Top Level Domains (ccTLD) including Internationalized Domain Names (IDN). Some registries require renewal up to 60 days in advance of the domain name expiration date. It is your responsibility to pay for your Renewal Fees in advance of the due date specified by 101domain regardless of the domain name expiration date. Failure to pay your Renewal Fees prior to the cpr144449003101 due date will result in a fee of $150 to renew your .com.ee domain. There may be a restore period between when the domain expires and when the domain can be registered again. In the event that you do not pay by the renewal date, your site may be inaccessible during this time so it is very important that you renew this extension before the renewal date.
Who is the registry that manages .com.ee domain names?
You may visit them here: Estonian Internet Foundation.cpr144449003101
.com.ee Domains Dispute & Policy

Last Update 20 August 2012. The most current .com.ee domains dispute policy can be found at: www.eestiinternet.ee/upload/files/Rules_of_the_Domain_Disputes_Committee.pdf
(superceeded by the Estonian version)

RULES OF THE DOMAIN DISPUTES COMMITTEE

1. GENERAL PROVISIONS
1.1. The Domain Disputes Committee (hereinafter the Committee) is a structural unit of the Estonian Internet Foundation (hereinafter the EIF) that settles disputes pertaining to registration of .ee domain names. Referral to the Committee does not preclude protection of rights in any other manner, including in judicial proceedings.
1.2. These rules (hereinafter the Rules) are based on article 11.1 of the Domain Regulation adopted by the Council of the EIF on 29.06.2010 (available at http://www.eestiinternet.ee/).
1.3. The Committee settles disputes on the basis of the Rules, the Domain Regulation and Estonian law.
1.4. The EIF organises the work of the Committee. Only members of the Committee settle disputes.
1.5. The Council of the EIF adopts the Rules, the List of Committee Members and amendments thereto.
1.6. The working language of the Committee is Estonian. The Committee has the right to demand that a person who submits foreign language documents have them translated into Estonian as well as to accept foreign language certificates.
2. DEFINITIONS
For the purposes of these Rules the following definitions shall have the following meaning:
2.1. Domain Name means a .ee domain name registered on the basis of the Domain Regulation and constituting the object of the Application;
2.2. Domain Regulation means the Domain Regulation adopted by the Council of the EIF on 29.06.2010;
2.3. EIF means the Estonian Internet Foundation;
2.4. Applicant means the person who submitted the Application;
2.5. Application means a document submitted by the Applicant on the basis of and in accordance with the Rules and along with any and all annexes for the purpose of initiation of a procedure in the Committee;
2.6. Registrant means the person in whose name the Domain Name that constitutes the object of the dispute has been registered;
2.7. Start Date of Procedure means the day when the Application compliant with the requirements has been submitted to the Committee and the Committee procedure fee has been paid to the current account of the Committee;
2.8. Party means the Applicant or the Registrant;
2.9. Parties means the Applicant and the Registrant jointly;
2.10. Rules means these Rules of the Domain Disputes Committee;
2.11. Prior Right means trademarks valid and registered in Estonia; names of individuals; names of entities registered in Estonia; names of the state, local authorities and their agencies; names of international and intergovernmental organisations;
2.12. Committee means the Domain Disputes Committee;
2.13. Committee Member means an individual who has consented to act as a member of the Committee and included in the List of Committee Members approved by the Council of the EIF;
2.14. List of Committee Members means a list of the Members of the Committee published on the website of the EIF;
2.15. Response to the Application means a document submitted by the Registrant in response to the Application on the basis of the Rules along with any and all annexes.
3. DELIVERY AND NOTICES
3.1. Upon submission of the Application to the Registrant, the Committee shall exploit reasonably available means in order to actually inform the Registrant of the Application.
3.2. The Registrant is deemed as actually informed of the Application if:
(a) a written notice on the submission of the Application has been sent to all postal addresses and/or fax numbers specified in the WHOIS database of the EIF under the details of the holder of the Domain Name, technical contact person and administrative contact person; and
(b) the Application has been sent by e-mail to the e-mail addresses of the technical contact person and administrative contact person of the Domain Name specified in the WHOIS database of the EIF; and
(c) the Application has been sent to the Registrant’s e-mail addresses submitted by the Applicant to the Committee pursuant to article 5.2.2.
3.3. Except for the event specified in article 3.2(a), any and all notices and evidence to be submitted on the basis of the Rules must be submitted electronically. The recipient of an electronically sent message is obligated to confirm receipt. In exceptional circumstances the Committee may accept the Party’s notices and evidence on paper or in another manner and in such an event the Party must always add a copy for the other Party in the same format. The Party that submitted the contact details is responsible for the correctness of the contact details and bears the risk of receipt of the notices sent to the respective contact persons.
3.4. If the Committee does not decide otherwise for exceptional reasons, all the notices submitted on the basis of the Rules are deemed as received by the addressee and the terms pertaining to the receipt of the notice start running as follows:
(a) in the case of an e-mail, once the addressee has confirmed the receipt of the e-mail or, at latest, on the first working day following the sending of the e-mail; or
(b) in the case of a fax, on the date indicated in the confirmation of the receipt of the sender's fax message; or
(c) in the case of mail, registered mail or sending by a courier, on the third working day following the submission of the notice to the provider of postal or courier services or on the working date of actual receipt of the notice (depending on which circumstance occurs earlier).
3.5. Any and all notices that have been submitted:
(a) by the Committee to any Party must be concurrently sent to the other Party;
(b) by the Party to the Committee after the Start Date of the Procedure, must be concurrently sent to the other Party.
3.6. The sender is obligated to preserve evidence of the fact and circumstances of sending and the evidence must be available for verification, where necessary.
3.7. If the Party that received the notice receives a notice that the delivery of the notice sent by it failed, the Party shall immediately inform the Committee of the circumstances of sending the notice.
4. WRITTEN PROCEDURE
The procedure in the Committee is a written procedure. No oral hearing takes place (including by way of a teleconference, video conference and web conference), unless the Committee decides on the basis of the right of discretion and special circumstances that an oral hearing is necessary for the purpose of making a decision on the Application.
5. APPLICATION
5.1. The procedure in the Committee may be started by any person, submitting an Application to the Committee if the Domain Name violates its rights for the purposes of article 15.4 of the Rules.
5.2. The Application and the evidence annexed thereto are submitted electronically and the following must be indicated therein:
5.2.1. the name, address and contact details of the Applicant and the same information on the representative if the Applicant is represented by a representative in the procedure; the e-mail address(es) where all the notices to be submitted to the Applicant in the course of the procedure are sent must be specified under the contact details;
5.2.2. the name of the Registrant and all details of the Registrant or its representative known to the Applicant (including mail and e-mail addresses, telephone and fax numbers) through which it is possible to contact the Registrant or its representative, including the possible contact details which the Applicant used in communicating with the Registrant before submission of the Application;
5.2.3. the Domain Name or Names that constitute the object of the dispute;
5.2.4. the choice of the Applicant whether the dispute is settled by a panel of one or three Members of the Committee; in the case of three Members of the Committee the names of the three Members of the Committee must be submitted from the List of Committee Members;
5.2.5. the name of the Registrar via whom the Domain Name has or Domain Names have been registered as of the submission of the Application;
5.2.6. the Prior Rights that the Applicant relies on;
5.2.7. the legal reasons for the Application, above all:
(a) why is the Domain Name identical or misleadingly similar to the Prior Right of the Applicant; and
(b) why the Domain Name has been registered in such a manner that the Registrant does not have the right or legitimate right to the Domain Name; or
(c) why the Domain Name was registered or is being used in bad faith.
5.2.8. The Applicant’s claim either for:
(a) cancellation of the Domain Name or
(b) handing the Domain Name over to the Applicant;
5.2.9. any and all initiated or completed legal proceedings that are directly or indirectly related to the domain name(s) constituting the object(s) of the dispute or the Applicant’s confirmation of the absence of respective proceedings.
5.3. The following must be added to the Application:
5.3.1. evidence by which the Applicant reasons its claim, including evidence of the existence of Prior Rights;
5.3.2. information about payment of the fee of the Committee;
5.3.3. the confirmation specified in article 8 of the Rules, which has been signed by the Applicant or its representative in hand or digitally;
5.3.4. the representative’s power of attorney, if the Applicant is represented by a representative.5.4. The object of the Application may be more than one Domain Name if the Parties are the same.
6. STEPS UPON cpr144449003101 SUBMISSION OF APPLICATION
6.1. The Committee sends the Applicant confirmation of receipt of the Application. If the Committee finds that the Application does not comply with the formal requirements specified in the Rules, the Committee shall inform the Applicant of the defects and gives the Applicant 7 calendar days for elimination of the respective deficiencies. If the Applicant fails to eliminate the deficiencies within the term, the Committee shall inform the Applicant of the refusal to accept the Application. The fee of the Commission paid by the Applicant is not refunded. Refusal to accept the Application on such basis does not deprive the Applicant of the right to submit a new, corrected Application.
6.2. If the Application complies with the formal requirements specified in the Rules and the Commission’s fee has fully accrued to the EIF’s current account, the Committee shall accept the Application. Concurrently with the acceptance, the EIF shall prohibit the cancellation and transfer of the Domain Name (see articles 5.3.6.1 and 5.3.6.2 of the Domain Regulation) until the procedure of settling the dispute or the judicial procedure following it has ended and the decision that has entered into force has been communicated to the EIF.
6.3. The Committee shall submit the Application to the Registrant within a reasonable term and at the same time informs the Applicant of the acceptance of the Application and submission thereof to the Registrant.
6.4. If the Application is filed against a domain name that has already been challenged, the procedure of the later Application shall be suspended until the decision in the first procedure has entered into force. If the Application in the first procedure is approved, upon entry into force of the decision the fees paid to the Committee by the submitters of the subsequent Applications shall be returned to them.
7. RESPONSE TO APPLICATION
7.1. The Registrant submits a Response to the Application within 20 calendar days after receiving the Application.
7.2. In the Response to the Application the Registrant must:
7.2.1. indicate the name, mail and e-mail addresses, telephone and fax numbers of the Registrant and its authorised representative (if any) and specify an e-mail address from among the contact details where all the notices to be submitted in the course of the procedure are to be submitted to the Registrant;
7.2.2. if the Applicant opted for a one-member Committee to resolve the dispute, inform whether the Registrant applies for a three-member Committee instead. If the Registrant opts for a three-member Committee, the Registrant shall pay an additional fee and submit the details of the payment along with a response to the Application. If the respective fee has not been paid, the dispute shall be resolved by a one-member Committee;
7.2.3. name any and all legal proceedings initiated or completed by any domain name or domain names constituting the object of any Application, which the Applicant has not specified in the Application;
7.2.4. submit the legal grounds that serve as the basis for the Response to the Application, especially submit the circumstances that show the Registrant's right or legitimate right to the Domain Name for the purposes of article 15.5 of the Rules.
7.3. The following must be added to the Response to the Application:
7.3.1. evidence, including evidence of the Registrant’s right or legitimate right that the Registrant relies on;
7.3.2. the confirmation specified in article 8 of the Rules, which has been signed by the Registrant or its representative in hand or digitally;
7.3.3. the representative’s power of attorney, if the Registrant is represented by a representative. No power of attorney needs to be added if the representative is the Registrant’s administrative contact person registered in the WHOIS database of the EIF, but the Committee may demand the submission of a power of attorney.
7.4. The Committee confirms to the Registrant the receipt of the Response to the Application. If the Committee finds that the Response to the Application does not comply with the formal requirements specified in the Rules, the Committee shall immediately inform the Registrant of the deficiencies and if the deficiencies can be eliminated, the Committee shall give the Registrant 7 calendar days for elimination of the respective deficiencies. If the Registrant fails to eliminate the deficiencies within the respective term, it shall be deemed that the Registrant has not submitted the Response to the Application.
7.5. The Committee shall immediately submit to the Applicant the Response complying with the formal requirements.
7.6. If the Registrant does not submit the Response to the Application or the Response to the Application does not comply with all the formal requirements and the Registrant fails to eliminate the deficiencies within the prescribed term, the Committee shall inform the Parties of the failure by the Registrant to perform the obligation and send the Response to the Application, which does not comply with the formal requirements, to the Applicant for information purposes. In such an event the Committee may settle the dispute solely on the basis of the Application.
7.7. The provisions of article 7.6 do not deprive the Registrant of the right to have a three-member Committee decide on the case, provided that the additional fee had been paid pursuant to article 7.2.2.
8. PARTY’S WARRANTY
The Applicant adds the following warranty to the Application and the Registrant adds the following warranty to the Response to the Application, thereby the warranty must be signed by the Party or the person authorised by the Party:
“This is to certify that any and all the submitted information is complete and true.

I consent to the processing of my personal data by the Committee to the extent necessary for performance of the Committee’s functions.

I consent to the full publication of the decision (incl. the personal data contained in the decision) made in the procedure on the EIF’s website.

In connection with the procedure in the Committee I waive any and all possible claims and legal measures with regard to the following persons:

(a) the EIF, including the members of its directing bodies, employees, advisors and representatives, except in the event of intentional unlawful acts or omissions;
(b) the Members of the Committee, except in the event of intentional unlawful acts or omissions;
(c) the Registrar, except in the event of intentional unlawful acts or omissions.”
9. APPOINTMENT OF COMMITTEE MEMBERS
9.1. The Application is reviewed by one Committee Member who is appointed at the discretion of the Committee from among the List of Committee Members, except if the Applicant or Registrant applies for a panel of three Members of the Committee.
9.2. If the Registrant has applied for a panel of three members of the Committee in its Response to the Application, the Applicant shall submit to the Committee the names of three Members of the Committee within five calendar days as of the day of delivery of the Response to the Application to the Applicant.
9.3. If the Applicant or the Registrant would like a panel of three Members of the Committee, the Committee shall appoint one member of the panel from among three candidates submitted by the Applicant, one member from among three candidates submitted by the Registrant and one member at its own discretion from the List of Committee Members. If any of the Parties has failed to submit its three candidates, the Committee shall, at its own discretion, appoint an additional member from the List of Committee Members.
9.4. After appointment of the Committee Members the Committee shall inform the Parties of the Committee Members and the date when the Committee makes a decision on the Application.
10. LIST, IMPARTIALITY AND INDEPENDENCE OF COMMITTEE MEMBERS
10.1. The List of Committee Members and amendments thereto are approved by the Council of the EIF. The List of Committee Members is published on the website of the EIF.
10.2. The Committee Members maintain confidentiality of the information submitted to them in the course of the procedure, unless such information has been submitted in a decision that is subject to publication.
10.3. A Committee Member must be and seem to be impartial and independent. A Committee Member may remove themselves if at any stage of the procedure any circumstances that may lead to reasonable doubts about the impartiality or independence of the Committee Member become evident or if the resolution of the case by the Member may seem partial and dependent. In such an event the Committee appoints a new Committee Member.
10.4. The Parties may request that a Committee Member be removed. The Party that requests the removal of a Committee Member must submit the reasons as to why it requests the removal. The removal application must be submitted within five calendar days after learning of the circumstances communicated by the Party that undermine the impartiality and independence of the Committee Member.
10.5. If one of the Parties requests that a Committee Member be removed, the other Party and the respective Committee Member shall have the right to reply to the removal request within five calendar days after receiving the removal request. The Committee Member appointed by the Committee decides on the removal and their decision is final and not subject to appeal.
11. ADDITIONAL SUBMISSIONS
The Committee may, based on the right of discretion, request or accept additional submissions or documents from both Parties in addition to the Application and the Response to the Application.
12. ADMISSION
If a Party to the procedure does not respond within the term set by the Committee, the Committee may deem it consenting to the statements of fact and legal statements or claims of the other Party (admission).
13. EXTENSION OF TERMS
At the request of a Party submitted before the expiry of the respective term or terms, the Committee may, based on the right of discretion and in the event of existence of special circumstances or by agreement of the Parties, extend the term.
14. AGREEMENT BETWEEN PARTIES, SUSPENSION OF PROCEDURE AND TERMINATION OF PROCEDURE
14.1. The Committee terminates the procedure once it has obtained confirmation from both Parties that the Parties have come to an agreement on the Domain Name constituting the object of the dispute.
14.2. If the Parties would like to negotiate in order to come to an agreement, the Parties may request that the Committee suspend the procedure for the term specified in the request. At the request of the Parties the Committee may extend the term for suspension of the procedure. The procedure continues with the receipt of the respective application from the Registrant or the Applicant or with the expiry of the established term.
14.3. If an action or another legal procedure has been initiated before or is initiated during the procedure in the Committee with regard to the Domain Name constituting the object of the dispute between the same Parties, the Committee may decide based on the right of discretion whether to suspend or terminate the Committee procedure or make a decision.
14.4. With good reason and on exceptional circumstances the Committee may suspend the procedure also at the request of one Party. In such an event the procedure continued on the Committee’s own initiative or on the basis of the request of the Party that applied for suspension.
14.5. The Committee also terminates the Procedure once it becomes evident that with regard to the Domain Name constituting the object of the dispute between the parties:
(a) the final decision by a competent court, court of arbitration or the Committee has been made; or
(b) the court has, by way of a measure for securing the action, prohibited a procedure in the Committee or taken measures for securing the action, which would impede enforcement of the Committee's decision.
15. DECISION
15.1. The Committee makes a decision on the basis of the Parties’ positions and documents, which have been submitted in accordance with the Rules.
15.2. The decisions of the Committee are final, they cannot be appealed against and they are binding upon the Parties, relevant Registrars and the EIF. This does not preclude the Party’s right to initiate a judicial procedure against the other Party, which results in the consequences set out in the Rules (see article 15.8).
15.3. The Committee makes a decision to approve the Application only regarding the deletion of a disputed Domain Name or transfer thereof to the Applicant.
15.4. The Committee approves the Application by a decision if the Applicant proves that:
(a) the Domain Name is identical or misleadingly similar to the Prior Right of the Applicant; and
(b) the Domain Name had been registered without the Registrant being entitled to having a legitimate interest in the Domain Name; or
(c) the Domain Name has been registered or is being used in bad faith.
15.5. The Registrant’s right or legitimate right to the Domain Name for the purposes of article 15.4(b) may be proven, among other things, but not only, by the following circumstances, if the Committee considers these circumstances as proven on the basis of all the submitted evidence:
(a) before the dispute the Registrant actually used the Domain Name or name that corresponded to the Domain Name in connection with provision of goods or services or make certifiable preparations for the same;
(b) the Registrar is well-known by the Domain Name, even if it has no legal protection for the name;
(c) the Registrant uses the Domain Name lawfully and for a noncommercial purpose and honestly, without the intention of misleading consumers or harming or taking advantage of the reputation of the Applicant or its Prior Right.
15.6. Among other things, but not only, the following circumstances may prove registration or use of the Domain Name in bad faith for the purposes of article 15.4(c), if the Committee finds that the following circumstances have occurred:
(a) the Domain Name had been registered or obtained directly with the aim of selling the Domain Name, granting the right of use of the Domain Name or otherwise transfer the Domain Name to the holder of the Prior Right or to the Applicant’s competitor for a fee that considerably exceeds the direct costs of registration of the Domain Name; or
(b) the Domain Name has been registered with the aim of preventing the exercise of the Prior Right in the respective Domain Name if:
(i) the Registrant has repeatedly carried out a similar activity; or
(ii) the Domain Name has not been used in the appropriate manner for a period of no less than two years following the date of registration;
(c) the main aim of registration of the Domain Name was to disturb the activities of the Applicant; or
(d) the Domain Name was used intentionally for attracting Internet users with the aim of making profit on the Registrant's websites or in other online places, creating the risk of confusion with the Prior Right; or
(e) the Domain Name is the name of an individual and there is no connection between the Registrant and the Domain Name, which would justify the use of the name. 15.7. A decision of the Committee of three Members is adopted by simple majority.
15.8. A decision of the Committee is made in writing, contains the reasons for the decision, the date of the decision and the name(s) of the Member(s) of the Committee who made the decision. If the Committee decides that the disputed Domain Name is to be cancelled or transferred to the Applicant, it shall be noted in the decision that the EIF must enforce the decision within 14 calendar days after its entry into force, unless the Registrant informs the EIF of initiation of a further judicial procedure against the Applicant and submits to the EIF a respective court ruling on securing the action (see articles 15.2 and 16).
15.9. If the Committee comes to the conclusion that the dispute is not subject to its competence, the Committee shall declare so in its decision.
15.10. The Committee shall send the decision to the Parties, the respective Registrar and the EIF within one month after confirming the receipt of the Response to the Application, which complies with the formal requirements or expiry of the term of submission of a Response to the Application.
15.11. The full text of the decision is published on the website of the EIF.
16. ENTRY INTO FORCE AND ENFORCEMENT OF DECISION
16.1. A decision of the Committee enters into force on the date of making the decision. The EIF does not enforce the decision before 14 calendar days have passed from the entry into force of the decision.
16.2. If the Committee decided to approve the Application, the Registrant shall have 14 calendar days from the date of making the decision in order to inform the EIF of the initiation of a judicial procedure against the Applicant and application of a measure securing the action, which prohibits the EIF from deleting the Domain Name or transferring it to the Applicant. Upon receiving such information and a ruling, the EIF shall not enforce the Committee's decision until the subsequent judicial procedure has come to an end and the judgment that has entered into force has reached the EIF.
17. FINAL PROVISIONS
17.1. The EIF and the Members of the Committee are not liable before the Parties for their acts or omissions in the course of the procedure held on the basis of the Rules, unless the EIF or a Member of the Committee has committed an intentional unlawful act.
17.2. The Rules shall be applicable to any and all Applications filed as of 5 July 2010.
17.3. If the Rules are amended during a procedure, the Rules in force at the time of taking a respective procedural step shall be applied.
17.4. Amendments to the Rules enter into force at least 30 days after their approval by the Council of the EIF. The Council of the EIF may set a longer period for the entry into force of amendments.In case of any wording misapprehensions between the English and Estonian version of this document, wording in Estonian is superior and legally binding.
.com.ee Glossary of Technical Terms

.INT
A top-level domain devoted solely to international treaty organizations that have independent legal personality. Such organizations are not governed by the laws of any specific country, rather by mutual agreement between multiple countries. IANA maintains the domain registry for this domain.

A record
The representation of an IPv4 address in the DNS system.

AAAA record
The representation of an IPv6 address in the DNS system.

Administrative contact
Majority of the registries require 4 contacts for a successful domain registration: Registrant, Administrative, Technical and Billing. The Administrative contact is intended to represent the Registrant(owner) of the domain, in any non-technical matters, regarding the management of the domain. Certain extensions require Administrative contact to confirm requests and accept notices about the domain name.

A-label
The ASCII-compatible encoded (ACE) representation of an internationalized domain name, i.e. how it is transmitted internally within the DNS protocol. A-labels always commence the with the prefix "xn--". Contrast with U-label.

ARPA
Originally a reference to the US Government agency that managed some of the Internet’s initial development, now a top-level domain used solely for machine-readable use by computers for certain protocols — such as for reverse IP address lookups, and ENUM. The domain is not designed for general registrations. IANA manages ARPA in conjunction with the Internet Architecture Board.

ASCII (American Standard Code for Information Interchange)
The standard for transmitting English (or "Latin") letters over the Internet. DNS was originally limited to only Latin characters because it uses ASCII as its encoding format, although this has been expanded using Internationalized Domain Names(IDN) for Applications.

Authoritative Name Server
A domain name server configured to host the official record of the contents of a DNS zone. Each Estonian .com.ee domain name must have a set of these so computers on the Internet can find out the contents of that domain. The set of authoritative name servers for any given domain must be configured as NS records in the parent domain.

Automatic Renewal
The service of automatic renewal allows the customers the convenience of automatic billing for the services ordered through the domain registrar. If the automatic renewal is selected, customer's credit card will be automatically charged for the service, which will avoid the interruption in service.

Billing Contact
Majority of the registries require 4 contacts for a successful domain registration: Registrant, Administrative, Technical and Billing. The Billing contact is responsible for the payment of the domain, and is usually assigned to the registrar managing the domain.

Caching Resolver
The combination of a recursive name server and a caching name server.

Cloaking Forwarding
Domains can be forwarded to another URL by using a forwarding service. Cloaking forwarding differs from Apache 301 forwarding by showing the content of the URL being forwarded to, however the URL bar displays the original domain name.

CNAME Record
A CNAME record is an abbreviation for Canonical Name record and is a type of resource record in the Domain Name System (DNS) used to specify that a domain name is an alias for another domain, the "canonical" domain. CNAME has a very specific syntax rule. CNAME can only be set up for the unique subdomain, meaning that it cannot be set up for any subdomain, which has already been set up for the domain. Thus CNAME is most commonly set up for WWW subdomain.

Country-code top-level domain (ccTLD)
A Class of Top Level Domains, generally assigned or reserved by a country, sovereign state, or territory. IANA is the organization, responsible for the ccTLD assignments. Since 2010 there 2 types of ccTLDs: 2 letter ASCII characters TLDs and IDN TLDs, which consist of the native language characters. Each country/territory is able to implement certain restrictions and requirements on the ccTLD assigned to them.

Cross-Registry Information Service Protocol (CRISP)
The name of the working group at the IETF that developed the Internet Registry Information Service (IRIS), a next-generation WHOIS protocol replacement.

Delegation
Any transfer of responsibility to another entity. In the domain name system, one name server can provide pointers to more useful name servers for a given request by returning NS records. On an administrative level, sub-domains are delegated to other entities. IANA also delegates IP address blocks to regional Internet registries.

Deletion
Deletion of the domain results in the domain record being removed from the registry's database. Domain deletion procedure and availability differs depending on each of the TLD's policy. Certain extensions require additional payment to delete a domain name.

DNS zone
A section of the Domain Name System name space. By default, the Root Zone contains all domain names, however in practice sections of this are delegated into smaller zones in a hierarchical fashion. For example, the .com zone would refer to the portion of the DNS delegated that ends in .com.

DNSSEC
A technology that can be added to the Domain Name System to verify the authenticity of its data. The works by adding verifiable chains of trust that can be validated to the domain name system.

Domain lock
In order to prevent unwanted changed to the domain names, customers have an ability to change the locks on their domain names. The domain lock availability depends on individual TLD, and includes clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited, clientRenewProhibited.

Domain Name
A unique identifier with a set of properties attached to it so that computers can perform conversions. A typical domain name is "icann.org". Most commonly the property attached is an IP address, like "208.77.188.103", so that computers can convert the domain name into an IP address. However the DNS is used for many other purposes. The domain name may also be a delegation, which transfers responsibility of all sub-domains within that domain to another entity. domain name label a constituent part of a domain name. The labels of domain names are connected by dots. For example, "www.iana.org" contains three labels — "www", "iana" and "org". For internationalized domain names, the labels may be referred to as A-labels and U-labels.

Domain Name Registrar
An entity offering domain name registration services, as an agent between registrants and registries. Usually multiple registrars exist who compete with each other, and are accredited. For most generic top-level domains, domain name registrars are accredited by ICANN.

Domain Name Registry
A registry tasked with managing the contents of a DNS zone, by giving registrations of sub-domains to registrants.

Domain Name Server
A general term for a computer hardware or software server, which answers requests to convert domain names into something else. These can be subdivided into authoritative name servers, which store the database for a particular DNS zone; as well as recursive name servers and caching name servers.

Domain Name System (DNS)
The global hierarchical system of domain names. A global distributed database contains the information to perform the domain name conversations, and the most central part of that database, known as the root zone is coordinated by IANA.

Dot or “."
Common way of referring to a specific top-level domain. Dot generally precedes the Top Level domain, such as dot com is written down as “.com.ee”.

Expiration date
The expiration date determines when the domain registration period ends. In order to avoid downtime for the domain, renewal of the domain at least two weeks before expiration date is strongly encouraged. After the expiration date passes, some registries maintain the record of the domain name under the same owner, however the DNS services are put on hold.

Extensible Provisioning Protocol (EPP)
A protocol used for electronic communication between a registrar and a registry for provisioning domain names.

Extension
Refers to the last portion of the domain name, located after the dot. Domain extension helps determine the registry, to which domain pertains, and allows to accurately classify the domain name.

First Come, First Served (FCFS)
Multiple applications for the same domain name are not accepted. The domain will be awarded to the first registrar who submits a registration request.

FTP
File Transfer Protocol does exactly what it says. The standard network protocol allows the transfer of files from one host to another. There are many FTP clients(programs) available, which allow you to connect to your host and transfer your completed content to your hosting provider's space.

Fully-Qualified Domain Mame (FQDN)
A complete domain name including all its components, i.e. "www.icann.org" as opposed to "www".

GAC Principles
A document, formally known as the Principles for the Delegation and Administration of ccTLDs. This document was developed by the ICANN Governmental Advisory Committee and documents a set of principles agreed by governments on how ccTLDs should be delegated and run.

General Availability Phase
Domains are awarded on first come first serve basis, granted that the domains are available after the previous phases have concluded.

Generic top-level domains (gTLDs)
A class of top-level domains that are used for general purposes, where ICANN has a strong role in coordination (as opposed to country-code top-level domains, which are managed locally).

Glue Record
An explicit notation of the IP address of a name server, placed in a zone outside of the zone that would ordinarily contain that information. All name servers are in-bailiwick of the Root Zone, therefore glue records is required for all name servers listed there. Also referred to as just "glue".

Hints File
A file stored in DNS software (i.e. recursive name servers) that tells it where the DNS root servers are located.

Hostname
The name of a computer. Typically the left-most part of a fully-qualified domain name.

Http
HyperText Transfer Protocol serves as the cornerstone protocol for World Wide Web, which allows the transfer of data between clients and servers.

IANA
See Internet Assigned Numbers Authority.

IANA Considerations
A component of RFCs that refer to any work required by IANA to maintain registries for a specific protocol.

IANA Contract
The contract between ICANN and the US Government that governs how various IANA functions are performed.

IANA Staff
See Internet Assigned Numbers Authority.

ICANN
Internet Corporation for Assigned Names and Numbers(ICANN) is responsible responsible for the coordination of maintenance and methodology of several databases of unique identifiers related to the namespaces of the Internet, and ensuring the network's stable and secure operation.

Internal transfer
Internal transfer refers to a transfer of a domain name within the same registrar. This procedure may be simpler, than starting a domain transfer, which involves 2 different registrars. The internal transfer is possible, after two parties involved in the internal transfer come to an agreement about the terms of the transfer.

Internationalized domain name (IDN)
Internet domain name, which allows the use of a language-specific script or alphabet, such as Arabic, Cyrillic, and Chinese. Adoption of IDN domain names is a significant step towards including non-English speakers into the world of Internet. Internationalized domain name is stored in Domain Name System as ASCII strings, which are transcribed by the use of Punycode.

Internet Architecture Board (IAB)
The oversight body of the IETF, responsible for overall strategic direction of Internet standardization efforts. The IAB works with ICANN on how the IANA protocol parameter registries should be managed. The IAB is an activity of the Internet Society, a non-profit organization.

Internet Assigned Numbers Authority (IANA)
A department of ICANN tasked with providing various Internet coordination functions, primarily those described in a contract between ICANN and the US Government. The functions relate to ensuring globally-unique protocol parameter assignment, including management of the root of the Domain Name System and IP Address Space. ICANN staff within this department is often referred to as "IANA Staff".

Internet Coordination Policy (ICP)
A series of documents created by ICANN between 1999 and 2000 describing management procedures.

Internet Engineering Steering Group (IESG)
The committee of area experts of the IETF’s areas of work, that acts as its board of management.

Internet Engineering Task Force (IETF)
The key Internet standardization forum. The standards developed within the IETF are published as RFCs.

Internet Protocol (IP)
The fundamental protocol that is used to transmit information over the Internet. Data transmitted over the Internet is transmitted using the Internet Protocol, usually in conjunction with a more specialized protocol. Computers are uniquely identified on the Internet using an IP Address.

IP address
A unique identifier for a device on the Internet. The identifier is used to accurately route Internet traffic to that device. IP addresses must be unique on the global Internet.

IPv4
Internet Protocol version 4. Refers to the version of Internet protocol that supports 32-bit IP addresses.

IPv6
Internet Protocol version 6. Refers to the version of Internet protocol that supports 128-bit IP addresses.

Landrush Phase
This phase allows you a greater chance to obtain a domain name prior to General Availability, typically for an increased fee. The fee generally varies depending on how early you want to register. Priority is either first-come, first-served or will go to an auction cpr144449003101 if there are multiple applicants, depending on registry rules. A common fee structure that will be in use is the Early Access Program (EAP). Further details on a specific extensions landrush phase can be found under the landrush section for that a particular domain.

Mail exchange (mx) record
MX record determines which server the mail client will be retrieving the mail from. The MX records for individual domains can be set up in the DNS records section of the client's control panel.

New Generic Top Level Domain (New gTLD)
Starting on July 15th, 2013 ICANN has started process of delegating new Generic Top Level Domains, opening up new opportunities for the internet community. New extensions include popular categories like professional domains, IDNs, general interest domains, and brand domain names.

NS record
a type of record in a DNS zone that signifies part of that zone is delegated to a different set of authoritative name servers.

Parent domain
The domain above a domain in the DNS hierarchy. For all top-level domains, the Root Zone is the parent domain. The Root Zone has no parent domain as it is as the top of the hierarchy. Opposite of sub-domain.

Parking
Many of the registrars offer a free service of domain parking. This allows the customer to quickly register a domain name, and choose the hosting solution at a later date. Very often the registrar's parking DNS servers allow DNS record modification.

Pre-Registration
Paid pre-registration allows you to purchase the domain in the General Availability phase, and the domain will be submitted as soon as the General Availability phase opens.

Primary name server
Practically every domain extension requires minimum 2 DNS servers in order for the domain to be successfully registered. Primary name server is responsible for storing information about the domain routing and making it available for requests.

PTR record
The representation of a IP address to domain name mapping in the DNS system.

Recursive Name Server
A domain name server configured to perform DNS lookups on behalf of other computers.

Redelegation
The transfer of a delegation from one entity to another. Most commonly used to refer to the redelegation process used for top-level domains.

Redelegation process
A special type of root zone change where there is a significant change involving the transfer of operations of a top-level domain to a new entity.

Redemption Grace Period
Redemption Grace Period(RGP) is a period after the expiration date, in which the domain still belongs to the same client, however the functionality is put on hold. The domain can usually be restored after paying for RGP fee. gTLDs often have a Renewal Period of 30 days before the Redemption Grace Period starts.

Regional Internet Registry (RIR)
A registry responsible for allocation of IP address resources within a particular region.

Registrant
See Registrant Contact

Registrant Contact
Majority of the registries require 4 contacts for a successful domain registration: Registrant, Administrative, Technical and Billing. The Registrant contact is the owner of the domain, and is the entity that holds right to use the particular domain name.

Registrar for .com.ee
An entity that can act on requests from a registrant in making changes in a registry. Usually the registrar is the same entity that operates a registry, although for domain names this role is often split to allow for competition between multiple registrars who offer different levels of support.

Registry Estonia .com.ee
The authoritative record of registrations for a particular set of data. Most often used to refer to domain name registry, but all protocol parameters that IANA maintains are also registries.

Registry Operator for .com.ee Estonia
The entity that runs a registry.

Reverse IP
A method of translating an IP address into a domain name, so-called as it is the opposite of a typical lookup that converts a domain name to an IP address.

RFCs
A series of Internet engineering documents describing Internet standards, as well as discussion papers, informational memorandums and best practices. Internet standards that are published in an RFC originate from the IETF. The RFC series is published by the RFC Editor.

Root
The highest level of the domain system.

Root Servers
The authoritative name servers for the Root Zone.

Root Zone
The top of the domain name system hierarchy. The root zone contains all of the delegations for top-level domains, as well as the list of root servers, and is managed by IANA.

Root Zone Management (RZM)
The management of the DNS Root Zone by IANA.

RZM Automation
A project to automate many aspects of the Root Zone Management function within IANA. Based on a software tool originally called "eIANA".

Secondary name server
Practically every domain extension requires minimum 2 DNS servers in order for the domain to be successfully registered. Secondary server is responsible for copying information from the primary server. The original purpose of secondary server is to take over the requests, if the primary server is down. Some of the registries no longer put an emphasis on which server is primary or secondary, but many international registries still use the old standard.

Sponsoring organization
The entity acting as the trustee of a top-level domain on behalf of its designated community.

SSL
Secure Sockets Layer (SSL) is a cryptographivc protocol, which is designed to provide communication security over internet. The data entered on the websites, using SSL, is encrypted, thus making it less susceptible to data theft.

Subdomain
In the domain hierarchy, or structure, subdomain is a domain, which is a part of a larger domain. For example, "www.icann.org" is a sub-domain of "icann.org", and "icann.org" is a sub-domain of "org". Subdomains can generally be setup through a DNS server management utility as A records or CNAME records.

Sunrise Phase
A phase in which holders of eligible trademarks have the opportunity to apply and register domain names that correspond to their trademarks. To participate in Sunrise for new gTLDs, trademark holders must validate their trademarks with the Trademark Clearinghouse (TMCH) first and must provide a valid Signed Mark Data (SMD) file for submission.

Technical Contact
Majority of the registries require 4 contacts for a successful domain registration: Registrant, Administrative, Technical and Billing. The Technical contact is intended to assist the Registrant(owner) contact in any queries that pertain to the technical aspects of managing the domain name.

Trademark Clearinghouse (TMCH)
The central database of verified trademarks that was created by ICANN to provide brand protection to trademark holders during ICANN’s new gTLD program. Its' a centralized database of verified trademarks, that is connected to each and every new Top Level Domain (TLD) that will launch.

Top-level domain (TLD)
The highest level of subdivisions with the domain name system. These domains, such as ".com.ee" and ".uk" are delegated from the DNS Root zone. They are generally divided into two distinct categories, generic top-level domains and country-code top-level domains.

Transfer
Most commonly, the term transfer refers to a inter-registrar transfer of registrations. The procedure of the tranfer will largely depend on the TLD, and is most commonly completed by requesting an authorization code from the current registrar and initiating the transfer at another registrar.

Trust anchor
A known good cryptographic certificate that can be used to validate a chain of trust. Trust anchor repository (TAR) Any repository of public keys that can be used as trust anchors for validating chains of trust. See Interim Trust Anchor Repository (ITAR) for one such repository for top-level domain operators using DNSSEC.

Trustee
An entity entrusted with the operations of an Internet resource for the benefit of the wider community. In IANA circles, usually in reference to the sponsoring organization of a top-level domain.

U-label
The Unicode representation of an internationalized domain name, i.e. how it is shown to the end-user. Contrast with A-label.

Unicode
A standard describing a repertoire of characters used to represent most of the worlds languages in written form. Unicode is the basis for internationalized domain names.

Uniform resource locator (URL)
Uniform Resource Locator(URL), commonly known as web address, is an address to a resource on the internet. The URL consists of two components: Protocol Identifier(i.e. http, https) and the Resource name(i.e. icann.org)

Unsponsored top-level domain
A sub-classification of generic top-level domain, where there is no formal community of interest. Unsponsored top-level domains(.COM, .NET, .ORG, etc.) are administered according to the policies and processes established by ICANN.

URL Forwarding
URL Forwarding or URL redirection refers to the most common type of forwarding offered by domain registrars. Forwarding occurs when all pages from one domain are redirected to another domain.

UTF-8
A standard used for transmitting Unicode characters.

Variant
In the context of internationalized domain names, an alternative domain name that can be registered, or mean the same thing, because some of its characters can be registered in multiple different ways due to the way the language works. Depending on registry policy, variants may be registered together in one block called a variant bundle. For example, "internationalise" and "internationalize" may be considered variants in English.

Variant bundle
A collection of multiple domain names that are grouped together because some of the characters are considered variants of the others.

Variant table
A type of IDN table that describes the variants for a particular language or script. For example, a variant table may map Simplified Chinese characters to Traditional Chinese characters for the purpose of constructing a variant bundle.

Web host (Hosting Provider)
Web host is a type of an Internet service, which allows users to host content and/or email services by providing hosting space. Most often the hosting providers include control panels and tools for building a website and maintaining mail records.

WHOIS
A simple plain text-based protocol for looking up registration data within a registry. Typically used for domain name registries and IP address registries to find out who has registered a particular resource. (Usage note: not "Whois" or "whois")

WHOIS database
Used to refer to parts of a registry’s database that are made public using the WHOIS protocol, or via similar mechanisms using other protocols (such as web pages, or IRIS). Most commonly used to refer to a domain name registry’s public database.

WHOIS gateway
An interface, usually a web-based form, that will perform a look-up to a WHOIS server. This allows one to find WHOIS information without needing a specialized computer program that speaks the WHOIS protocol.

WHOIS server
A system running on port number 43 that accepts queries using the WHOIS protocol.

Wire format
The format of data when it is transmitted over the Internet (i.e. "over the wire"). For example, an A-label is the wire format of an internationalized domain name; and UTF-8 is a possible wire format of Unicode.

XML
A machine-readable file format for storing structured data. Used to represent web pages (in a subset called HTML) etc. Used by IANA for storing protocol parameter registries.

Zone (DNS Records)
The zone file, also know as the DNS records is a vital component of DNS system, which contains various DNS records, which point to the location of content and email servers for each individual domain. Editing zone is made possible in the client's control panel.

Signed Mark Data (SMD)
A Signed Mark Data (SMD) is file that will allow you to register domain names during the sunrise period of new gTLD’s and request other services. It validates that you trademark has been verified within the Trademark Clearinghouse (TMCH).

Trademark Claims
The trademark claims period extends for 90 days after the close of the Sunrise period. During the Claims period, anyone attempting to register a domain name matching a trademark that is recorded in the Trademark Clearinghouse will receive a notification displaying the relevant mark information. If the notified party goes and ahead and registers the domain name the Trademark Clearinghouse will send a notice to those trademark holders with matching records in the Clearinghouse, informing them that someone has registered the domain name.