Final Check by Registry Operator Sample Clauses

Final Check by Registry Operator. The Registrar acknowledges that even if the Registrar has approved a Domain Name Application, that Domain Name Application may still be rejected by the Registry Operator in performing the final integrity checks.
AutoNDA by SimpleDocs
Final Check by Registry Operator. The Registrar acknowledges that even if it has approved an Approved Application, the Approved Application may still be rejected by the Registry Operator following its completion of final security and integrity checks.

Related to Final Check by Registry Operator

  • Termination by Registry Operator (a) Registry Operator may terminate this Agreement upon notice to ICANN if (i) ICANN fails to cure any fundamental and material breach of ICANN’s covenants set forth in Article 3, within thirty (30) calendar days after Registry Operator gives ICANN notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that ICANN is in fundamental and material breach of such covenants, and (iii) ICANN fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (b) Registry Operator may terminate this Agreement for any reason upon one hundred eighty (180) calendar day advance notice to ICANN.

  • Registry Operator has (i) ceased to conduct its business in the ordinary course; or (ii) filed for bankruptcy, become insolvent or anything analogous to any of the foregoing under the laws of any jurisdiction anywhere in the world; or

  • Emergency Escalation initiated by Registrars Registry Operator will maintain an emergency operations department prepared to handle emergency requests from registrars. In the event that a registrar is unable to conduct EPP transactions with the registry for the TLD because of a fault with the Registry Service and is unable to either contact (through ICANN mandated methods of communication) the Registry Operator, or the Registry Operator is unable or unwilling to address the fault, the registrar may initiate an emergency escalation to the emergency operations department of ICANN. ICANN then may initiate an emergency escalation with the Registry Operator as explained above.

  • COVENANTS OF REGISTRY OPERATOR Registry Operator covenants and agrees with ICANN as follows:

  • Maintenance of Offices, Agencies and Transfer Books by the Depositary; Registrar Upon execution of this Deposit Agreement, the Depositary shall maintain at the Depositary’s Office facilities for the execution and delivery, registration and registration of transfer, surrender and exchange of Receipts, and at the offices of the Depositary’s Agents, if any, facilities for the delivery, registration of transfer, surrender and exchange of Receipts, all in accordance with the provisions of this Deposit Agreement. The Depositary shall keep books at the Depositary’s Office for the registration and registration of transfer of Receipts, which books during normal business hours shall be open for inspection by the record holders of Receipts; provided that any such holder requesting to exercise such right shall certify to the Depositary that such inspection shall be for a proper purpose reasonably related to such person’s interest as an owner of Depositary Shares evidenced by the Receipts. The Depositary may close such books, at any time or from time to time, when deemed expedient by it in connection with the performance of its duties hereunder. The Depositary may, with the approval of the Company, appoint a Registrar for registration of the Receipts or the Depositary Shares evidenced thereby. If the Receipts or the Depositary Shares evidenced thereby or the Stock represented by such Depositary Shares shall be listed on one or more national securities exchanges, the Depositary will appoint a Registrar (acceptable to the Company) for registration of such Receipts or Depositary Shares in accordance with any requirements of such exchange. Such Registrar (which may be the Depositary if so permitted by the requirements of any such exchange) may be removed and a substitute registrar appointed by the Depositary upon the request or with the approval of the Company. If the Receipts, such Depositary Shares or such Stock are listed on one or more other stock exchanges, the Depositary will, at the request and at the expense of the Company, arrange such facilities for the delivery, registration, registration of transfer, surrender and exchange of such Receipts, such Depositary Shares or such Stock as may be required by law or applicable securities exchange regulation. The Depositary may from time to time appoint Depositary’s Agents to act in any respect for the Depositary for the purposes of this Deposit Agreement and may at any time appoint additional Depositary’s Agents and vary or terminate the appointment of such Depositary’s Agents. The Depositary will notify the Company of any such action.

  • Registry Lock Registry Operator may offer the Registry Lock service, which is a registry service that allows an authorized representative from the sponsoring Registrar, request the activation or deactivation of any of the following EPP statuses: serverUpdateProhibited, serverDeleteProhibited and⁄or serverTransferProhibited.

  • Appointment of Subcustodians; Use of Securities Depositories (a) Bank is authorized under this Agreement to act through and hold Customer's Global Assets with subcustodians, being at the date of this Agreement the entities listed in Schedule 1 and/or such other entities as Bank may appoint as subcustodians ("Subcustodians"). At the request of Customer, Bank may, but need not, add to Schedule 1 an Eligible Foreign Custodian where Bank has not acted as Foreign Custody Manager with respect to the selection thereof. Bank shall notify Customer in the event that it elects to add any such entity. Bank shall use reasonable care, prudence and diligence in the selection and continued appointment of such Subcustodians. In addition, Bank and each Subcustodian may deposit Global Assets with, and hold Global Assets in, any securities depository, settlement system, dematerialized book entry system or similar system (together a "Securities Depository") on such terms as such systems customarily operate and Customer shall provide Bank with such documentation or acknowledgements that Bank may require to hold the Global Assets in such systems. (b) Any agreement Bank enters into with a Subcustodian for holding Bank's customers' assets shall provide that: (i) such assets shall not be subject to any right, charge, security interest, lien or claim of any kind in favor of such Subcustodian or its creditors, except a claim of payment for their safe custody or administration or, in the case of cash deposits, except for liens or rights in favor of creditors of the Subcustodian arising under bankruptcy, insolvency or similar laws; (ii) beneficial ownership of such assets shall be freely transferable without the payment of money or value other than for safe custody or administration; (iii) adequate records will be maintained identifying the assets as belonging to Customer or as being held by a third party for the benefit of Customer; (iv) Customer and Customer's independent public accountants will be given reasonable access to those records or confirmation of the contents of those records; and (v) Customer will receive periodic reports with respect to the safekeeping of Customer's assets, including, but not limited to, notification of any transfer to or from Customer's account or a third party account containing assets held for the benefit of Customer. Where a Subcustodian deposits Securities with a Securities Depository, Bank shall cause the Subcustodian to identify on its records as belonging to Bank, as agent, the Securities shown on the Subcustodian's account at such Securities Depository. The foregoing shall not apply to the extent of any special agreement or arrangement made by Customer with any particular Subcustodian. (c) Bank shall have no responsibility for any act or omission by (or the insolvency of) any Securities Depository. In the event Customer incurs a loss due to the negligence, bad faith, willful misconduct, or insolvency of a Securities Depository, Bank shall make reasonable endeavors to seek recovery from the Securities Depository. (d) The term Subcustodian as used herein shall mean the following: (i) a "U.S. Bank" as such term is defined in rule 17f-5; and (ii) an "Eligible Foreign Custodian" as such term is defined in rule 17f-5 and any other entity that shall have been so qualified by exemptive order, rule or other appropriate action of the SEC. (iii) For purposes of clarity, it is agreed that as used in Section 5.2(a), the term Subcustodian shall not include any Eligible Foreign Custodian as to which Bank has not acted as Foreign Custody Manager. (e) The term 'securities depository' as used herein when referring to a securities depository located outside the U.S. shall mean an "Eligible Securities Depository" as defined in rule 17f-7, or that has otherwise been made exempt pursuant to an SEC exemptive order. (f) The term 'securities depository' as used herein when referring to a securities depository located in the U.S. shall mean a "Securities Depository" as defined in rule 17f-4.

  • Reservations for Registry Operations The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator may activate in the DNS at All Levels up to one hundred (100) names (plus their IDN variants, where applicable) necessary for the operation or the promotion of the TLD. Registry Operator must act as the Registered Name Holder of such names as that term is defined in the then-current ICANN Registrar Accreditation Agreement (RAA). These activations will be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator must either (i) register such names through an ICANN-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to ICANN for compliance with ICANN Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder). At Registry Operator’s discretion and in compliance with all other terms of this Agreement, such names may be released for registration to another person or entity. Registry Operator may withhold from registration or allocate to Registry Operator names (including their IDN variants, where applicable) at All Levels in accordance with Section 2.6 of the Agreement. Such names may not be activated in the DNS, but may be released for registration to another person or entity at Registry Operator’s discretion. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Upon ICANN’s request, Registry Operator shall provide a listing of all names withheld or allocated to Registry Operator pursuant to Section 2.6 of the Agreement. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]

  • REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!