Generic Top-Level Domain (gTLD) Registry Agreements

gTLD Registry Agreements establish the rights, duties, liabilities, and obligations ICANN requires of registry operators to run gTLDs.

本内容仅提供以下语言版本

  • English

.TEL Registry Agreement | Appendix S

.TEL Registry Agreement | Appendix S

  ICANN Logo

Appendix S
(30 May 2006)



Part I .tel sTLD Charter

Part II Delegated Authority

Part III Description of .tel Sponsored TLD Community

Part IV Start-Up Plan

Part V Selection of Registrars

Part VI Public WHOIS (4 February 2008)

Part VII Additional Provisions

Appendix S — Part I

.tel Charter

This sTLD Charter (the "Charter") identifies (a) the purposes for which the .tel sTLD (the "sTLD") is delegated, and (b) the community to be served by its delegation.

Subject to Registry Operator's compliance with this Sponsored TLD Registry Agreement, including all attachments and appendices thereto (the "Agreement") and any Temporary Specifications or Policies or Consensus Policies as defined in the Agreement:

1. The .tel sTLD will serve individuals, persons, groups, businesses, organizations, or associations that wish to store and publish their contact information using the DNS.

The .tel community is defined and distinguishable from the broader Internet community through the novel and different purpose for which registrants will use their domain names. In effect, the community is defined by the activity of its members. This is reflected in the user-defined content of their delegated zones (NAPTR records rather than Address records) as this defines the sTLD's use for finding people not machines.

2. Because the .tel community is defined by usage, it is critical that this usage be enforced to ensure integrity of the community. Therefore, each registrant will be required to agree to an Acceptable Use Policy (AUP) that states that their delegated domain will not include user-defined A, AAAA, or A6 resource records.

3. Registry Operator will manage the sTLD in accordance with the provisions of this Agreement and will, without limitation:

a. Establish policies and procedures for the sTLD;

b. Establish registration requirements for the sTLD, which may, without limitation, include obligations related to verification of registrant eligibility, acceptance of the Acceptable Use Policy, and other policies and procedures for the sTLD;

c. Permit eligible persons to register names within the sTLD in accordance with the sTLD policies;

d. Operate a web site to inform prospective registrants about registration policies and procedures;

e. Post on its web site information about its activities, procedures and policies, along with meeting minutes and information about decisions taken so that interested members of the community will have an opportunity to be aware of and respond to Registry Operator's actions and understand how to participate in the sTLD; and

f. Permit the creation of and participation in a self-organizing body by stakeholders that is intended to facilitate participation in the development of policy for the sTLD in an open and transparent manner.

4. The .tel Registry will operate using the standard "Delegation Only" model. The .tel registry servers will not hold or use NAPTRs internally, and so will not return NAPTRs in response to any query. The .tel registry will not allow numeric-only domains to be registered at the registry level.

Appendix S - Part II

Delegated Authority

Subject to Registry Operator's compliance with this Sponsored TLD Registry Agreement, including all attachments and appendices thereto (the "Agreement") and any Temporary Specifications or Policies or Consensus Policies as defined in the Agreement, and provided the scope of the Charter is not exceeded:

Registry Operator shall have delegated authority to develop policy for the sTLD in the following areas:

sTLD Product Management

1. Establishment of domain naming conventions to be used in the Registry Operator sTLD.

2. Functional and performance specifications for Registry Services, other than those specified in Appendix 7 of this Agreement.

3. Management of Registry Services and products, including but not limited to:

a. Variations, modifications, or extensions of any Registry Service or product that do not represent material changes to a previously approved Registry Service or product.

b. Changes to policies and restrictions associated with or necessitated by approved Registry Service or product.

c. Pricing of all Registry Service or product.

d. Marketing activities including but not limited to branding, naming, promotions and promotional products, packaging or pricing of such promotions.

4. Modification of deployment timelines, rollout plans, and implementation details for approved Registry Service or product.

5. Creation of policies and procedures under which certain second and third level names may be reserved, operated or offered on the most appropriate basis including auctions.

6. Establishment of policies regarding how third level names may be offered for registration.

Restrictions on Registration and Policies for Use

6. Policies regarding eligibility to register a domain name in the sTLD, which need not be uniform for all names within the sTLD.

7. Restrictions on the types of domain names that may be registered in the sTLD, such as prohibitions on certain types of strings.

8. Restrictions and policies on how registered names may be used, which need not be uniform for all names within the sTLD.

9. Identification and reservation of names that will not be available for second level registrations.

10. Reservation of names to be withheld from registration in the sTLD (in addition to those names reserved by ICANN and set forth in Appendix 6).

11. Establishment of policies applicable to registrants and/or registrars related to acceptance of the Acceptable Use Policy.

12. Mechanisms for enforcement applicable to registrants and/or registrars related to adherence to the Acceptable Use Policy, including procedures for revocation, suspension or cancellation of registrations.

13. Management and modification of .tel policy development processes, structures and procedures.

