ds

.飞利浦.xn--kcrx77d1x4a

Internationalised top-level domain

RDAPbrand TLD

Nobody outside the registry can register here. .飞利浦 is a brand TLD run by Koninklijke Philips 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 Philips N.V.
Lookup
RDAPanswers for it
DNSSEC
Signed1 DS record in the root
Level
Secondmybrand.飞利浦

Check a name

Names under .飞利浦 cannot be registered, but ds will still tell you what the registry says.

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--kcrx77d1x4a

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

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

ds mybrand --tld xn--kcrx77d1x4a --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
Koninklijke Philips N.V.Based in Netherlands. Delegated 2015-02-13, record last updated 2023-11-30.
Registry site
nic.xn--kcrx77d1x4aWhere 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
rdap.nic.xn--kcrx77d1x4a · whois.nic.xn--kcrx77d1x4aWhat the registry itself tells IANA it runs. They agree with what ds asks.

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
  • brand ICANN records Specification 13 — a brand TLD, closed to the public
  • 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
  • a.nic.xn--kcrx77d1x4a37.209.192.92001:dcd:1::9
  • b.nic.xn--kcrx77d1x4a37.209.194.92001:dcd:2::9
  • c.nic.xn--kcrx77d1x4a37.209.196.92001:dcd:3::9
  • x.nic.xn--kcrx77d1x4a156.154.172.822610:a1:1074::1:82
  • y.nic.xn--kcrx77d1x4a156.154.173.822610:a1:1075::1:82
  • z.nic.xn--kcrx77d1x4a156.154.174.822610:a1:1076::1:82
The 6 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 52825RSA/SHA-256 · SHA-2565BB0DDA1180FDF0F6C0932F027C0B6FAF19CFA8E9848F954046D4BD63EBFBC5C
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--kcrx77d1x4a. NS and dig +norec @a.root-servers.net xn--kcrx77d1x4a. DS.

Also run by Koninklijke Philips N.V.