Editing Top-level domain (section)

==Proposed domains==
{{Further|Proposed top-level domain}}

Around late 2000, [[ICANN]] discussed and finally introduced<ref>{{cite web |title=InterNIC FAQs on New Top-Level Domains |publisher=Internic.net |date=2002-09-25 |url=https://www.internic.net/faqs/new-tlds.html |access-date=2013-03-28}}</ref> [[.aero]], [[.biz]], [[.coop]], [[.info]], [[.museum]], [[.name]], and [[.pro]] TLDs. Site owners argued that a similar TLD should be made available for adult and pornographic websites to settle the dispute of obscene content on the Internet, to address the responsibility of US service providers under the US [[Communications Decency Act]] of 1996. Several options were proposed including ''xxx'', ''sex'' and ''adult''.<ref>[https://datatracker.ietf.org/doc/html/rfc3675 RFC 3675:] .sex Considered Dangerous</ref> The [[.xxx]] top-level domain eventually went live in 2011.<ref>{{cite web |title=What is top-level Domain {{!}} TLD meaning - Namecheap |url=https://www.namecheap.com/domains/what-is-a-tld-definition/ |access-date=2023-06-26 |website=namecheap.com}}</ref>

An older proposal consisted of seven new gTLDs: arts, firm, [[.info]], nom, rec, [[.shop]], and [[.web]].<ref>{{cite web |title=(historical) gTLD MoU |url=http://www.gtld-mou.org/docs/faq.html#2.1 |url-status=dead |archive-url=https://web.archive.org/web/20080613083133/http://www.gtld-mou.org/docs/faq.html#2.1 |archive-date=13 June 2008}}</ref> Later [[.biz]], [[.info]], [[.museum]], and [[.name]] covered most of these old proposals.

During the 32nd International Public ICANN Meeting in Paris in 2008, ICANN started a new process of TLD naming policy to take a "significant step forward on the introduction of new generic top-level domains".<ref>{{cite web |title=32nd International Public ICANN Meeting |publisher=ICANN |date=22 June 2008 |url=https://archive.icann.org/en/meetings/paris2008/}}</ref> This program envisioned the availability of many new or already proposed domains, as well as a new application and implementation process.<ref>{{cite web |date=15 June 2009 |title=New gTLD Program |url=https://www.icann.org/en/topics/new-gtld-program.htm |url-status=dead |archive-url=https://web.archive.org/web/20090617071629/https://www.icann.org/en/topics/new-gtld-program.htm |archive-date=17 June 2009 |access-date=15 June 2009 |publisher=ICANN}}</ref> Observers believed that the new rules could result in hundreds of new gTLDs being registered.<ref>[https://circleid.com/posts/86269_icann_approves_overhaul_top_level_domains/ ICANN Board Approves Sweeping Overhaul of Top-level Domains], CircleID, 26 June 2008.</ref>

On 13 June 2012, [[ICANN]] announced nearly 2,000 applications for top-level domains, which began installation throughout 2013.<ref>{{cite web |title=The Top 10 Proposed New Top Level Domains So Far |url=https://www.pcworld.com/article/465250/the_top_10_proposed_new_top_level_domains_so_far.html |access-date=12 June 2012}}</ref><ref>{{cite web |title=Reveal Day 13 June 2012 – New gTLD Applied-For Strings |publisher=Newgtlds.icann.org |url=https://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en |access-date=2013-03-28 |url-status=dead |archive-url=https://web.archive.org/web/20120615092059/https://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en |archive-date=15 June 2012}}</ref> The first seven – ''bike'', ''clothing'', ''guru'', ''holdings'', ''plumbing'', ''singles'', and ''ventures'' – were released in 2014.<ref>{{cite web |title=What the new top-level domains from ICANN mean for you - Digital Trends |website=Digital Trends |date=5 February 2014 |url=https://www.digitaltrends.com/computing/will-new-top-level-domains-change-use-web/}}</ref>

===Rejected domains===
ICANN rejected several proposed domains to include [[.home]] and [[.corp]] due to conflicts regarding gTLDs that are in use in internal networks.

Investigation into the conflicts was conducted at ICANN's request by [[Interisle Consulting]]. The resulting report was to become known as the Name Collision<ref>{{cite web |title=Name Collision |website=ICANN Wiki |url=https://icannwiki.org/Name_Collision |access-date=5 July 2021}}</ref> issue, which was first reported at ICANN 47.<ref>{{cite web |title=ICANN 47 |website=ICANN Wiki |url=https://icannwiki.org/ICANN_47 |access-date=5 July 2021}}</ref>