14. Responsibility to develop and adapt the structures and procedures of the interim PAG and PAG to ensure effectiveness, and to define their level of interaction with and representation on the SO Board.

Registry Operations and Performance Management

15. Except as specifically set forth in the Agreement, all matters concerning the operation of the registry for the sTLD.

16. Selection of back-end registry provider and establishment of the terms of agreement between the Registry Operator and the provider.

17. Selection of application and software development service providers, and the authority to establish terms of agreements and enter into contracts with such providers.

18. Functional and performance specifications and scope for Registry Services, other than those specified in the Appendix 7 of the Agreement.

19. Performance of Eligibility and Name-Selection Services (ENS Services), either directly by the Registry Operator or by one or more organizations or individuals to which it delegates the responsibility for performing ENS Services.

20. Operational capability decisions, including location, staffing, organization structure, capital expenditure, suppliers and, consistent with ICANN approved policies related to selection and management of ICANN-Accredited Registrars, distribution and promotional channels.

21. Other operations-related processes and procedures, including but not be limited to:

a. Internal operations of the Registry Operator;

b. Registry/Registrar relations and channel management, including the terms and conditions contained in the registry/registrar agreement, and selection of ICANN-Accredited Registrars to act as registrars for the Sponsored TLD, consistent with Part V of this Appendix S;

c. Terms and conditions required to be included in the end-user registration agreement;

d. Mechanisms for resolution of disputes between owners of rights in names (such as trademarks) and registrants;

e. Mechanisms for enforcement of acceptable use policies and other registration restrictions and policies; and

f. Provisions for publication of registry and registrar data.

Other

22. Except as set out in this Agreement, other areas of responsibility as ICANN and Registry Operator may agree in writing from time to time.

23. Any other policies or practices not inconsistent with the Agreement, ICANN Temporary Specifications and Policies, or Consensus Policy.

Appendix S — Part III

Description of Sponsored TLD Community

The .tel sTLD is intended to serve the needs of individuals, persons, groups, businesses, organizations, or associations that wish to store their contact information using the DNS.

The .tel community refers to those individuals, persons, groups, businesses, organizations, or associations eligible to register in the .tel sTLD according to this Agreement and the .tel Charter (Part I to this Appendix S). The .tel community is open to those who have registered .tel domains, as well as service and application providers that support the community.

The Registry Operator may extend or amend the description of the Community consistent with the terms of the Agreement and the .tel Charter.

Appendix S — Part IV

Start-Up Plan

START-UP PLAN Subject to Registry Operator's compliance with this TLD Registry Agreement, including all attachments and appendices thereto (the "Agreement") and any Temporary Specifications or Policies or Consensus Policies as defined in the Agreement, and provided the scope of the Charter is not exceeded:

Registry Operator will implement the following start-up plan:

Background

The start-up plan provides for the orderly introduction of the .tel sTLD in a transparent, and logical way, for the purpose of ensuring competition, fairness and reliability for ICANN-Accredited Registrars, registrants, and the sTLD Community (as defined in Part 3 of this Appendix S). It is intended to create a stable and effective registration process for the benefit of the Internet community in general, and effected stakeholders in particular while minimizing the number of conflicts within the Community or with third parties.

The plan consists of a multiphase process that will be executed by Registry Operator.

Timeline

Registry Operator plans to introduce and begin to support products and services on the following approximate and estimated timeline. All referenced dates are based on the date of the signature of the ICANN Agreement (IA).

Date

Event

In-Progress

Policy development.

Community awareness.

Applications design and development.

ICANN Agreement ("IA")

ICANN contract signature.

IA + 30 days

Third-party registry service provider contract awarded.

IA + 90 days

Registry Operator publishes policy documents.

IA + 120 days

Policy documents finalized.

Acceptable Use Policy finalized.

Registry Operator publishes Registrar agreements.

IA + 150 days

All Registrar agreements finalized.

IA + 180 days

Registrar accreditation begins.

IA + 210 days

OT&E testing begins.

IA + 270 days

OT&E testing ends.

Sunrise begins (60 days).

IA + 330 days

Landrush Period begins (30 days).

IA + 360 days

Full operations begin.

Agreement and Policy Development

In order to establish a structure that best serves the sTLD Community, Registry Operator has commenced development of the various agreements and policies needed in connection with the operation of the .tel sTLD. Registry Operator will continue during the start-up period with publication and execution as outlined in the Timeline section.

Third Party Registry Service Provider

Registry Operator will identify, for ICANN's review and approval (such approval not to be unreasonably withheld), its third party provider of outsourced registry operations for the registry and will conclude contract negotiations with such third party provider. Outsourced registry operations will include, but are not limited to, interfaces for registrars, WHOIS-database, 24x7 customer service and technical support.

OT&E Testing

Registry Operator will conduct comprehensive testing of the registry system and registration procedures (including the interfaces with Registrars and the ENS Services provider(s)). OT&E testing shall confirm that all entities involved in the registration process are prepared for the commencement of full operations.

