.bcg TLD Details
The .bcg domain name extension will operate as a restricted registry, in which The Boston Consulting Group, Inc. can create and control domain spaces that promote its brand's identity and authenticity. In this regard, the .bcg TLD will be used by The Boston Consulting Group, Inc. to provide information, services and resources to consumers in a way that promotes trust, convenience and utility.
- The Boston Consulting Group, Inc.
- Whois Server
- gTLD - Generic Top Level Domain
- Registration Date
- 11 February 2016
- Registered Domains
- 1Last updated 8 June 2017
- No restrictions found, however, TLDs from organizations are generally restricted to the registered company.
- Whois Result for .bcg
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: BCG organisation: The Boston Consulting Group, Inc. address: One Beacon Street address: Boston, MA 02108 address: United States contact: administrative name: Global Digital Marketing Programs Director organisation: The Boston Consulting Group, Inc. address: One Beacon Street address: Boston, MA 02108 address: United States phone: +1.617 973 1200 fax-no: +1.617 973 1399 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.BCG 2a01:8840:d2:0:0:0:0:25 126.96.36.199 nserver: A2.NIC.BCG 2a01:8840:d5:0:0:0:0:25 188.8.131.52 nserver: B0.NIC.BCG 2a01:8840:d3:0:0:0:0:25 184.108.40.206 nserver: C0.NIC.BCG 2a01:8840:d4:0:0:0:0:25 220.127.116.11 ds-rdata: 48108 7 1 1fcab02e25c47f8c985a150f983dc199d3e6b9be ds-rdata: 48108 7 2 e085676a3b8056349653315e5df6709bb16844ba1dbd701517ffea8b79f7a32e whois: whois.afilias-srs.net status: ACTIVE remarks: Registration information: http://www.bcg.com created: 2016-02-11 changed: 2016-03-09 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.