.codex
Is .codex a real TLD? Who’s applying to run it?
.codex is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is OpenAI.
A brand-flavored word with little use as a web address suffix; outside the applicant's own use, demand would be thin.
the applicant itself as a brand namespace, and otherwise a small set of developer tools, AI projects, archives and game lore sites that like the word
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 single tech company claims an ordinary dictionary noun because its own software product has overwritten the word's everyday meaning, so the namespace serves one product's ecosystem rather than anyone who legitimately uses the word.
Same bet: a Latinate real word taken by one vendor as the identity of a developer-facing platform, where the value rests entirely on the product brand holding and the namespace becoming docs/SDK/service addressing for that platform's users.
Same bet in kind — a pre-existing common word repurposed as a single owner's developer-platform brand with an engineer audience putting its identity there — but weaker because it was a mature licensed platform with a third-party ecosystem rather than a young product still proving the brand sticks.
What a .codex domain is
.codex is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. One application for it is on ICANN’s Reveal Day list.
Is the .codex domain extension real yet?
.codex 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 .codex domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .codex name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .codex was .chrome, delegated on 15 September 2014.
Is .codex a real TLD?
Not yet. .codex is not in the DNS root, so nothing resolves under it. It’s here because .codex is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- OpenAI · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The record shows one confirmed application from OPENAI OPCO, LLC with no category tag and no contention, which reads as a brand-style application (inference from the single-applicant pattern, not a stated fact). As a string, 'codex' is a dictionary word for a bound manuscript and is used loosely in software, gaming and AI contexts as a product or lore term, but it does not function as a natural address suffix the way a role or sector word does; 'name.codex' asks for an explanation in nearly every use. By analogy, single-word open gTLDs with a tech flavor but no suffix semantics (e.g. .codes-type strings) have stayed low-volume with thin aftermarkets, while .dev-type strings became developer standards because the suffix completes a phrase. If this were run as a closed brand space, third-party address value would be nil; the rubric's assumption of general availability is what keeps it off the floor. It is not in 30-49 because there is no evidence or plausible mechanism for volume registrations or a meaningful resale market beyond a brand halo; it is not in 1-9 because the word is memorable, the applicant is a large AI company, and an open .codex would attract some AI/dev-tool and hobbyist registrations plus speculative flips. Main market uncertainty: whether the operator opens the namespace to third parties at all, and if so whether its brand association pulls developer and AI-project demand or instead deters it as 'someone else's brand'.