.kz Domain Registration

Kazakhstan Domain - .kz Domain Registration

Top Selling Kazakhstani Domains



.kz Registry logo

Registration Pricing

  • 1 Year 38.00 USD
  • 2 Years 74.48 USD
  • 3 Years 110.58 USD
  • 4 Years 145.92 USD
  • 5 Years 180.50 USD
  • 6 Years 214.32 USD
  • 7 Years 247.38 USD
  • 8 Years 279.68 USD
  • 9 Years 311.22 USD
  • 10 Years 342.00 USD

Application Fee

Registration Time Frame

1 Day


Requirements

Yes Details Are Individual .kz domain registrations allowed?

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

No Details Are there requirements, documents, or information needed for .kz?

Yes Details Are some .kz domain names restricted?

No Details Does .kz domain have a special use?

No Details Other information I need to know about .kz?

No Details Are there any additional fees for .kz?

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

No Details WHOIS Privacy service available?

Trustee / Proxy service offered? Fees? No Details


.kz Domain FAQ

.kz General FAQ
Kazakhstan is the world's largest landlocked country and a former member of the Soviet Union.It is ethnically and culturally diverse and has an estimated population of approximately 16.6 million people. The official languages are Kazakh and Russian.

The economy of Kazakhstan is based mostly on energy, with oil and gas resources cpr144449003101 dominating the sector. In addition, agriculture still plays an important role in the country's economy.

Why should I buy a .kz domain name?
Kazakhstan has a strong and growing 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 .kz 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?

List of reserved domain names, having determined destination comprises of itself:

  • ORG.KZ - intended for registration of third level domain names for nonprofit organizations, residents of Republic Kazakhstan;
  • EDU.KZ - intended for registration of third level domain names for organizations of residents RK, having licenses of educational activity;
  • NET.KZ - intended for registration of third level domain names for organizations in the scope of networks cpr144449003101 of data base communications, having corresponding licenses of Ministry of the Transport and Communications of Republic Kazakhstan;
  • GOV.KZ - intended for registrations of third level domain names for organizations of government sector of Republic Kazakhstan;
  • MIL.KZ - intended for registrations of third level domain names for organizations of Ministry of Defense of Republic Kazakhstan;
  • COM.KZ - intended for registrations of third level domain names for commercial organizations and in purposes of registered trade mark protection;
What is the registration term allowed for .kz domain names?
The minimum term for .kz cpr144449003101 domain names is 1 year(s).
Can anyone register a .kz domain name?

YesAre Individual .kz domain registrations allowed?

YesCompany or legal entities registrations allowed for .kz?

NoAre there requirements, documents, or information needed for .kz?

YesAre some .kz domain names restricted?

Propaganda, narcotics, ethnic, and violent names and activities and those against the laws of Kazakhstan are prohibited. See FAQs for complete restrictions.

NoDoes .kz domain have a special use?

NoOther information I need to know about .kz?

NoAre there any cpr144449003101 additional fees for .kz?

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

NoWHOIS Privacy service available?

Yes.kz Trustee / Proxy service offered? Fees?

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

Available at Checkout

.kz Trustee / Proxy Fee: per
.kz Trustee / Proxy Setup Fee:

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

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

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

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

Yes, You can register IDNs in the following languages

Grace period for .kz 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 .kz 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 .kz domain names?
You may visit them here: Kazakhstan Network Information Center (KazNIC).cpr144449003101
.kz Domains Dispute & Policy

Last Update 20 August 2012. The most recent source for .kz domains dispute policy can be found at: www.nic.kz/rules/policy.jsp

KZ DOMAIN NAME DISPUTE POLICY

Revision 01
Effective January 1, 2000