Sunrise Period

The goal of the Sunrise period is twofold. Firstly, it will allow prospective registrants with trademarks or other prior rights to register them as domains in the sTLD and to resolve potential disputes arising from overlapping or inconsistent claims. Secondly, the Sunrise period will ensure stable registry operations and prepare for full operations, allowing for the adjustment of policies and processes if required. The Sunrise period is scheduled to last for a period of 60 days.

In order to avoid abusive or ineligible registrations, rights holders will be required to provide additional information during the registration process regarding their rights. A confirmation process will be established to verify ownership rights in requested domains.

During the Sunrise period, Registry Operator will closely monitor the day-to-day operations of the registry and adjust policies and processes as necessary to ensure stable registry operation and prepare for commencement of full operations.

Landrush Period

The Landrush Period will allow for multiple applications for the same domain to be accepted through a fair and equitable procedure.

Live Operation

Full operations will provide continuous and stable registry operation to the Internet Community. Registry Operator will accept domain name registration requests from all eligible registrants through participating Registrars, those ICANN-Accredited Registrars who have executed a contact with Registry Operator.

Registrations will generally be accepted on a first-come, first served basis. The UDRP will be used to resolve trademark or name resolution disputes.

Registry Operator may from time to time update registration operations and procedures and offer new products and services consistent with the Sponsored TLD Registry Agreement.

Products and Services

Registry Operator intends to make the products and services described in the Product List hereto available. Registry Operator reserves the right to establish start-up procedures, determine appropriate testing periods, and conduct service validation for new products and services.

Registry Reserved Names

Registry Operator intends to reserve certain second and third level premium and special purpose names, to be permanently reserved, operated or offered on the most appropriate basis including auctions.

Modification of Timeline

Registry Operator reserves the right to modify the Timeline as reasonably necessary in light of technical or market factors or delays in the development of policies for the sTLD.

Appendix S — Part IV

Start-up Plan

.TEL Product List

Any products and services consistent with the Sponsored TLD Registry Agreement, including without limitation, the following:

Standard Products

.Tel Product

Description & Features

Market

Proposed Model

P01

Sunrise Second Level Domains with Rights Confirmation

Restricted registration of Second Level Domains for holders of trademark(s) or other prior rights. Conducted prior to service launch during a 60 day window. Confirmation of rights to be conducted.

Rights Holders

Minimum 3 year registration.

One-time fee for Rights Confirmation

P02

Land Rush Registrations

Special procedure for unrestricted registration of Second Level Domains conducted prior to service launch during a 30 day window.

Consumers

Single or multi-year registration

P03

Second Level Domain Registrations

Continuous registration of Second Level Domains.

Consumers

Single or multi-year registration

P04

Premium and Special Purpose Names

Premium and special purpose names to be reserved, operated, or offered on the second and third level on the most appropriate basis to be determined including auctions (in partnership with selected registrars).

Consumers

Single or multi-year registration

P05

Redemption Grace Period Services

Post deletion domains held for 30 days, only original registrant can redeem domain for fee.

Domain name registrants

One-time fee

P06

Bulk Transfer

Registrar to registrar bulk transfer of domain names (consistent with ICANN transfer policies).

Registrars

Transaction based fee dependent on number of domains transferred

P07

Bulk WHOIS

Specific service to provide for high volume WHOIS requests.

WHOIS customers

Subscription based fee to be determined

P08

Domain Auto Renewal

Registry will automatically renew domain registration for one year after a set time interval following expiration. A registrar has the duration of the auto-renewal grace period to delete the domain and receive a refund for the automatic renewal.

Domain name registrants

Included with domain

P09

.TEL Listing

Optional listing for .TEL registrants stored in a database to allow for searches, with keywords, names, and/or location parameters.

Consumers and domain name registrants

Listing included with domain

Future Products

.Tel Product

Description & Features

Market

Proposed Model

P10

Digital Certificates

Digital certification services to provide for verified identity and enhanced security for .TEL domain holders.

Domain name registrants

Fee to be determined

P11

Multi-Lingual Domain Registration

General registration of Internationalized Second Level Domains. Services will follow applicable ICANN IDN Guidelines.

Consumers

Multi-year registration

P12

.TEL Watch

Monitoring service to notify registrant of any change in registration data.

Domain name registrants

Yearly fee in addition to base registration, to be determined

Appendix S — Part V

Selection of Registrars

Subject to Registry Operator's compliance with this Sponsored TLD Registry Agreement, including all attachments and appendices thereto (the "Agreement") and any Temporary Specifications or Policies or Consensus Policies as defined in the Agreement, and provided the scope of the Charter is not exceeded:

Registry Operator will select registrars from among ICANN-Accredited Registrars in a manner that promotes the following characteristics in the group of authorized ICANN-Accredited Registrars and contract on the following basis:

1. Recognition of the specific aspects of the community to be supported by the sTLD and a willingness to participate in that spirit;

2. Thorough understanding of the principles and goals underlying sTLD policies, including without limitation the domain name management policy;

