.қаз.xn--80ao21a

Internationalised top-level domain

WHOIS

Register: —first year
Renew: —a year
Transfer: —to move it
Registrars: —quoting it
Lookup: WHOISanswers for it
DNSSEC: Signed1 DS record in the root
Level: Secondmybrand.қаз

Check a name

One command, straight against the registry — no account, no page to load.

Name

Fills the command and the registrar links below in with your own name. The page is static — nothing is looked up here, and nothing you type leaves the browser.

ds mybrand --tld xn--80ao21a

Add --where for the registrars and the registry's rules, --registry for the server that answered, or --all-info for everything at once.

What it costs

No registrar in the price table bundled with ds quotes .қаз, so the CLI prints no figure beside it — one of 927 such TLDs. That is a gap in the table as often as it is a TLD nobody sells. See Prices for supplying your own table with --pricing-file.

Who can register

No eligibility rule is on file for .қаз, which is not the same as a promise that it is open: the list is hand-maintained and covers the restricted TLDs a registrar is likely to offer you. Check the registry's own page before counting on a name. 81 TLDs do carry a rule — see Who can register.

How `ds` answers for it

RDAP first, WHOIS second — the same order for every TLD. .қаз has no RDAP service, so the answer comes from WHOIS text on port 43.

WHOIS: whois.nic.kzQueried on port 43, from the bundled whois.json. The name is called free when the reply contains nothing found — text matching, which is why RDAP is preferred where it exists.

ds mybrand --tld xn--80ao21a --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .қаз today. See Accuracy notes.

The registry

From IANA's delegation record for .қаз. .қаз is a country-code TLD.

Run by: Association of IT Companies of KazakhstanBased in Kazakhstan. Delegated 2011-09-15, record last updated 2023-03-07.
Registry site: www.nic.kzWhere the registry documents .қаз — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: whois.nic.kzWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: ns.nic.kzns1.nic.kzns2.nic.kzThe 3 authoritative servers for the .қаз zone — what the root delegates to. Nothing ds queries directly; they are what makes a registered name resolve.

What it is

Derived from the root zone and ICANN's registry list — each one is a fact with a source.

country-code IANA Root Zone Database types it "country-code"
idn the label is punycode — an internationalised TLD; unicode is how it reads

In the root zone

The delegation itself, read out of the root zone — serial 2026090900, on 2026-09-09. The registry section above is IANA's record of what .қаз was delegated to; this is what the root actually answers with when a resolver asks it where .қаз lives.

Delegated to: ns.nic.kz194.0.21.52001:678:98:1::5
ns1.nic.kz185.79.212.72a01:7640:9000::7
ns2.nic.kz204.61.216.1432001:500:14:6143:ad::1
The 3 name servers the root hands out for .қаз, with the glue addresses that come with them — every one of them answers over IPv6. None of this is what ds queries: these servers know which names exist, not who registered them.
DNSSEC: Signed — 1 DS record in the root
key 12941ECDSA P-256/SHA-256 · SHA-2561E67E661E644F9C2CC122CF6307CE2BA434A1D3AEBEC08769BF5A28EC697F8DB
Each one is a fingerprint of .қаз's own signing key, published by the root and signed with the root's key — which is how a resolver that trusts only one key can prove an answer under .қаз came from its registry and was not tampered with in transit. It says nothing about who owns a name or whether one is free.

Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net xn--80ao21a. NS and dig +norec @a.root-servers.net xn--80ao21a. DS.