Skip to content

.삼성.xn--cg4bki

Internationalised top-level domain

RDAP

Register
—first year
Renew
—a year
Transfer
—to move it
Registrars
—quoting it
Lookup
RDAPanswers 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.

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.

Check a name under .삼성ds mybrand --tld xn--cg4bki

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 an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.

RDAP
https://nic.samsung/rdapFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://nic.samsung/rdap/domain/mybrand.xn--cg4bki — a 404 means the name is free.

ds mybrand --tld xn--cg4bki --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 generic TLD.

Run by
SAMSUNG SDS CO., LTDBased in Korea (the Republic of). Delegated 2013-12-12, record last updated 2026-06-15.
Registry site
samsungregistry.comWhere 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
nic.samsung · whois.krWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
n1-a1.aka-ns.netn1-a13.aka-ns.netn1-a20.aka-ns.netn1-a26.aka-ns.netn1-a4.aka-ns.netn1-a7.aka-ns.netns1.dns.samsungThe 7 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.

  • generic IANA Root Zone Database types it "generic"
  • idn the label is punycode — an internationalised TLD; unicode is how it reads
  • new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — see delegated

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
  • ns1.dns.samsung140.238.4.102603:c022:8004:5d05:ca27:7608:ff55:38fe
  • n1-a1.aka-ns.net23.2.10.12600:1405:4800::1
  • n1-a4.aka-ns.net23.59.162.12600:1405:7800::1
  • n1-a7.aka-ns.net96.16.208.12600:1405:a800::1
  • n1-a13.aka-ns.net184.29.150.12600:1405:400::1
  • n1-a20.aka-ns.net184.29.154.12600:1405:2400::1
  • n1-a26.aka-ns.net184.29.157.12600:1405:3c00::1
The 7 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 32836RSA/SHA-256 · SHA-256505E77C3FA6C758F7ED26BB5BC8B82D23611382107B01C285634EDBCFF31DA34
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--cg4bki. NS and dig +norec @a.root-servers.net xn--cg4bki. DS.