Back

18(b) How do you expect that your proposed gTLD will benefit registrants, Internet users, and others?

gTLDFull Legal NameE-mail suffixDetail
.contactTop Level Spectrum, Inc.topspectrum.comView
i.) What is the goal of your proposed gTLD in terms of areas of specialty, service levels, or reputation?
It is our expectation that .contact will be primarily used by companies and enthusiasts. Given the wide range of things that can be contacted we do not intend to limit the gTLD to a specific community. We believe that “contact” is a internationally understood concept and word, and that the average Internet user will understand that the content of a .contact domain will be geared towards giving out contact information for the registrant or subject of the domain.
We hope to create a community that uses the domains with respect and helps users better contact people and companies that use the domains. We hope to solidify a positive and recognizable reputation as the best TLD for finding people’s contact information.

ii.) What do you anticipate your proposed gTLD will add to the current space, in terms of areas of competition, differentiation, or innovation?
Implementing .contact into the root zone is not only necessary due to the scarcity of desirable domains in the Internet’s most prominent TLDs, but further necessitated by the size and diversity of the ideas around products and services. contact does not fit well under any of the current gTLDs: for example, contact is not necessarily a “commercial,” “organized,” “informational,” or “business” endeavour. Further, given that thoughts and ideas around products transcend national boundaries, it also does not fit well into the purview of ccTLDs. The .contact TLD will provide a competitive alternative for those with the primary interest organizing contact information. We believe that creating a .contact TLD will facilitate more dialogue and educational opportunities than any other current TLD.
This does not mean we expect that all of the contact-centric sites will want to move to a .contact extension. Many organizations and individuals may think that their current website is better served by .com, or that their non-profit sucks website is at home in .org. Consequently, by adding a .contact to the root zone, ICANN will be improving existing TLDs by allowing them to become more focused on their intended significance, while simultaneously providing a differentiated and specific extension.

iii.) What goals does your proposed gTLD have in terms of user experience?
Top Level Spectrum believes the .contact extension, though broadly defined by the wide spectrum of what constitutes contact, is largely self-explanatory and its content readily apparent to both potential registrants and end-consumers. We hope that the Internet experience of both types of users will therefore be enhanced and simplified by the implementation of .contact into the root zone. Internet users browsing and using sites with a .contact extension will be confident that the website they are navigating will be related to sharing contact information. We hope that this interaction between content providers and content consumers will allow the Internet’s userbase to work in greater concert and to strengthen their connections globally.

iv.) Provide a complete description of the applicant’s intended registration policies in support of the goals listed above.
Given that we recognize the expansiveness and diversity of what constitutes contact, we intend to offer .contact domains through ICANN-accredited registrars, using an open registration policy that requires no verification of any certification, training, or other quantifiable measure of merit. Additionally, it is our goal to remain in compliance with typical registration policies used by the domain name industry. Through targeted marketing efforts and niche pricing levels, we expect to see that a large majority of the domains registered will be by those with plans to develop sites related to receiving contact on products or services. Companies that wish to identify complaints may find it useful to own and operate a .contact domain in a dedicated way.

We will fully implement the requirements made by the ICANN Board with regards to the Trademark Clearinghouse, the URS, Trademark PDDRP, the RRDRP, and the UDRP. We believe the these measures have been suitably developed to prevent defensive registrations, bad faith registrations, and other malicious registrations.

v.) Will your proposed gTLD impose any measures for protecting the privacy or confidential information of registrants or users? If so, please describe any such measures.

