.metaai
Is .metaai a real TLD? Who’s applying to run it?
.metaai is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Meta.
A closed company-brand TLD: useful only to its one owner as a product address, with no open market or resale value for anyone else.
the applicant's own product, developer and infrastructure teams, who could route an AI assistant's web and app endpoints under a name the company controls end to end; no outside buyer group exists
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: a platform giant takes a parent-brand-derived string for one frontier-technology product line rather than its corporate name, so the TLD only ever means that company's tech offering and only works if the parent's platform reputation already carries developers and enterprise buyers.
Also a single hyperscaler putting its flagship technology-platform product (not the company itself) on a closed TLD aimed at developers and enterprise customers, differing only in that the string is a coined brand word instead of parent brand plus category.
Structurally the identical construction — corporate master brand welded to the category it is operating in — a division-level string nobody but the parent could use, whose whole value depends on pre-existing recognition of the brand half.
What a .metaai domain is
.metaai 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 .metaai domain extension real yet?
.metaai 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 .metaai domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .metaai name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .metaai was .aws, delegated on 25 March 2016.
Is .metaai a real TLD?
Not yet. .metaai is not in the DNS root, so nothing resolves under it. It’s here because .metaai is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Meta · first recordedICANN
“MRHL2653T-T18682 · Meta Registry Holdings LLC · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The record lists one confirmed application of ICANN type 'brand' from Meta Registry Holdings LLC, so this is a single-registrant namespace: no third parties can register, so there is no registration volume, no pricing dynamic and no aftermarket by construction. The string's entire value sits with one owner. Why not 30-49: that band presumes registrations happening at volume or on price with a thin aftermarket; a closed brand TLD has neither, so it cannot reach it regardless of brand strength. Why not 1-9: a well-resourced operator can plausibly use a brand TLD as a genuine primary identity for a flagship product, and by analogy (flagged as analogy) a minority of brand TLDs from the earlier round are in live use for primary properties, which is a realistic market for this owner even if not for the public. The string pairs a globally recognised company name with 'ai', which fits a consumer-facing AI assistant as a canonical address; that keeps it near the top of the band rather than the bottom. Main market uncertainty: whether the owner actually deploys it as a primary identity over the next 5 years or holds it defensively, as (analogy) many brand TLDs have been held with little or no public use; counts of used versus dormant brand TLDs are unknown to me and not in the verified facts. Secondary uncertainty: whether users would treat a two-word company-plus-ai label as a natural address versus the company's existing second-level domains.