1. KazNIC Organization ("KazNIC") is responsible for the registration of second-level Internet domain names in the top level KZ domain. KazNIC registers these second-level domain names on a "first come, first served" basis. By registering a domain name, KazNIC does not determine the legality of the domain name registration, or otherwise evaluate whether that registration or use may infringe upon the rights of a third party.
2. The entity applying for a domain name ("registrant") is solely responsible for selecting its own domain name ("domain name") and maintaining for the continued accuracy of the registration record. The registrant, by completing and submitting the Domain Name Registration Agreement ("Registration Agreement"), represents that the statements in its application are true and that the registration of the selected domain name, to the best of the registrant's knowledge, does not interfere with or infringe upon the rights of any third party. The registrant also represents that the domain name is not being registered for any unlawful purpose.
3. KazNIC neither acts as arbiter nor provides resolution of disputes between registrants and third party complainants arising out of the registration or use of a domain name. This Domain Name Dispute Policy ("Policy") does not confer any rights, procedural or substantive, upon third party complainants. Likewise, complainants are not obligated to use this Policy.
4. This Policy does not limit the administrative or legal procedures KazNIC may use when third party conflicts arise, or when KazNIC is presented with information that a domain name violates the legal rights of a third party, including, but not limited to, information that the display or use of the domain name is expressly prohibited by a Kazakstani legislation or International regulations.
5. Modifications. The registrant acknowledges and agrees that KazNIC may modify or amend this Policy from time to time, and that such changes are binding upon the registrant. KazNIC will post the revised Policy at
http://nic.kz/rules/policy.jsp
at least thirty (30) calendar days before it becomes effective.
6. Indemnity. The registrant hereby agrees to defend, indemnify and hold harmless (i) KazNIC, its officers, directors, employees and agents, and (ii) the Ministry of Transport and Communications ("MTC"), its officers, directors, and employees (collectively, the "Indemnified Parties"), for any loss or damages awarded by a court of competent jurisdiction resulting from any claim, action, or demand arising out of or related to the registration or use of the domain name. Such claims shall include, without limitation, those based upon trademark or service mark infringement, tradename infringement, dilution, tortious interference with contract or prospective business advantage, unfair competition, defamation or injury to business reputation. Each Indemnified Party shall send written notice to the registrant of any such claim, action, or demand against that party within a reasonable time. The failure of any Indemnified Party to give the appropriate notice shall not affect the rights of the other Indemnified Party. KazNIC recognizes that certain educational and governmental entities may not be able to provide complete indemnification. If the registrant is (i) a governmental or non-profit educational entity, and (ii) not permitted by law or under its organizational documents to provide indemnification, the registrant must notify KazNIC in writing and, upon receiving appropriate proof of such restriction, KazNIC may provide an alternative provision for such a registrant.
7. Revocation. The registrant agrees that KazNIC shall have the right in its sole discretion to revoke, suspend, transfer or otherwise modify a domain name registration upon thirty (30) calendar days prior written notice, or at such time as KazNIC receives a properly authenticated order from a court of competent jurisdiction, or arbitration award, requiring the revocation, suspension, transfer or modification of the domain name registration.
8. Dispute Initiation. Registrant agrees that while KazNIC can neither act as an arbiter nor provide resolution of disputes arising out of the registration and use of a domain name, KazNIC may be presented with information that a domain name possibly violates the trademark rights of a trademark owner. KazNIC may apply the procedures described in Section 9 when a third party complainant ("complainant") presents KazNIC with satisfactory evidence of both trademark ownership and written notice to the domain name registrant describing the legal harm the trademark owner is incurring. The documents required in support of a complainant's written request that KazNIC invoke Section 9, Dispute Procedures, must include:
(a) An original, certified copy, not more than six (6) months old, of a trademark registration ("certified registration"), which is in full force and effect and is identical to a second-level domain name (i.e., not including KZ) on the principal or equivalent registry of any country (copies certified in accordance with 37 CFR 2.33(a)(1)(viii) or its successor will meet this standard for registrations in jurisdictions other than the United States). Trademark or service mark registrations from the supplemental or equivalent registry of any country, or from individual states or provinces of a nation, will not be accepted. Trademarks incorporating a design will not be accepted; and
(b) A copy of the written prior notice sent to the domain name registrant by the complainant, and a representation by the complainant indicating the mode of delivery of the notice (e.g., first class mail, overnight delivery) and the factual basis for believing that the domain name registrant received the notice. Notices must be sent to the mailing address of the domain name registrant as provided in KazNIC' WHOIS database. The notice to the domain name registrant must clearly state that the complainant believes the registration and use of the disputed domain name violates the trademark rights of the complainant; the notice must also clearly allege the factual and legal bases for the belief. KazNIC will not undertake any separate investigation of the statements in such notice.
9. Dispute Procedures. In those instances where a third party claim is based upon and complies with Section 8(a and b), KazNIC may apply the following procedures, which recognize that trademark ownership does not automatically extend to the right to register a domain name and which reflect no opinion on the part of KazNIC concerning the ultimate determination of the claim:
(a) KazNIC shall determine the creation date of the registrant's domain name registration ("domain name creation date").
(b) If the registrant's domain name creation date precedes the effective date of the valid and subsisting certified registration owned by the complainant, KazNIC will take no action on the complainant's request.
(c) If the domain name creation date is after the effective date of the valid and subsisting certified registration owned by the complainant, then KazNIC shall request from the registrant proof of ownership of registrant's own registered trademark or service mark by submission of a certified registration, of the type and nature specified in Section 8(a) above. The certified registration must be owned by the registrant and the effective date must be prior to the date of any third party's notice of a dispute to the registrant. If the registrant satisfies the requirements of this Section 9(c), KazNIC will take no further action on the complainant's request.
(d) If the domain name creation date is after the effective date of the valid and subsisting certified registration owned by the complainant, and the registrant fails to provide a certified registration as specified in Section 8(a) to KazNIC within thirty (30) calendar days of receipt of KazNIC' dispute notification letter, KazNIC will assist the registrant with registration of a new domain name, and will allow the registrant to maintain both names simultaneously for up to ninety (90) calendar days to allow an orderly transition to the new domain name. KazNIC will provide such assistance to a registrant if and only if, within thirty (30) calendar days of receipt of cpr144449003101 KazNIC dispute notification letter, the registrant (1) submits a Registration Agreement requesting the registration of a new domain name; and (2) submits an explicit written request to KazNIC' Office, including an identification of the registrant's desired new domain name and the NIC tracking number (for example, KZ-981125.1234) assigned by KazNIC in response to the new Registration Agreement. At the end of the ninety (90) calendar day period of simultaneous use, KazNIC will place the disputed domain name on "Hold" status, pending resolution of the dispute. As long as a domain name is on "Hold" status, that domain name registered to the registrant shall not be available for use by any party.
(e) In the event the registrant fails to select one of the following options by a written response, received by KazNIC within thirty (30) calendar days of receipt of KazNIC' dispute notification letter, KazNIC will place the domain name on "Hold" (wherein the domain name will not be available for use by any party) pending resolution of the dispute:
(1) Provide the documentation required by Section 9(c) of this Policy,
(2) Relinquish the domain name and transfer it to the complainant,
(3) Register a new and different domain name pursuant to Section 9(d) of this Policy, or
(4) File a civil action and provide a copy of a file-stamped complaint pursuant to Section 10 of this Policy.
(f) KazNIC will reinstate the domain name placed in "Hold" status, or will not place it in "Hold" status, (i) upon receiving a properly authenticated temporary or final order by a court of competent jurisdiction, or arbitration award, stating which party to the dispute is entitled to the domain name, (ii) if KazNIC receives other satisfactory evidence from the parties of the resolution of the dispute, or (iii) the complainant requests that the domain name not be placed on "Hold".
(g) A domain name registrant involved in Dispute Procedures remains subject to the terms and conditions of the Registration Agreement, including fees.
10. Litigation. Independent of the provisions of Section 9 of the Policy, in the event that:
(a) The registrant files a civil action related to the registration and use of the domain name against the complainant in a court of competent jurisdiction, and provides KazNIC with a copy of the file-stamped complaint, KazNIC will maintain the status quo ante of the domain name record pending a temporary or final decision of the court. For example, if the domain name is not on "Hold," it will not be placed on "Hold;" if the domain name is already on "Hold", it will remain on "Hold." In such cases, KazNIC will deposit control of the domain name into the registry of the court by supplying the registrant with the registry certificate for deposit. While the domain name is in the registry of the court, KazNIC will not make any changes to the domain name record unless ordered by the court. The registrant also shall promptly provide copies of any and all pleadings filed in the action to KazNIC upon KazNIC request.
(b) The complainant files a civil action related to the registration and use of the domain name against the registrant in a court of competent jurisdiction, and provides KazNIC with a copy of the file-stamped complaint, KazNIC will maintain the status quo ante of the domain name record pending a temporary or final decision of the court. For example, if the domain name is not on "Hold," it will not be placed on "Hold;" if the domain name is already on "Hold", it will remain on "Hold." KazNIC will deposit control of the domain name into the registry of the court by supplying the complainant with the registry certificate for deposit. While the domain name is in the registry of the court, KazNIC will not make any changes to the domain name record unless ordered by the court.
(c) In both instances, under Section 10(a and b), KazNIC will abide by those provisions of temporary or final court orders, or arbitration awards, directing the disposition of the domain name, without being named as a party to the civil action. The civil action must include the domain name registrant as a party. If named as a party to a civil action, KazNIC shall not be limited to the above actions, but reserves the right to raise any and all defenses deemed appropriate, and to take any other action necessary to defend itself.
(d) A domain name registrant involved in Litigation remains subject to the terms and conditions of the Registration Agreement, including fees.
11. DISCLAIMER. THE REGISTRANT AGREES THAT KAZNIC WILL NOT BE LIABLE FOR ANY LOSS OF REGISTRATION AND USE OF REGISTRANT'S DOMAIN NAME, OR FOR INTERRUPTION OF BUSINESS, OR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LOST PROFITS) REGARDLESS OF THE FORM OF ACTION WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, EVEN IF KAZNIC HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL KAZNIC' MAXIMUM LIABILITY EXCEED FIVE HUNDRED ($500.00) US DOLLARS.
12. Notices. All notices between Network Solutions and its registrants permitted or required under this Policy shall be in writing and shall be delivered by personal delivery, courier delivery, facsimile transmission, and/or by first class mail, and shall be deemed given upon delivery, transmission, or seven (7) calendar days after deposit in the mail, whichever occurs first. Initial notices shall be sent to the domain name registrant at the address of the domain name registrant listed in KazNIC WHOIS database.
13. Non-Agency. Nothing contained in this Policy shall be construed as creating any agency, partnership, or other form of joint enterprise between the parties.
14. Non-Waiver. The failure of KazNIC to require performance by the registrant of any provision hereof shall not affect the full right to require such performance at any time thereafter; nor shall the waiver by KazNIC of a breach of any provision hereof be taken or held to be a waiver of the provision itself.
15. Breach. The registrant's failure to abide by any provision under this Policy may be considered by KazNIC to be a material breach and KazNIC may provide a written notice, describing the breach, to the registrant. If, within thirty (30) calendar days of the date of such notice, the registrant fails to provide evidence, which is reasonably satisfactory to KazNIC, that it has not breached its obligations, then KazNIC may revoke registrant's registration of the domain name. Any such breach by a registrant shall not be deemed to have been excused simply because KazNIC did not act earlier in response to that, or any other, breach by the registrant.
16. Invalidity. In the event that any provision of this Policy shall be unenforceable or invalid under any applicable law or be so held by applicable court decision, such unenforceability or invalidity shall not render this Policy unenforceable or invalid as a whole. KazNIC will amend or replace such provision with one that is valid and enforceable and which achieves, to the extent possible, the original objectives and intent of KazNIC as reflected in the original provision.
17. Entirety. This Policy, as amended, and the current Registration Agreement together constitute the complete and exclusive agreement between KazNIC and the registrant, and supersede and govern all prior proposals, agreements, or other communications. The registrant agrees that registration of a domain name constitutes an agreement to be bound by this Policy, as amended from time to time.
.kz 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 Kazakhstani .kz 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 “.kz”.

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 .kz
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 Kazakhstan .kz
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 .kz Kazakhstan
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 ".kz" 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.