Difference between revisions of ".dev"

From ICANNWiki
Jump to navigation Jump to search
(actually not true. A few others did too.)
Line 29: Line 29:
 
==Name Collision Issues==
 
==Name Collision Issues==
 
In October 2013 [[ICANN]] released their final assessment and mitigation plan for the [[Name Collision]] issue that was facing the New gTLD program. On 18 November 2013, ICANN announced the applied-for strings that were eligible for an alternative path towards delegation that would allow applicants to proceed without waiting for further mitigation research and plans to be published. 25 strings, including .dev, were not eligible for the alternative path, and will have to wait for more plans to be published before continuing towards delegation.<ref>[https://newgtlds.icann.org/en/announcements-and-media/announcement-2-17nov13-en Announcement 17 Nov 13, ICANN.org] Retrieved 20 Feb 2014</ref>
 
In October 2013 [[ICANN]] released their final assessment and mitigation plan for the [[Name Collision]] issue that was facing the New gTLD program. On 18 November 2013, ICANN announced the applied-for strings that were eligible for an alternative path towards delegation that would allow applicants to proceed without waiting for further mitigation research and plans to be published. 25 strings, including .dev, were not eligible for the alternative path, and will have to wait for more plans to be published before continuing towards delegation.<ref>[https://newgtlds.icann.org/en/announcements-and-media/announcement-2-17nov13-en Announcement 17 Nov 13, ICANN.org] Retrieved 20 Feb 2014</ref>
 
== mandatory HTTPS ==
 
.Dev and .app are the first TLDs to make HTTPS mandatory on all websites in the zone by enforcing [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HSTS] compliance. Google maintains a list known as the [https://hstspreload.org/ HSTS Preload List] which is honored by Chrome and most other modern browsers. Anyone can submit their site to the list, which tells browsers: “insecure HTTP is disabled for this domain”. Non-HTTPS-protected sites on the list therefore not load at all, rather than the typical fallback behavior of displaying an insecure site. The entire .dev zone has [https://hstspreload.org/?domain=dev been added to the HSTS Preload List.]
 
  
 
==References==
 
==References==

Revision as of 23:22, 8 May 2018

Status: Proposed
Registry: Charleston Road Registry Inc.
Registry Backend: Google Corporation
Type: Generic TLD
Category: Technology
Priority #: 530 - Amazon
1065 - Google (Charleston Road Registry Inc.)
nTLDStats
Registrations: 272,269
Parked Domains: 109,917
Parked Domain %: 40.37 %
Important Dates
Delegation: 18 December 2014
General Availability: 28 February 2019

More Information: 1}}

.dev is a proposed generic top level domain name (gTLD) in ICANN's new gTLD expansion program.

Current Applicant

  1. Google (Charleston Road Registry Inc.)- This is one of the 101 new gTLDs filed by the company.[1]

Previous Applicant

  1. Amazon- The company has applied for 76 new gTLDS, including .dev, through its office in Luxembourg.[2]

Amazon Withdraws

Amazon withdrew their application for the .dev TLD in July 2014 after an assumed private deal or auction that left Google as the only applicant for the string. Google also won .drive in the same month against Amazon, while Amazon became the sole applicant for .you and .talk after Google withdrew.[3]

Name Collision Issues

In October 2013 ICANN released their final assessment and mitigation plan for the Name Collision issue that was facing the New gTLD program. On 18 November 2013, ICANN announced the applied-for strings that were eligible for an alternative path towards delegation that would allow applicants to proceed without waiting for further mitigation research and plans to be published. 25 strings, including .dev, were not eligible for the alternative path, and will have to wait for more plans to be published before continuing towards delegation.[4]

References