.no Domain Registration

Norway Domain - .no Domain Registration

Top Selling Norwegian Domains

Related Alternative Generic Domains

No Requirements Necessary

Related Alternative Generic .no domain


.no Registry logo

Registration Pricing

  • 1 Year 97.00 USD

Application Fee

Registration Time Frame

3 Days


Requirements

Yes Details Are Individual .no domain registrations allowed?

Yes Details Company or legal entities registrations allowed for .no?

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

Yes Details Are some .no domain names restricted?

No Details Does .no domain have a special use?

Yes Details Other information I need to know about .no?

No Details Are there any additional fees for .no?

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

No Details WHOIS Privacy service available?

Trustee / Proxy service offered? Fees? Yes Details


.no Domain FAQ

.no General FAQ
The kingdom of Norway is a Nordic unitary Constitutional Monarchy located on the western portion of the Scandinavian Peninsula. It is the second least densely populated country in Europe with an estimated population of approximately 5 million people. The official language is Norwegian.

The Norwegian economy is one of the wealthiest in the world. It is a mixed economy cpr144449003101 that is supported largely by Norway's vast natural resources, including petroleum, hydropower, fish, forests and minerals.

Why should I buy a .no domain name?
Norway has astrong and stable economy, and the influx of new business into the area provides an opportunity to capitalize on the needs of the emerging consumer and cpr144449003101 commercial markets. The .no 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?
15. Applicant's responsibilities and duties

15.1 Before submitting an application, applicants must familiarize themselves with the domain name policy. Applicants shall ensure that the registration of the domain name does not violate the domain name policy or Norwegian law or the rights of third parties, and does not create an unwarranted impression of being associated with public-sector administration or the exercise of public powers. Norid does not undertake any checking of this. The applicant bears the sole responsibility, including criminal liability and liability for damages, for consequences of the registration and use of the domain name.

15.2 The applicant is obliged to comply with the domain name policy for the .no domain in force at any time. The domain name policy is available at http://www.norid.no/navnepolitikk.html

15.3 The applicant must provide correct information, both at the time of application and for as long as the registration is maintained.

15.4 The applicant must keep the registered information (both cpr144449003101 contact and technical information) up to date at all times.

15.5 The applicant must reply to queries from Norid regarding the continued accuracy of the registered information. The applicant must then document the information provided.

15.6 Before submitting an application, the applicant must sign a declaration form (Appendix G) certifying inter alia that, to the best of his or her knowledge, registration or use of the name does not violate any third party's registered or unregistered rights to the name, and does not violate Norwegian law as discriminatory, defamatory, pornographic or otherwise illegal, and does not create an unwarranted impression of being associated with public-sector administration or the exercise of public powers. In the declaration form, the applicant agrees that the registry may withdraw an assigned domain name when it is obvious that the assignment is in conflict with conditions that have been mentioned or with the domain name policy in any other way. The declaration form is to be signed and sent by fax, as a scanned attachment to email, or by ordinary post to a registrar who is obliged to keep it on file. If a copy is sent, the applicant must keep the original. The applicant is obliged to present the original at Norid's request.

15.7 If a complaint is laid against the applicant's registration in accordance with the rules and procedures that the domain name policy stipulates for complaints, the applicant agrees to participate in the complaint process, as well as to be bound by the decision of the ADR Committee. The applicant accepts the obligation to cover the complaint fee, which amounts to 4 times the court fee, if the complainant wins the dispute..

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

YesAre Individual .no domain registrations allowed?

YesCompany or legal entities registrations allowed for .no?

YesAre there requirements, documents, or information needed for .no?

Must be registered in the Norwegian Business Register (Brønnøysund Register Centre). Provide exact name of company, contact person, address and phone in Norway.

Individuals: Must be registered in the National Registry (Folkeregisteret)and have a Norwegian post address. Follow the instructions here: http://pid.norid.no to get the PID number used for registration.

YesAre some .no domain names restricted?

Violating rights of third parties, names and activities that are unlawful, offensive, or otherwise against the laws of Norway are prohibited. See FAQs for complete restrictions.

NoDoes .no domain have a special use?

cpr144449003101

YesOther information I need to know about .no?

Limit of 100 domains per company.

NoAre there any additional fees for .no?

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

NoWHOIS Privacy service available?

Yes.no Trustee / Proxy service offered? Fees?

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

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 .no domain name?
bluesit.com offers hosting and email service for .no. You can order hosting, email service and SSL certificates at checkout or you can contact sales.cpr144449003101
How do I transfer my .no domain name?

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

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

Yes, You can register IDNs in the following languages

