Common use of Exceptional Access to Thick Registration Data Clause in Contracts

Exceptional Access to Thick Registration Data. In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-to-date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification. SCHEDULE OF RESERVED NAMES Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable: Example. The ASCII label “EXAMPLE” shall be withheld from registration or allocated to Registry Operator at the second level and at all other levels within the TLD at which Registry Operator offers registrations (such second level and all other levels are collectively referred to herein as, “All Levels”). Such label may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, such withheld or allocated label shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such name without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

Exceptional Access to Thick Registration Data. In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-to-date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Appendix 1A Data EscrowEscrow Specification. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 2.1 of this SpecificationAppendix. SCHEDULE OF RESERVED NAMES .NET Registry Agreement Appendix 6 Schedule of Reserved Names (1 July 2017) Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve names formed with the following labels from initial (i.e., i.e. other than renewal) registration within the TLD. If using self-allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable: Example: A. Labels Reserved at All Levels. The ASCII label “EXAMPLE” following names shall be withheld from registration or allocated to Registry Operator reserved at the second level and at all other levels within the TLD at which Registry Operator offers registrations (such makes registrations: ICANN-related names: aso gnso icann internic ccnso IANA-related names: afrinic apnic arin example gtld-servers iab iana iana-servers iesg ietf irtf istf lacnic latnic rfc-editor ripe root-servers B. Additional Second-Level Reservations. In addition, the following names shall be reserved at the second level and all other levels are collectively referred to herein as, “level: All Levels”)single-character labels. Such All two-character labels shall be initially reserved. The reservation of a two-character label may not be activated in the DNS, and may not string shall be released for registration to any person the extent that the Registry Operator reaches agreement with the government and country-code manager, or entity other than Registry Operatorthe ISO 3166 maintenance agency, whichever appropriate. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, such withheld or allocated label shall be transferred as specified by ICANN. The Registry Operator may self-allocate and renew such name without use also propose release of an ICANN accredited registrar, which will not be considered Transactions for purposes these reservations based on its implementation of Section 6.1 of measures to avoid confusion with the Agreementcorresponding country codes.

Exceptional Access to Thick Registration Data. In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-to-date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Appendix 1A Data EscrowEscrow Specification. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 2.1 of this SpecificationAppendix. SCHEDULE OF RESERVED NAMES Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve names formed with the following labels from initial (i.e., i.e. other than renewal) registration within the TLD. If using self-allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable: ExampleLabels Reserved at All Levels. The ASCII label “EXAMPLE” following names shall be withheld from registration or allocated to Registry Operator reserved at the second level and at all other levels within the TLD at which Registry Operator offers registrations (such makes registrations: ICANN-related names: aso gnso icann internic ccnso IANA-related names: afrinic apnic arin example gtld-servers iab iana iana-servers iesg ietf irtf istf lacnic latnic rfc-editor ripe root-servers Additional Second-Level Reservations. In addition, the following names shall be reserved at the second level and all other levels are collectively referred to herein as, “level: All Levels”)single-character labels. Such All two-character labels shall be initially reserved. The reservation of a two- character label may not be activated in the DNS, and may not string shall be released for registration to any person the extent that the Registry Operator reaches agreement with the government and country-code manager, or entity other than Registry Operatorthe ISO 3166 maintenance agency, whichever appropriate. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, such withheld or allocated label shall be transferred as specified by ICANN. The Registry Operator may self-allocate and renew such name without use also propose release of an ICANN accredited registrar, which will not be considered Transactions for purposes these reservations based on its implementation of Section 6.1 of measures to avoid confusion with the Agreementcorresponding country codes.