Overview
- .meet is a generic top-level domain (gTLD) proposed and applied for in ICANN's New gTLD Program by Afilias.
- The string was promoted as a namespace intended for meeting, matchmaking and online dating/companionship services — a dedicated online space to make people and services discoverable for relationship-seeking purposes.
History
- Applicant: Afilias.
- Registry Agreement signed with ICANN: 16 January 2014 (Afilias received the Registry Agreement after completing required processes to become Registry Operator).
- Delegation to the DNS Root Zone: 27 March 2014, completing the successful application and delegation of the .meet string.
- Priority/Reference: listed with a priority number 1511 associated with Afilias in application records.
Usage and Audience
- Target audience described in the application:
- Entrepreneurs and companies in the online dating and companionship industry.
- Registrars and vendors who could build services around .meet registrants.
- Individual registrants seeking discoverability for dating, social or companionship-related identities.
- Intended uses included building portals, secure/confidential identities, matchmaking services, and other industry-specific offerings to differentiate from general-purpose TLDs like .com, .net or .info.
Registration Rules
- General availability: .meet was proposed as an open TLD, generally available to all registrants except during the Sunrise period.
- Registration periods: generally offered for terms of 1 to 10 years, with no registration term greater than ten years.
- Sunrise/initial registrations: names registered during Sunrise may have minimum initial-term requirements (the application gave the example that Sunrise names might require at least a one-year initial registration).
SEO and Brand Impact
- The applicant positioned .meet as a way for services and individuals to differentiate their online presence from generic TLDs, improving discoverability within its niche.
- The application anticipated that as adoption and content in the .meet namespace grew, search engines might modify algorithms to specifically target .meet content, potentially increasing the TLD's visibility and relevance.
Notable Cases or Examples
- Key milestones:
- Registry Agreement with ICANN signed: 16 January 2014.
- Delegated to the DNS Root Zone: 27 March 2014.
- The applicant projected potential growth (an example projection in the application anticipated approximately 15,000 domains under management after three years if adoption followed expectations).
Operator
Charleston Road Registry Inc.
Whois
% IANA WHOIS server
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object
domain: MEET
organisation: Charleston Road Registry Inc.
address: 1600 Amphitheatre Parkway
address: Mountain View CA 94043
address: United States of America (the)
contact: administrative
name: TLD Admin
organisation: Google Inc
address: 111 8th Avenue
address: New York NY 10011
address: United States of America (the)
phone: +1 404 978 8419
fax-no: +1 650 492 5631
e-mail: iana-contact@google.com
contact: technical
name: TLD Engineering
organisation: Google Inc
address: 76 Ninth Avenue, 4th Floor
address: New York NY 10011
address: United States of America (the)
phone: +1 404 978 8419
fax-no: +1 650 492 5631
e-mail: crr-tech@google.com
nserver: NS-TLD1.CHARLESTONROADREGISTRY.COM 2001:4860:4802:32:0:0:0:69 216.239.32.105
nserver: NS-TLD2.CHARLESTONROADREGISTRY.COM 2001:4860:4802:34:0:0:0:69 216.239.34.105
nserver: NS-TLD3.CHARLESTONROADREGISTRY.COM 2001:4860:4802:36:0:0:0:69 216.239.36.105
nserver: NS-TLD4.CHARLESTONROADREGISTRY.COM 2001:4860:4802:38:0:0:0:69 216.239.38.105
nserver: NS-TLD5.CHARLESTONROADREGISTRY.COM 2001:4860:4805:0:0:0:0:69 216.239.60.105
ds-rdata: 56669 8 2 92e856a377729b77ccfa92121fdfb3dc6e82c9adabfef4876765e4027d2d7afb
whois:
status: ACTIVE
remarks: Registration information: https://www.registry.google
created: 2014-03-20
changed: 2025-04-11
source: IANA
