.messenger
Is .messenger a real TLD? Who’s applying to run it?
.messenger is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Meta.
A single-company brand name: useful to its owner for product links, not a namespace anyone else can register or trade in.
the applicant itself, as a closed brand namespace for its messaging product; no third-party registrants or resellers in the picture
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet exactly: a short, singular English generic for a real-time messaging channel, open enough that any conversation product or support vendor could put its primary identity on it, and dependent on the category word being read as the function rather than as one company's product.
Also a plain conversation generic bought as a namespace for communication identity, but it is an action word rather than a tool/agent noun, so it invites looser editorial and community uses instead of one clear class of messaging operator.
Same shape of bet — a channel named by its ordinary noun, aimed at providers and anyone branding a messaging service — though the channel it names is an open protocol with many incumbent providers, where the target's noun reads as a single application.
What a .messenger domain is
.messenger is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. One application for it is on ICANN’s Reveal Day list.
Is the .messenger domain extension real yet?
.messenger is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .messenger domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .messenger name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .messenger was .chat, delegated on 4 February 2015.
Is .messenger a real TLD?
Not yet. .messenger is not in the DNS root, so nothing resolves under it. It’s here because .messenger is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Meta · first recordedICANN
“MRHL2653T-T10763 · Meta Registry Holdings LLC · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The verified-facts block records one application for .messenger, by Meta Registry Holdings LLC, ICANN application type: brand, status confirmed. Treated as a brand TLD, the string is a closed namespace: the only realistic buyer is the applicant, so end-use utility is whatever the operator chooses to do with it (short links, support pages, redirects for a messaging product) and resale/aftermarket value is effectively absent because nobody else can register under it. Why not the band above (30-49): that band assumes registrations happening at volume or on price with a thin aftermarket; a brand-type TLD has no public registration channel at all, so there is no volume and no aftermarket to be thin. Why not the band below (1-9): the string is not without a market, because the operator is a plausible active user with a real product name matching the string, and the generic word 'messenger' is clear and memorable enough that a product-link deployment would be understood by non-experts. Analogy (flagged as analogy): earlier-round brand TLDs held by large technology companies have ranged from dormant defensive holdings to modestly deployed link or content namespaces; the modal outcome in my judgment has been limited public visibility rather than primary-identity use, which caps this string near the lower-middle of its band. Main market uncertainty: whether the operator deploys .messenger as a visible product-link or identity surface over the next 5 years, or holds it largely defensively; the score would move within the 10-29 band on that alone. Everything about user base size, link volume, or other brand-TLD deployment statistics is unknown to me under the rules here and is not asserted.