What is .飞利浦?
Brand TLDs operate under Specification 13 of ICANN's registry agreement. It lets a trademark owner keep every second-level name for itself, so you won't find .飞利浦 names for sale at any registrar.
ICANN's records put the delegation of .飞利浦 on April 7, 2015. Like most of the newer endings, it was applied for in the 2012 New gTLD Program round and its registry agreement was signed on November 7, 2014.
In the DNS, .飞利浦 is stored as the ASCII string xn--kcrx77d1x4a (its "A-label"). Browsers and apps that support IDNs show the native script instead.
Koninklijke Philips N.V. also runs one other TLD, including .philips.
Under the hood, the root zone points to 6 name servers for .飞利浦, every one of them reachable over IPv6. The delegation is DNSSEC-signed, so resolvers can verify that answers for .飞利浦 haven't been tampered with on the way. Registration data is published over RDAP and WHOIS (the WHOIS server is whois.nic.xn--kcrx77d1x4a).
Same registry, other endings
1 other TLD shares this operator.
.飞利浦 FAQ
What country is .飞利浦?
None. .飞利浦 is a generic top-level domain, so it isn't tied to any country.
Who owns the .飞利浦 domain extension?
Koninklijke Philips N.V. operates .飞利浦 as its registry, under a registry agreement with ICANN.
When was .飞利浦 created?
.飞利浦 was delegated to the DNS root zone on April 7, 2015.
Is .飞利浦 a valid domain?
Yes. .飞利浦 is an active top-level domain in the DNS root zone, delegated in 2015, so .飞利浦 addresses work in every browser.
Can I buy a .飞利浦 domain?
No. .飞利浦 is a brand TLD under ICANN Specification 13, so names are reserved for Koninklijke Philips N.V.
Is .飞利浦 DNSSEC-signed?
Yes, the root zone holds a DS record for .飞利浦.
Sources
Data from IANA root zone version 2026102000. Last changed November 30, 2023. Spotted something wrong? Tell us.