As per the current requirements in Section 4 of the Registry Agreement, we will implement all necessary thick WHOIS services. We recognize how imperative it is for each registry and ICANN-accredited registrar to be in full compliance with ICANN’s current WHOIS standards, and we plan to update our policy in accordance with any future measures taken by the ICANN Board in regard to the continuous work by the GNSO’s WHOIS Task Force and other recommendations from the SOs. We have no plans to implement any privacy or confidential measures other than fully implementing any and all such measures required by ICANN.
gTLDFull Legal NameE-mail suffixDetail
.hotelFegistry, LLCfegistry.comView
i.) What is the goal of your proposed gTLD in terms of areas of specialty, service levels, or reputation?
It is our expectation that .hotel will be primarily used by companies and enthusiasts. Given the wide range of what can be classified under hotel we do not intend to limit the gTLD to a specific community. We believe that “hotel” is a internationally understood concept and word, and that the average Internet user will understand that the content of a .hotel domain will be geared towards hotels and places users can stay.
We hope to create a community that uses the domains with respect and helps users find hotel related resources. We hope to solidify a positive and recognizable reputation as the best TLD for finding Hotel related things.

ii.) What do you anticipate your proposed gTLD will add to the current space, in terms of areas of competition, differentiation, or innovation?
Implementing .hotel into the root zone is not only necessary due to the scarcity of desirable domains in the Internet’s most prominent TLDs, but further necessitated by the size and diversity of the ideas around products and services. Hotel does not fit well under any of the current gTLDs: for example, hotel is not necessarily a “commercial,” “organized,” “informational,” or “business” endeavour. Further, given that thoughts and ideas around Hotel transcend national boundaries, it also does not fit well into the purview of ccTLDs. The .hotel TLD will provide a competitive alternative for those with the primary interest in organizing around the Hotel brand. We believe that creating a .hotel TLD will facilitate discovery of more hotels than any other current TLD.
This does not mean we expect that all of the hotel-centric sites will want to move to a .hotel extension. Many organizations and individuals may think that their current website is better served by .com, or that their non-profit hotel website is at home in .org. Consequently, by adding a .hotel to the root zone, ICANN will be improving existing TLDs by allowing them to become more focused on their intended significance, while simultaneously providing a differentiated and specific extension.

iii.) What goals does your proposed gTLD have in terms of user experience?
Fegistry believes the .hotel extension, though broadly defined by the wide spectrum of what constitutes hotel, is largely self-explanatory and its content readily apparent to both potential registrants and end-consumers. We hope that the Internet experience of both types of users will therefore be enhanced and simplified by the implementation of .hotel into the root zone. Internet users browsing and using sites with a .hotel extension will be confident that the website they are navigating will be related to hotel. We hope that this interaction between content providers and content consumers will allow the Internet’s userbase to work in greater concert and to strengthen their connections globally.

iv.) Provide a complete description of the applicant’s intended registration policies in support of the goals listed above.
Given that we recognize the expansiveness and diversity of what constitutes hotel, we intend to offer .hotel domains through ICANN-accredited registrars, using an open registration policy that requires no verification of any certification, training, or other quantifiable measure of merit. Additionally, it is our goal to remain in compliance with typical registration policies used by the domain name industry. Through targeted marketing efforts and niche pricing levels, we expect to see that a large majority of the domains registered will be by those with plans to develop sites related to hotels. Companies that wish to be identified as in the hotel industry may want to operate a .hotel domain in a dedicated way.

We will fully implement the requirements made by the ICANN Board with regards to the Trademark Clearinghouse, the URS, Trademark PDDRP, the RRDRP, and the UDRP. We believe the these measures have been suitably developed to prevent defensive registrations, bad faith registrations, and other malicious registrations.

v.) Will your proposed gTLD impose any measures for protecting the privacy or confidential information of registrants or users? If so, please describe any such measures.

As per the current requirements in Section 4 of the Registry Agreement, we will implement all necessary thick WHOIS services. We recognize how imperative it is for each registry and ICANN-accredited registrar to be in full compliance with ICANN’s current WHOIS standards, and we plan to update our policy in accordance with any future measures taken by the ICANN Board in regard to the continuous work by the GNSO’s WHOIS Task Force and other recommendations from the SOs. We have no plans to implement any privacy or confidential measures other than fully implementing any and all such measures required by ICANN.