View source for .sexy

{{TLD|
|logo   =
|status = Active
|manager  =
|country   = 
|language =
|translation =
|registryprovider   =
|registrations   =
|date  =
|type   = [[gTLD|Generic]]
|category = [[:Category:Lifestyle New gTLDs|Lifestyle]]
|community  =
|priority = 373 - [[Uniregistry]], Corp.
|keypeople  =
}}

'''.sexy''' is an active [[gTLD]] that was proposed in [[ICANN]]'s [[New gTLD Program]]. [[Uniregistry]] manages the TLD as its [[Registry]] and was the sole applicant.<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref> The proposed application succeeded and was delegated to the [[Root Zone]] on 14 November, 2013.<ref name="delegation">[http://domainincite.com/15051-sexy-and-10-more-gtld-now-in-the-root .sexy and 10 More gTLDs now in the Root, Domain Incite] Retrieved 15 November 2013</ref>

==Objection==
Saudi Arabia's Communications and Information Technology Commission (CITC) filed an objection against the TLD.<ref>[http://www.slate.com/blogs/future_tense/2012/08/16/icann_top_level_domain_applications_saudi_arabia_apparently_objects_to_catholic_gay_bible_.html?from=rss/&wpisrc=newsletter_slatest Saudi Arabia Apparently Objects to .Catholic, .Gay, .Bible, and 28 More Proposed New Top-Level Domains, slate.com]</ref>
===European Commission Communiqué===
The [[European Commission]] flagged the application for .bio outside of ICANN's defined remediation processes.

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.

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>

===.sx===
The .sx Registry submitted a formal String Confusion objection against the string, though it later asked that its objection be withdrawn.<ref>[http://domainincite.com/13368-uniregistry-is-too-sexy-for-new-gtld-objection Uniregistry is Too Sexy For New gTLD Objection, DomainIncite.com] Published and Retrieved 11 June 2013</ref>

==Independent Objector==
The [[Independent Objector]]  is responsible for determining if a new gTLD application is in the best interest of the Internet community. If not, he or she will file formal objections against a new gTLD application. [[Alain Pellet]], a law professor from the University of Paris and a former member of the United Nations International Law Commission and International Court of Justice, was chosen by ICANN to serve as the sole independent objector for the [[New gTLD Program]] in May, 2012. <ref>[http://www.icann.org/en/news/announcements/announcement-14may12-en.htm Independent Objector for New gTLD Program Selected]. ICANN. Published 2012 May 14.</ref> The position was created by ICANN in accordance with the implementation of the [[New gTLD Program]]. As defined, the IO may be an individual or organization and must not be affiliated with any applicant and must carry out their responsibility without bias.<ref>[http://domainincite.com/wanted-somebody-to-object-to-new-gtlds/ Wanted: somebody to object to new gTLDs]. Domain Incite. Published 2011 November 23. Retrieved 2012 November 15.</ref> 

In December 2012 Mr. Pellet released his first correspondence on actual TLDs, commenting on so-called "Controversial strings". Those strings include: [[.adult]], [[.sex]], [[.porn]], [[.sexy]], [[.hot]], [[.gay]], [[.lgbt]], [[.persiangulf]], [[.vodka]], and [[.wtf]]. A string seemed to have been deemed "controversial" by Mr. Pellet if it received a substantial amount of objections during the public comment period. He addresses each TLD separately and at length, noting the objection, and turning to International law and precedent to determine whether an objection from his point of view, of defending the public interest, is warranted. In each case he concludes that the objections are not supported by international law and that regional, cultural, and personal issues influence the objections rather than broadly accepted treaties, laws, or international cultural trends. He has reserved the right to later object to the strings, but at that time it was deemed that the "controversial strings" are in fact not offensive to the greater public interest and Internet users.<ref>[http://www.independent-objector-newgtlds.org/english-version/the-independent-objector-s-comments-on-controversial-applications/ The Independent Objectors Comments on Controversial Applications, Independent-Objector-NewgTLDs.org]Retrieved 8 Jan 2013</ref>

With regards to .sexy, and the other sex related applications, the [[Independent Objector]] notes that most all objections raise concerns about greater space created for pornographic material, and cite moral, religious, or cultural issues with this fact. Mr. Pellet notes that there is no singular international consensus on the morality of pornographic material and it is one decided by local governments with regards to domestic perceptions and cultural and moral norms. He goes on to note that the creation of a .adult TLD could have the effect of clearly labeling pornographic material, thereby making it easier for offended people to avoid or block such content. He notes that the only widely accepted international norm and treaties on the matter that overlap specifically address the harm or exploitation of children, including with regards to sexual or pornographic scenarios. However, he notes that there is no reason to believe that the creation of a .adult TLD will make it easier to disseminate material that offends in this regard, and it could even prove to more closely regulate pornography and potentially offensive material.<ref>[http://www.independent-objector-newgtlds.org/english-version/the-independent-objector-s-comments-on-controversial-applications/adult-general-comment/ Adult General Comment, Independent-Objector-NewgTLDs.org]</ref>

==Contract Signed==
On Sept 11, 2013 [[Uniregistry]] received a [[Registry Agreeement]] signed by [[ICANN]] for .sexy after passing the [[Initial Evaluation]].<ref>[http://domainincite.com/14450-four-more-new-gtlds-including-sexy-get-contracts Four More New gTLDs Get Contracts, Domain Incite] Retrieved 12 Sept 2013</ref>

==Delegation==
.sexy was delegated to the [[Root Zone]] of the [[DNS]] on November 14, 2013, completing the successful application for the string. [[Uniregistry]] had its first 2 applicants delegated on that day, including this application and [[.tattoo]].<ref name="delegation"></ref>
===Sunrise===
The Registry announced that their [[Sunrise Period]] for the string would begin 11 December 2013 and end on 09 February 2014.<ref>[http://newgtlds.icann.org/en/program-status/sunrise-claims-periods TLD Startup Information, ICANN.org] Retrieved 11 December 2013</ref>

===Acceptable Use Policy===
Uniregistry published their Acceptable Use Policy for the .sexy TLD in January of 2014. The policy states, among other things, that domain names registered under the .sexy TLD shall not contain sexual content or nudity on the front page of the website. This requires .sexy sites with adult content to implement a porn-free front page with age verification, which is already considered good practice for porn websites.<ref>[http://domainincite.com/15637-uniregistry-bans-front-page-porn-in-sexy Uniregistry Bans Front-Page Porn in .sexy, DomainIncite] Retrieved 24 Jan 2014</ref>

==References==
{{reflist}}

[[Category:TLD]]
[[Category:Lifestyle New gTLDs|sexy]]
[[Category:TLDs with Registry Agreements|sexy]]