Contractual and Operational Compliance Audits. (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and
Contractual and Operational Compliance Audits. ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15. Any audit conducted pursuant to Section 2.11(a) will be at ICANN’s expense, unless (i) Registry Operator (A) controls, is controlled by, is under common control or is otherwise Affiliated with, any ICANN accredited registrar or registrar reseller or any of their respective Affiliates, or (B) has subcontracted the provision of Registry Services to an ICANN accredited registrar or registrar reseller or any of their respective Affiliates, and, in either case of (A) or (B) above, the audit relates to Registry Operator’s compliance with Section 2.14, in which case Registry Operator shall reimburse ICANN for all reasonable costs and expenses associated with the portion of the audit related to Registry Operator’s compliance with Section 2.14, or (ii) the audit is related to a discrepancy in the fees paid by Registry Operator hereunder in excess of 5% in a given ...
Contractual and Operational Compliance Audits. (a) ICANN may from time to time (not to exceed once per calendar quarter) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article II of this Agreement and its covenants contained in Article III of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than five (5) business days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its covenants contained in Section 3.1.
Contractual and Operational Compliance Audits. (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit during regular business hours and in such a manner as to not unreasonably disrupt the operations of Registry Operator. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information reasonably necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than ten (10) calendar days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15.
Contractual and Operational Compliance Audits. (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess EBERO Service Provider’s compliance with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and (b) use commercially reasonable efforts to conduct such audit in such a manner as to not unreasonably disrupt EBERO Service Provider’s operations. As part of such audit and upon request by ICANN, EBERO Service Provider shall timely provide all responsive documents, data and any other information necessary to demonstrate EBERO Service Provider’s compliance with this Agreement. ICANN will treat any information obtained in connection with such audits that is appropriately marked or otherwise designated in writing as confidential (as required by Section 7.14) as EBERO Service Provider’s Confidential Information in accordance with Section 6.13.
Contractual and Operational Compliance Audits. ICANN may from time to time (not to exceed oncetwice per calendar quarteryear) conduct contractual compliance audits to assess compliance by Registry Operator with its covenants contained in Section 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN shall give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN. As part of such audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information necessary to demonstrate Registry Operator’s compliance with this Agreement. Upon no less than fivethree (53) calendarbusiness days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with its covenants contained in Section 2 of this Agreement. Any such audit will be at ICANN’s expense, unless such audit is related to a discrepancy in the fees paid by Registry Operator hereunder in excess of 5% to ICANN’s detriment. In the latter event, Registry Operator shall reimburse ICANN for all reasonable costs and expenses associated with such audit, which reimbursement will be paid together with the next Registry-Level Fee payment due following the date of transmittal of the cost statement for such audit. Notwithstanding the foregoing, if Registry Operator is found not to be in compliance with its covenants contained in Section 2 of this Agreement in two consecutive audits conducted pursuant to this Section 2.11, ICANN may increase the number of such audits to one per calendar quarter.
Contractual and Operational Compliance Audits. Final text will be posted on ICANN website; agreement reference to be replaced by hyperlink.
Contractual and Operational Compliance Audits. In addition to those audit rights set forth in Sections 2.3 and 2.6, ICANN may from time to time, at its expense, conduct contractual compliance audits to assess compliance by Registry Operator with the termsits covenants contained in Section 2 of this Agreement. As part of any contractual compliance audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information necessary to demonstrate Registry Operator's compliance with this Agreement. Upon no less than five days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance by Registry Operator with the termsits covenants contained in Section 2 of this Agreement. (Section 2.11 (Note -- for Community-Based TLDs Only) Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies.)
Contractual and Operational Compliance Audits. In addition to those audit rights set forth in Sections 2.3 and 2.6, ICANN may from time to time, at its expense, conduct contractual compliance audits to assess compliance with the terms of this Agreement. As part of any contractual compliance audit and upon request by ICANN, Registry Operator shall timely provide all responsive documents, data and any other information necessary to demonstrate Registry Operator's compliance with this Agreement. Upon no less than five days notice (unless otherwise agreed to by Registry Operator), ICANN may, as part of any contractual compliance audit, conduct site visits during regular business hours to assess compliance with the terms of this Agreement.
