.dabur TLD Details
The .dabur domain name extension will operate as a restricted registry, in which Dabur India Limited can create and control domain spaces that promote its brand's identity and authenticity. In this regard, the .dabur TLD will be used by Dabur India Limited to provide information, services and resources to consumers in a way that promotes trust, convenience and utility.
- Dabur India Limited
- Whois Server
- gTLD - Generic Top Level Domain
- Registration Date
- 15 January 2015
- Registered Domains
- 9Last updated 24 November 2018
- No restrictions found, however, TLDs from organizations are generally restricted to the registered company.
- Whois Result for .dabur
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: DABUR organisation: Dabur India Limited address: Dabur Tower, Kaushambi, Sahibabad address: Ghaziabad, Uttar Pradesh address: 201010 address: India contact: administrative name: Head, IT organisation: Dabur India Limited address: Dabur Tower, Kaushambi, Sahibabad address: Ghaziabad, Uttar Pradesh address: 201010 address: India phone: +91.1203982000 fax-no: +91.1204374935 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.DABUR 2a01:8840:ae:0:0:0:0:25 22.214.171.124 nserver: A2.NIC.DABUR 2a01:8840:b1:0:0:0:0:25 126.96.36.199 nserver: B0.NIC.DABUR 2a01:8840:af:0:0:0:0:25 188.8.131.52 nserver: C0.NIC.DABUR 2a01:8840:b0:0:0:0:0:25 184.108.40.206 ds-rdata: 19761 7 1 07a2f4a7e8d08de6e5e6447912e600b0db1b6469 ds-rdata: 19761 7 2 53a018fe3e95bfb559c780b1ad542730ad65f3d723d80749c2535cbe8df83fc5 whois: whois.afilias-srs.net status: ACTIVE remarks: Registration information: http://www.dabur.com created: 2015-01-15 changed: 2015-01-25 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.