Common use of Searchability Clause in Contracts

Searchability. Offering searchability capabilities for the Registration Data is optional but if offered by the Registry Operator it shall comply with the specification described in this section. 1.3.1 Registry Operator will offer searchability as a web-based service. 1.3.2 Registry Operator will offer partial match capabilities on each of the following fields: domain name, contacts and registrant’s name, and contact and registrant’s postal address, including all the sub-fields described in EPP (e.g., street, city, state or province, etc.), and may offer partial match capabilities on other fields, in each case subject to applicable law. 1.3.3 Registry Operator will offer exact-match capabilities, at least, on the following fields: Registrar ID, name server name, and name server’s IP address (only applies to IP addresses stored by the registry, i.e., glue records). 1.3.4 Registry Operator will offer Boolean search capabilities supporting, at least, the following logical operators to join a set of search criteria: AND, OR, NOT. 1.3.5 Search results will include domain names matching the search criteria. 1.3.6 Registry Operator will: 1) implement appropriate measures to avoid abuse of this feature (e.g., permitting access only to legitimate authorized users); and 2) ensure the feature is in compliance with any applicable privacy laws and ICANN Consensus Policies and Temporary Policies. 1.3.7 Registry Operator shall only offer the searchability capabilities required in the RDAP Technical Implementation Guide and RDAP Response Profile in the RDAP Directory Services.

Searchability. Offering searchability capabilities for the Registration Data registration data provided via RDDS is optional but if offered by the Registry Operator it shall comply with the specification described in this section. 1.3.1 3.1 Registry Operator will offer searchability as a web-based service. 1.3.2 3.2 Registry Operator will offer partial match capabilities on each of the following fields: domain name, contacts and registrant’s name, and contact and registrant’s postal address, including all the sub-fields described in EPP (e.g., street, city, state or province, etc.), and may offer partial match capabilities on other fields, in each case subject to applicable law. 1.3.3 3.3 Registry Operator will offer exact-match capabilities, at least, on the following fields: Registrar ID, name server name, and name server’s IP address (only applies to IP addresses stored by the registry, i.e., glue records). 1.3.4 3.4 Registry Operator will offer Boolean search capabilities supporting, at least, the following logical operators to join a set of search criteria: AND, OR, NOT. 1.3.5 3.5 Search results will include domain names matching the search criteria. 1.3.6 3.6 Registry Operator will: 1) implement appropriate measures to avoid abuse of this feature (e.g., permitting access only to legitimate authorized users); and 2) ensure the feature is in compliance with any applicable privacy laws and ICANN Consensus Policies and Temporary Policies. 1.3.7 3.7 Registry Operator shall only offer the searchability capabilities required in the RDAP Technical Implementation Guide and RDAP Response Profile in the RDAP Directory Services., as described in Section 2.1 of Appendix 5B.

Searchability. Offering searchability capabilities for the Registration Data registration data provided via RDDS is optional but if offered by the Registry Operator it shall comply with the specification described in this section. 1.3.1 3.1. Registry Operator will offer searchability as a web-based service. 1.3.2 3.2. Registry Operator will offer partial match capabilities on each of the following fields: domain name, contacts and registrant’s name, and contact and registrant’s postal address, including all the sub-fields described in EPP (e.g., street, city, state or province, etc.), and may offer partial match capabilities on other fields, in each case subject to applicable law. 1.3.3 3.3. Registry Operator will offer exact-match capabilities, at least, on the following fields: Registrar ID, name server name, and name server’s IP address (only applies to IP addresses stored by the registry, i.e., glue records). 1.3.4 3.4. Registry Operator will offer Boolean search capabilities supporting, at least, the following logical operators to join a set of search criteria: AND, OR, NOT. 1.3.5 3.5. Search results will include domain names matching the search criteria. 1.3.6 3.6. Registry Operator will: 1) implement appropriate measures to avoid abuse of this feature (e.g., permitting access only to legitimate authorized users); and 2) ensure the feature is in compliance with any applicable privacy laws and ICANN Consensus Policies and Temporary Policies. 1.3.7 3.7. Registry Operator shall only offer the searchability capabilities required in the RDAP Technical Implementation Guide and RDAP Response Profile in the RDAP Directory Services., as described in Section 2.1 of Appendix 5B.

