Registrant Data Sample Clauses

Registrant Data. 9.1 The Registrar shall:
AutoNDA by SimpleDocs
Registrant Data a. The Registrar must retain full, accurate and validated details for the Registrant for whom a registration has been made using a Proxy Service. For avoidance of doubt this must not be another proxy or privacy service of any sort.
Registrant Data. The Registrar is not entitled to claim any Intellectual Property Rights in the Registrant Data.
Registrant Data. 9.6.1 You must not knowingly provide poor quality Registrant data. If You find out that a Registrant has provided poor quality data You should attempt to correct the data.
Registrant Data. The Registrar is not entitled to claim any Intellectual Property Rights in and to the Registrant Data. All rights relating to Registrant Data will be retained and held by the Registry for the benefit and protection of each Namespace as a whole.
Registrant Data. Within thirty (30) days following the Race, WTC will provide a report to the TCVB which will include the following information:
Registrant Data. You must not knowingly provide poor quality Registrant data. If you find out that a Registrant has provided poor quality data you should attempt to correct the data.Consumers are currently allowed to opt-out of providing their postal address on the WHOIS where allowed by the registry. You should take reasonable steps to ensure the opt-out is used correctly and not set this field to default to "opt-out" unless you can show that all your Registrants are consumers. If you receive a request to register a domain name for a customer you must register the domain name in your customer's name. You may only register the domain name in your or your organisation's name with the explicit prior written consent of your customer. You agree that if you register a domain on behalf of a third party, Ask4 can pass on the contact details of that third party to the Registry Administrator if required to do so by the Registry.
AutoNDA by SimpleDocs

Related to Registrant Data

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

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

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

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

  • NERC Registration If and to the extent any of the NTO’s facilities are NERC jurisdictional facilities, the ISO will register for certain NERC functions applicable to those NTO facilities. Such functions may include, without limitation, those functions designated by NERC to be “Reliability Coordinator” and “Balancing Authority” and “Transmission Planner” and “Planning Coordinator.” The Parties agree to negotiate in good faith the compliance obligations for the NERC functions applicable to, and to be performed by, each Party with respect to the NTO’s facilities. Notwithstanding the foregoing, the ISO shall register for the “Transmission Operator” function for all NTO Transmission Facilities under ISO Operational Control identified in Appendix A-1 of this Agreement.

  • Registrar Data 1.6.1 Query format: whois “registrar Example Registrar, Inc.”

  • USER REGISTRATION You may be required to register with the Site. You agree to keep your password confidential and will be responsible for all use of your account and password. We reserve the right to remove, reclaim, or change a username you select if we determine, in our sole discretion, that such username is inappropriate, obscene, or otherwise objectionable.

  • Electronic Registry of Eligible Employees (Registrants (a) Employees covered by this Agreement are eligible for listing on the Registry if they are employees who have received notice of layoff or have been laid off and are either:

  • Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are operations of the registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the registry DNS servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy as defined in Specification 1; (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within the scope of (a), (b) or (c) above.

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