Grace period for .no 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 .no 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 .no domain names?
You may visit them here: UNINETT Norid.cpr144449003101
.no Domains Dispute & Policy
17. Complaints
17.1 Complaint type A: For domain names registered after 1 October 2003, the holder of rights to names may complain on the basis that the registration or use of the domain name entails an infringement of their rights. Public-sector bodies may complain that the registration creates an unwarranted impression that it is associated with public-sector administration or the exercise of public powers. The respondent in complaints of this type is the holder of the domain name in connection with which the complaint is made. The time limit for complaints is 3 years from the registration of the domain name. See Appendix H for details and for the complaint procedure.
17.2 Complaint type B: A domain name applicant or holder may file a complaint against decisions made by Norid in relation to the domain name policy. No complaint may be filed against decisions made by Norid as the secretariat in complaint cases. The only permissible grounds for complaint are that the decision is in conflict with the domain name policy for .no. The respondent in complaints of this type is Norid. The time limit for complaints is 30 calendar days from the date on which notification of the decision was received by the applicant or domain name holder. The decision is regarded as received by the applicant/domain name holder at the latest 14 days after the decision has been sent from Norid to the registrar. See Appendix I for details and for the complaint procedure. Norid can reverse or change the decision on its own initiative if the complaint is found to be justified.
17.3 Complaint type C: For domain names registered after 1 October 2003, Norid may complain that a domain name has been registered in conflict with the declaration form. The Norwegian Post and Telecommunications Authority may complain that a domain name has been registered in conflict with the applicable administrative regulations [forskrift]. The respondent in complaints of this type is the holder of the domain name in connection with which the complaint is made. The time limit for complaints is 3 years from the registration of the domain name. See Appendix J for details and for the complaint procedure.
17.4 For all complaints, the time limit for submitting complaints is cancelled when Norid receives a valid complaint in accordance with the complaint procedures in effect. If a further one or more valid complaints relating to the same registration are received while the dispute resolution process is taking place, resolution of the complaint that has been received first is completed before the next case is initiated. In the event of several complaints, the cases are initiated in the sequence in which they are received by the secretariat. A new case is initiated only if the respondent is still the same as when the complaint was filed. Norid acts as the secretariat, receiving complaints and forwarding replies between the parties. The complaints are heard and resolved by the independent Alternative Dispute Resolution (ADR) Committee. Norid is obliged to implement the decisions of the ADR Committee.
17.5 The ADR Committee may refuse a case if it finds that the case is so complex or doubtful, or if such inadequate information is provided about the case that it is not suitable for consideration and decision by the ADR Committee. The committee may also refuse the case if the prerequisites for consideration of the complaint do not exist.

Last Update 20 August 2012. The most current .no domains complaint proceedure can be found at: www.norid.no/navnepolitikk.en.html#link16

Appendix H: Complaint that the registration or use of the domain name infringes the complainant's rights, or ulawfully appears to be public administration or the execution of public authority.

