What is .meet?
.meet entered the DNS root zone on March 27, 2014, 12 years ago. It came out of ICANN's New gTLD Program, the 2012 application round that grew the root from 22 generic TLDs to well over a thousand.
Charleston Road Registry Inc. operates a large portfolio of 46 TLDs, including .ads, .android, .app, .boo and .cal.
On the technical side, .meet is served by 5 authoritative name servers, every one of them reachable over IPv6. It is also DNSSEC-signed: the root zone carries a DS record for .meet, which lets validating resolvers check its answers cryptographically. Registration data is published over RDAP.
Same registry, other endings
45 other TLDs share this operator.
.meet FAQ
What does .meet mean?
.meet is a generic top-level domain named for the word "meet". It doesn't belong to any country.
What country is .meet?
None. .meet is a generic top-level domain, so it isn't tied to any country.
Who owns the .meet domain extension?
Charleston Road Registry Inc. operates .meet as its registry, under a registry agreement with ICANN.
When was .meet created?
.meet was delegated to the DNS root zone on March 27, 2014.
Is .meet a valid domain?
Yes. .meet is an active top-level domain in the DNS root zone, delegated in 2014, so .meet addresses work in every browser.
Can I buy a .meet domain?
.meet names are sold through ICANN-accredited registrars. Some gTLDs restrict who can register, so read Charleston Road Registry Inc.'s policy if you're unsure.
Is .meet DNSSEC-signed?
Yes, the root zone holds a DS record for .meet.
Sources
Data from IANA root zone version 2026102000. Last changed April 11, 2025. Spotted something wrong? Tell us.
