.shangrila TLD Details
The .shangrila domain name extension will operate as a restricted registry, in which Shangri‐La International Hotel Management Limited can create and control domain spaces that promote its brand's identity and authenticity. In this regard, the .shangrila TLD will be used by Shangri‐La International Hotel Management Limited to provide information, services and resources to consumers in a way that promotes trust, convenience and utility.
- Shangri‐La International Hotel Management Limited
- Whois Server
- gTLD - Generic Top Level Domain
- Registration Date
- 24 June 2016
- Registered Domains
- 11Last updated 14 July 2019
- No restrictions found, however, TLDs from organizations are generally restricted to the registered company.
- Whois Result for .shangrila
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: SHANGRILA organisation: Shangri‐La International Hotel Management Limited address: 28/F. Kerry Centre 683 King’s Road, Quarry Bay address: Hong Kong contact: administrative name: Legal Executive organisation: Shangri‐La International Hotel Management Limited address: 28/F. Kerry Centre address: 683 King’s Road, Quarry Bay address: Hong Kong phone: +852 2820 0418 fax-no: n/a e-mail: email@example.com contact: technical name: Registry Customer Service organisation: Verisign, Inc. address: 12061 Bluemont Way address: Reston Virginia 20190 address: United States phone: +1-703-925-6999 fax-no: +1-703-948-3978 e-mail: firstname.lastname@example.org nserver: AC1.NSTLD.COM 126.96.36.199 2001:500:120:0:0:0:0:30 nserver: AC2.NSTLD.COM 188.8.131.52 2001:500:121:0:0:0:0:30 nserver: AC3.NSTLD.COM 184.108.40.206 2001:500:122:0:0:0:0:30 nserver: AC4.NSTLD.COM 220.127.116.11 2001:500:123:0:0:0:0:30 ds-rdata: 19245 8 2 1EB085C06EA9A775A07B82AEF3435F047A624A705046F3CDB64843F410ABB5A8 whois: whois.nic.shangrila status: ACTIVE remarks: Registration information: http://www.shangri-la.com/ created: 2016-06-24 changed: 2016-07-02 source: IANA
- This record was retrieved from our local cache, and is 3 days old. If you want to see the latest whois, please click here to clear the cache.