Common use of ICANN Access Clause in Contracts

ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. .com Registry Agreement Appendix 4A Format and Content for Registry Operator Monthly Reporting (Effective as of June 20, 2020) Registry Operator shall provide the following monthly reports, each as described in greater detail below, for the TLD: (1) the Service Level Agreement Performance Report; (2) the Per-Registrar Transactions Report; and (3) the Registry Functions Activity Report. The Service Level Agreement Performance Reports shall be submitted to ICANN via email to <registry- xxxxxxx@xxxxx.xxx>. The Per-Registrar Transactions Reports and the Registry Functions Activity Reports shall be submitted to ICANN using the API described in draft-xxxxxx-icann- registry-interfaces, see xxxxx://xxxxx.xxxx.xxx/html/draft-xxxxxx-icann-registry-interfaces (the “Registry Interfaces Specification”). If not already an RFC, Registry Operator will use the most recent draft version of the Registry Interfaces Specification available as of June 20, 2020. Registry Operator may at its election use newer versions of the Registry Interfaces Specification after June 20, 2020. Once the Registry Interfaces Specification is published as an RFC, Registry Operator will implement the RFC version no later than one hundred eighty (180) calendar days after it is published. ICANN may request in the future that the reports be delivered by other means and using other formats. For each of the reports, ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Appendix 4A, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. .com .NET Registry Agreement Appendix 4A 4 Format and Content for Registry Operator Monthly Reporting (Effective as of June 20, 2020) Registry Operator shall provide the following monthly reports, each as described in greater detail belowin this Appendix, for the TLD: (1) the Service Level Agreement Performance Report; (2) the Per-Registrar Transactions Report; and (3) the Registry Functions Activity Report. The Service Level Agreement Performance Reports shall be submitted to ICANN via email to <registry- xxxxxxx@xxxxx.xxxxxxxxxxx-xxxxxxx@xxxxx.xxx>. The Per-Per- Registrar Transactions Reports and the Registry Functions Activity Reports shall be submitted to ICANN using the API described in draft-xxxxxx-icann- registryicann-registry- interfaces, see xxxxx://xxxxx.xxxx.xxx/html/draft-xxxxxx-icann-registry-interfaces xxxxx://xxxxxxxxxxx.xxxx.xxx/doc/draft-xxxxxx-icann-registry-interfaces (the “Registry Interfaces Specification”). If not already an RFC, Registry Operator will use the most recent draft version of the Registry Interfaces Specification available as of June 20July 1, 20202023. Registry Operator may at its election use newer versions of the Registry Interfaces Specification after June 20July 1, 20202023. Once the Registry Interfaces Specification is published as an RFC, Registry Operator will implement the RFC version no later than one hundred eighty (180) calendar days after it is published. ICANN may request in the future that the reports be delivered by other means and using other formats. For each of the reports, ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Appendix 4A4, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. .com .NET Registry Agreement Appendix 4A 4 Format and Content for Registry Operator Monthly Reporting (Effective as of June 20, 2020) Registry Operator shall provide the following monthly reports, each as described in greater detail belowin this Appendix, for the TLD: (1) the Service Level Agreement Performance Report; (2) the Per-Registrar Transactions Report; and (3) the Registry Functions Activity Report. The Service Level Agreement Performance Reports shall be submitted to ICANN via email to <registry- xxxxxxx@xxxxx.xxxxxxxxxxx-xxxxxxx@xxxxx.xxx>. The Per-Registrar Transactions Reports and the Registry Functions Activity Reports shall be submitted to ICANN using the API described in draft-xxxxxx-icann- icann-registry-interfaces, see xxxxx://xxxxx.xxxx.xxx/html/draft-xxxxxx-icann-registry-interfaces xxxxx://xxxxxxxxxxx.xxxx.xxx/doc/draft-xxxxxx-icann-registry-interfaces (the “Registry Interfaces Specification”). If not already an RFC, Registry Operator will use the most recent draft version of the Registry Interfaces Specification available as of June 20July 1, 20202023. Registry Operator may at its election use newer versions of the Registry Interfaces Specification after June 20July 1, 20202023. Once the Registry Interfaces Specification is published as an RFC, Registry Operator will implement the RFC version no later than one hundred eighty (180) calendar days after it is published. ICANN may request in the future that the reports be delivered by other means and using other formats. For each of the reports, ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Appendix 4A4, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from specifyfrom time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. .com Registry Agreement Appendix 4A 4 Format and Content for Registry Operator Monthly Reporting (Effective as of June 20, 2020) Registry Operator shall provide the following monthly reports, each as described in greater detail below, for the TLD: (1) the Service Level Agreement Performance Report; (2) the Per-Registrar Transactions Report; and (3) the Registry Functions Activity Report. The Service Level Agreement Performance Reports shall be submitted to ICANN via email to <registry- xxxxxxx@xxxxx.xxx>. The Per-Registrar Transactions Reports and the Registry Functions Activity Reports shall be submitted to ICANN using the API described in draft-xxxxxx-icann- registry-interfaces, see xxxxx://xxxxx.xxxx.xxx/html/draft-xxxxxx-icann-registry-interfaces xxxxx://xxxxxxxxxxx.xxxx.xxx/doc/draft-xxxxxx-icann-registry-interfaces (the “Registry Interfaces Specification”). If not already an RFC, Registry Operator will use the most recent draft version of the Registry Interfaces Specification available as of June 20December 1, 20202024. Registry Operator may at its election use newer versions of the Registry Interfaces Specification after June 20December 1, 20202024. Once the Registry Interfaces Specification is published as an RFC, Registry Operator will implement the RFC version no later than one hundred eighty (180) calendar days after it is published. ICANN may request in the future that the reports be delivered by other means and using other formats. For each of the reports, ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Appendix 4A4, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from specifyfrom time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. .com Registry Agreement Appendix 4A 4 Format and Content for Registry Operator Monthly Reporting (Effective as of June 20, 2020) Registry Operator shall provide the following monthly reports, each as described in greater detail below, for the TLD: (1) the Service Level Agreement Performance Report; (2) the Per-Registrar Transactions Report; and (3) the Registry Functions Activity Report. The Service Level Agreement Performance Reports shall be submitted to ICANN via email to <registry- xxxxxxx@xxxxx.xxx>. The Per-Registrar Transactions Reports and the Registry Functions Activity Reports shall be submitted to ICANN using the API described in draft-xxxxxx-icann- registry-interfaces, see xxxxx://xxxxx.xxxx.xxx/html/draft-xxxxxx-icann-registry-interfaces xxxxx://xxxxxxxxxxxxxxxx.xxxx.xxx/htmldoc/draft-xxxxxx-icann-registry- interfaces (the “Registry Interfaces Specification”). If not already an RFC, Registry Operator will use the most recent draft version of the Registry Interfaces Specification available as of June 20, 20202020.December 1, 2024. Registry Operator may at its election use newer versions of the Registry Interfaces Specification after June 20, 20202020.December 1, 2024. Once the Registry Interfaces Specification is published as an RFC, Registry Operator will implement the RFC version no later than one hundred eighty (180) calendar days after it is published. ICANN may request in the future that the reports be delivered by other means and using other formats. For each of the reports, ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Appendix 4A4A4, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

