Jump to content

.meet

From ICANNWiki
Status: Delegated
Type: Generic
Category: Lifestyle
Priority #: 1511 - Afilias

More information:

.meet is a proposed TLD in ICANN's New gTLD Program. The applicant is Afilias.[1] The proposed application succeeded and was delegated to the Root Zone on 27 March 2014.[2]

Application Details[edit | edit source]

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

"There is currently a proliferation of online dating and companionship services on the Internet. Research shows that there are over 1,500 Internet dating sites in the U.S. alone, creating confusing choices for consumers. Most consumers do not have the time, money, or desire to use the services of more than a few dating services. As a result of this fragmented industry, consumers have limited choices of people to select from when they seek their ideal date or the perfect companion.

The purpose of .MEET is to create an Internet namespace which could be used by visionary entrepreneurs and⁄or the existing online dating and companionship matching providers to become the gathering place on the Internet for many of the more than 40 million online companionship seekers.

This new online namespace could be used to create a .MEET portal destination to facilitate the creation of secure, confidential and easily accessible Internet identities to enable Internet users to find registrars to become registrants of .MEET.

.MEET domains could also appeal to organizations supporting the online dating and companion industry. Online dating and companionship services may be interested in obtaining a .MEET domain to differentiate their services from other businesses that are now using a .COM, .NET, .INFO or other all-purpose TLD.

Registrars could collaborate with leading industry vendors to create new and never-before possible services to leverage the unique and easily identifiable .MEET registrant. Using existing or new offerings, .MEET registrants may want to create personalized, secure and anonymous Internet identities to make themselves easily discoverable by the entire universe of online relationship seekers.

The .MEET domain name and the registrants that obtain the .MEET TLD would help to catalyze a more efficient online dating and companionship service on the Internet. Using simple match-making features, large numbers of .MEET registrants, over time, could motivate visionary entrepreneurs or a visionary industry player to provide a more complete, market-driven service for consumers.

People would quickly come to know that others are actively seeking relationships and they can become easily discoverable under a .MEET domain. Over time, facilitated by new apps and virtual communities, visionary entrepreneurs, registrars and new and existing industry players, using proven social media capabilities, could help .MEET registrants to create more and better content to expand the size of the virtual community they serve. As the .MEET TLD is increasingly adopted and content accrues, search engines could modify their algorithms to specifically target .MEET sites and content, making the TLD even more accessible, relevant and useful. Due to these dynamics, we anticipate that we could have 15,000 domains under management (DUMs) after three years.

.MEET will be an open TLD, generally available to all registrants (except in the Sunrise period).

In general, domains will be offered for periods of one to ten years, but no greater than ten years. Initial registrations made in the Sunrise period may have a minimum number of years required. For example, there may be a policy that all Sunrise names must be registered for an initial term of at least one year."[3]

Contract Signed[edit | edit source]

On 16 January 2014 Afilias received a Registry Agreement signed by ICANN for .meet after passing all the required processes needed to become a Registry Operator for the string.[4]

Delegation and Availability[edit | edit source]

.meet was delegated to the Root Zone of the DNS on 27 March, 2014, completing the successful application for the string.[2]

References[edit | edit source]