3. Demonstrated ability to support, or commitment to arrange, provisioning and maintenance of NAPTR Resource Records and other related features as specified by Registry Operator Guidelines for their sTLD registrations;

4. Demonstrated ability to provide Eligibility and Name-Selection Services (ENS Services) and demonstrated familiarity with the needs of the sTLD Community in the language and region(s) served by the registrar, and established modes for reflecting these needs in the ENS Services processes;

5. The existence of proven systems designed to avoid submission of unqualified or incomplete applications that will burden the ENS system or make it impossible for Registry Operator to fulfill its commitments to ICANN;

6. Dedicated willingness and ability to propagate and enforce sTLD policies in an observant and diligent manner and in accordance with policies and procedures prescribed by Registry Operator;

7. Commitment to adhere strictly to the Acceptable Use Policy, in particular with the requirement not to allow the inclusion of user-defined Address Resource Records in the DNS Zone Files;

8. Dedicated willingness to comply with Acceptable Use Enforcement notices, to include suspension of non-compliant domain registrations;

9. Broad geographic distribution and language diversity of registrars;

10. Established collaborative contact with one or several associations representing Providers and Representatives (as defined in Part 3 above) in the language and geographical region or sector served by the registrar;

11. Established business relationships with applicable Service Providers and Community Representatives in the region(s) served by the registrar;

12. Demonstrated willingness and ability to publicize and market the sTLD, to follow all sTLD marketing guidelines, and to develop and use sTLD marketing materials as appropriate;

13. Demonstration that sufficient staff resources are available and able to interface with automated and manual elements of the sTLD registry process;

14. Demonstrated willingness to implement modifications and revisions reasonably deemed by the Registry Operator to be required based on the characteristics and functions of the sTLD;

15. The existence of proven systems to avoid transfer disputes among registrars;

16. Demonstrated willingness to share relevant marketing information with Registry Operator, including, consistent with applicable law, information about current registrants with whom the registrar has relationships who are eligible for registration;

17. Willingness and ability to post and refresh a minimum deposit against which fees will be drawn;

Registry Operator has not established a minimum or maximum number of Registrars that will be selected for the sTLD. Registry Operator will accept applications from any ICANN-accredited Registrar. Registry Operator will evaluate and determine whether to appoint an applicant Registrar to serve as a Registrar for the TLD based on the demonstrated ability to sufficiently meet all of the above criteria.

Registry Operator will enter into agreements with Registrars only after such a determination has been concluded. Registry Operator will periodically review and, as appropriate, revise its selection of Registrars based on such criteria.

Appendix S — Part VI

Public WHOIS Specification

Subject to Registry Operator's compliance with this Sponsored TLD Registry Agreement, including all attachments and appendices thereto (the “Agreement”) and any Temporary Specifications or Policies or Consensus Policies as defined in the Agreement, and provided the scope of the Charter is not exceeded:

Registry Operator will implement the following Public WHOIS Specification:

A. Specification

Subject to any future policy regarding WHOIS data adopted by ICANN, domain name registrants will be required to provide correct and accurate contact information and, as permitted by applicable law, consent to selected information being made public for legitimate purposes.

Until a generally accepted specification replacing RFC 3912 is available, the Registry Operator will provide RFC 3912 compliant WHOIS service. The specification contained in this Part VI to Appendix S is subject to change by agreement of the Registry Operator and ICANN during the design process as well as during the IETF standards process. In addition, Registry Operator agrees to implement changes to this specification specified by ICANN to conform to IETF provreg working group's protocol specification no later than 135 days after the IETF specification is adopted as a Proposed Standard [RFC 2026, section 4.1.1].

B. Data Provided In Response to WHOIS Queries

With respect to the amount and type of domain name registrant data provided in response to queries of the WHOIS service by the general public, the WHOIS service will distinguish between domain name registrants that are companies, businesses, partnerships, non-profit entities, associations, or other types of legal constructs (“Legal Persons”), and domain name registrants that are human beings, perceptible through the senses and subject to physical laws (“Natural Persons”). Domain name registrants will be required to specify whether they qualify as Legal Persons or Natural Persons by clicking the appropriate box during the registration process.

1. WHOIS Data for Legal Persons

Full WHOIS data for domain name registrants that are Legal Persons will be available to the general public at no cost. Queries of the WHOIS service related to Legal Persons will always return full and complete standard WHOIS data, including applicable personal data such as Registrant ID, Registrant Name, Organization, Address (street, city, state, postal code, and country), Phone Number, Facsimile Number, and Email Address. Legal Persons will not be permitted to opt out of disclosing such information in response to queries submitted to the WHOIS service.

The Registry Operator reserves the right, however, to take any preventive action necessary to prohibit any requestor of WHOIS data from using the WHOIS service to collect WHOIS data on Legal Persons for marketing purposes, spamming, data-mining, or unlawful purposes.

