Periodic Access to Thin Registration Data Clause Samples

POPULAR SAMPLE Copied 1 times
Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of the Registry Services, analyze the operational stability of the DNS and facilitate compliance checks and audits of accredited registrars, Registry Operator will provide ICANN on a daily basis with up-to-date registration data as specified in this Section 5.1. Data will include data committed as of 00:00:00 UTC on the previous day. On an annual basis, ICANN will publish a summary of the research projects that utilized this data in the preceding year, along with a listing of any organizations the raw data was shared with to conduct the research. 5.1.1 Contents. Registry Operator will provide the following data for all registered domain names: domain name, domain name repository object id (roid), Registrar ID (IANA ID), statuses, last updated date, creation date, expiration date, and name server names. For sponsoring registrars, Registry Operator will provide: registrar name, registrar ID (IANA ID), hostname of registrar WHOIS server (which shall continue to be provided after January 28, 2025, if provided by registrar) and URL of registrar. Registry Operator shall not provide any additional data elements.
View SourceView Similar (6)
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.
View SourceView Similar (2k)
Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services, analyze the operational stability of the DNS, and 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. On an annual basis, ICANN will publish a summary of the research projects that utilized this data in the preceding year, along with a listing of any organizations the raw data was shared with to conduct the research. 3.1.1 Contents. Registry Operator will provide the following data for all registered domain names: domain name, domain name repository object id (roid), Registrar ID (IANA ID), statuses, last updated date, creation date, expiration date, and name server names. For sponsoring registrars Registry Operator will provide: registrar name, registrar id (IANA ID), hostname of registrar WHOIS server (this data element may be omitted after the WHOIS Services Sunset Date), and URL of registrar. Registry Operator shall not provide any additional data elements.
View SourceView Similar (11)
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. 3.1.1. Contents. Registry Operator will provide, at least, the following data for all registered domain names: domain name, domain name repository object id (roid), registrar id (IANA ID), statuses, last updated date, creation date, expiration date, and name server names. For sponsoring registrars, at least, it will provide: registrar name, registrar repository object id (roid), hostname of registrar Whois server, and URL of registrar.
View SourceView Similar (5)
Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services, analyze the operational stability of the DNS, and as well as tofacilitate 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. On an annual basis, ICANN will publish a summary of the research projects that utilized this data in the preceding year, along with a listing of any organizations the raw data was shared with to conduct the research.
View SourceView Similar (5)
Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of the Registry Services, analyze the operational stability of the DNS and facilitate compliance checks and audits of accredited registrars, Registry Operator will provide ICANN on a daily basis with up-to-date registration data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous day. 2.1.1 Contents. Registry Operator must only provide the following data for all registered domain names: domain name, domain name repository object id (roid), Registrar ID (IANA ID), statuses, last updated date, creation date, expiration date, and name server names. For sponsoring registrars, Registry Operator must only provide: registrar name, registrar ID (IANA ID), hostname of registrar Whois server, and URL of registrar.
View SourceView Similar (4)
Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services, analyze the operational stability of the DNS, and as well as tofacilitate 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. 3.1.1 Contents. Registry Operator will provide, at least, the following data for all registered domain names: domain name, domain name repository object id (roid), Registrar ID (IANA ID), statuses, last updated date, creation date, expiration date, and name server names. For sponsoring registrars, at least, it Registry Operator will provide: registrar name, registrar id (IANA ID), hostname of registrar Whois serverWHOIS server (this data element may be omitted after the WHOIS Services Sunset Date), and URL of registrar. Registry Operator shall not provide any additional data elements.
View Source
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. 3.1.1. Contents. Registry Operator will provide the following data for all registered domain names: domain name, registrar id (IANA ID), statuses, last updated date, creation date, expiration date, and name server names. For sponsoring registrars, it will provide: registrar name, hostname of registrar Whois server, and URL of registrar.
View Source
Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of the Registry Services, analyze the operational stability of the DNS and facilitate compliance checks and audits of accredited registrars, Registry Operator will provide ICANN on a daily basis with up-to-date registration data as specified ▇▇▇▇▇.▇▇ this Section 5.1. Data will include data committed as of 00:00:00 UTC on the day previous day. On an annual basis, ICANN will publish a summary of the research projects that utilized this data in the preceding year, along with a listing of any organizations the raw data was shared with to conduct the research.
View Source

