.kai
Is .kai a real TLD? Who’s applying to run it?
.kai is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is XYZ. Juming named .kai as a backup string for its .gem application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A short name-like string that could suit brands called Kai and AI-flavored products, but demand is narrow and resale value thin.
brands, apps and AI assistants that already use Kai as a product name, plus personal sites for people named Kai; a small secondary pull from the string's meanings in Greek, Maori, Japanese and pinyin
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .gem application, shown as deactivated: another applicant applied for the same string or named it as a backup
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 .kai: a bare human name opened as a namespace where the buyer is any individual or family who already carries that name and wants it as their primary identity, so the whole case rests on how many name-bearers will pay for a personal address rather than on any category of commerce.
Also a very short, soft, East-Asian-rooted syllable that doubles as a personal name, sold on affinity and memorability to individuals and small creators rather than to an industry, so it wins or loses on cultural warmth and pronounceability exactly as .kai does.
The string is likewise a common given name with no category meaning, so whoever registers it is putting a person's name on the internet; it is a weaker match only because a long Anglo first name has none of the short cross-cultural pickup that .kai is betting on.
What a .kai domain is
.kai 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 .kai domain extension real yet?
.kai 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 .kai domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .kai name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .kai was .kim, delegated on 23 January 2014.
Is .kai a real TLD?
Not yet. .kai is not in the DNS root, so nothing resolves under it. It’s here because .kai is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Band chosen: 30-49, usable but limited. .kai is a short, pronounceable string that reads as a given name and a brand word, and it ends in 'ai', which gives it a faint AI flavor that some product teams may find attractive as a brandable alternative to the AI namespace. It is not in the 50-69 band because there is no category in which a serious project would reach for .kai without explanation: it is not a word that describes a product class, a place, or an industry, and demand is tied to projects that happen to carry the name Kai or want a name-like suffix. By analogy (flagged as analogy), personal-name and short-word new gTLDs have tended to attract modest volume driven by promotional pricing, with thin aftermarkets and few operating businesses using them as primary identity; by the same analogy, a portfolio operator's short-string launches have often leaned on low-price volume rather than premium brand positioning, which is why the string sits in the volume-or-price band rather than a niche-demand band. It is not in the 10-29 band because the string is a real, widely used given name and brand word with several cross-language meanings (Greek 'and', Maori 'food', Japanese and pinyin syllables), so it has more than event-driven or joke appeal and a plausible set of real primary-identity users. On the record, XYZ.COM LLC holds the confirmed standard application (ID XL2625T-T40935), a second standard application by TechEdge Limited (ID TL2645T-T29492, a replacement string of .gem) is deactivated, and XYZ's .inv application names this .kai application as its primary; these facts inform adoption likelihood only and are stated neutrally. Figures for comparable TLD registration counts, prices or aftermarket sales are unknown here and are deliberately not stated. Main market uncertainty: whether buyers read .kai as an AI-adjacent brandable suffix (which would widen demand to AI startups and product names beyond people called Kai) or purely as a given-name string, which would keep demand narrow over the next 5 years.