.kz WHOIS Lookup
.kz is the country-code extension of Kazakhstan, operated by KazNIC. Look up a .kz address and see what the record contains.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.kz WHOIS Lookup: KazNIC Records and Their Fields
.kz is the country-code extension of Kazakhstan, delegated into the root zone on 19 September 1994 and operated by KazNIC. Queries are answered by whois.nic.kz on port 43, and in our measurement on 12 August 2026 the reply carried twenty-one field labels. The extension has no registered RDAP endpoint, so port 43 is the only channel for registration data, and the zone carries a DS record in the root.
The layout of the reply belongs to the era before WHOIS output settled into a standard. Labels are padded with dots up to the colon so that all values line up in one column, and blocks carry headings of their own instead of field prefixes — the organisation using the name, the administrative contact and the name server list each sit under a separate heading. For a human reader the output is tidy. For a parser it is laborious: the padding has to be stripped to find where the label ends and the value begins, and the block headings have to be recognised separately.
The content is rich all the same. The organisation using the name arrives with its name, address, city and country; the administrative contact comes with a handle, a name, a phone number and an email; and the name servers are listed together with their IP addresses. On the date side there is creation and last modified, while no expiry date is published. The status line gives both a code and its plain-language equivalent. Our result screen fills four fields. For another regional extension keeping its own vocabulary, see .am WHOIS lookup; for a larger record layout in the same region, .ru WHOIS lookup.
About the .kz extension
- Extension
- .kz
- WHOIS server
- whois.nic.kz
- RDAP endpoint
- This extension has no RDAP endpoint in the IANA bootstrap registry.
- Registry
- The Association of IT Companies of Kazakhstan, operated by KazNIC
- Delegated
- 19 September 1994
- Measured label count
- 21 field labels (12 August 2026)
- Layout
- Labels padded with dots; blocks separated by section headings
- Not published
- No expiry date appears in the record
WHOIS FAQ
What do the dotted labels in a .kz reply mean?
They are nothing more than an alignment device. After the label name, dots fill the space up to the colon so that every value starts in the same column. They carry no meaning and are not part of the label. When parsing, that padding has to be stripped; otherwise the label is read together with the dots and matches none of the known field names.
Why is the .kz status line written in two parts?
Because the registry gives both the code and its explanation. In the record we measured, the line began with a short code and continued, after a dash, with the same state expressed in plain words. The aim is to help the reader: you understand the state without memorising a vocabulary of status codes. A tool processing this line has to separate the two parts, or it will take the explanation for part of the code.
Why is there no expiry date in a .kz record?
The registry does not publish that field. The record we measured carried a creation date and a last modified date, but no expiry. So you can see when a record began and not when it ends. If you need to track the term of an address, that information comes from the party holding the record; in this extension the WHOIS reply does not answer the question.
Does a .kz lookup show the registrant?
It does. In the record we measured, the name, street address, city, postal code and country of the organisation using the name arrived open, and the administrative contact added a handle, a name, a phone number and an email. The masking that settled across generic extensions does not cover country extensions, so the identity side stays open here and the registrant field on the result screen is populated.
Which time zone do the dates in a .kz record use?
The reply says so itself. In the record we measured, the creation and last modified lines closed with the time zone in brackets, and the value showed a zero offset, meaning the dates were in universal time. That is a good habit on the registry's part: when the time zone is written out, moving a date into another system calls for no guesswork.
Is there an RDAP endpoint for the .kz extension?
There is not. In our measurement on 12 August 2026 IANA's bootstrap list carried no RDAP address for .kz. The single channel for registration data is the server on port 43, and the reply arrives as plain text. RDAP becoming the authoritative source for generic extensions does not cover country extensions, and this one carries on with a format of its own.
How does an available .kz name look in a lookup?
As a reply with no record block. In our measurement a name that was not registered drew no organisation, contact or date blocks from the server, and the result screen marked it as available. Availability works correctly for this extension. Results that look available are cached for five minutes and registered ones for six hours.