.conex
Is .conex a real TLD? Who’s applying to run it?
.conex is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is CONEX SAS.
A company-name string with one applicant; useful to that brand for its own sites, with no open market or resale value expected.
the applicant organization itself, for its own products, portals and partner channels; there is no open buyer group unless the registry chooses to sell names to third parties
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 coined, word-like corporate name with no public recognition, filed by the company itself so the namespace serves only its own identity, portals and partner channels rather than any outside registrant.
Same bet: a short, pronounceable, generic-looking name that is in fact a mid-size non-household engineering company's own trademark, so the only plausible primary identity on it is the applicant's own.
Same bet of a closed single-company namespace for an obscure B2B technical brand, differing only in that the string reads more like a surname or initialism than a coined connectivity-flavoured word.
What a .conex domain is
.conex 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 .conex domain extension real yet?
.conex 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 .conex domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .conex name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .conex was .bostik, delegated on 25 November 2015.
Is .conex a real TLD?
Not yet. .conex is not in the DNS root, so nothing resolves under it. It’s here because .conex is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- CONEX SAS · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The verified record shows a single confirmed application from CONEX SAS, an applicant whose name matches the string; by analogy with prior-round applications of this shape, that pattern usually indicates a single-registrant brand namespace rather than an open TLD (inference from analogy, not a recorded fact). 'Conex' is not a common English dictionary word; it reads as a company name, with a faint echo of 'connect/connection' abbreviations that could give it modest tech or connectivity appeal if it were ever sold openly. It is not in the 30-49 band because, as the string stands, no volume registrations, price-driven demand or aftermarket are plausible: the only likely registrant is the brand, so names cannot be bought or resold by outsiders. It is not in the 1-9 band because the applicant does gain genuine, if narrow, end-use utility: a brand-controlled namespace for its own primary identity, portals and partner links, which analogous brand TLDs from the 2012 round have used for exactly that purpose (analogy; some such TLDs saw real use, many saw little, and a number were voluntarily withdrawn). Over the next 5 years the realistic outcome is a small, closed set of names serving one organization. Main market uncertainty: whether the registry keeps the string closed or opens it to third parties, and whether the 'connect'-like reading gives it any pull with tech buyers if opened; a closed brand namespace sits at the low end of this band, an open short tech string could reach the 30-49 band.