For the fields returned in response to queries of the WHOIS service for Legal Persons, and an example of a returned record, please see the “WHOIS Output Format Specification—Legal Persons” section (D.1) below.

2. WHOIS Data for Natural Persons

Full WHOIS data for domain name registrants that are Natural Persons may or may not be available to the general public at no cost, depending on whether the applicable domain name registrant elects to make his or her personal information available in response to queries of the WHOIS service.

Unlike Legal Persons, domain name registrants that are Natural Persons will be given the option to elect whether or not their personal information is disclosed by the WHOIS service in response to queries from the general public. The default option will be for all personal information to be disclosed by the WHOIS service. In order to override this default option, the domain name registrant that is a Natural Person will have to specifically elect not to have such personal information disclosed by clicking the appropriate box during the registration process.

a. Natural Persons Who Opt-In (Default Option)

For any domain name registrant that is a Natural Person and that does not elect to have his or her personal information withheld from disclosure by the WHOIS service, queries by the general public of the WHOIS service related to such Natural Person will return full and complete standard WHOIS data at no cost, including personal data such as Registrant ID, Registrant Name, Organization, Address (street, city, state, postal code, and country), Phone Number, Facsimile Number, and Email Address.

The Registry Operator reserves the right to take any preventive action necessary to prohibit any requestor of WHOIS data from using the WHOIS service to collect WHOIS data on Natural Persons for marketing purposes, spamming, data-mining, or unlawful purposes.
For the fields returned in response to queries of the WHOIS service for Natural Persons that opt-in to full disclosure (or that do not elect to change the default setting), and an example of a returned record, please see the “WHOIS Output Format Specification—Natural Persons (Opt-In)” section (D.2) below.

b. Natural Persons Who Opt-Out

If a domain name registrant that is a Natural Person elects to withhold his or her personal information from disclosure by the WHOIS service, queries by the general public of the WHOIS service related to such Natural Person will return only limited WHOIS data, including Domain Name, Domain ID, Sponsoring Registrar, Sponsoring Registrar IANA ID, Domain Status, Registrant ID, Registrant Name, Name Server, created by registrar, last updated by registrar, domain registration date, domain expiration date, and domain last updated date. No personal information relating to the domain name registrant will be available through the WHOIS service for Natural Persons who have opted-out of disclosing such personal information.

Instead of such personal information, requestors of WHOIS data on such Natural Persons will be informed that the Natural Person has elected to withhold certain personal information from disclosure by the WHOIS service, and will be provided with a link to the Registry Operator's Special Access Service. Through this Special Access Service, requestors will be able to obtain secure access to the personal information of Natural Persons who have opted not to disclose such information in the public WHOIS service. However such requestors must be able to demonstrate a legitimate need for access to such personal information—see the “Special Access Service” section (B.3) below.

The Registry Operator reserves the right to take any preventive action necessary to prohibit any requestor of WHOIS data from using the WHOIS service to collect WHOIS data on Natural Persons for marketing purposes, spamming, data-mining, or unlawful purposes.

For the fields returned in response to queries of the WHOIS service for Natural Persons that opt-out of full disclosure, and an example of a returned record, please see the “WHOIS Output Format Specification—Natural Persons (Opt-Out)” section (D.3) below.

3. Special Access Service

As described above, the WHOIS service will provide a link to the Special Access Service in response to queries for WHOIS data on Natural Persons that have opted not to disclose personal information. The Special Access Service will be a secure website operated by the Registry Operator through which requestors can obtain such personal information that has not been disclosed within the WHOIS service.

Requestors with a legitimate need to access undisclosed personal information of domain name registrants that are Natural Persons will be able to obtain such access, under certain terms and conditions. A Requestor will only be required to complete the online form described below in “Initial Sign-Up and Activation” upon initial use of the Special Access Service. Requestors will be permitted to complete this online sign-up and activation form at any time after the WHOIS service has been made available to the public. Each subsequent time that a requestor needs to use the Special Access Service, they will only need to follow the procedure described below in “Online Use of Special Access Service.”

a. Initial Sign-Up and Activation

Before using the Special Access Service for the first time, a requestor must complete the online sign-up and activation process described below. A requestor will only be required to complete this step upon initial use of the Special Access Service. There will be no charge for this online sign-up and activation process.

The link provided by the WHOIS service will direct the requestor to a secure online sign-up page for the Special Access Service. The requestor will be required to submit their Company Name, Contact Name, Address (street address, city, state, postal code, and country), Email Address and Telephone Number. To confirm that the requestor is a verifiable person or company a personal identification number and a URL link will be mailed or sent by courier to the postal address provided by the requestor.. The cost of such courier service will be at the requestor’s expense.

The link that was sent to the requestor will take them to a secure Special Access Service activation page. The requestor will then enter their personal identification number in order to activate their Special Access Service account. Upon activation, a user name and password will be sent to the email address provided by the requestor above. The user name and password provided to the requestor will be used to access the Special Access Service, subject to the terms and conditions being met for each new request.

b. Online Use of Special Access Service

