Symantec Corporation (NASDAQ;SYMC) has won the rights to operate the new gTLD .Security beating Donuts and Defender Security.
You might recall that Defender Security, filed Legal Rights Objections to all other applicants in .Home which was subsequently knocked out by domain collision.
.Security was one of 11 new gTLD’s that are scheduled to be auctioned off in the ICANN Last Resort Auction in December.
There will also be a new gTLD .Secure.
According to its application here is what Symantec Corporation plans for .Security are:
The intended future mission and purpose of the .SECURITY gTLD is to serve as a trusted, hierarchical, secure, and intuitive namespace provided by Symantec for its consumers. Symantec is committed to moving forward with a .SECURITY gTLD application; however at the time of filing this application, there has not been enough time, and currently there is not enough market information available, to fully analyze and evaluate all potential use case options.
Symantec will be analyzing and evaluating other gTLD applications as well as general market adoption to determine short- and long-term potential best-in-class use case options to most effectively serve and enhance Symantec’s online strategy as a leading provider of information security and protection.
As a company, Symantec’s unique focus is to eliminate risks to information, technology, and processes independent of the device, platform, interaction, or location. Symantec helps individuals, small and medium-sized businesses, and global organizations ensure that their information, technology infrastructures, and related processes are protected and easily managed. Symantec delivers solutions that allow customers to access information when they need it and make it available to all of those who should have access to it. The .SECURITY gTLD will be in line with the company’s current focus by providing a trusted, hierarchical, secure, and intuitive namespace.
Symantec intends to initially limit registration and use of domain names within the .SECURITY gTLD to Symantec and its qualified subsidiaries and affiliates. This initial limited use will allow Symantec to establish its operations and achieve full sustainability. This limited distribution coupled with the other requirements set forth in Specification 9 of the template Registry Agreement is intended to exempt Symantec from its annual Code of Conduct Compliance requirements.
After Stage 2 (see below), Symantec will evaluate whether opportunities exist to carry out the business strategy for the gTLD through expansion that continues the sustainable operations of the registry through fee-based registrations to parties other than Symantec and its qualified subsidiaries and affiliates.
Symantec currently plans a three-stage rollout for the .SECURITY gTLD:
Stage 1:
The initial stage of implementation of the gTLD will involve Symantec registering a limited number of .SECURITY second-level domain names.
This initial use will provide Symantec’s IT and security personnel the time to run a number of tests to ensure seamless and secure access using the .SECURITY gTLD domain names, interoperability with various software and Web-based applications, and unbroken and secure use of all names. This initial allocation will also allow the appropriate Symantec staff to coordinate with the internal and external staff responsible for the delegation and setup phases of the .SECURITY gTLD to ensure a proper transition from delegation to full operation.
Stage 2:Once all testing has been successfully completed, Symantec will begin allocating domain names in .SECURITY for more widespread internal corporate use. It is in Stage 2 that Symantec will evaluate expanding the operations of the gTLD to permit registration by other registrants such as licensees and⁄or strategic partners. Should an assessment of its expansion strategy lead to a decision to extend registration rights to other parties, this expansion is currently planned to take place during Stage 3. However, any expansion would be conditioned upon a review of Specification 9 (Registry Code of Conduct) set forth in the template Registry Agreement to ensure compliance with Symantec’s business model.
Stage 3
Based on its evaluations, Symantec will assess and determine whether its business plan and expansion strategy should be augmented by extending registration rights to a broader class of licensees, strategic partners, customers of Symantec, and⁄or other third parties. It is anticipated by Symantec that changes to the domain name industry, and particularly the impact of generic term gTLDs, will take at least five years to be realized and assessed. Any decision to expand the gTLDs beyond corporate, subsidiary, and affiliate use will take into account this experience as well as the technical analysis of potential expansion.
Notwithstanding this potential future expanded use of the .SECURITY namespace beginning in the sixth year of operation, Symantec currently anticipates implementing a throttle mechanism to ensure that any proposed expansion is controlled and responsible.
Specifically, under the throttle mechanism Symantec would cease registration of domain names to this potential expanded universe of registrants if and when Symantec reaches 90 percent of the annual 50,000-domain name transaction currently provided for in the template Registry Agreement. Symantec believes that is prudent to incorporate this “time-out” into the business plan in order to reevaluate potential future growth and the necessary resources to ensure that this growth does not negatively impact the secure and stable operation of the .SECURITY namespace when approaching the 50,000-domain name transaction threshold.
David Walker says
It may well be a selling point if each domain included a Symantec multiple domain name SSL certificate. However, the rate for one starts at $399 for their entry level certificate which lacks features that other companies offer for significantly less, going upwards of $1499 yearly. The certificate might be the point of sink or swim for the registry to meet their 45,000/90% registration quota as the domain could possibly be put to one use, while the certificate is utilized for almost everything else.