Generic Top-Level Domain (gTLD) Registry Agreements
Unsponsored TLD Agreement: Appendix O (.name)
Unsponsored TLD Agreement: Appendix O (.name) (29 June 2001) |
||
The Whois service is compliant with RFC 954. It substantially consists of two parts:
The .name Whois service provides a central, openly accessible system for information regarding a particular domain name registration on .name. In the .com, .net and .org TLDs today, persons seeking information are forced to query each Registrar's individual databases to find the requested information. Further, the information returned is not always consistent and uniformly represented. The .name Whois is a central repository for the Whois information on .name, eliminates the fragmentation and consistently represents the Whois information across all domain name registrations, SLD E-mail registrations and Defensive Registrations. The Registry Whois system has been designed for robustness, availability and performance. Provisions for detection of abusive usage, like excessive numbers of queries from one source, have been taken into account, and other countermeasures against abuse will be activated if necessary. The Registry Operator will initially provide at least two operational Whois sites running simultaneously at two different locations. These Whois sites will be situated in the main data center on a high availability system, and at the disaster recovery site, which will be located in another country on a different backbone network. All Whois servers will run an update daemon. For Whois servers at the main data center, the update application will only be accessible from the internal network (using separate network interface cards). External Whois sites, including the Disaster Recovery site Whois server, will utilize a secure communication channel for these updates. An update scheme such as described above ensures that the Whois data is as accurate as possible, with optimal bandwidth usage. In the event of a failure on the update machine, an operator will be notified via e-mail (and optionally an additional SMS channel). An onsite standby machine will be configured and ready to use at all times; update service will be resumed when this standby machine replaces the failed server. Data for this standby machine will be held on the central storage system. This Appendix is subject to change by agreement of Registry Operator and ICANN during the design process as well as during the IETF standards process. Further, Registry Operator reserves the right to develop these services internally or outsource management of the facilities to an external contractor under terms that are consistent with the standards of the proposed service. In addition, Registry Operator agrees to implement changes to this Appendix specified by ICANN to conform to the IETF provreg working group's protocol specification no later than 135 days after the IETF specification is adopted as a Proposed Standard [RFC 2026, section 4.1.1]. The Whois service is described in more detail below. Registry Operator will make available a Whois interface on its website which can also be linked to by each ICANN-Accredited Registrar that is a party to a Registry-Registrar Agreement with Registry Operator. The information available in the Whois database will be returned in two formats: (i) a results page on the website and (ii) where requested as described below, an e-mail report. Returned data on the Web-based Whois service For the fields contained in the returned Data in the Results Page on the website (identical to the port 43 Whois), and an example of a record returned, please see the Whois Output Fields section below. Returned data in the e-mail report: For the fields contained in the returned SLD E-mail Whois report and an example of a record returned, please see the SLD E-mail Whois Output section below. The e-mail report will be compiled instantly and sent to the e-mail address specified by the requestor. The e-mail report will be provided upon request, subject to the requirements described below. The interface for requesting an e-mail report will be provided on the same web page as the interface for the website report. The e-mail report will also include a list of other domain name or SLD E-mail address registrations held by the same registrant, as determined by the Registrant ID. When requesting the e-mail report, the requestor must provide the following fields:
Data collected from or about requestors will be used only to document the request and will not be used for any commercial purpose whatsoever. Error Message The response of any request may be an error or a successful query. If an error occurs, the service uses different error messages, depending on the severity and cause of the error. The service will send a message describing the error, the reason for the failure, and possibly an explanation of how to solve the problem. The subject of such a mail will contain the phrase "Whois query error". Format of Responses. 1. The format of responses will follow a semi-free text format outline below, preceded by a disclaimer specifying the rights of the Registry Operator, and the user querying the database. The data reported will be formatted in such a way that it should be possible to, by relatively simple means, use software to extract data. 2. Each data object shall be represented as a set of key/value pairs, where each key runs from the start of the line, until the first colon (":"), and where any white space found immediately preceding the first colon shall not be counted as part of the key. All data excluding the first continuous sequence of white space following the first colon, up to but excluding the line feed should count as part of the value. 3. All Whois data will be in the ASCII character set, which has encoding compatible with UTF-8 for easy transition to including internationalized data, and as per the IETF's recommendations on i18n in Internet protocols. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 4. All record and key types shall be specified in a publicly available description on the Registry Operator's website, and the URL should be published in the Whois results. The key names and record types should change as infrequently as possible, and only in the case of serious technical reasons and/or changes to the data reported or format thereof is mutually agreed upon by ICANN and the Registry Operator. Minimum Data Update Frequency. Under normal operations the Registry Operator shall make reasonable efforts to continuously update the data as requests are handled, in a matter of seconds or minutes. The Registry Operator shall ensure that records in the Whois server are updated no later than 24 hours after the registration or modification transaction with the registrar is completed. Protocols Through Which Access is Provided. Access to the Whois data is provided through a subset of the Whois protocol, supporting exact queries for domain names, defensive registrations, contacts, registrar name, nameserver hostname and nameserver ip-address. The Whois data will also be accessible through the Registry web interface as described above. Apart from as specified above, bulk access to the Whois data will be made available as specified in Appendix P and Appendix Q. Security. The update connection from the Registry Operator's main site to the Whois service located at the disaster recovery site (and other external Whois sites, should the Registry Operator choose to expand them in number) will be implemented via a VPN (Virtual Private Network) service, to minimize the risk of unauthorized access to the contents of the Whois database. The Whois service at the main site is already within the firewall and other security systems, therefore posing a reduced security risk. The update server application will run as a user with low permission levels to prevent unauthorized access to the system. General security measures such as password aging policy, firewalls, Intrusion Detection Systems (IDS) and network traffic monitoring systems will be provided for the Whois services, as further described in the Security section of Appendix C. The Whois output will be returned with the respective key/value pairs, which will eliminate the need for registrars to store additional information in their own local database, then combine it with the registry Whois information when they present it to end users. The proposed capability will also ensure that end users will view the same information no matter which registrar they use to retrieve Whois data. III - Query and Output for Reports Delivered by Web Page and Port 43 All queries shall be in ASCII and shall be interpreted in a case-insensitive manner. The following keywords (in parentheses below) restrict a search to an exact match on a specific object type:
By default, if no object type control is specified, then the Domain Name field of the Domain object is searched. Whois Output Fields and Query Example Domain Record: A Whois query that results in domain information will return the following fields from the Domain object and the associated data from host and contact objects. This set of data is also referred to as the Domain Record. Input: Registrant ID: CNT-1111 Admin ID: CNT-2222 Tech Organization: DOMAINADMINISTRATION LTD Tech Name: DOMAINADMIN JOHN SMITH Tech Address: 140 OXFORD STREET Tech City: LONDON Tech State/Province: Tech Country: UK Tech Postal Code: WC12 4AB Tech Phone Number: +44207123456 Tech Fax Number: +44207123457 Tech Email: DOMAINADMIN@DOMAINADMINISTRATION.CO.UK Billing ID: CNT-2222 Name Server: NS1.SMITH.NAME Created On: MAY 15, 2001 A Whois query that results in Nameserver information will return the following. This set of information is referred to as the Nameserver Record. Input: Output: Created on: MAY 5, 2001 Contact Record: A Whois query that results in contact information will return the following. This set of information is referred to as the Contact Record. Input: Output: Registrar Record: A Whois query that results in Registrar information will return the following. This set of information is referred to as the Registrar Record. Input: Output: Created On: MAY 5, 2001 Defensive Registration Record: A Whois query that results in Defensive Registration information will return the following. This set of information is referred to as the Defensive Registration Record Input: Output: Registrant ID: DRH-024 Admin ID: DRH-024 Billing ID: DRH-024 Created On: MAY 15, 2001 IV - Query and Output for Reports Delivered by E-Mail All queries shall be in ASCII and shall be interpreted in a case-insensitive manner. Queries for domain name and SLD e-mail address are supported. The requirements for queries are described in item I above. The following information will be returned in the e-mail report requested from the website: Domain record Input (entered on web page): john.smith.name (other information described in item I above must also be provided). Output: Tech ID: CNT-2222 Billing ID: CNT-2222 Name Server: NS1.SMITH.NAME Created On: MAY 15, 2001
Input (entered on web page): john@smith.name (other information described in item I above must also be provided). Output: Registrant ID: CNT-1111 Tech ID: CNT-2222 Billing ID: CNT-2222 Created On: MAY 15, 2001
Comments concerning the layout, construction and functionality of this site should be sent to webmaster@icann.org. Page Updated 20-Oct-2002 |