Registration and administration of domain names Sample Clauses

Registration and administration of domain names. The Registry undertakes to register and administer domain names for the benefit of the holder designated by the Registrar according to the provisions of the OID and the Registry’s GTC, unless this Agreement contains any provisions to the contrary.
AutoNDA by SimpleDocs

Related to Registration and administration of domain names

  • Registration of Agreement The registration of License agreements should be done within 30 days of signing of agreement, the licensee/ lessee (registration fees, stamp duty etc to be fully borne by the licensee/lessee) and the duly registered documents to be submitted to Maha-Metro for records. Any amendment in the contract agreement, if required to be registered, shall also be registered within 30 days from the date of amendment and duly registered documents shall be submitted to Maha-Metro for record. In case the registration of the license/lease agreement /amendment is not done within the 30 days of signing of license/lease agreement/ amendment, it shall be treated as “Material Breach of Contract”. The Licensee will be given 30 days time to cure the defaults In case Licensee fail to remedify the default to the satisfaction of the Maha-Metro within the cure period, Maha-Metro may terminate the License agreement after expiry of cure period duly forfeiting the security deposit/ any other amount paid by Licensee.

  • Domain Name Registration If Customer submits a Service Order(s) for domain name registration services, the following terms shall also apply:

  • Registration Information Customer shall be responsible for the accuracy and legality of all account, Agent, and registration information (including without limitation Customer’s legal name and payment information, Customer/Agent contact information, and any personal data included therein) (“Registration Information”) and the means of its acquisition.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).

  • Registration Data Upon placing an order for Pilot Voice, and at subsequent times as requested by Pilot, Customer agrees to provide Pilot with its (i) true, accurate, current, and complete business name, (ii) physical addresses where Voice Service will be used, (iii) 911 registered address for each applicable endpoint, (iv) a designated Account Administrator, and (v) user email addresses, phone numbers, and any other requested data which may be necessary to administer its Voice Service account (the “Account”) (collectively, “Registration Data”). Customer represents and warrants that the information it provides is accurate, current, and complete, and agrees to promptly update any of the information if it changes. If Customer provides Registration Data that is false, inaccurate, not current, incomplete, fraudulent, or otherwise unlawful, Pilot has the right, in its sole discretion, to suspend or terminate the Voice Services and refuse any and all current or future use of all Voice Services by Customer, its business(es), affiliates and all users of its Account. Upon provision of all Registration Data and acceptance of Customer’s Service Order, Pilot may provide Customer’s designated Account Administrator and other Pilot Voice users with, as applicable, administrator or user web portal logins and other Account information. Customer is solely liable for any transactions or activities by it or any third- party that occurs on its Account. Customer shall immediately notify Pilot of any unauthorized use of its Account or if any other breach of security has occurred. In no event shall Pilot be liable for any unauthorized, third-party use of your Account.

  • Registration of Contractor All contractors and subcontractors must comply with the requirements of Labor Code Section 1771.1(a), pertaining to registration of contractors pursuant to Section 1725.5. Bids cannot be accepted from unregistered contractors except as provided in Section 1771.1. This project is subject to compliance monitoring and enforcement by the Department of Industrial Relations. After award of the contract, Contractor and each Subcontractor shall furnish electronic payroll records directly to the Labor Commissioner in the manner specified in Labor Code Section 1771.4.

  • REGISTRATION OF EZ2BID 3.1 E-bidders will log in into ESZAM AUCTIONEER SDN BHD secured website. E-bidders shall provide true, current and accurate information to register as a user.

  • Registration of Contractors Contractor and all subcontractors must comply with the requirements of labor code section 1771.1(a), pertaining to registration of contractors pursuant to section 1725.5. Registration and all related requirements of those sections must be maintained throughout the performance of the Contract.

  • Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-­‐to-­‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

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