.kpn
Generic top-level domain
Nobody outside the registry can register here. .kpn is a brand TLD run by Koninklijke KPN N.V., which under ICANN's Specification 13 means its operator is the only permitted registrant. ds reports names here as PRIVATE rather than AVAILABLE, and leaves the zone out of --tld all unless you pass --private include. See Brand and reserved TLDs.
- Registration
- Closedno public names
- Operator
- Koninklijke KPN N.V.
- Lookup
- RDAPanswers for it
- DNSSEC
- Signed2 DS records in the root
- Level
- Secondmybrand.kpn
Check a name
Names under .kpn cannot be registered, but ds will still tell you what the registry says.
ds mybrand --tld kpnAdd --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 .kpn, 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, though here it is neither: the zone is closed. See Prices for supplying your own table with --pricing-file.
Who can register
Nobody outside Koninklijke KPN N.V. — see the note at the top of this page.
How ds answers for it
RDAP first, WHOIS second — the same order for every TLD. .kpn has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.
- RDAP
https://rdap.centralnic.com/kpnFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://rdap.centralnic.com/kpn/domain/mybrand.kpn— a 404 means the name is free.
ds mybrand --tld kpn --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .kpn today. See Accuracy notes.
The registry
From IANA's delegation record for .kpn. .kpn is a generic TLD.
- Run by
- Koninklijke KPN N.V.Based in Netherlands. Delegated 2015-12-04, record last updated 2024-06-04.
- Published services
rdap.centralnic.comWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
a.nic.kpnb.nic.kpnc.nic.kpnd.nic.kpnThe 4 authoritative servers for the .kpn zone — what the root delegates to. Nothingdsqueries 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.
genericIANA Root Zone Database types it "generic"brandICANN records Specification 13 — a brand TLD, closed to the publicnew-gtldICANN delegated it on or after 2013-10-23, when the 2013 round opened — seedelegated
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 .kpn was delegated to; this is what the root actually answers with when a resolver asks it where .kpn lives.
- Delegated to
a.nic.kpn194.169.218.902001:67c:13cc::1:90b.nic.kpn185.24.64.902a04:2b00:13cc::1:90c.nic.kpn212.18.248.902a04:2b00:13ee::90d.nic.kpn212.18.249.902a04:2b00:13ff::90
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 2 DS records in the root
- key 6010RSASHA1-NSEC3-SHA1 · SHA-256
E5A8E92B179784641C4FCB989BD6946EA85A03812039F5061922D1815992FBC6 - key 10051RSASHA1-NSEC3-SHA1 · SHA-256
F265871198C769849F8ACF952F01FCD412C9B3DC5DBF8FCA98911D5052C0A240
- key 6010RSASHA1-NSEC3-SHA1 · SHA-256
Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net kpn. NS and dig +norec @a.root-servers.net kpn. DS.