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

Prototypical answer:

gTLDFull Legal NameE-mail suffixDetail
.secureArtemis Internet Inc.artemisinternet.comView

i. Service Level and Reputation

The goal of .Secure is to create a safe, dependable mechanism for end-users to operate on the Internet. As we stated in 18a, .Secure focuses on honoring users’ intention to safely access any service, so individuals, organizations and corporations of any size and in any industry will be allowed to register under .secure. All registrants will need to comply with our Security and Code of Conduct policies. Continuous automated and manual enforcement of these policies will help cement .Secure’s reputation as a trustworthy TLD for businesses to host critical services that users feel safe visiting.

Our goal of serving the most important applications and brands on the Internet requires us to provide a level of customer service and reliability well above other gTLDs. This is why we very carefully selected a premier registry services provider, ARI, and why we are supplementing their already excellent capabilities with our own customer service staff and redundant systems.

ii. Differentiation

Our .Secure offering will create a trustworthy portion of the namespace for corporations, non-profits and individuals who care about the security of their online transactions. We will have significant differentiation from other gTLDs based upon our unique and rigorous authentication procedures, our meaningful security standards, and our ongoing enforcement program. We will also be technically innovative, openly collaborating to develop and deploy new standards. While we intend to be the safest and most secure gTLD on the Internet, we are also striving to improve security for all users and gTLDs via our technical leadership.

The three core principals of .Secure are Verify, Secure and Enforce. These principals differentiate our offering in these ways:

Verify- Unlike the vast majority of new gTLDs, .Secure will require the submission of verifiable documentation as to the identity of a Registrant, and every domain will be examined and approved by a human expert. The creation of a trustworthy namespace will set .Secure apart from other TLD options.

Secure- We are building ground-breaking technology with the help of major software developers and web properties. .Secure will differentiate itself by being an early user of this technology and the enforcement of security standards on all registrants, but we hope that our open standards will be adopted by other TLDs to improve security across the Internet.

Enforce- The .Secure gTLD will be unique for running a continuous automated enforcement program that detects and scans subdomains for violations of our security or acceptable use policies. Enforcement actions will be undertaken by human domain abuse experts, and will range from increasingly urgent notifications to suspension of domain resolution.

iii. User Experience

Our goal is to provide effortless security to end-users. Securely using the Internet currently requires constant vigilance and a significant amount of technical knowledge. How many end users send sensitive data without the protection of a securely configured HTTPS connection? How many click through the various warning presented to them by their browser? How many install email encryption software and then distribute their keys to their friends?

We aim to give users effortless security. The user only needs to type .Secure after their intended address to insure that their software knows that they wish to utilize optimal protections during their session.

The new gTLD process provides us with a novel opportunity to create a portion of the Internet that requires the most secure configurations and technologies. We intend our .Secure domain to be the leader in this space, although our goal is to work through the Domain Policy Working Group to help secure other new gTLDs and to create technologies that provide these security upgrades to all namespaces.

iv. Registration Policies

Our registration process will be based upon the standard domain and EPP lifecycle. We will use existing EPP and SRS facilities, such as the ServerHOLD state, to delay activation (DNS resolution) of purchased domains while our identity verification procedures are executed. The initial registration steps of finding and purchasing a domain will be equivalent to other gTLDs. We will offer registrants differentiated validation levels based upon their intended use of the domain, and they will be required to upload documentation appropriate to their domain type. Artemis staff will then validate the documents and measure the application against the .Secure registration policy, effectively guarding against typo-squatters and trademark infringement.


The following classes of domain names will not be available to registrants at Sunrise, Landrush or subsequent periods:

- Classes and groups of names listed in Specification 5 of the new gTLD Registry Agreement.
- Geographic names, also described in Specification 5 as detailed in Q22 and mentioned in Q21.
- Following past gTLD practices, .Secure will reserve its own name, registry operations names and variations of each (i.e. nic.secure, and registry.secure). These will redirect to our website or will be used to support related registry infrastructure services.
- ICANN and Internet standards bodies will have domains related to them reserved in the .Secure namespace. These bodies may request use of these reservations by following a request process we will make publically available at a later date.

The .Secure reserved name list will be published to the general public at least 30 days prior to the start of our Sunrise period to inform registrars, potential registrants and interested end-users.


- The .Secure Registry will also designate a set of “premium names,” which will be set aside for distribution via special mechanisms. Premium names have been a standard feature of gTLD and ccTLD rollouts since 2005. The list of premium names will be published publicly before the Sunrise period begins, so that registrars and potential registrants will know which names have been set aside.

- .Secure will distribute names in a transparent and ethical manner. To this end we will create and enforce ethical distribution policies and procedures. For example, in the case of distribution by auction, insiders (defined as employees and contractors) will be prohibited from participating.

- In Q.29 we discuss rights protection measures at length. .Secure intends to extend it’s use of the Trademark Claims Service to notify mark holders of matching registrations not only through the Sunrise and Landrush periods, but also throughout General Availability.


As required by ICANN and in support of the mission of .Secure we provide several transparent dispute mechanisms to address claims for .Secure domain names. These include:
- We will offer a specific Sunrise Dispute Policy. This dispute procedure will be active during the Sunrise Period for the protection of qualified trademark holders. This is detailed in Question 29.
- We will support the Uniform Dispute Resolution Policy (UDRP) as required by ICANN. This is detailed in Question 29.
- We will comply with the URS specifications in Applicant Guidebook Module 5 to offer a Universal Rapid Suspension service. This is detailed in Question 29.
- Our service provider ARI has provisioned systems to take in and administrate cases as required in ICANN’s Registrar Transfer Dispute Resolutions Policy. We detail this in Question 28.

v. Privacy

One of the key goals of .Secure is to improve the safety of end-users data on the Internet. .Secure domains will be required to adhere to a strict code of conduct that will include industry leading privacy and disclosure requirements. The ubiquitous use of security technologies by .Secure registrants will reduce the risk of privacy breaches by unauthorized access, and our validation requirements and swift action on abuse complaints will help weed out scammers and other malicious actors bent on leveraging a user’s private information for economic gain.

Where required by local law, .Secure will support related and required privacy measures in the display and release of registry related data.

In respect of Article 2.17 in the new gTLD Registry Agreement, our registrars will be required to gain the permission of each registrant for the collection and use of Personal Data as required by the registry. Required uses of data include the publishing of said data in Whois and sharing of such data with outside parties, as required by our contract with ICANN or by lawful order. We will notify the registrars of any intended change to any policies relating the use of this Personal Data.

Similar gTLD applications: (0)

gTLDFull Legal NameE-mail suffixzDetail