Searchability. Offering searchability capabilities for the onthe Registration Data DataDirectory Services is optional but if offered by the Registry Operator it shall comply with the specification described in this section. 1.3.1 Registry Operator will offer searchability on the as a web-based Directory service. 1.3.2 Registry Operator will offer partial match capabilities capabilities, at least,on each of the following fields: domain name, contacts and registrant’s name, and contact and registrant’s postal address, including all the sub-fields described in EPP (e.g., street, city, state or province, etc.), and may offer partial match capabilities on other fields, in each case subject to applicable law. 1.3.3 Registry Operator will offer exact-match capabilities, at least, on the following fields: Registrar ID, name server name, and name server’s IP address (only applies to IP addresses stored by the registry, i.e., glue records). 1.3.4 Registry Operator will offer Boolean search capabilities supporting, at least, the following logical operators to join a set of search criteria: AND, OR, NOT. 1.3.5 Search results will include domain names matching the search criteria. 1.3.6 Registry Operator will: 1) implement appropriate measures to avoid abuse of this feature (e.g., permitting access only to legitimate authorized users); and 2) ensure the feature is in compliance with any applicable privacy laws and or policiesand ICANN Consensus Policies and Temporary Policies. 1.3.7 Registry Operator shall only offer the searchability capabilities required in the RDAP Technical Implementation Guide and RDAP Response Profile in the RDAP Directory Services.

Searchability. Offering searchability capabilities for the Registration Data is optional but if offered by the Registry Operator it shall comply with the specification described in this section. 1.3.1 Registry Operator will offer searchability as a web-based service. 1.3.2 Registry Operator will offer partial match capabilities capabilities, on each of the following fields: domain name, contacts and registrant’s name, and contact and registrant’s postal address, including all the sub-sub- fields described in EPP (e.g., street, city, state or province, etc.), and may offer partial match capabilities on other fields, in each case subject to applicable law. 1.3.3 Registry Operator will offer exact-match capabilities, at least, on the following fields: Registrar ID, name server name, and name server’s IP address (only applies to IP addresses stored by the registry, i.e., glue records). 1.3.4 Registry Operator will offer Boolean search capabilities supporting, at least, the following logical operators to join a set of search criteria: AND, OR, NOT. 1.3.5 Search results will include domain names matching the search criteria. 1.3.6 Registry Operator will: 1) implement appropriate measures to avoid abuse of this feature (e.g., permitting access only to legitimate authorized users); and 2) ensure the feature is in compliance with any applicable privacy laws and ICANN Consensus Policies and Temporary Policies. 1.3.7 Registry Operator shall only offer the searchability capabilities required in the RDAP Technical Implementation Guide and RDAP Response Profile in the RDAP Directory Services.

Searchability. Offering searchability capabilities for on the Registration Data Directory Services is optional but if offered by the Registry Operator it shall comply with the specification described in this section. 1.3.1 1.11.11.10.1 Registry Operator will offer searchability as a on the web-based serviceDirectory Service. 1.3.2 1.11.21.10.2 Registry Operator will offer partial match capabilities capabilities, at least, on each of the following fields: domain name, contacts and registrant’s name, and contact and registrant’s postal address, including all the sub-fields described in EPP (e.g., street, city, state or province, etc.), and may offer partial match capabilities on other fields, in each case subject to applicable law. 1.3.3 1.11.31.10.3 Registry Operator will offer exact-match capabilities, at least, on the following fields: Registrar registrar idRegistrar ID, name server name, and name server’s IP address (only applies to IP addresses stored by the registry, i.e., glue records). 1.3.4 1.11.41.10.4 Registry Operator will offer Boolean search capabilities supporting, at least, the following logical operators to join a set of search criteria: AND, OR, NOT. 1.3.5 1.11.51.10.5 Search results will include domain names matching the search criteria. 1.3.6 1.11.61.10.6 Registry Operator will: 1) implement appropriate measures to avoid abuse of this feature (e.g., permitting access only to legitimate authorized users); and 2) ensure the feature is in compliance with any applicable privacy laws and ICANN Consensus Policies and Temporary Policiesor policies. 1.3.7 Registry Operator shall only offer the searchability capabilities required in the RDAP Technical Implementation Guide and RDAP Response Profile in the RDAP Directory Services.