ICANN Access. Registry Operator shall provide bulk access to the zone files for the TLD to ICANN or its designee on a continuous basis in the manner ICANN may reasonably specify from time to time. Access will be provided at least daily. Zone files will include SRS data committed as close as possible to 00:00:00 UTC. .com Registry Agreement Appendix 4A Format and Content for Registry Operator Monthly Reporting (Effective as of June 20, 2020) Registry Operator shall provide the following monthly reports, each as described in greater detail below, for the TLD: (1) the Service Level Agreement Performance Report; (2) the Per-Registrar Transactions Report; and (3) the Registry Functions Activity Report. The Service Level Agreement Performance Reports shall be submitted to ICANN via email to <registry- xxxxxxx@xxxxx.xxxxxxxxxxx-xxxxxxx@xxxxx.xxx>. The Per-Registrar Transactions Reports and the Registry Functions Activity Reports shall be submitted to ICANN using the API described in draft-xxxxxx-icann- icann-registry-interfaces, see xxxxx://xxxxx.xxxx.xxx/html/draft-xxxxxx-icann-registry-interfaces (the “Registry Interfaces Specification”). If not already an RFC, Registry Operator will use the most recent draft version of the Registry Interfaces Specification available as of June 20, 2020. Registry Operator may at its election use newer versions of the Registry Interfaces Specification after June 20, 2020. Once the Registry Interfaces Specification is published as an RFC, Registry Operator will implement the RFC version no later than one hundred eighty (180) calendar days after it is published. ICANN may request in the future that the reports be delivered by other means and using other formats. For each of the reports, ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Appendix 4A, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).