Type your domain and click Check
WHOIS records of barcodemakersoftware.net
Domain Information
clientdeleteprohibited
clienttransferprohibited
Registrar Information
Dates
Nameservers
Contact information
Response from WHOIS Server
If you don't find any information above, check the original response.
Domain Name: barcodemakersoftware.net Registry Domain ID: 2695317704_DOMAIN_NET-VRSN Registrar WHOIS Server: whois.ename.com Registrar URL: http://www.ename.net Updated Date: 2022-05-11T14:59:24Z Creation Date: 2022-05-11T06:58:38Z Registrar Registration Expiration Date: 2023-05-11T06:58:38Z Registrar: DOMAIN NAME NETWORK PTY LTD Registrar IANA ID: 1527 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +86.4000044400 Domain Status: clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited Registrant State/Province: GD Registrant Country: CN Registrant Email: https://whois.ename.net/contact/barcodemakersoftware.net Admin Email: https://whois.ename.net/contact/barcodemakersoftware.net Tech Email: https://whois.ename.net/contact/barcodemakersoftware.net Name Server:ns1.taoa.com Name Server:ns2.taoa.com DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2022-07-01T16:23:02Z <<< For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en
What is Whois?
Accoriding to Wikipedia, "WHOIS (pronounced as the phrase "who is") is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block or an autonomous system, but is also used for a wider range of other information. The protocol stores and delivers database content in a human-readable format.[1] The current iteration of the WHOIS protocol was drafted by the Internet Society, and is documented in RFC 3912."