Use of Registry or Centralised WHOIS Service Information Sample Clauses

Use of Registry or Centralised WHOIS Service Information. The Registrar must not use information obtained from the Registry or auDA's Centralised WHOIS Service to solicit business from, or to otherwise make contact with, a Registrant, unless: 13.1.1 the Registrar is the registrar of the Registrant, as identified in the Registry; or 13.1.2 the Registrant has previously contacted the Registrar in respect of the registration of a Domain Name; or 13.1.3 the Registrant is otherwise a customer of the Registrar and has authorised the Registrar to use information obtained to accept business from or contact with the Registrant; or 13.1.4 both the Registrant and the Registrant's registrar (as identified in the Registry) have consented in writing to such use of the information.
AutoNDA by SimpleDocs

Related to Use of Registry or Centralised WHOIS Service Information

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Use of Service Areas The service areas, as located within the Project, shall be ear- marked for purposes such as parking spaces and services including but not limited to electric sub-station, transformer, DG set rooms, underground water tanks, Pump rooms, maintenance and service rooms, firefighting pumps and equipment etc. and other permitted uses as per sanctioned plans. The Allottee shall not be permitted to use the services areas in any manner whatsoever, other than those earmarked as parking spaces and the same shall be reserved for use by the Association for rendering maintenance services.

  • Abuse and Neglect of Children and Vulnerable Adults: Abuse Registry Party agrees not to employ any individual, to use any volunteer or other service provider, or to otherwise provide reimbursement to any individual who in the performance of services connected with this agreement provides care, custody, treatment, transportation, or supervision to children or to vulnerable adults if there has been a substantiation of abuse or neglect or exploitation involving that individual. Party is responsible for confirming as to each individual having such contact with children or vulnerable adults the non-existence of a substantiated allegation of abuse, neglect or exploitation by verifying that fact though (a) as to vulnerable adults, the Adult Abuse Registry maintained by the Department of Disabilities, Aging and Independent Living and (b) as to children, the Central Child Protection Registry (unless the Party holds a valid child care license or registration from the Division of Child Development, Department for Children and Families). See 33 V.S.A. §4919(a)(3) and 33 V.S.A. §6911(c)(3).

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

  • Use of FIIOC’s and FSC's Name The Trust shall not use the name of FIIOC and FSC in any Prospectus, sales literature or other material relating to the Trust or any Fund of the Trust in a manner not consented to by FIIOC and FSC prior to use; provided, however, that FIIOC and FSC shall approve all uses of its name which merely refer in accurate terms to its appointments, duties or fees hereunder or which are required by the Securities and Exchange Commission ("SEC" or “Commission”) or a state securities commission; and further, provided that in no event shall such approval be unreasonably withheld.

  • USE OF NASA NAME AND NASA EMBLEMS A. NASA Name and Initials Partner shall not use "National Aeronautics and Space Administration" or "NASA" in a way that creates the impression that a product or service has the authorization, support, sponsorship, or endorsement of NASA, which does not, in fact, exist. Except for releases under the "Release of General Information to the Public and Media" Article, Partner must submit any proposed public use of the NASA name or initials (including press releases and all promotional and advertising use) to the NASA Associate Administrator for the Office of Communications or designee ("NASA Communications") for review and approval. Approval by NASA Office of Communications shall be based on applicable law and policy governing the use of the NASA name and initials. B. NASA Emblems Use of NASA emblems (i.e., NASA Seal, NASA Insignia, NASA logotype, NASA Program Identifiers, and the NASA Flag) is governed by 14 C.F.R. Part 1221. Partner must submit any proposed use of the emblems to NASA Communications for review and approval.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.

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

  • Certification Regarding Prohibition of Boycotting Israel (Tex Gov. Code 2271)

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