1. General provisions
1.1 Registrations that may form the subject of complaints to the Alternative Dispute Resolution (ADR) Committee A domain name holder must participate in the complaint process if the complaint is received within the deadline. The deadline is 3 years from the registration date. A change of holder counts as a deletion followed by a new registration. The date of the change becomes the new registration date for the domain, which is used to calculate the complaint deadline. Complaints received after the deadline will be rejected.
1.2 Requirements for the basis of the complaint
1.2.1 Complaint that the registration or use of the domain name infringes the complainant's rights The complainant must provide evidence that the complainant holds rights to a name or mark which is identical to or resembles the domain name, and that the holder's registration or use of the domain name was undertaken in bad faith. Bad faith shall be interpreted to mean that the holder knew or should have known that the registration or use of the domain name could infringe on someone else's rights. Some examples of relevant factors: the registration was made for the purpose of selling or leasing the domain name to the complainant, or to one of the complainant's competitors for monetary gain the domain was registered to prevent the complainant from registering a name the complainant has rights to, or to hinder the complainant in other ways, e.g. preventing the complainant from utilizing their rights the domain was registered to mislead others into assuming that the name is connected to the complainant or the complainant's business the domain is used to unlawfully profit from the complainant's rights, or in a way that is detrimental to the complainant's rights the holder has also made other registrations in bad faith the holder has acted in breach of the Marketing Practices Act (Markedsføringsloven)
1.2.2 Complaint that the registration or use of the domain name creates an unwarranted impression that it is associated with public-sector administration or the exercise of public powers. The access to complain according to this clause is reserved for public bodies. The complainant must document that they have rights to a name or mark that is identical to or easily confused with the domain name. The bad faith requirement will be considered satisfied if the domain name is confusable with the complainant's name or their public powers, or would mislead people into believing that it is connected to the complainant or the complainant's public powers.
1.3 The ADR Committee's decision
If the ADR Committee finds that the complainant holds rights to a name or mark which is identical to or resembles the domain name, and that the domain name has been registered or used in bad faith, the Committee may decide that the name must be deleted or transferred to the complainant. The ADR Committee may not make a different decision to the one claimed by the complainant. The ADR Committee may refuse a case if it finds that the case is so complex or doubtful that it is not suitable for consideration and decision by the ADR Committee. The ADR Committee may not make a decision in conflict with the regulations in effect for the .no domain. The ADR Committee may not make a decision about compensatory damages or coverage of costs for the parties. The ADR Committee's decision may not result in the loss of rights for parties other than the two that are involved in the complaint. The ADR Committee's decision is final and no further complaint may be made about it. The decision does not impede any of the parties from subsequently submitting the dispute to the ordinary courts of law.
1.4 Liability Norid, Norid's employees, the ADR Committee and members of the ADR Committee cannot be held liable for actions or omissions made in connection with the complaint proceedings, unless the actions or omissions were in bad faith.
1.5 Transfer of the domain name while the complaint proceedings are in progress From the time that Norid sends a complaint to the holder in accordance with Clause 2.4 until the complaint proceedings are concluded, the domain name is blocked for transfer from the holder. If the ADR Committee's decision entails a compulsory deletion or transfer of the domain name to the complainant, the hold is maintained until the Committee's decision is implemented. An exception is made if the holder wishes to transfer the name to the complainant. If the holder deletes the domain name while the complaint proceedings are in progress, Norid will block the domain name for registration until the complaint has been decided or concluded in any other way. If the ADR Committee decides that the domain name is to be transferred to the complainant, Norid will implement the decision in accordance with the complaint procedure. If not, the hold on the domain name will be removed without further notice.
2. Complaint procedure
2.1 cpr144449003101 Communication
The complaint, and the subsequent response from the holder, are to be sent to Norid at the following addresses: klage@norid.no and Domeneklagenemnda, c/o UNINETT Norid AS, NO-7465 Trondheim, Norway. The same applies to any other correspondence to Norid or to the ADR Committee in connection with the complaint. Enclosures or other items that cannot be sent electronically are to be sent only as ordinary post. All communication from Norid to the parties or their representatives shall take place by A (priority) post or fax or e-mail, cf 2.3 b.) and 2.5 b.). If one party wishes to change contact information while the complaint proceedings are in progress, Norid shall be informed about this immediately. Norid will pass on the complaint (cf Clause 2.3) to the holder of the domain name in question in one of the following ways: by sending the complaint by A (priority) mail or fax or e-mail to the holder, to the contact information that has been registered in the Whois database for the domain name in question. If contact information for the holder specified by the complainant (cf 2.3 g) varies from what is registered, the complaint is also sent to the address specified by the complainant. All communication from Norid to one party shall be sent with a copy to the other party. All communication shall be in Norwegian. E-mail shall be sent in pure text if possible. Unless otherwise set out in these rules or specifically decided by Norid or the ADR Committee, all communication shall be regarded as received: if sent by fax, on the date it was sent if sent as A (priority) mail, on the second working day after the postmark date if sent as e-mail, on the date of transmission Where the communication is received in more than one way, it is considered to be received on the earliest date of receipt.
2.2 Time limit for complaint
The complaint must be lodged with Norid by the time limit for complaints, which is 3 years after the date on which the domain was registered.
2.3 The complaint
The complaint shall: not exceed 2000 words (not including the declarations that are required in j) below and attachments), state whether the complainant wishes to be contacted directly or via a representative, and specify the e-mail address, telephone number, fax number and postal address to be used, state whether the complainant wishes to participate in voluntary mediation, specify the domain name to which the complaint refers, include the reason for the complaint, enclosing the evidence that the complainant will present for his or her claim, including documentation of the rights that the complainant claims to hold to a name or mark that is identical to or resembles the domain name, as well as documentation that the holder's registration or use has been undertaken in bad faith, specify whether the complainant seeks to have the domain name transferred or deleted, provide the details of the holder's contact information that are known by the complainant, include information about pending and concluded cases in the courts of law which are related to the disputed domain name and which are known to the complainant, provide information about any previous complaints about the same domain name from the same complainant, and in this case provide details of which changes have arisen since the ADR Committee last decided the case, include the following declaration: The complainant declares that he or she accepts the framework that the domain name policy with appendixes provides for the complaint procedure. The information provided in this complaint is, to the best of the complainant's knowledge, complete and correct. The complaint has not been submitted in bad faith, and the claim presented in the complaint is in accordance with the complaint regulations in effect and the applicable laws. The complainant is aware that submitting the complaint entails blocking the disputed domain name for transfer while the complaint proceedings are in progress, and that the complainant is liable if this results in loss to the holder. close with the signature of the complainant or the complainant's representative include a table of contents listing all the enclosures accompanying the complaint. be submitted on Norid's form in accordance with the guidelines. When the complaint has been sent to Norid, the complainant must pay the complaint fee in accordance with Clause 2.13 and send the receipt for payment of the complaint fee to Norid.
2.4 Opening of the complaint proceedings
If Norid finds that the complaint is in accordance with the complaint regulations in effect, the complaint shall be sent to the holder within 3 working days after Norid has received the receipt showing that the complainant has paid the fee in accordance with Clause 2.13. If Norid does not receive the receipt for payment of the complaint fee within 10 working days after Norid has received the complaint, Norid will regard the complaint as withdrawn. This does not impede the complainant from submitting a new complaint. If Norid finds that the complaint is not in accordance with the complaint regulations in effect, Norid shall immediately inform the complainant about the defects found in the complaint. If the complainant does not send a new corrected complaint within 3 working days after receiving such information, the complaint will be refused. This does not impede the complainant from submitting a new complaint. If the ADR Committee has found that the complainant has misused the opportunity to complain (cf Clause 2.9 e) three times during a period of two years, Norid will reject all complaints from the complainant for a period of two years.
2.5 Response from the holder
The holder must send his or her response to the complaint to Norid within 20 working days after the date on which the holder is considered to have received the complaint. The response shall: not exceed 2000 words (not including the declaration that is recommended in i) below and attachments), state whether the holder wishes to be contacted directly or via a representative, and specify the e-mail address, telephone number, fax number and postal address to be used; state whether the holder wishes to participate in voluntary mediation close with the signature of the holder or the holder's representative include a table of contents listing all the enclosures accompanying the response. include information about cases pending and concluded in the courts which are related to the domain name to which the complaint applies and which are known to the holder, be submitted on Norid's form in accordance with the guidelines The response should: include the holder's reason for rejecting the complainant's claim, enclosing the evidence that the holder will present for his or her assertion, include the following declaration: The information provided in this response is to the best of the holder's knowledge complete and correct. The domain name has not been registered or used in bad faith. If the response submitted is not in accordance with the complaint regulations in effect, Norid shall immediately inform the holder about the defects found in the response. If the holder does not send a new corrected response within 3 working days after receiving such information, it will be assumed that the response has not been received, and the parties will be informed that the complaint is to be sent to the ADR Committee.
2.6 Submission to the ADR Committee
Norid sends the complaint and response to the ADR Committee within 5 working days after a valid response has been received. If no response has been received, the complaint is sent to the ADR Committee within 5 working days after the deadline for the holder's response. A copy of any valid response is sent to the complainant when the case is sent to the ADR Committee. As soon as the case has been sent to the ADR Committee, Norid will inform the parties of this and of the date on which a decision is likely to be available in normal conditions.
2.7 Voluntary mediation
If the parties have stated that they desire this, the ADR Committee will start mediation within 3 working days from the Committee's receipt of the complaint. Mediation is undertaken by one of the Committee's members. Mediation will be conducted in the manner that the ADR Committee finds most practical. If the parties reach an agreement, the mediator informs Norid of this and the complains proceedings will be concluded without a formal decision. Mediation shall not influence the ADR Committee's hearing of the case if the parties do not reach agreement. If the parties do not reach agreement through mediation within 10 working days, the ADR Committee will proceed to hear the case and to make a decision. The mediator will not participate in the case hearing. At any time during the mediation period, each of the parties may inform the ADR Committee that he or she no longer wishes to continue the mediation. The ADR Committee will then proceed to hear the case and to make a decision.
2.8 Stay and conclusion of the complaint proceedings without a decision Both parties have a duty to inform Norid immediately if a case is filed with the courts in connection with a domain name that forms the subject of a complaint. The complaint case will be stayed in anticipation of a final and legally enforceable decision, and resumed only if no final judgement is given or no court settlement is reached, and only if the complainant requires this. The complaint proceedings will be concluded if no claim for resuming them is submitted within 5 working days after the case is closed by the courts. Both parties have a duty to notify Norid without undue delay when the case is concluded in the courts. The complaint proceedings will be concluded without a decision if the parties reach agreement and inform Norid of this. If the holder sends notification of a transfer to the complainant, Norid will implement the transfer, and the complaint case will be concluded without further notice.
2.9 The ADR Committee's decision
The ADR Committee shall send its decision to Norid within 15 working days from the date on which mediation between the parties ends. The proceedings of the Committee are in writing. If the Committee finds it necessary, it may specify that the parties must appear before the Committee, through attendance in person or through a telephone conference or videoconference, or in the manner that the Committee finds appropriate. No meeting involving attendance in person shall be held without the complainant's consent. The Committee may ask the parties for further written information or documentation. The Committee may not take into account information or documents that are received beyond the submissions that the parties provide in accordance with the complaint procedure or that the Committee itself has requested. The decision shall be in writing and shall include the grounds for the decision. It shall specify the date of the decision, as well as the names of the complaints Committee members who have heard the case. If the ADR Committee finds that the complaint represents misuse of the opportunity to complain, in an attempt to impede the holder from temporary or permanent use of the domain name, this shall be indicated in the decision.
2.10 Information about the decision and publication
Within 3 working days from the date on which Norid has received a decision from the domain complaints Committee, Norid shall forward the decision to the parties, and at the same time state the date for implementation of the decision. All decisions will be published in full on Norid's Web pages and in Lovdata's information system Lovdata Online. If so required by one of the parties, information about technical equipment and procedures as well as operational and business matters which should be kept confidential for competitive reasons out of consideration for the party to which the information relates shall be excluded from publication. Requirements for secrecy must be submitted by the parties without being specially requested and in the parties' ordinary submissions. The ADR Committee decides whether, and if so, how parts of the Committee's decision shall be excluded from public access. A decision by the ADR Committee will be made public, even if it is not implemented because the case has been filed with the courts, the parties reach an amicable settlement, the holder voluntarily transfers the domain name to the complainant, or the time limit for cooperation (cf. 2.11, first paragraph, last sentence) has been exceeded.
2.11 Implementation
If the ADR Committee decides that a domain name is to be deleted or transferred to the complainant, Norid will implement the decision by making the necessary changes in the domain-name database 7 working days from the date on which the decision has been sent to the parties. If the decision is that the domain name is to be transferred, the complainant may choose to have it transferred to a third party (proxy). The complainant must ensure that they or their proxy satisfy all the requirements for domain registrations set by the domain name policy. If the complainant does not cooperate to make the transfer happen, the decision is annulled 15 working days after it has been sent to the parties. If the complainant's claim is disallowed, the hold on transferring the disputed domain name will be removed within one working day after Norid has been informed of the ADR Committee's decision. Implementation will be postponed if Norid receives a written confirmation that a legal process has started to contest the ADR Committee's decision within the 7 working days. In this case Norid will still block transfer of the domain name, cf Clause 1.5, but will not make any changes to the registration before Norid receives documentation that the parties have reached a court settlement or that a final and legally enforceable decision has been made. Norid will implement the changes involved in the settlement or the court decision as soon as possible, and within 3 working days after Norid has received documentation of the settlement or court decision. If the holder sends notification of transfer to the complainant, Norid will always implement the transfer, regardless of whether or not the dispute is being heard by the ADR Committee or by the courts.
2.12 Extension of time limits
In extraordinary circumstances, Norid or the ADR Committee may extend the time limits that are specified in the complaint procedure.
2.13 Fee
The fee in effect for submitting a complaint to the ADR Committee is 4 times the court fee ("CF"). Fees are calculated to cover actual costs, and are paid in full to the members of the committee. If Norid has not received a receipt for payment from the complainant within 10 working days after Norid has received the complaint, Norid will regard the complaint as withdrawn, cf Clause 2.4. Norid will refund the fee to the complainant if the ADR Committee rules in favour of the complainant's demands. The domain holder is then obliged to pay the fee to Norid. Norid will invoice the domain holder at the same time as when the notification of implementation is sent. In a new dispute case between the same complainant and the same domain holder regarding the same domain name, when the new dispute is initiated after the complainant exceeded the time limit for cooperation in clause 2.11, first paragraph, last sentence, c) does not apply. No claim for a refund of the fee may be made. If the ADR Committee decides that a meeting is to be held with attendance in person (cf Clause 2.9 b.) the complainant shall pay an extra charge of from 3 to 6 times the court fee. The amount of the extra charge and the deadline for payment are determined by Norid in consultation with the ADR Committee on the basis of the extra time that it is assumed that the meeting will require.
.no 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 Norwegian .no 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 “.no”.

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 .no
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 Norway .no
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 .no Norway
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 ".no" 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.