Periodic Access to Thin Registration Data Sample Clauses

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.
Sample 1Sample 2Sample 3See All (2k)
AutoNDA by SimpleDocs
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.
Sample 1Sample 2Sample 3See All (10)
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.
Sample 1Sample 2Sample 3See All (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. 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.
Sample 1Sample 2Sample 3See All (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.
Sample 1Sample 2Sample 3See All (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.
Sample 1Sample 2Sample 3See All (4)
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.
Sample 1
AutoNDA by SimpleDocs
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.
Sample 1
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 xxxxx.xx 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.
Sample 1

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.

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

  • 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. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • Effect of Failure to File and Obtain and Maintain Effectiveness of Registration Statement If (i) a Registration Statement covering all of the Registrable Securities required to be covered thereby and required to be filed by the Company pursuant to this Agreement is (A) not filed with the SEC on or before the respective Filing Deadline (a “Filing Failure”) or (B) not declared effective by the SEC on or before the respective Effectiveness Deadline (an “Effectiveness Failure”) or (ii) on any day after the Effective Date sales of all of the Registrable Securities required to be included on such Registration Statement cannot be made (other than during an Allowable Grace Period (as defined in Section 3(r)) pursuant to such Registration Statement (including, without limitation, because of a failure to keep such Registration Statement effective, to disclose such information as is necessary for sales to be made pursuant to such Registration Statement, to register a sufficient number of shares of Common Stock or to maintain the listing of the Common Stock) (a “Maintenance Failure”) then, as partial relief for the damages to any holder by reason of any such delay in or reduction of its ability to sell the underlying shares of Common Stock and not as a penalty (which remedy shall not be exclusive of any other remedies available at law or in equity), the Company shall pay to each holder of Registrable Securities relating to such Registration Statement an amount in cash equal to one and one-half percent (1.5%) of the aggregate Purchase Price (as such term is defined in the Securities Purchase Agreement) of such Investor’s Registrable Securities included in such Registration Statement on each of the following dates: (i) the day of a Filing Failure; (ii) the day of an Effectiveness Failure; (iii) the initial day of a Maintenance Failure; (iv) on every thirtieth day after the day of a Filing Failure and thereafter (pro rated for periods totaling less than thirty days) until such Filing Failure is cured; (v) on every thirtieth day after the day of an Effectiveness Failure and thereafter (pro rated for periods totaling less than thirty days) until such Effectiveness Failure is cured; and (vi) on every thirtieth day after the initial day of a Maintenance Failure and thereafter (pro rated for periods totaling less than thirty days) until such Maintenance Failure is cured. The payments to which a holder shall be entitled pursuant to this Section 2(f) are referred to herein as “Registration Delay Payments.” Registration Delay Payments shall be paid on the earlier of (I) the dates set forth above and (II) the third Business Day after the event or failure giving rise to the Registration Delay Payments is cured. In the event the Company fails to make Registration Delay Payments in a timely manner, such Registration Delay Payments shall bear interest at the rate of one and one-half percent (1.5%) per month (prorated for partial months) until paid in full. Notwithstanding anything herein or in the Securities Purchase Agreement to the contrary (i) no Registration Delay Payments shall be due and payable with respect to the Warrants or the Warrant Shares and (ii) in no event shall the aggregate amount of Registration Delay Payments (other than Registration Delay Payments payable pursuant to events that are within the control of the Company) exceed, in the aggregate, 10% of the aggregate Purchase Price.

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