.copilot
Is .copilot a real TLD? Who’s applying to run it?
.copilot is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Microsoft.
A single-company brand domain for Microsoft's Copilot AI line; useful to its owner, but no public registrations or resale market.
the applicant itself and its product teams, as a brand-controlled namespace for Copilot-branded AI products and services; no third-party buyer group
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: an ordinary dictionary word that one platform vendor has made its flagship product identity, so the string only works as a namespace if the public reads the product meaning instead of the generic one, and the owner keeps it closed rather than selling the category.
Same bet again — a plain common noun claimed by a single software giant as the name of its primary computing surface, where the applicant is defending a brand that happens to be a word anyone else could also claim generically.
Shares the forward bet on owning the namespace of an emerging class of automated software agents, but the string stays an open category noun that many vendors could legitimately use, whereas .copilot is that category word already fused to one vendor's brand.
What a .copilot domain is
.copilot 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 .copilot domain extension real yet?
.copilot 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 .copilot domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .copilot name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .copilot was .android, delegated on 12 November 2014.
Is .copilot a real TLD?
Not yet. .copilot is not in the DNS root, so nothing resolves under it. It’s here because .copilot is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Microsoft · first recordedICANN
- Band chosen: 10-29 (vanity/joke/narrow). The record shows one confirmed application, from Microsoft Corporation, and no category tag; the string matches the name of that company's AI assistant product line, so this reads as a dot-brand rather than an open namespace. Judged as it would stand in market, the best-fit buyer is the operator itself, and the value is brand control, defensive coverage and an optional product namespace (by analogy: large-technology dot-brands from the prior round were, in my general understanding, mostly used lightly or held in reserve, with few becoming a visible primary web identity; this is inference from analogy, not a verified fact). It is not in the 30-49 band because there is no volume registration path, no price-driven demand and no aftermarket at all for a closed brand string; it is not in the 1-9 band because the string is attached to a heavily marketed AI product brand, so operator end-use (product endpoints, developer surfaces, campaign addresses) over the next 5 years is plausible and would carry real credibility when used. The generic sense of the word (an assistant, an aviation role, other vendors' assistant products) gives the string AI-category resonance, but under single-brand control that resonance does not translate into addresses anyone else can buy. Main market uncertainty: whether the operator actually routes live product traffic through the TLD or treats it as a defensive hold; the former would push the score toward the upper end of the band, the latter toward the lower end.