PROVISION OF REGISTRATION DATA Sample Clauses

PROVISION OF REGISTRATION DATA. As part of the registration process, you are required to provide us with certain information and to update this information to keep it current, complete and accurate. This information includes the information contained in the Whois directory, including:
Sample 1Sample 2Sample 3See All (32)
AutoNDA by SimpleDocs
PROVISION OF REGISTRATION DATA. Over and above the obligations already described in this Agreement, you are required to provide us the UIN (Unique Identification Number), as issued by the .TRAVEL Registry to an entity that is eligible to hold a .travel domain name.
Sample 1Sample 2Sample 3See All (10)
PROVISION OF REGISTRATION DATA. (1) Provision of Registration Data: As part of the registration process, the Contractees are required to provide Directi with certain information and to update this information to keep it current, complete and accurate. This information includes but is not restricted to:
Sample 1Sample 2Sample 3See All (5)
PROVISION OF REGISTRATION DATA. As part of the registration process, you are required to provide us with certain information and to update this information to keep it current, complete and accurate. You must provide contact information, including name, email address, postal address and telephone number, for use in disputes relating to the Defensive Registration. You understand and agree that this contact information will be provided as part of the Whois record for the Defensive Registration. You further understand that the foregoing registration data may be transferred outside of the European Community, such as to the United States, and you expressly consent to such export. In addition to the information provided in subsection 1. above, Phase I Defensive Registrants must also provide:
Sample 1Sample 2See All (4)
PROVISION OF REGISTRATION DATA. As part of the registration process, you are required to provide us with certain information and to keep the information true, current, complete, and accurate at all times. The information includes the following: (A) your full name; (B) your postal address; (C) your e-mail address; (D) your voice telephone number; (E) your fax number (if applicable); (F) the name of an authorized person for contact purposes in the case of a registrant that is an organization, association, or corporation; (G) the IP addresses of the primary nameserver and any secondary nameserver for the domain name; (H) the corresponding names of the primary and secondary nameservers; (I) the full name, postal address, e-mail address, voice telephone number, and, when available, fax number of the administrative, technical, and billing contacts, and the name holder for the domain name; and (J) any remark concerning the domain name that should appear in the Whois directory.
Sample 1
PROVISION OF REGISTRATION DATA. As part of the registration process, you are required to provide us with certain information and to keep the information true, current, complete, and accurate at all times. The information includes the following: (A) your full name; (B) your postal address; (C) your e-mail address; (D) your voice telephone number; (E) your fax number (if applicable); (F) the name of an authorized person for contact purposes in the case of a registrant that is an organization, association, or corporation; (G) the IP addresses of the primary nameserver and any secondary nameserver for the domain name;
Sample 1
PROVISION OF REGISTRATION DATA a) Provision of Registration Data. As part of the registration process, you are required to Provide us with certain information and to update this information to keep it current, complete and accurate. This information includes (i) your full name, postal address, e-mail address, voice telephone number, and fax number if available; (ii) the name of an authorized person for contact purposes in the case of a registrant that is an organization, association, or corporation; (iii) the IP addresses of the primary nameserver and any secondary nameserver(s) for the domain name; (iv) the corresponding names of those nameservers;
Sample 1
AutoNDA by SimpleDocs
PROVISION OF REGISTRATION DATA. 3.1. Provision of Registration Data. As part of the registration process, you are required to provide us with certain information and to update this information to keep it current, complete and accurate. This information includes (i) your full name, postal address, e-mail address, voice telephone number, and fax number if available; (ii) the name of an authorized person for contact purposes in the case of a registrant that is an organization, association, or corporation; (iii) the IP addresses of the primary name server and any secondary name server(s) for the domain name; (iv) the corresponding names of those name servers; (v) the full name, postal address, e-mail address, voice telephone number, and fax number if available of the technical contact for the domain name; (vi) the full name, postal address, e-mail address, voice telephone number, and fax number if available of the administrative contact for the domain name; (vii) the name, postal address, e-mail address, voice telephone number, and fax number if available of the billing contact for the domain name; and (viii) any remark concerning the registered domain name that should appear in the WHOIS directory. You agree and understand that the foregoing registration data will be publicly available and accessible on the WHOIS directory as required by ICANN/Registry Policy and may be sold in bulk in accordance with the ICANN Agreement.
Sample 1
PROVISION OF REGISTRATION DATA. As part of the registration process, you are required to provide us with certain information and to update this information to keep it current, complete and accurate. This information includes: (i) the Registered Name; (ii) the names of the primary nameserver and secondary nameserver(s) for the Registered Name; (iii) your name, postal address, e-mail address, voice telephone number and (where available) fax number; (iv) the name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the Registered Name; (v) the name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the Registered Name; (vi) the name, postal address, e-mail address, voice telephone number, and fax number if available of the billing contact for the Registered Name; (vii) any remark concerning the registered domain name that should appear in the Whois directory; and (viii) any other data CNNIC, as the Registry, requires be submitted to it. You agree and understand that the foregoing registration data will be publicly available and accessible on the Whois directory pursuant to the CNNC Policy. Any information collected by us concerning an identified or identifiable natural person ("Personal Data") will be used in connection with the registration of your domain name(s) and for the purposes of this Agreement and as required or permitted by the CNNIC.
Sample 1

Related to PROVISION OF REGISTRATION DATA

  • 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.

  • Termination of Registration Rights The right of any Holder to request registration or inclusion of Registrable Securities in any registration pursuant to Subsections 2.1 or 2.2 shall terminate upon the earliest to occur of:

  • Expenses of Registration All expenses incurred in connection with registrations, filings or qualifications pursuant to Sections 2 and 3, including, without limitation, all registration, listing and qualifications fees, printers, legal and accounting fees shall be paid by the Company.

  • Delay of Registration No Holder shall have any right to obtain or seek an injunction restraining or otherwise delaying any registration pursuant to this Agreement as the result of any controversy that might arise with respect to the interpretation or implementation of this Section 2.

  • Assignment of Registration Rights The rights under this Agreement shall be automatically assignable by the Investors to any transferee of all or any portion of such Investor’s Registrable Securities if: (i) the Investor agrees in writing with the transferee or assignee to assign such rights, and a copy of such agreement is furnished to the Company within a reasonable time after such assignment; (ii) the Company is, within a reasonable time after such transfer or assignment, furnished with written notice of (a) the name and address of such transferee or assignee, and (b) the securities with respect to which such registration rights are being transferred or assigned; (iii) immediately following such transfer or assignment the further disposition of such securities by the transferee or assignee is restricted under the 1933 Act or applicable state securities laws; (iv) at or before the time the Company receives the written notice contemplated by clause (ii) of this sentence the transferee or assignee agrees in writing with the Company to be bound by all of the provisions contained herein; and (v) such transfer shall have been made in accordance with the applicable requirements of the Securities Purchase Agreement.

  • Bulk Registration Data Access to Icann 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.

  • 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.”]

  • 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.

  • 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.

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