Public Whois Specification Sample Clauses

Public Whois Specification. The Whois service substantially consists of two parts: • Port 43 Whois services • Web-based Whois services Registry Operator’s Whois service is the authoritative Whois service for all second-level Internet domain names registered in the .INFO top-level domain and for all hosts registered using these names. This service shall be available to anyone. It shall be available via port 43 access and via links at the Registry Operator’s web site. Provisions for the detection of abusive usage of Registry Operator’s Whois system (e.g., excessive numbers of queries from one source), and corresponding protective measures, have been implemented, and Registry Operator may implement further countermeasures against abuse as necessary. Registry Operator’s Whois service will be updated on a near real-time basis. The Whois servers shall provide results in ASCII for standard and IDN .info domains. The status values reported will be those stated in xxxx://xxx.xxxx.xxx/rfc/rfc5731.txt except that domains in PendingDelete status will be reported as either PENDING-DELETE (Restorable) or PENDING-DELETE (Scheduled for release) as appropriate.
AutoNDA by SimpleDocs
Public Whois Specification. Subject to Registry Operator’s compliance with this Registry Operator TLD Registry Agreement, including all attachments and appendices thereto (the “Agreement”) and any Temporary Specifications or Policies or Consensus Policy as defined in the Agreement, and provided the scope of the Charter is not exceeded: Registry Operator will implement the following public WHOIS specification:
Public Whois Specification. RFC954-Conformant Whois The standard Whois service is intended as a lookup service for registries, registrars, registrants, as well as for other individuals and businesses that wish to query details of domain names or nameservers stored in the registry. The standard Whois service will provide a central location for all authoritative .aero TLD data. The registry provides a front-end web interface to allow convenient user access to the Whois service. The RFC954-conformant Whois service will be engineered to handle moderate transaction load and be integral to the standard suite of Registry Services. The Whois service will return a single response per domain name or nameserver query. The RFC954-conformant Whois service will conform to the requirements of Appendix 5. The RFC954-conformant service provided by the registry will have the following features: • Standard protocol accessible over port 43. • Batch-style or near real time updates. • Additional fields capability. • Whois Service Data Elements Whois Service Data Elements The RFC954-conformant service will include the following data elements: • The name of the domain name registered; • The IP addresses of the primary nameserver and secondary nameserver(s) of the name registered, if applicable, i.e. nameserver has a .aero name.; • The corresponding names of those nameservers; • The identity of the sponsoring registrar; • The ENS_AuthId identifying the authorization of the registration, (this enables tracking of registrations performed using the same ENS_AuthId); • The original creation date and term of the registration; • The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the domain name registrant; • The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the name registered; • The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the name registered; and • The Maintainer URL (email or website). The maintainer is a person that has been designated by the Registrar for the registration of the domain (for example a reseller, could also depend on the registrant).
Public Whois Specification. Without prejudice to the relevant provisions of the UPU Acts and any other decisions, policies, regulations and rules of procedure adopted by the UPU for the .POST sTLD, subject to the Sponsor’s compliance with the .POST sTLD Agreement and any Temporary Specifications or Policies or Consensus Policies as defined therein and provided the scope of the Charter is not exceeded, the Sponsor shall ensure the implementation of the following public WHOIS specification: SPECIFICATION Subject to any future policy regarding WHOIS data adopted by ICANN, domain name registrants will be required to provide correct contact information and, as permitted by the UPU Acts, by any other decisions, policies, regulations and rules of procedure adopted by the UPU for the .POST sTLD or by applicable law, consent to selected information being made public for legitimate purposes. A participating Registrar, at the Registrar’s expense, will be required to provide those wishing to query the WHOIS database (other than for marketing purposes or other purposes contrary to the .POST sTLD policy) with access to complete and up-to-date data for each registered domain name record (subject to applicable privacy policies) including, but not limited to the following: • Domain name and the TLD in which the domain name is registered; • Status of the domain name, e.g., "on hold" or "pending delete"; • Registrant's name and postal address; • Administrative/technical contacts' name, postal address, e-mail address, telephone number and (if any) facsimile number; • Original registration date, expiration date and date on which the database was last updated; • Internet Protocol addresses and corresponding names of primary and secondary; • Name servers for the domain name; and • Registrar's identification information. In order to assist complainants under the UDRP to determine whether a pattern of "bad faith" has been demonstrated by a particular registrant, the information set forth above will be available on a publicly accessible database, subject to applicable privacy policies, which will be searchable by domain name, registrant's name, registrant's postal address, contacts' names, Registrars Contact IDs and Internet Protocol address without arbitrary limit. In order to provide an effective WHOIS database, Boolean search capabilities may be offered. Registrars shall be required to participate in the operation of a cross-registry WHOIS database, which will provide searching capabilities and access to a...
Public Whois Specification. Public Whois for the .cat Sponsored TLD will be provided according to the specification described in Part VI of Appendix S.
Public Whois Specification. Subject to Registry Operator's compliance with the Agreement and any Temporary Specifications or Policies or Consensus Policy as defined in the Agreement, and provided the scope of the Charter is not exceeded, Registry Operator will implement the following public WHOIS specification: PURPOSE Provision of a WHOIS database for the sTLD will assist registrants and appointed contact persons for associated registrations to protect their rights to use the registered domain names.

Related to Public Whois Specification

  • Class Specifications The Human Resources Division shall determine:

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

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