After the requestor receives their user name and password via email, they will be able to consult the Special Access Service by using their user name and password to log into the Special Access Service.

After logging into the Special Access Service, the requestor will complete an information request form indicating the domain name about which additional information is requested, and they will be required to demonstrate a legitimate need to access this additional information by selecting the reason such access is requested from a drop down menu. If the appropriate reason is not listed in the drop down menu, the requestor must select “Other” and specify the reason. The requestor will also be required to agree (via a click through agreement) to accept the terms and conditions of access, which specify the following: (i) they have a legitimate reason for accessing the information, (ii) they will not use the data for marketing purposes, spamming, data-mining, or unlawful purposes, (iii) they will not share information derived from the Special Access Service with any individual or entity that is not bound by the terms of the Special Access Service, (iv) they will not share their user name and password with any unauthorised third parties, (v) they understand and acknowledge that they will be accessing personal information, and (vi) they understand and acknowledge that the Registry Operator records information about all searches of the Special Access Service (including the reason for such search).

To prevent data-mining and other forms of bulk data access, each Special Access Service request will be limited to five (5) queries per twenty four (24) hours.

The Registry Operator reserves the right to revoke any requestor’s right to use the Special Access Service or to take any other preventive action necessary to prohibit any requestor from using the Special Access Service to collect data on Natural Persons for marketing purposes, spamming, data-mining, or unlawful purposes.
For the fields returned in response to queries of the Special Access Service for Natural Persons that opt-out of full disclosure, and an example of a returned record, please see the “Output Format Specification—Special Access Service” section (D.4) below.

c. Additional Fields Capability

If necessary, the Registry Operator may introduce additional fields to the list of WHOIS fields described in this document. Those fields will be preceded and identified by appropriate tags.

By default, the WHOIS service searches for domain names. By using the following keywords, the search type can be determined:


Keywords (case insensitive)



Type



do, domain

Search for domain objects. Only the "Domain Name" field is used



ho, host

Search only by name server objects. The input string is matched against “Host Name” or the “Host ID” field contents



Contact

Search for contact objects in the “Contact ID” field



Registrar

Search for registrar objects in the "Registrar ID" or "Registrar Organization" field



ap, application

Search for an application object (i.e. for requests during the sunrise period). Input string is matched against the “Domain Name” or “Application ID” fields.


In addition, further restriction on the search can be requested by including the following keyword in the query:


Keywords (case insensitive)



Option



Id

Search is performed in the respective ID field


Finally, the degree of detail shown in the response can be controlled by the following keywords:


Keywords (case insensitive)



Option



=, full

Always return the complete data, even if multiple entries are found



sum, summary

Always return summarized data, even if only a single entry is found


The last token in the input is taken as the search parameter.

If the search parameter is “help” and no object type is given, no search is performed, but a short summary about the input format is returned.

d. Output Format Specification

All lines in the response data are terminated by CR/LF pairs. Lines that contain comments, legal notes or similar, start with a percent sign ('%'). If the output consists of multiple objects, they are separated by at least one empty line. The objects themselves (including the related sub objects, like referenced contacts of a domain) do not contain empty lines. If no objects match the search query, “NOT FOUND” is returned. The object data is composed of multiple key-value lines. Key and value of a key-value pair are separated by a colon (':'). The key may contain space characters.

Example:

Domain Name: example.tel
Name Server: blue.example.tel 192.0.2.1
Name Server: red.example.tel 192.0.2.2

The actual published data depends on the registry policy and, where appropriate, the Domain Owner’s disclosure settings. If data is not disclosed, the respective key-value pair is omitted. In contrast, empty fields (like the organization in the given example), are included. This allows the client to differentiate between the two cases.

Depending on the query and options, either a long or short format is produced.

1. WHOIS Output Format Specification—Legal Persons

