.plex
Is .plex a real TLD? Who’s applying to run it?
.plex is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Intercap.
Applied for as a brand-type TLD, so addresses would serve one owner's identity rather than a public market.
the applying organisation and its own products, properties and partners, if the brand-type application on record is run as a closed namespace
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 short everyday English word claimed as the primary identity of one company's consumer media-delivery product, where the whole value rests on customers already saying that word to mean that service rather than its dictionary sense.
Same bet in a narrower register: a clipped near-generic noun used as a tech company's media-library brand, asking a word that sounds like a category to read unmistakably as one product's name.
Same bet at larger scale: a coined short platform brand for home entertainment whose string only works because an existing installed base of users already treats it as a proper name, not a word.
What a .plex domain is
.plex 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 .plex domain extension real yet?
.plex 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 .plex domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .plex name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .plex was .sling, delegated on 10 August 2016.
Is .plex a real TLD?
Not yet. .plex is not in the DNS root, so nothing resolves under it. It’s here because .plex is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Intercap · first recordedICANN
“EDI2665T-T28371 · Endpoint Domains, Inc. · primary IRI2679T-T96997 · Intercap Registry Inc. · replacement string of .wiz · Deactivated NA2626T-T63059 · ShortDot (Ireland) Limited · replacement string of .ask · Deactivated XL2625T-T48604 · XYZ.COM LLC · replacement string of .con · Deactivated”ICANN
- Band chosen: 10-29 (vanity/narrow). The record shows one application, by Intercap Registry Inc., with ICANN application type "brand" and no contention. A brand-type application points to a closed namespace: addresses are used by the applicant for its own identity, not sold to third parties, so there is no public registration volume and no aftermarket. By analogy (flagged as such), dot-brands from the 2012 round mostly saw light internal use, with some operators redirecting a handful of names and others never using the TLD in public; a few used it as a genuine primary identity, which is the ceiling here. The string itself is short, pronounceable and carries a product-name feel (as in "-plex" suffixes), so if it were run as the owner's primary identity it could hold some brand credibility, which is why it sits above 1-9 rather than "no realistic market". It is not in 30-49 because there is no evidence of open registrations at volume or on price, and no third-party buyer group exists under a brand-type model. Main market uncertainty: whether the owner actually migrates its primary identity onto .plex or treats it as a defensive or redirect-only asset; how the namespace would be used is unknown.