South Korea's .kr and .한국 Join the IANA RDAP Registry
IANA has added South Korea's ASCII and Korean-script country-code domains to its DNS bootstrap registry, allowing RDAP clients to discover KRNIC's service through the standard bootstrap process.
Update details
- Change
- Added to the IANA bootstrap registry
- Effective date
- September 16, 2026
- Affected resources
.kr, .xn--3e0b707e- RDAP endpoint
https://rdap.nic.or.kr/- Browser access
- Simple browser GET supportedChecked September 17, 2026 · HTTP 200
IANA’s RDAP bootstrap registry now includes South Korea’s .kr country-code top-level domain and its Korean-script internationalized counterpart, .한국.
The registry entry maps both labels to the KRNIC RDAP base URL, https://rdap.nic.or.kr/.
In the machine-readable bootstrap file, .한국 appears in its ASCII-compatible form, xn--3e0b707e. RDAP clients use that encoded label when matching a domain against the registry.
What changed
The IANA DNS bootstrap file published on September 16, 2026 includes a service record for:
| Display form | Bootstrap label |
|---|---|
.kr | kr |
.한국 | xn--3e0b707e |
Neither label appeared in IANA’s previous snapshot published on September 9. The new record means standards-compliant clients can now find KRNIC’s RDAP service without a separately maintained endpoint list.
What it means for RDAPLookup
South Korea now moves from Not IANA-listed to IANA-listed in the State of RDAP dataset. The checked-in bootstrap snapshot has also been refreshed so builds can retain the new classification when the live IANA file is unavailable.
An IANA listing establishes the official discovery route. It does not, by itself, guarantee continuous availability, complete registration data, browser cross-origin access or full protocol conformance.
At the time of testing on September 17, 2026, KRNIC’s endpoint supported the simple cross-origin GET used by RDAPLookup. A browser request from rdaplookup.org for nic.or.kr returned HTTP 200 with an RDAP domain response. This is a point-in-time observation and does not establish support for every preflighted request or guarantee future availability.
For more detail on how clients turn a TLD label into an authoritative query URL, read How to Find the RDAP Server for a Domain.