ICANNWiki

.security: Difference between revisions

← Older edit
MarkWD (talk | contribs)
Bureaucrats, Check users, Interface administrators, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Editors (Semantic MediaWiki), steward, Suppressors, Administrators, Temporary account IP viewers
25,069 edits
VisualWikitext
Disentangled this entry from ".protection"
 
(15 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{TLD|
{{TLD|
|logo  =
|country =  
|status = Proposed
|logo = .s.p.jpg
|manager  =
|introduced=14 May 2015
|country   = International
|tld_status = Active
|language =
|registry = XYZ.COM LLC
|translation =  
|tld_type = gTLD
|stringcontention =
|registryprovider  =
|registrations  =
|date  =
|type  =[[gTLD|Generic]]
|category= [[:Category:Commerce New gTLDs|Commerce]]
|community  =
|priority = 728 - [[Symantec Corporation]]<br>1139 - [[Defender Security Company]]<br>1600 - [[Donuts]] (Fern Trail, LLC)
|keypeople  =
}}
}}


'''.security''' is a proposed [[TLD]] in [[ICANN]]'s [[New gTLD Program]].
'''.security''' is an open generic top-level domain (gTLD) in the 2012 ICANN New gTLD Program. The string was originally applied for by [[Symantec Corporation]] and later assigned to [[XYZ.COM LLC]] (the XYZ Registry). [[CentralNic]] provides the registry back-end. The TLD was delegated to the DNS root on 15 September 2015 and entered general availability on 27 January 2016. <ref name="IANA">[https://www.iana.org/domains/root/db/security.html IANA Root Zone Database: .security]</ref><ref name="ICANNRA">[https://www.icann.org/resources/agreement/security-2015-05-14-en ICANN .security Registry Agreement (14 May 2015)]</ref><ref name="ICANNAssign">[https://www.icann.org/public-comments/xyzcom-proxy-service-2015-12-10-en ICANN Public Comment: Supplementary Registration Proxy Service / Assignment Background (.SECURITY) (L25)]</ref><ref name="DomainInciteBuy">[https://domainincite.com/18808-xyz-buys-security-and-protection-from-symantec DomainIncite: "XYZ buys .security and .protection from Symantec" (24 Jun 2015)]</ref><ref name="ICANNCase">[https://newgtlds.icann.org/sites/default/files/security-protection-us-letter-15sep16-en.pdf ICANN New gTLD Case Study: .SECURITY / .PROTECTION (15 Sep 2016)]</ref><ref name="GoDaddySec">[https://www.godaddy.com/help/about-security-domains-20063 GoDaddy: About .SECURITY domains]</ref>


==Applicants==
== Overview ==
# [[Defender Security Company]]
.security is marketed to organizations whose offerings involve information security, cybersecurity services, identity protection, and physical security (e.g., home or corporate security businesses). Registry marketing has positioned the string as a way to signal trustworthiness or to segment security-related initiatives, microsites, or rebrands. <ref name="NICMkt">[https://nic.security/ Advancing Online Security – The .Security Registry]</ref><ref name="ICANNCase" />
# [[Donuts]] (Fern Trail, LLC) This applicant submitted a [[PIC|Public Interest Commitment]], which can be downloaded [https://gtldresult.icann.org/application-result/applicationstatus/applicationdetails/593 here].
# [[Symantec Corporation]]<ref>[http://gtldresult.icann.org/application-result/applicationstatus/viewstatus Security Status, ICANN.org]</ref>


===European Commission Communiqué===
== Registration Policies ==
The [[European Commission]] flagged all applications for .security outside of ICANN's defined remediation processes.
.security domains are available to the public on a first-come, first-served basis through ICANN-accredited registrars under standard XY​Z Registry policies. There are no inherent eligibility restrictions beyond technical syntax rules and general ICANN/registry compliance obligations. The registry reserves the right to withhold, allocate, or sell reserved and premium names and to take action against abusive registrations. IDNs are supported where offered by the registry/registrar. <ref name="XYZPol" /><ref name="GoDaddySec" />


Just after [[ICANN]]'s [[GAC]] issued its Early Warnings, which are advice given from one GAC member country to an applicant warning it of potential issues within its application, the [[European Commission]] issued a letter to all applicants within the [[New gTLD Program|new gTLD program]]. The letter highlights 58 applications that "could raise issues of compatibility with the existing legislation .. and/or with policy positions and objectives of the European Union." It notes a desire to open a dialogue with each offending applicant.
== See also ==
* [[.protection]]


The Commission specifically notes that this objection is not a part of the GAC Early Warning process, and goes on to note that "the Commission does not consider itself legally bound to [ICANN] processes," given that there is not legal agreement between the two bodies.<ref>[http://domainincite.com/docs/20121127093808906.pdf DomainIncite.com/Docs] Published 27 Nov 2012, Retrieved 11 Dec 2012</ref><ref>[http://domainincite.com/11130-europe-rejects-icanns-authority-as-it-warns-of-problems-with-58-new-gtlds Europe Rejects ICANNs Authority As it Warns of Problems with 58 New gTLDs, DomainIncite.com] Published 27 Nov 2012, Retrieved 11 Dec 2012</ref>
== References ==
 
==References==
{{reflist}}
{{reflist}}
[[Category:TLD]]
[[Category:Commerce New gTLDs|security]]
Retrieved from "https://staging.icannwiki.org/.security"