Domain ID: D38482
Domain Name: example.tel
Sponsoring Registrar: ANOTHER REGISTRAR LTD
Sponsoring Registrar IANA ID: 2334
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Registrant ID: C343238
Registrant Name: Sams Flowers Limited
Registrant Organization: CORE Sams Flowers Limited
Registrant Street: 9 Wilfred Street
Registrant City: London
Registrant State/Province: London
Registrant Postal Code: SW1E 6PL
Registrant Country: United Kingdom
Registrant Country Code: UK
Registrant Phone: +442078280000
Registrant Email: info@samsflowers1234.com
Administrative Contact ID: C343238
Administrative Contact Name: Sams Flowers Limited
Administrative Contact Organization: Sams Flowers Limited
Administrative Contact Address1: 9 Wilfred Street
Administrative Contact City: London
Administrative Contact State/Province: London
Administrative Contact Postal Code: SW1E 6PL
Administrative Contact Country: United Kingdom
Administrative Contact Country Code: UK
Administrative Contact Phone: +442078280000
Administrative Contact Email: info@samsflowers1234.com
Technical Contact ID: C343238
Technical Contact Name: Sams Flowers Limited
Technical Contact Organization: Sams Flowers Limited
Technical Contact Street: 9 Wilfred Street
Technical Contact City: London
Technical Contact State/Province: London
Technical Contact Postal Code: SW1E 6PL
Technical Contact Country: UK
Technical Contact Phone: +442078280000
Technical Contact Email: : info@samsflowers1234.com
Billing Contact ID: C343239
Billing Contact Name: Sams Flowers Limited
Billing Contact Organization: Sams Flowers Limited
Billing Contact Street: 9 Wilfred Street
Billing Contact City: London
Billing Contact State/Province: London
Billing Contact Postal Code: SW1E 6PL
Billing Contact Country: United Kingdom
Billing Contact Country Code: UK
Billing Contact Phone: +441632960502
Billing Email: info@samsflowers1234.com
Name Server: ns1.example.tel 172.16.1.1
Name Server: ns2.example.tel 172.16.1.2
Created by Registrar: ANOTHER REGISTRAR LTD
Last Updated by Registrar: ANOTHER REGISTRAR LTD
Last Transferred Date: Thu Mar 10 16:02:32 GMT 2005
Domain Registration Date: Wed Mar 27 00:01:00 GMT 2002
Domain Expiration Date: Wed Mar 26 23:59:59 GMT 2008
Domain Last Updated Date: Mon Feb 26 10:20:29 GMT 2007























































Regarding the included contact data, see below also.

Host Data Format
Host ID: H38473
Host Name: ns3.example.tel
Registrar ID: IANA-15
Created On: 2001-07-23 17:53:02 GMT
Last Updated On: 2002-11-01 09:21:47 GMT
Status: ok
IP Address: 172.16.1.3
IP Address: 3FFE:3273:1002::FE99:3BC7







Contact Data Format
Contact ID: C123456
Status: ok
Name: Kenneth McCormick
Contact Information: Disclosure of contact data is restricted because of UK and EU Data Protection legislation. Details for this contact ID may be available by looking up an appropriate domain object in the WHOIS system. The contact details for this contact ID can also be obtained through the Telnic Special Access Service. Please visit http://www.sas.nic.tel for more information.



2. WHOIS Output Format Specification—Natural Persons (Opt-In)

Domain ID: D38482
Domain Name: example.tel
Registrar ID: IANA-15
Created On: 2001-07-23 17:53:02 GMT
Last Updated On: 2002-11-01 09:21:47 GMT
Expiration Date: 2005-07-23 17:53:02 GMT
Status: ok
Registrant ID: C343238
Registrant Name: John Q. Public
Registrant Organization: None
Registrant Street: 123 Example Street
Registrant City: Springfield
Registrant State/Province: Illinois
Registrant Postal Code: 12345
Registrant Country: United States
Registrant Country Code: US
Registrant Phone: +12125551212
Registrant Email: jqpublic@ispemailserviceprovider.com
Administrative Contact ID: C343238
Administrative Contact Name: John Q. Public
Administrative Contact Organization: None
Administrative Contact Street: 123 Example Street
Administrative Contact City: Springfield
Administrative Contact State/Province: Illinois
Administrative Contact Postal Code: 12345
Administrative Contact Country: United States
Administrative Contact Country Code: US
Administrative Contact Phone: +12125551212
Administrative Contact Email: jqpublic@ispemailserviceprovider.com
Technical Contact ID: C343238
Technical Contact Name: John Q. Public
Technical Contact Organization: None
Technical Contact Street: 123 Example Street
Technical Contact City: Springfield
Technical Contact State/Province: Illinois
Technical Contact Postal Code: 12345
Technical Contact Country: United States
Technical Contact Country Code: US
Technical Contact Phone: +12125551212
Technical Contact Email: jqpublic@ispemailserviceprovider.com
Billing Contact ID: C343238
Billing Contact Name: John Q. Public
Billing Contact Organization: None
Billing Contact Street: 123 Example Street
Billing Contact City: Springfield
Billing Contact State/Province: Illinois
Billing Contact Postal Code: 12345
Billing Contact Country: United States
Billing Contact Country Code: US
Billing Contact Phone: +12125551212
Billing Contact Email: jqpublic@ispemailserviceprovider.com
Name Server: ns1.example.tel 172.16.1.1
Name Server: ns2.example.tel 172.16.1.2



















































Regarding the included contact data, see below also.

Host Data Format
Host ID: H38473
Host Name: ns3.example.tel
Registrar ID: IANA-15
Created On: 2001-07-23 17:53:02 GMT
Last Updated On: 2002-11-01 09:21:47 GMT
Status: ok
IP Address: 172.16.1.3
IP Address: 3FFE:3273:1002::FE99:3BC7







Contact Data Format
Contact ID: C123456
Status: ok
Name: Kenneth McCormick
Contact Information: Disclosure of contact data is restricted because of UK and EU Data Protection legislation. Details for this contact ID may be available by looking up an appropriate domain object in the WHOIS system. The contact details for this contact ID can also be obtained through the Telnic Special Access Service. Please visit http://www.sas.nic.tel for more information.



