What is .shangrila?
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 .shangrila names for sale at any registrar.
.shangrila entered the DNS root zone on July 2, 2016, 10 years ago. It came out of ICANN's New gTLD Program, the 2012 application round that grew the root from 22 generic TLDs to well over a thousand.
Shangri‐La International Hotel Management Limited also runs one other TLD, including .香格里拉.
On the technical side, .shangrila is served by 4 authoritative name servers, every one of them reachable over IPv6. It is also DNSSEC-signed: the root zone carries a DS record for .shangrila, which lets validating resolvers check its answers cryptographically. Registration data is published over RDAP and WHOIS (the WHOIS server is whois.nic.shangrila).
Same registry, other endings
1 other TLD shares this operator.
.shangrila FAQ
What country is .shangrila?
None. .shangrila is a generic top-level domain, so it isn't tied to any country.
Who owns the .shangrila domain extension?
Shangri‐La International Hotel Management Limited operates .shangrila as its registry, under a registry agreement with ICANN.
When was .shangrila created?
.shangrila was delegated to the DNS root zone on July 2, 2016.
Is .shangrila a valid domain?
Yes. .shangrila is an active top-level domain in the DNS root zone, delegated in 2016, so .shangrila addresses work in every browser.
Can I buy a .shangrila domain?
No. .shangrila is a brand TLD under ICANN Specification 13, so names are reserved for Shangri‐La International Hotel Management Limited.
Is .shangrila DNSSEC-signed?
Yes, the root zone holds a DS record for .shangrila.
Sources
Data from IANA root zone version 2026102000. Last changed August 11, 2023. Spotted something wrong? Tell us.
