Common use of WHOIS Data Directory Services Clause in Contracts

WHOIS Data Directory Services. Registry Operator will operate a WHOIS service available via port 43 in accordance with RFC 3912, and a web-based WHOIS Service at <xxx.xxxxxxxx.xxx/xxxxx> providing free public query-based access to at least the following elements in the following format. 1.1 The format of responses shall follow a semi-free text format outlined below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2 Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3 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. 1.4 The fields specified below set forth the minimum output requirements. Registry Operator must implement only those sections of the Registry Registration Data Directory Services Consistent Labeling and Display Policy (xxxxx://xxx.xxxxx.xxx/resources/pages/rdds-labeling-policy-2024-02-21-en) in conjunction with this Appendix 5A that are relevant to the type of TLD operated, e.g., “thick” or “thin” registry model (e.g. exclude information from any contact: registrant, admin, tech, billing etc.). As of the Effective Date, the .com TLD is considered a “thin” registry model. 1.5 Domain Name Data

WHOIS Data Directory Services. Registry Operator will operate a WHOIS service available via port 43 in accordance with RFC 3912, and a web-based WHOIS Service at <xxx.xxxxxxxx.xxx/xxxxx> providing free public query-based access to at least the following elements in the following format. 1.1 The format of responses shall follow a semi-free text format outlined below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2 Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3 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. 1.4 The fields specified below set forth the minimum output requirements. Registry Operator must implement only those sections of the Registry Registration Data Directory Services Consistent Labeling and Display Policy (xxxxx://xxx.xxxxx.xxx/resources/pages/rdds-labeling-policy-2024-02-21-en) in conjunction with this Appendix 5A that are relevant to the type of TLD operated, e.g., “thick” or “thin” registry model (e.g. exclude information from any contact: registrant, admin, tech, billing etc.). As of the Effective Date, the .com TLD is considered a “thin” registry model. 1.5 Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD 1.5.2 Response format:

WHOIS Data Directory Services. Until the WHOIS Services Sunset Date, Registry Operator will operate a WHOIS service available via port 43 in accordance with RFC 3912, and a web-based WHOIS Service at <xxx.xxxxxxxx.xxx/xxxxx> providing free public query-based access to at least the following elements in the following format. 1.1 1.1. The format of responses shall follow a semi-free text format outlined below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3 1.3. 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. 1.4 1.4. The fields specified below set forth the minimum output requirements. Registry Operator must implement only those sections of the Registry Registration Data Directory Services Consistent Labeling and Display Policy (xxxxx://xxx.xxxxx.xxx/resources/pages/rdds-labeling-policy-2024-02-21-enxxxxx://xxx.xxxxx.xxx/ resources/pages/rdds-labeling-policy-2017-02-01-en) in conjunction with this Appendix 5A that are relevant to the type of TLD operated, e.g., “thick” or “thin” registry model (e.g. exclude information from any contact: registrant, admin, tech, billing etc.). As of the Effective Date, the .com .net TLD is considered a “thin” registry model. 1.5 1.5. Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD 1.5.2 Response format: