.co.im Domain Registration

Isle of Man Domain - .co.im Domain Registration

Top Selling Manx Domains



.co.im Registry logo

Registration Pricing

  • 1 Year 19.95 USD
  • 2 Years 39.10 USD
  • 5 Years 94.76 USD
  • 10 Years 189.53 USD

Application Fee

Registration Time Frame

Instant


Requirements

Yes Details Are Individual .co.im domain registrations allowed?

Yes Details Company or legal entities registrations allowed for .co.im?

Yes Details Are there requirements, documents, or information needed for .co.im?

Yes Details Are some .co.im domain names restricted?

No Details Does .co.im domain have a special use?

Yes Details Other information I need to know about .co.im?

No Details Are there any additional fees for .co.im?

No Details Do I need a trademark/brand name to register .co.im?

No Details WHOIS Privacy service available?

Trustee / Proxy service offered? Fees? No Details


.co.im Domain FAQ

.co.im General FAQ
The Isle of Man is a self governing Crown Dependency of the United Kingdom that is located in the Irish Sea between Ireland and Great Britain. Inhabited since 6500 BC, the Isle of Man has a rich cultural history. The estimated population is approximately 85,000 people, and the official languages are English and Manx.

The Isle of Man is a low-tax economy with favorable tax structures for individuals and corporations. As a result, offshore banking is a key cpr144449003101 sector of the economy. Manufacturing and tourism contribute greatly to the economy as do fishing and agriculture, albeit to a much lesser extent.

Why should I buy a .co.im domain name?
The Isle of Man has a strong and stable economy, and the influx of new business into the area provides an opportunity to capitalize on the needs of the emerging cpr144449003101 consumer and commercial markets. The .co.im extension is ideal for companies based in the region to help present a professional image and show your commitment to the region to local customers.
What name can I register?

Internationalised domain names are not currently offered and so domain namesthat start with the characters "xn--" (i.e. "xn" followed by two dashes) may not be registered.

The complete domain name may not be more than sixty-four Characters long in total, but can be any number from 3 to 64 (inclusive of ".im").

Content restrictions on Domain Names and maintenance of the restricted word lists.

An application for a domain name may be rejected for one of the following reasons:

