Compliance with Operational Requirements Sample Clauses

Compliance with Operational Requirements. Registrar agrees to comply with, and shall include in its registration agreement with each Registered Name Holder as appropriate, operational standards, policies, procedures, and practices for the Registry TLD established from time to time by VNDS in a non-arbitrary manner and applicable to all registrars (“Operational Requirements”), including affiliates of VNDS, and consistent with VNDS's Registry Agreement with ICANN, as applicable, upon VNDS's notification to Registrar of the establishment of those terms and conditions.
Sample 1Sample 2Sample 3See All (20)
AutoNDA by SimpleDocs
Compliance with Operational Requirements. Registrar shall comply with each of the following requirements, and further shall include in its registration agreement with each Registered Name Holder, as applicable, an obligation for such Registered Name Holder to comply with each of the following requirements:
Sample 1Sample 2Sample 3See All (17)
Compliance with Operational Requirements. The Registrar shall comply with each of the following requirements, as may be in effect from time to time, and, further, shall include in its registration agreement with each Registrant an obligation for such Registrant to comply with each of the following requirements:
Sample 1Sample 2
Compliance with Operational Requirements. The Registrar shall comply with each of the following requirements, as may be in effect from time to time, and, further shall include in its registration agreement with each Registrant an obligation for such Registrant to comply with operational standards, policies, procedures, and practices for the SLD established from time to time by the Registry in a non-arbitrary manner and applicable to all Registrars (Operational Requirements), including affiliates of the Registry, as applicable, upon the Registry’s notification to the Registrar of the establishment of those terms and conditions upon 90 (ninety) days’ notice, except in circumstances where a regulatory body or law enforcement mandates registries to meet shorter deadlines, in which case the Registrar will work with the Registry to agree on an appropriate date to implement such changes.
Sample 1Sample 2
Compliance with Operational Requirements. Registrar shall comply with each of the following requirements, and further shall include in its registration agreement with each Registered Name Holder, as applicable, an obligation for such Registered Name Holder to comply with each of the following requirements: ICANN standards, policies, procedures, and practices for which Verisign has monitoring responsibility in accordance with the Registry Agreement or other arrangement with ICANN; and Operational standards, policies, procedures, and practices for the Registry TLD established from time to time by Verisign in a non-arbitrary manner and applicable to all registrars ("Operational Requirements"), including affiliates of Verisign, and consistent with Verisign's Registry Agreement with ICANN, as applicable, upon Verisign's notification to Registrar of the establishment of those terms and conditions.
Sample 1
Compliance with Operational Requirements. The Borrower must have complied with all the Bank's operational requirements to the satisfaction of the Bank.
Sample 1
Compliance with Operational Requirements. The Customer must have complied with all the Bank’s operational requirements to the satisfaction of the Bank.
Sample 1
AutoNDA by SimpleDocs
Compliance with Operational Requirements. Registrar shall comply with each of the following requirements, and further shall include in its registration agreement with each Registered Name Holder, as applicable, an obligation for such Registered Name Holder to comply with each of the following requirements: ICANN standards, policies, procedures, and practices for which Verisign has monitoring responsibility in accordance with the Registry Agreement or other arrangement with ICANN; and Operational standards, policies, procedures, and practices for the Registry TLD established from time to time by Verisign in a non- arbitrary manner and applicable to all registrars ("Operational Requirements"), including affiliates of Verisign, and consistent with Verisign's Registry Agreement with ICANN, as applicable, upon Verisign's notification to Registrar of the establishment of those terms and conditions. Resolution of Technical Problems or Breach of Agreement. Registrar agrees to employ necessary employees, contractors, or agents with sufficient technical training and experience to respond to and fix all technical problems concerning the use of the Supported Protocol, the APIs and the systems of Verisign in conjunction with Registrar's systems. Registrar agrees that in the event of significant degradation of the System or other emergency, or upon Registrar's violation of Operational Requirements or breach of this Agreement, Verisign may, in its sole discretion, temporarily suspend or restrict access to the System. Such temporary suspensions or restrictions shall be applied in a nonarbitrary manner and shall apply fairly to any registrar similarly situated. Prohibited Domain Name Registrations. In addition to complying with ICANN standards, policies, procedures, and practices limiting domain names that may be registered, Registrar agrees to comply with applicable statutes and regulations limiting the domain names that may be registered. ICANN Requirements. Verisign's obligations hereunder are subject to modification at any time as the result of ICANN-mandated requirements and consensus policies. Notwithstanding anything in this Agreement to the contrary, Registrar shall comply with any such ICANN requirements in accordance with the timeline defined by ICANN.
Sample 1

Related to Compliance with Operational Requirements

  • Compliance with OFAC None of the Company and its Subsidiaries or, to the Company’s knowledge, any director, officer, agent, employee or affiliate of the Company and its Subsidiaries or any other person acting on behalf of the Company and its Subsidiaries, is currently subject to any U.S. sanctions administered by the Office of Foreign Assets Control of the U.S. Department of the Treasury (“OFAC”), and the Company will not, directly or indirectly, use the proceeds of the Offering hereunder, or lend, contribute or otherwise make available such proceeds to any subsidiary, joint venture partner or other person or entity, for the purpose of financing the activities of any person currently subject to any U.S. sanctions administered by OFAC.

  • Compliance with Environmental Laws Except as otherwise described in the Prospectus, and except as would not, individually or in the aggregate, result in a Material Adverse Change (i) neither the Company nor any of its subsidiaries is in violation of any federal, state, local or foreign law or regulation relating to pollution or protection of human health or the environment (including, without limitation, ambient air, surface water, groundwater, land surface or subsurface strata) or wildlife, including without limitation, laws and regulations relating to emissions, discharges, releases or threatened releases of chemicals, pollutants, contaminants, wastes, toxic substances, hazardous substances, petroleum and petroleum products (collectively, “Materials of Environmental Concern”), or otherwise relating to the manufacture, processing, distribution, use, treatment, storage, disposal, transport or handling of Materials of Environmental Concern (collectively, “Environmental Laws”), which violation includes, but is not limited to, noncompliance with any permits or other governmental authorizations required for the operation of the business of the Company or its subsidiaries under applicable Environmental Laws, or noncompliance with the terms and conditions thereof, nor has the Company or any of its subsidiaries received any written communication, whether from a governmental authority, citizens group, employee or otherwise, that alleges that the Company or any of its subsidiaries is in violation of any Environmental Law; (ii) there is no claim, action or cause of action filed with a court or governmental authority, no investigation with respect to which the Company has received written notice, and no written notice by any person or entity alleging potential liability for investigatory costs, cleanup costs, governmental responses costs, natural resources damages, property damages, personal injuries, attorneys’ fees or penalties arising out of, based on or resulting from the presence, or release into the environment, of any Material of Environmental Concern at any location owned, leased or operated by the Company or any of its subsidiaries, now or in the past (collectively, “Environmental Claims”), pending or, to the Company’s knowledge, threatened against the Company or any of its subsidiaries or any person or entity whose liability for any Environmental Claim the Company or any of its subsidiaries has retained or assumed either contractually or by operation of law; and (iii) to the best of the Company’s knowledge, there are no past or present actions, activities, circumstances, conditions, events or incidents, including, without limitation, the release, emission, discharge, presence or disposal of any Material of Environmental Concern, that reasonably could result in a violation of any Environmental Law or form the basis of a potential Environmental Claim against the Company or any of its subsidiaries or against any person or entity whose liability for any Environmental Claim the Company or any of its subsidiaries has retained or assumed either contractually or by operation of law.

Time is Money Join Law Insider Premium to draft better contracts faster.