Related to Periodic Access to Thin Registration Data

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

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

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Delay of Registration; Furnishing Information (a) No Holder shall have any right to obtain or seek an injunction restraining or otherwise delaying any such registration as the result of any controversy that might arise with respect to the interpretation or implementation of this Section 2. (b) It shall be a condition precedent to the obligations of the Company to take any action pursuant to Section 2.2, 2.3 or 2.4 that the selling Holders shall furnish to the Company such information regarding themselves, the Registrable Securities held by them and the intended method of disposition of such securities as shall be required to effect the registration of their Registrable Securities. (c) The Company shall have no obligation with respect to any registration requested pursuant to Section 2.2 or Section 2.4 if the number of shares or the anticipated aggregate offering price of the Registrable Securities to be included in the registration does not equal or exceed the number of shares or the anticipated aggregate offering price required to originally trigger the Company’s obligation to initiate such registration as specified in Section 2.2 or Section 2.4, whichever is applicable.

  • Suspension of Sales; Adverse Disclosure; Restrictions on Registration Rights 3.4.1 Upon receipt of written notice from the Company that a Registration Statement or Prospectus contains a Misstatement, each of the Holders shall forthwith discontinue disposition of Registrable Securities until he, she or it has received copies of a supplemented or amended Prospectus correcting the Misstatement (it being understood that the Company hereby covenants to prepare and file such supplement or amendment as soon as practicable after the time of such notice), or until he, she or it is advised in writing by the Company that the use of the Prospectus may be resumed. 3.4.2 If the filing, initial effectiveness or continued use of a Registration Statement in respect of any Registration at any time would (i) require the Company to make an Adverse Disclosure, (ii) require the inclusion in such Registration Statement of financial statements that are unavailable to the Company for reasons beyond the Company’s control or (iii) in the good faith judgment of the majority of the Board, be seriously detrimental to the Company, and the majority of the Board concludes as a result that it is essential to defer such filing, initial effectiveness or continued use at such time, the Company may, upon giving prompt written notice of such action to the Holders (which notice shall not specify the nature of the event giving rise to such delay or suspension), delay the filing or initial effectiveness of, or suspend use of, such Registration Statement for the shortest period of time determined in good faith by the Company to be necessary for such purpose. In the event the Company exercises its rights under this Section 3.4.2, the Holders agree to suspend, immediately upon their receipt of the notice referred to above, their use of the Prospectus relating to any Registration in connection with any sale or offer to sell Registrable Securities until such Holder receives written notice from the Company that such sales or offers of Registrable Securities may be resumed, and in each case maintain the confidentiality of such notice and its contents. 3.4.3 Subject to Section 3.4.4, if (i) during the period starting with the date 60 days prior to the Company’s good faith estimate of the date of the filing of, and ending on a date 120 days after the effective date of, a Company-initiated Registration, and provided that the Company continues to actively employ, in good faith, all commercially reasonable efforts to maintain the effectiveness of the applicable Shelf Registration, or (ii) if, pursuant to Section 2.1.4, Holders have requested an Underwritten Shelf Takedown and the Company and such Holders are unable to obtain the commitment of underwriters to firmly underwrite such offering, then, in each case, the Company may, upon giving prompt written notice of such action to the Holders, delay any other registered offering pursuant to Section 2.1.4. 3.4.4 The right to delay or suspend any filing, initial effectiveness or continued use of a Registration Statement pursuant to Section 3.4.2 or a registered offering pursuant to Section 3.4.3 shall be exercised by the Company, in the aggregate, for not more than 90 consecutive calendar days or more 120 total calendar days in each case, during any 12-month period.