.mckinsey TLD Details
The .mckinsey domain name extension will operate as a restricted registry, in which McKinsey Holdings, Inc. can create and control domain spaces that promote its brand's identity and authenticity. In this regard, the .mckinsey TLD will be used by McKinsey Holdings, Inc. to provide information, services and resources to consumers in a way that promotes trust, convenience and utility.
- McKinsey Holdings, Inc.
- Whois Server
- gTLD - Generic Top Level Domain
- Registration Date
- 21 July 2016
- Registered Domains
- 1Last updated 7 April 2019
- No restrictions found, however, TLDs from organizations are generally restricted to the registered company.
- Whois Result for .mckinsey
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: MCKINSEY organisation: McKinsey Holdings, Inc. address: 555 California Street address: San Francisco, CA 94194 address: United States contact: administrative name: Associate General Counsel organisation: McKinsey Holdings, Inc. address: 555 California Street address: San Francisco, CA 94194 address: United States phone: +1 404 335 3000 fax-no: +1 404 521 1743 e-mail: email@example.com contact: technical name: Senior Director, DNS Infrastructure Group organisation: Afilias address: Building 3, Suite 105 address: 300 Welsh Road address: Horsham, PA 19044 address: United States phone: +1 215.706.5700 fax-no: +1 215.706.5701 e-mail: firstname.lastname@example.org nserver: A0.NIC.MCKINSEY 2a01:8840:e6:0:0:0:0:25 126.96.36.199 nserver: A2.NIC.MCKINSEY 2a01:8840:e9:0:0:0:0:25 188.8.131.52 nserver: B0.NIC.MCKINSEY 2a01:8840:e7:0:0:0:0:25 184.108.40.206 nserver: C0.NIC.MCKINSEY 2a01:8840:e8:0:0:0:0:25 220.127.116.11 ds-rdata: 21081 7 1 1c77dd23709ad50c0ad2ba7aa8dd70cb6a06cfdb ds-rdata: 21081 7 2 e683f1c2c4249e0ee733ecb0c5cebe220c1fac450987b726ab6a304099bb17f1 whois: whois.nic.mckinsey status: ACTIVE remarks: Registration information: http://www.mckinsey.com/ created: 2016-07-21 changed: 2017-07-20 source: IANA
- This record was retrieved from our local cache, and is 2 days old. If you want to see the latest whois, please click here to clear the cache.