.deploy
Is .deploy a real TLD? Who’s applying to run it?
.deploy is contested: 2 applications for it are on ICANN’s Reveal Day list, as of 7 October 2026. They are WITH YOU MEDYA GIDA SANAYİ VE TİCARET LİMİTED ŞİRKETİ and OpenAI.
A developer-vocabulary verb that reads well on a product URL but has shown little pull as a primary identity.
developer-tool and infrastructure startups, hosting and CI/CD platforms, and indie builders naming a shipping/launch product or a per-app endpoint
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 as .deploy: an unowned piece of software-engineering shorthand that only its own trade reads as meaningful, sold as neutral namespace to developers and dev-tool vendors rather than to any consumer category.
The sibling lifecycle term in the same register — jargon with essentially no meaning outside engineering — betting that a release-pipeline word is valuable because practitioners already type it daily, not because any public audience searches for it.
Also a generic process verb a tooling vendor would put its primary identity on, but the bet is split: it carries a large construction-trade audience alongside the software one, where .deploy is almost purely technical.
What a .deploy domain is
.deploy is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. 2 applications for it are on ICANN’s Reveal Day list.
Is the .deploy domain extension real yet?
.deploy 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 .deploy domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .deploy name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .deploy was .dev, delegated on 18 December 2014.
Is .deploy a real TLD?
Not yet. .deploy is not in the DNS root, so nothing resolves under it. It’s here because .deploy is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
“OOL2614T-T79659 · OPENAI OPCO, LLC · primary · contention set 2026-65 WYMG2568-T96993 · WITH YOU MEDYA GIDA SANAYİ VE TİCARET LİMİTED ŞİRKETİ · primary · contention set 2026-65”ICANN
- Band chosen: 30-49, usable but limited. The string is a verb from core developer vocabulary, so it has semantic utility on an action-style URL (a launch page, a hosted-app endpoint, a CI product), and the developer category is one where a well-run TLD has become a genuine category standard (inference from analogy: .dev). It is not in the 50-69 band because verb/action strings in the same vocabulary (analogy: .run, .build, .codes) have tended to attract modest registration volume and thin aftermarkets rather than sustained primary-identity use; most serious developer-tool companies still choose a noun-style or default namespace and use the verb string, if at all, as a secondary or product URL. It is not in the 10-29 band because the demand is not event-driven or jokey: hosting, deployment and agent-runtime products are a growing buyer pool over the next 5 years, and a short verb that describes exactly what those products do is a plausible identity for some of them. The record shows two confirmed applicants in contention set 2026-65, one being OpenAI OpCo, LLC; this is stated neutrally and only informs adoption likelihood: an operator with a large developer platform could drive end-use registrations through platform-linked naming, which would raise utility but could also narrow the TLD toward a single ecosystem and limit open-market resale. The second applicant also names .atlas as a replacement string on the record, which says nothing about the market for .deploy itself. Main market uncertainty: whether the TLD is operated as an open generic developer namespace or as a platform-tied namespace, since the former yields a .run-like modest open market and the latter yields possibly high end-use volume with little aftermarket.