Jump to content

.gmail: Difference between revisions

From ICANNWiki
Added delegation date to userbox.
m Text replacement - "Category:TLD" to "Category:GTLD"
Tags: Mobile edit Mobile web edit
 
Line 33: Line 33:
{{reflist}}
{{reflist}}


[[Category:TLD]]
[[Category:GTLD]]


__NOTOC__
__NOTOC__

Latest revision as of 18:27, 28 November 2024

Status: Delegated
Registry Provider: Google
Date Implemented: 27 August 2014
Type: Brand TLD

More information:



.gmail is a Brand TLD that was proposed in ICANN's New gTLD Program. The successful applicant is Google (Charleston Road Registry Inc.).[1] It was delegated to the Root Zone of the DNS on the 27th August 2014.[2]

Application Details

The following is excerpted from the applicant's response to question #18:

"The sole purpose of the proposed gTLD, .gmail, is to provide a dedicated Internet space where Google can continue to innovate on its Gmail offerings. The mission of the proposed gTLD is to provide a dedicated domain space in which to enact second-level domains that relate to a group of Gmail accounts associated with individuals or organizations. Second-level domains in the proposed gTLD, .gmail, will automatically be delegated to Googleʹs DNS servers, which will in turn provide authoritative DNS responses pointing the userʹs web browsers and other communication software to Gmail’s servers. The mission of the proposed gTLD is to simplify the Gmail user experience by facilitating the generation of new Gmail addresses, such as john@smith.gmail. This mission will enhance consumer choice by providing new availability in the second-level domain space, expanding Gmail’s namepsace, improving the Gmail user experience, and signaling the kind of communication services available to the owner of an @... Gmail account."[3]

Contract Signed

On 1st May 2014, Google (Charleston Road Registry Inc.) received a Registry Agreement signed by ICANN for .gmail after passing the Initial Evaluation.[4]

Delegation

.gmail was delegated to the Root Zone of the DNS on the 27th August, 2014, completing the successful application for the string.[5]

References