ul>
  • It is included on the .im Black List;
  • Is on the Reserved Domain cpr144449003101 List and is unavailable for registration;
  • Upon review by the Designated Official if the domain name is deemed to be profane or otherwise undesirable it may be withdrawn and added to the Black List retrospectively.
  • An application for a domain may be referred for approval if it includes words or terms which are in the list for referral. This includes words, which are connected to regulated activities on the Isle of Man.

    The lists of undesirable words and words for referral are maintained by us in consultation with the Isle of Man Government and are not in the public domain.

    The lists are subject to change without notice.

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

    YesAre Individual .co.im domain registrations allowed?

    YesCompany or legal entities registrations allowed for .co.im?

    YesAre there requirements, documents, or information needed for .co.im?

    Domain should match company/brand name if you are registering as a company.

    YesAre some .co.im domain names restricted?

    Names on the restricted or black list, undesirable names, and identical names to those registered are prohibited. See FAQs for complete restrictions.

    NoDoes .co.im domain have a special use?

    YesOther information I need to know about .co.im?

    Single letter domains available for $2300, 2-letter domains available for $1128.00, please contact us to order.
    cpr144449003101

    NoAre there any additional fees for .co.im?

    NoDo I need a trademark/brand name to register .co.im?

    NoWHOIS Privacy service available?

    Yes.co.im Trustee / Proxy service offered? Fees?

    Don't Have All of These Requirements for Isle of Man .co.im? Our trustee service provides the required local contact information. Note: Registration for 2 years may be required on some extensions.

    Available at Checkout

    .co.im Trustee / Proxy Fee: per
    .co.im Trustee / Proxy Setup Fee:

    How long does it take to register my .co.im domain name?
    The domain registration time frame for .co.im during general availability is Instant. .co.im is not cpr144449003101 expected to launch until Instant. Once launched, a registration time frame will be available.
    What are the characters and valid character lengths for .co.im domain names?
    Domain Names must:
    • have minimum of 3 and a maximum of 64 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.co.im); and
    • not include a space (e.g. www.ab cd.co.im).
    Trustee Service for .co.im

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

    cpr144449003101

    Trustee service is not available for this extension

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

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

    To transfer your .co.im 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 .co.im requirements before transfer out can be started.
    Can I hide my registration information (Private WHOIS)?
    No. At present the .co.im 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 .co.im domain name in different languages (Internationalized Domain Name)?

    No, .co.im does not cpr144449003101 support Internationalized Domain Names

    Grace period for .co.im 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 .co.im 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 .co.im domain names?
    You may visit them here: Isle of Man Domain Name Registry.cpr144449003101
    .co.im Domains Dispute & Policy

    Last Update 20 August 2012. The most recent source for .co.im domains dispute policy can be found at: www.nic.im/pdfs/disputeresolution.pdf

    IM Dispute Resolution Procedure
    (IM DRP)
    26 June 2006

    1. Process Overview
    Dispute Resolution Steps:
    1 – The Complainant initiates a Complaint in accordance with section 8 below and with reference to the evidence of abusive registration section 3 below.
    2 – We check the complaint is compliant with the DRP and notify the Respondent in accordance with section 9.
    3 – The Respondent has 15 days to provide a written response in accordance with section 10 below and with reference to section 4 demonstrating why it is not an abusive registration.
    4 – A dispute resolution case is opened and we submit the complaint documents to the Designated Official.
    5 - The Designated Official may request further statements in accordance with section 12.
    6 – The Designated Official reaches a decision in accordance with section 15 and informs us who notifies both parties.
    7 – The dispute resolution case is then closed.
    Appeal Steps:
    1 – Either party has 10 days to raise an appeal in accordance with section 14, which must be accompanied by an appeal fee payment of £500 from the initiating party and evidence supporting the appeal.
    2 – We submit the appeal to the Designated Official.
    3 – Any new information presented is considered by the Designated Official in conjunction with the original case notes. The Designated Official makes a final binding decision and notifies us.
    4 – We notify both parties.
    5 – The appeal is closed.
    2. Dispute Resolution Procedure
    A. A Respondent must submit to proceedings under the IM DRP if a Complainant asserts to the Designated Official, according to the IM DRP, that:
    i. The Complainant has Rights in respect of a name or mark which is dentical or similar to the Domain Name; and
    ii. The Domain Name, in the hands of the Respondent, is an Abusive registration.
    B. The Complainant is required to prove to the Designated Official that both elements are present on the balance of probabilities.
    C. We recommend that both Parties use our guidance, which includes the IM Rules and help information, which can be found on our website.
    3. Evidence of Abusive Registration
    A. A non-exhaustive list of factors which may be evidence that the Domain Name is an Abusive Registration is as follows:
    i. Circumstances indicating that the Respondent has registered or otherwise acquired the Domain Name primarily:
    a. for the purposes of selling, renting or otherwise transferring the Domain Name to the Complainant or to a competitor of the Complainant, for valuable consideration in excess of the Respondent's documented out-of-pocket costs directly associated with acquiring or using the Domain Name;
    b. as a blocking registration against a name or mark in which the Complainant has Rights; or
    c. for the purpose of unfairly disrupting the business of the Complainant;
    ii. Circumstances indicating that the Respondent is using the Domain Name in a way which has confused people or businesses into believing that the Domain Name is registered to, operated or authorised by, or otherwise connected with the Complainant;
    iii. The Complainant can demonstrate that the Respondent is engaged in a pattern of registrations where the Respondent is the registrant of domain names (under .im or otherwise) which correspond to known names or trade marks in which the Respondent has no apparent rights, and the Domain Name is part of that pattern;
    iv. It is independently verified that the Respondent has given false contact details to us; or
    v. The Domain Name was registered as a result of a relationship between the Complainant and the Respondent, and the Complainant:
    a. has been using the Domain Name registration exclusively; and
    b. paid for the registration and/or renewal of the Domain Name registration.
    B. Failure on the Respondent's part to use the Domain Name for the purposes of e-mail or a web-site is not in itself evidence that the Domain Name is an Abusive registration.
    C. There shall be a presumption of Abusive registration if the Complainant proves that Respondent has been found to have made an Abusive registration in three (3) or more IM DRP cases in the two (2) years before the Complaint was filed. This presumption can be rebutted (see paragraph 4 (C)).
    4. How the Respondent may demonstrate in its response that the Domain Name is not an Abusive Registration
    A. A non-exhaustive list of factors which may be evidence that the Domain Name is not an Abusive registration is as follows:
    i. Before being aware of the Complainant’s cause for complaint (not necessarily the 'complaint' under the IM DRP), the Respondent has
    a. used or made demonstrable preparations to use the Domain Name or a Domain Name which is similar to the Domain Name in connection with a genuine offering of goods or services;
    b. been commonly known by the name or legitimately connected with a mark which is identical or similar to the Domain Name;
    c. made legitimate non-commercial or fair use of the Domain Name;
    or
    ii. The Domain Name is generic or descriptive and the Respondent is making fair use of it;
    iii. In relation to paragraph 3(A)(v); that the Registrant's holding of the Domain Name is consistent with an express term of a written agreement entered into by the Parties; or
    iv. In relation to paragraphs 3(A)(iii) and/or 3(C); that the Domain Name is not part of a wider pattern or series of registrations because the Domain Name is of a significantly different type or character to the other domain names registered by the Respondent.
    B. Fair use may include sites operated solely in tribute to or in criticism of a person or business.
    C. If paragraph 3(C) applies, to succeed the Respondent must rebut the presumption by proving in the Response that the registration of the Domain Name is not an Abusive registration.
    5. Without Prejudice
    Documents and information which are 'without prejudice' (or are marked as being 'without prejudice') may be used in submissions and may be considered by the Designated Official except that the Designated Official will not consider such materials if the Designated Official believes that it is in the interests of justice that the document or information be excluded from consideration.
    6. Submission to the Designated Official
    All complaints will be submitted to the Designated Official when the Respondent has made a response or a period of 15 days has elapsed after notifying the Respondent in accordance with paragraph 10 below . The Designated Official will come to a written decision.
    7. Communication
    A. We will send a complaint to the Respondent by using, in our discretion, any of the following means:
    i. sending the complaint by first class post, fax or e-mail to the Respondent at the contact details shown as the registrant or other contacts in our Domain Name register database entry for the Domain Name in dispute;
    ii. sending the complaint in electronic form (including attachments to the extent available in that form) by e-mail to;
    iii. postmaster@<the Domain Name in dispute>; or
    iv, if the Domain Name resolves to an active web page (other than a generic page which we conclude is maintained by an ISP for parking Domain Names), to any e-mail address shown or e-mail links on that web page so far as this is practicable; or
    v. sending the complaint to any addresses provided to us by the Complainant so far as this is practicable.
    B. All written communication to a Party or a Party's representative under the IMDRP shall be made by fax, first class post or e-mail.
    C. Communication shall be made in English. E-mail communications should be sent in plain text so far as this is practicable.
    D. During the course of proceedings under the IM DRP, if either Party wishes to change its contact details it must notify us of all changes.
    E. Except as otherwise provided in this IM DRP or as otherwise decided by us or the Designated Official, all communications provided for under this IM DRP shall be deemed to have been received:
    i. if sent by facsimile, on the date transmitted; or
    ii. if sent by first class post, on the second Day after posting; or
    iii. if sent via the Internet, on the date that the communication was transmitted;
    iv. and, unless otherwise provided herein, the time periods provided for under the IM DRP shall be calculated accordingly.
    F. Any communication between:
    i. us and any Party shall be copied by us to the other Party and the Designated Official, below; and
    ii. a Party to another Party shall be copied by the sender to us and we will copy such correspondence to the Designated Official.
    8. The Complaint
    A. Any person or entity may submit a complaint to us in accordance with IM DRP. In exceptional circumstances, we may have to suspend our ability to accept complaints. If so, we will post a message to that effect on our web-site which will indicate when the suspension is likely to be lifted.
    cpr144449003101
    B. More than one person or entity may jointly make a complaint. Where this occurs the joint Complainants must:
    i. all sign the hard copy of the complaint (or have it signed on their behalf);
    ii. specify one of the Complainants, or a single representative, who will be the 'lead Complainant' who will receive correspondence on behalf of all the Complainants and is entitled to act on behalf of them all and
    iii. specify which Complainant the Complainants wish to become the sole registrant of each Domain Name(s) which are the subject of the complaint if the Complainants are successful (this does not bind the Designated Official).
    C. The Complainant may send the complaint to us in hard copy or in electronic form. Electronic submissions are preferred. The Complainant shall:-
    i. not exceed 2000 words;
    ii. specify whether the Complainant wishes to be contacted direct or through an authorised representative, and set out the e-mail address, telephone number, fax number and postal address which should be used;
    iii. set out any of the Respondent's contact details which are known to the Complainant;
    iv. specify the Domain Name which is the subject of the dispute and the name or mark which is identical or similar to the Domain Name and in which the Complainant asserts it has Rights;
    v. describe in accordance with the IM DRP the grounds on which the complaint is made including in particular: what Rights the Complainant asserts in the name or mark; why the Domain Name should be considered to be an Abusive registration in the hands of the Respondent; and discuss any applicable aspects of paragraph 3 above as well as any other grounds which support the Complainant’s assertion;
    vi. specify whether the Complainant is seeking to have the Domain Name transferred, suspended or cancelled;
    vii. tell us whether any legal proceedings have been commenced or terminated in connection with the Domain Name which is the subject of the complaint;
    viii. state that the Complainant will submit to the exclusive jurisdiction of the Isle of Man courts with respect to any legal proceedings seeking to reverse the effect of a decision requiring the suspension, cancellation, transfer or other amendment to a Domain Name registration, and that the Complainant agrees that any such legal proceedings will be governed by Manx law;
    ix. agree that its claims and remedies concerning the registration of the Domain Name, the dispute, or the dispute's resolution shall be solely against the Respondent and that neither we nor our directors, officers, employees or servants nor any Designated Official shall be liable for anything done or omitted in connection with any proceedings under the Dispute Resolution Service.
    x. state that the information contained in this complaint is to the best of the Complainant’s knowledge true and complete, and that this complaint is not being presented in bad faith and the matters stated in this complaint comply with the Procedure and applicable law.
    xi. agree that if the Designated Official orders a transfer of the Domain Name(s) to be bound by our Terms and Conditions for the Registration of Domain Names, and in particular the provisions relating to our processing of personal data.
    xii. by submitting a complaint agree to be bound by the conditions of this clause (8).
    xiii. where a hard copy is sent attach two copies of any documentary or other evidence on which the Complainant relies including correspondence and any trade mark registration and/or evidence of use of or reputation in a name or mark, together with an index of the material attached.
    D. The complaint may relate to more than one Domain Name, provided that those Domain Names are registered in the name of the Respondent.
    9. Notification of Complaint
    A. We will check that the complaint complies with the IM DRP and, if so, we will forward it to the Respondent together with our explanatory coversheet.
    B. If we find that the complaint does not comply with the IM DRP, we will promptly notify the Complainant of the deficiencies we have identified. The Complainant shall have three (3) Days from receipt of notification within which to correct the deficiencies and return the complaint to us, failing which we will deem the complaint to be withdrawn. This will not prevent the Complainant submitting a different complaint to us.
    C. Proceedings under the IM DRP will commence on the earliest date upon which the complaint is deemed to have been received by the Respondent.
    10. The Response
    A. Within fifteen (15) Days of the date of commencement of proceedings under the IM DRP, the Respondent may submit a response to us.
    B. We will forward the response to the Complainant and the Designated Official.
    C. The Respondent must send the response to us in hard copy and (except to the extent not available for attachments) in electronic form to us at the addresses set out in our explanatory coversheet. The response shall:
    i. not exceed 2000 words;
    ii. include any grounds the Respondent wishes to rely upon to rebut the Complainant’s assertions including any relevant factors set out in paragraph 4 above;
    iii. specify whether the Respondent wishes to be contacted direct or through an authorized representative, and set out the e-mail address, telephone number, fax number and postal address which should be used;
    iv tell us whether any legal proceedings have been commenced or terminated in connection with the Domain Name which is the subject of the complaint;
    v. conclude with the following statement followed by the signature of the Respondent or its authorized representative:- "The information contained in this response is to the best of the Respondent's knowledge true and complete and the matters stated in this response comply with the IM DRP and applicable law."; and
    vi. attach three copies of any documentary or other evidence on which the Respondent relies including correspondence and any trade mark registration and/or evidence of use of or reputation in a name or mark together with an index of the material attached.
    D. If the Respondent does not submit a response, we will notify the Parties that the Designated Official has been requested to review the complaint and come to a judgment based on the submissions received.
    11. Communication Between Parties and the Designated Official
    A Party and the Designated Official may not communicate directly. All communications between a Party and the Designated Official must be via us.
    12. Further Statement
    In addition to the complaint, the response and appeal, the Designated Official may request further statements or documents from the Parties. The Designated Official will not be obliged to consider any statements or documents from the Parties which he or she has not received according to the Policy or this Procedure or which he or she has not requested.
    13. In Person Hearings
    No in person hearings (including hearings by conference call, video conference and web conference) will be held unless the Designated Official determines in his or her sole discretion and in exceptional cases, that such a hearing is necessary to enable him or her to come to a decision.
    14. Appeal, Repeat Complaints and Availability of Court Proceedings
    A. Either Party will have the right to appeal a decision under the IM DRP.
    B. A request for appeal must be submitted in writing within 10 days of notification of the decision. The request must be accompanied by:
    i. A full response submitted in writing, not exceeding 1000 words which setsout in detail the grounds and reasons why the decision should be sent to appeal.
    ii. A fee of £500 payable to "Domicilium (IOM) Limited"
    C. The appeal will be considered by the Designated Official by review of the appeal response and any further information requested.
    D. The decision after appeal will be final.
    E. The operation of the IM DRP will not prevent either the Complainant or the Respondent from submitting the dispute to the Isle of Man courts.
    15. Designated Official Decision
    A. The Designated Official will decide a complaint on the basis of the Parties' submissions, the IM DRP.
    B. Unless exceptional circumstances apply, an Designated Official shall forward his or her decision to us.
    C. The decision shall be in writing and signed, provide the reasons on which it is based, indicate the date on which it was made and identify the name of the Designated Official.
    D. If the Designated Official concludes that the dispute is not within the scope of paragraph 2 of the Policy, he or she shall state that this is the case. If, after considering the submissions, the Designated Official finds that the complaint was brought in bad faith, for example in an attempt at Reverse Domain Name Hijacking, the Designated Official shall state this finding in the decision. If the Complainant is found on three separate occasions within a 2-year period to have brought a complaint in bad faith, we will not accept any further complaints from that Complainant for a period of 2 years.
    16. Implementation of Designated Official Decisions
    A. If the Designated Official makes a decision that a Domain Name registration should be cancelled, suspended, transferred or otherwise amended, we will implement that decision by making any necessary changes to the Register. We will use the details set out in the Complaint form unless you specify other details to us in good time.
    17. Transfers During a Dispute
    A. A Respondent may not transfer a Domain Name registration:
    i. once a Complaint has been passed to the Designated official; or
    ii. whilst proceedings under the IM DRP are ongoing in relation to the Domain Name or for a period of ten (10) Days after their conclusion, unless to the Complainant as a result of a settlement reached between the Parties and approved by us; or
    iii. whilst a court proceeding or arbitration in respect of the Domain Name registration is ongoing in a court of competent jurisdiction. We reserve the right to reverse any transfer of a Domain Name registration whichdoes not comply with this paragraph.
    B. A Respondent may not without the Complainant’s consent (which the Complainant will not unreasonably withhold) transfer the hosting of a Domain Name to another ISP whilst proceedings under the IM DRP are ongoing in relation to the Domain Name or for a period of ten (10) Days after the conclusion of the IM DRP.
    18. Settlement or Other Grounds for Termination
    A. If, before a decision is made the Parties agree and notify us of a settlement which we approve we will terminate proceedings under the IM DRP.
    B. If, before a decision is made, it becomes unnecessary or impossible to continue proceedings under the IM DRP for any reason, we will terminate proceedings unless a Party raises justifiable grounds for objection within a period of time which we will determine.
    19. Effect of Court Proceedings
    A. If legal proceedings relating to a Domain Name which is the subject of a complaint are issued in a court of competent jurisdiction before or during the course of proceedings under the IM DRP and are brought to our attention, wewill suspend the proceedings, pending the outcome of the legal proceedings.
    B. A Party must promptly notify us if it initiates legal proceedings in a court of competent jurisdiction in relating to a Domain Name which is the subject of a complaint during the course of proceedings under the IM DRP.
    20. Notification and Publication
    A. We will communicate a decision to the Parties according to paragraph 7 above and will publish all decisions in full on our web site.
    B. Decisions may contain the contact details of the Parties.
    21. Exclusion of Liability
    A. Neither we nor our directors, officers, employees or servants nor any Designated Official shall be liable to a party for anything done or omitted in connection with any proceedings under the IM DRP unless the act or omission is shown to have been in bad faith.
    22. Modifications to the IM DRP
    A. We reserve the right to make reasonable modifications to the IM DRP at any time. We will only do so when we have good reason. Each such change will be published in advance (where practicable, 30 calendar days in advance) on our web site: http://www.nic.im and will become binding and effective upon the date specified therein.
    B. The Respondent will be bound by the IM DRP which is current at the time the Complaint is passed to the Designated Official until the dispute is concluded.
    .co.im 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 Manx .co.im 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 “.co.im”.

    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 .co.im
    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 Isle of Man .co.im
    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 .co.im Isle of Man
    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 ".co.im" 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.