.safe
Status: | Delegated |
Registry Provider: | Neustar |
Type: | Generic |
Category: | Technology |
More information: |
.safe is a delegated TLD in ICANN's New gTLD Program. Amazon was the sole applicant and it succeeded in delegating the TLD to the Root Zone on 05 December 2015. .SAFE Delegation. Retrieved 10 Dec 2015.[1]
Application Details edit
The following is excerpted from the applicant's response to question # 18:
"The .SAFE registry will benefit registrants and Internet users by offering a stable and secure foundation for online communication and interaction.
What is the goal of your proposed gTLD in terms of areas of specialty, service levels or reputation? Amazon intends for its new .SAFE gTLD to provide a unique and dedicated platform for stable and secure online communication and interaction. The .SAFE registry will be run in line with current industry standards of good registry practice.
What do you anticipate your proposed gTLD will add to the current space in terms of competition, differentiation or innovation? Amazon values the opportunity to be one of the first companies to own a gTLD. A .SAFE registry will: • Provide Amazon with additional controls over its technical architecture, offering a stable and secure foundation for online communication and interaction. • Provide Amazon a further platform for innovation. • Enable Amazon to protect its intellectual property rights.
What goals does your proposed gTLD have in terms of user experience? Amazon intends for its new .SAFE gTLD to provide a unique and dedicated platform for stable and secure online communication and interaction. Provide a complete description of the applicant’s intended registration policies in support of the goals above Amazon’s Intellectual Property group will be responsible for the development, maintenance and enforcement of a Domain Management Policy. The Domain Management Policy will define (i) the rules associated with eligibility and domain name allocation, (ii) the license terms governing the use of a .SAFE domain name, and (iii) the dispute resolution policies for the .SAFE gTLD. Amazon will continually update the Domain Management Policy as needed to reflect Amazon’s business goals and, where appropriate, ICANN consensus policies. Registration of a domain name in the .SAFE registry will be undertaken in four steps: (i) Eligibility Confirmation, (ii) Naming Convention Check, (iii) Acceptable Use Review, and (iv) Registration. All domains in the .SAFE registry will remain the property of Amazon. For example, on the rules of eligibility, each applied for character string must conform to the .SAFE rules of eligibility. Each .SAFE name must:
- be at least 3 characters and no more than 63 characters long
- not contain a hyphen on the 3rd and 4th position (tagged domains)
- contain only letters (a-z), numbers (0-9) and hyphens or a combination of these
- start and end with an alphanumeric character, not a hyphen
- not match any character strings reserved by ICANN
- not match any protected country names or geographical terms
Additionally:
- Internationalized domain names (IDN) may be supported in the .SAFE registry at the second level.
- The .SAFE registry will respect third party intellectual property rights.
- .SAFE domains may not be delegated or assigned to third party organizations, institutions, or individuals.
- All .SAFE domains will carry accurate and up-to-date registration records.
Amazon’s Intellectual Property group reserves the right to revoke a license to use a .SAFE domain name, at any time, if any use of a .SAFE domain name violates the Domain Management Policy. Will your proposed gTLD impose any measures for protecting the privacy of confidential information of registrants or users? Yes. Amazon will implement appropriate privacy policies respecting requirements of local jurisdictions. For example, Amazon is a participant in the Safe Harbor program developed by the U.S. Department of Commerce and the European Union."[2]
References edit
- ↑ Reveal Day 13 June 2012 – New gTLD Applied-For Strings
- ↑ Application Download, gTLDresult.ICANN.org Retrieved 28 Feb 2013