3. WHOIS Output Format Specification—Natural Persons (Opt-Out)

Domain Name: example.tel

Domain ID: D15658373

Sponsoring Registrar: ANOTHER REGISTRAR LTD

Sponsoring Registrar: IANA ID: 303

Domain Status: ok
Registrant Name: John Q. Private
Administrative/Billing/Technical Contact: The registrant is a non-trading individual who has opted to have their details omitted from the WHOIS service. Please visit http://www.sas.nic.tel for more information.

Name Server: ns5.example.tel

Name Server: ns6.example.tel

Created by Registrar: DIRECT INFORMATION PVT LTD DBA PUBLICDOMAINREGISTRY.COM

Last Updated by Registrar: DIRECT INFORMATION PVT LTD DBA PUBLICDOMAINREGISTRY.COM

Domain Registration Date: Sun Dec 17 14:38:18 GMT 2006

Domain Expiration Date: Sun Dec 16 23:59:59 GMT 2007

Domain Last Updated Date: Sat Jul 21 07:03:18 GMT 2007

4. Output Format Specification—Special Access Service

Queries for data using the Special Access service will return results as per the Full Output specification for Opt-In Natural Persons, as shown in “WHOIS Output Format Specification—Natural Persons (Opt-In)” (D.2).

E.            Application Format
During the Sunrise period, Telnic will provide a free, public, web-based service through its Validation Agent for checking the status of Sunrise applications.
F            Web WHOIS Service
The web WHOIS service shares the same functionality as the port 43 service, with the exception that the input is implemented by using the means of HTML, i.e. by text input fields, radio buttons and check boxes. The output format is the same as described above. It is included in the HTML page in a way that can easily be copied by common browsers. To support the input and output of non-US-ASCII characters, the service uses the UTF-8 encoding.




G. Matrix of WHOIS and Special Access Service Data Availability

The table below provides an overview of the data that will be available through the WHOIS and Special Access Service mechanisms. This table is provided for convenience only and is subject to the more detailed description of these mechanisms included in this Part VI of Appendix S.

WHOIS Field Name
Legal Person (Full WHOIS)
Natural Person (Opt-in WHOIS)
Natural Person (Opt-out WHOIS)
Special Access Service (Web)
Domain Name:
X
X
X
X
Domain ID:
X
X
X
X
Sponsoring Registrar:
X
X
X
X
Sponsoring Registrar IANA ID:
X
X
X
X
Domain Status:
X
X
X
X
Registrant ID:
X
X
X
X
Registrant Name:
X
X
X
X
Registrant Address1:
X
X
-
X
Registrant City:
X
X
-
X
Registrant State/Province:
X
X
-
X
Registrant Postal Code:
X
X
-
X
Registrant Country:
X
X
-
X
Registrant Country Code:
X
X
-
X
Registrant Phone Number:
X
X
-
X
Registrant Email:
X
X
-
X
Administrative Contact ID:
X
X
X
X
Administrative Contact Name:
X
X
X
X
Administrative Contact Address1:
X
X
-
X
Administrative Contact City:
X
X
-
X
Administrative Contact State/Province:
X
X
-
X
Administrative Contact Postal Code:
X
X
-
X
Administrative Contact Country:
X
X
-
X
Administrative Contact Country Code:
X
X
-
X
Administrative Contact Phone Number:
X
X
-
X
Administrative Contact Email:
X
X
-
X
Billing Contact ID:
X
X
X
X
Billing Contact Name:
X
X
X
X
Billing Contact Address1:
X
X
-
X
Billing Contact City:
X
X
-
X
Billing Contact State/Province:
X
X
-
X
Billing Contact Postal Code:
X
X
-
X
Billing Contact Country:
X
X
-
X
Billing Contact Country Code:
X
X
-
X
Billing Contact Phone Number:
X
X
-
X
Billing Contact Email:

X
X
-
X
Technical Contact ID:
X
X
X
X
Technical Contact Name:
X
X
X
X
Technical Contact Address1:
X
X
-
X
Technical Contact City:
X
X
-
X
Technical Contact State/Province:
X
X
-
X
Technical Contact Postal Code:
X
X
-
X
Technical Contact Country:
X
X
-
X
Technical Contact Country Code:
X
X
-
X
Technical Contact Phone Number:
X
X
-
X
Technical Contact Email:
X
X
-
X
Name Server:

X
X
X
X
Created by Registrar:
X
X
X
X
Last Updated by Registrar:
X
X
X
X
Domain Registration Date:
X
X
X
X
Domain Expiration Date:
X
X
X
X
Domain Last Updated Date:
X
X
X
X

 

Appendix S — Part VII

Miscellaneous Provisions

Privacy Considerations

Registry Operator may, at its discretion, submit to ICANN for its consideration and approval (such approval not to be unreasonably withheld) a proposal for additional measures to be implemented by Registry Operator that are designed to further safeguard data provided by registrants.