.han
Is .han a real TLD? Who’s applying to run it?
.han is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Gabia, Inc..
A short Korean and Chinese heritage word; fine for surname or cultural sites, unlikely to be a serious main web address.
people and organisations with the surname Han, Korean or Han-Chinese heritage projects, and fan or cultural sites wanting a short three-letter suffix
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 .han: a vast ethnolinguistic nation's own name for itself, offered as one shared identity namespace that spans many states rather than any single government or company, so it only works if a credible body can claim to speak for the whole people.
Also a people's endonym rather than a place or a product — a stateless-but-named ethnic community buying primary identity in the word it calls itself, with the same custodianship question of who is entitled to run a peoplehood string.
Another insider self-label for a shared ethnocultural identity used worldwide, so the buyer is a member asserting belonging, though it is informal diaspora vocabulary rather than the formal ethnonym of a civilization.
What a .han domain is
.han is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Culture. One application for it is on ICANN’s Reveal Day list.
Is the .han domain extension real yet?
.han 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 .han domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .han name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .han was .arab, delegated on 23 May 2017.
Is .han a real TLD?
Not yet. .han is not in the DNS root, so nothing resolves under it. It’s here because .han is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Gabia, Inc. · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The string carries several meanings at once - a widespread Korean and Chinese surname, the Korean cultural concept 'han', the Han Chinese ethnic group and Han dynasty, a Japanese feudal-domain term, and a pop-culture character name - which makes it memorable but semantically diffuse: 'brand.han' does not tell a visitor what the site is unless the owner is leaning on heritage or a surname. The record shows a single standard (not community or geographic) application by Gabia, Inc. with .san named as a replacement string, which the record treats as a straight namespace play rather than a community-backed identity TLD; nothing on the record ties it to a Korean- or Chinese-language distribution channel. Analogy (flagged): surname TLDs such as .kim have seen modest registrations with little primary-identity use, while .wang drew volume in China largely on promotional pricing with a thin aftermarket; cultural-identity TLDs such as .scot, .cymru, .eus and .bzh sustain small loyal bases but need explaining outside their communities. It is not in the 30-49 band because nothing on the record indicates a price- or channel-driven volume engine, and in English-language markets the string reads as a name fragment rather than a category; it is not in the 1-9 band because the surname, heritage and three-letter brevity give it a real if shallow vanity and community market, and short three-letter strings tend to hold some aftermarket interest. Main market uncertainty: whether the registry positions .han as a Korean identity namespace (the romanised '한') with wide registrar distribution in Korean-language markets, which could lift it into the 30-49 band; whether Han-surname or Han-Chinese demand materialises in Chinese-language markets is unknown and could cut either way.