Generic Top-Level Domain (gTLD) Registry Agreements
.NET Registry Agreement Appendix 5 | Whois Specifications
 |
.NET Registry Agreement Appendix 5 Whois Specifications (1 July 2011) |
|
|
Registry Operator's Whois service is the authoritative Whois service for all second-level Internet domain names registered in the.NET top-level domain and for all hosts registered using these names. This service is available to anyone. It is available via port 43 access and via links at the Registry Operator's web site. It is updated daily. To use Registry Whois via port 43 enter the applicable parameter on the command line as illustrated below: For a domain name: whois "domain verisign.net" For a registrar name: whois "registrar Go Daddy Software, Inc." For a nameserver: whois "DNS3.REGISTER.NET" or whois "nameserver 216.21.234.72" By default, Whois performs a very broad search, looking in all record types for matches to your query in these fields: domain name, nameserver name, nameserver IP address, and registrar names. Use keywords to narrow the search (for example, 'domain root'). Specify only part of the search string to perform a "partial" search on domain. Every domain starting with the string will be found. A trailing dot (or dots) after your text or the partial keyword indicates a partial search. For example, entering 'mack.' will find "Mack", "Mackall", "Mackay", and so on. To use Registry Whois using the web interface: Go to www.verisign-grs.net/whois Click on the appropriate button ("domain," "registrar" or "nameserver") Enter the applicable parameter: Domain name including the TLD (e.g., verisign-grs.net) Full name of the registrar including punctuation, "Inc.", etc. (e.g., America Online, Inc.) Full host name or the IP address (e.g., ns1.crsnic.net or 198.41.3.39) Click on the "submit" button. For all registered second-level domain names in .NET, information as illustrated in the following example is displayed in a thin format, where the entry parameter is the domain name (including the TLD): Domain Name: VERISIGN-GRS.NET >>> Last update of whois database: Wed, 2 Feb 2005 07:52:23 EST <<< For all ICANN-accredited registrars who are authorized to register .net second-level domain names through Registry Operator, information as illustrated in the following example is displayed, where the entry parameter is the full name of the registrar (including punctuation, "Inc.", etc.): >>> Last update of whois database: Wed, 2 Feb 2005 07:52:23 EST <<< >>> Last update of whois database: Wed, 2 Feb 2005 07:52:23 EST <<< Whois Provider Data Specification Registry Operator shall provide bulk access to up-to-date data concerning domain name and nameserver registrations maintained by Registry Operator in connection with the Registry TLD on a daily schedule, only for purposes of providing free public query-based access to up-to-date data concerning domain name and nameserver registrations in multiple TLDs, to a party designated from time to time in writing by ICANN. The specification of the content and format of this data, and the procedures for providing access, shall be as stated below, until changed according to the Registry Agreement. Content The data shall be provided in three files: A. Domain file. One file shall be provided reporting on the domains sponsored by all registrars. For each domain, the file shall give the domainname, servername for each nameserver, registrarid, and updateddate. B. Nameserver file. One file shall be provided reporting on the nameservers sponsored by all registrars. For each registered nameserver, the file shall give the servername, each ipaddress, registrarid, and updateddate. C. Registrar file. A single file shall be provided reporting on the registrars sponsoring registered domains and nameservers. For each registrar, the following data elements shall be given: registrarid, registrar address, registrar telephone number, registrar e-mail address, whois server, referral URL, updateddate and the name, telephone number, and e-mail address of all the registrar's administrative, billing, and technical contacts. Format The format for the above files shall be as specified by ICANN, after consultation with Registry Operator. Procedures for Providing Access The procedures for providing daily access shall be as mutually agreed by ICANN and Registry Operator. In the absence of an agreement, the files shall be provided by Registry Operator sending the files in encrypted form to the party designated by ICANN by Internet File Transfer Protocol. Whois Data Specification - ICANN Registry Operator shall provide bulk access by ICANN to up-to-date data concerning domain name and nameserver registrations maintained by Registry Operator in connection with the .NET TLD on a daily schedule, only for purposes of verifying and ensuring the operational stability of Registry Services and the DNS.. The specification of the content and format of this data, and the procedures for providing access, shall be as stated below, until changed according to the Registry Agreement. Content The data shall be provided in three files: A. Domain file. One file shall be provided reporting on the domains sponsored by all registrars. For each domain, the file shall give the domainname, servername for each nameserver, registrarid, and updateddate. B. Nameserver file. One file shall be provided reporting on the nameservers sponsored by all registrars. For each registered nameserver, the file shall give the servername, each ipaddress, registrarid, and updateddate. C. Registrar file. A single file shall be provided reporting on the registrars sponsoring registered domains and nameservers. For each registrar, the following data elements shall be given: registrarid, registrar address, registrar telephone number, registrar e-mail address, whois server, referral URL, updateddate and the name, telephone number, and e-mail address of all the registrar's administrative, billing, and technical contacts. Format The format for the above files shall be as specified by ICANN, after consultation with Registry Operator. Procedures for Providing Access The procedures for providing daily access shall be as mutually agreed by ICANN and Registry Operator. In the absence of an agreement, an up-to-date version (encrypted using a public key supplied by ICANN) of the files shall be placed at least once per day on a designated server and available for downloading by ICANN by Internet File Transfer Protocol. |
||