.cos
Is .cos a real TLD? Who’s applying to run it?
Nobody has applied for .cos in its own right, as of 7 October 2026. ETHOS DIGITAL PUBLIC BENEFIT CORPORATION named .cos as the replacement string of its .cdn application.
A short, ambiguous three-letter ending with no clear owner meaning; memorable for a few niches but rarely a serious primary address.
cloud-storage and content-delivery vendors, plus cosmetics, cosplay and casual-slang brands wanting a short three-letter suffix
No applications recorded for this TLD yet.
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 almost exactly: a three-letter string that reads as an initialism with several unrelated meanings and no owning constituency, so an open-registry operator has to manufacture demand from shape and price rather than sell to a buyer group that already calls itself that.
Also a three-letter string carrying multiple live readings at once (device, place, person's name, slang), filed as a general open namespace rather than for one trade, though its readings cluster tighter around one industry than .cos's do, giving it a more identifiable registrant base.
The same brevity-as-product bet by an operator with no defined registrant category, but it makes no semantic claim at all, where .cos is sold on having several plausible meanings rather than none.
What a .cos domain is
.cos is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. Nobody has applied for .cos in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .cos domain extension real yet?
.cos is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .cos domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .cos name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .cos was .icu, delegated on 2 May 2015.
Is .cos a real TLD?
Not yet. .cos is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .cos as part of an application for another string. Every entry on this page links to its source.
- ETHOS DIGITAL PUBLIC BENEFIT CORPORATION · first recordedICANN
“EDPB2563-T87820 · ETHOS DIGITAL PUBLIC BENEFIT CORPORATION · replacement string of .cdn”ICANN
- Band chosen: 10-29 (vanity/narrow). The verified facts show .cos on the record as a replacement string for a primary .cdn application by ETHOS DIGITAL PUBLIC BENEFIT CORPORATION, with no category tag and zero contention; that lineage suggests an infrastructure framing ("cos" is used by some vendors as shorthand for cloud object storage), but the string itself carries several competing readings — cosmetics, cosplay, the informal spelling of "because", cosine, and an existing fashion retail brand name — none of which is strong enough to make .cos the obvious choice for any one buyer group. By analogy (flagged as analogy), short ambiguous strings from the 2012 round such as .ooo or .one tended to see demand driven by price promotions and vanity hacks rather than sustained primary-identity use, with thin aftermarkets; .cos looks similar. It is not in the 30-49 band because there is no identifiable registrant category likely to register at volume on its own merits, and the brand signal is diffuse rather than weak-but-present. It is not in the 1-9 band because the string is short, pronounceable, trademark-adjacent in beauty and fashion, and has a plausible infrastructure hook that a determined operator could market to developers. Main market uncertainty: whether the operator positions .cos as a developer/storage namespace (which would compete against established .io/.dev/.cloud habits) or as a consumer beauty/cosplay namespace (which would compete against .beauty/.makeup-style strings and .com), since the two positionings imply very different demand shapes.