.metaglasses
Is .metaglasses a real TLD? Who’s applying to run it?
.metaglasses 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 string for a glasses product line; nobody else can register on it, so it has no open market.
the applicant itself, Meta, for product, support and campaign addresses tied to its glasses line; no third-party 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-scale manufacturer carves out a TLD for one consumer hardware line rather than its corporate name, wagering that the device line has enough standalone identity to be worth its own namespace alongside the house brand.
Same bet again — a single hardware product line owned outright by one company, where the string must carry a device ecosystem (buyers, developers, accessories) and not just a corporate letterhead.
The nearest parallel to the generic-category half of the string: one company trademarking a device-category word and betting the TLD can make the category synonymous with its own product, with the risk that the word reads as a common noun anyone could claim.
What a .metaglasses domain is
.metaglasses 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 .metaglasses domain extension real yet?
.metaglasses 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 .metaglasses domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .metaglasses name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .metaglasses was .xperia, delegated on 5 August 2015.
Is .metaglasses a real TLD?
Not yet. .metaglasses is not in the DNS root, so nothing resolves under it. It’s here because .metaglasses is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Meta · first recordedICANN
“MRHL2653T-T79143 · Meta Registry Holdings LLC · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The record shows one application, filed by Meta Registry Holdings LLC as ICANN application type brand, with no contention; applicant facts are stated neutrally and used only to judge adoption. A brand-type string is normally restricted to the applicant, so the best-fit buyer is the company itself and there is no public registration or aftermarket. It is not in the 30-49 band because that band requires registrations at volume or on price; a closed brand string has neither, and the brand signal belongs to the product name rather than to the TLD. It is not in the 1-9 band because a realistic use exists: a product-line string can carry device, support, pairing or campaign addresses under a memorable name, and the string maps to a concrete consumer product category (smart glasses, increasingly positioned around on-device AI assistants), which gives it more plausible live use than a pure holding-company string. By analogy (flagged as analogy), earlier-round brand TLDs have mostly been used lightly for redirects or microsites, with some operators later retiring them and only a minority adopting the string as a primary identity; the typical outcome has been a defensive or vanity asset rather than a namespace. Main market uncertainty over the next 5 years: whether the applicant routes real product identity (device setup, firmware, account and support flows) through this string or treats it as a defensive hold beside its existing domains, which is the difference between the low and high end of this band.