.sou
Is .sou a real TLD? Who’s applying to run it?
.sou is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is .TOP Registry.
A short pinyin-style word TLD likely to sell on price in China with little brand pull or resale value.
Chinese-market registrants and domain speculators buying short, cheap pinyin-word names, with a secondary Portuguese-speaking "sou" (I am) personal-identity angle
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.
Taking .sou as the Portuguese "I am", this is literally the same bet one language over: a first-person copula sold as a personal-identity namespace to a single language community, where the entire thesis is that individuals will hang their own name in front of a verb instead of buying a category word.
Also a tiny everyday non-English word meaning personhood, pitched to individuals inside one language market as the place for their primary identity, but it is a noun naming people rather than a self-declaration the registrant speaks in the first person.
Same gamble that a minimal grammatical identity word can carry primary-identity registrations, but English-global and far more addressable by brands speaking to customers than by individuals speaking about themselves, which changes the buyer from a person to a marketing department.
What a .sou domain is
.sou 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 .sou domain extension real yet?
.sou 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 .sou domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .sou name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .sou was .soy, delegated on 19 April 2014.
Is .sou a real TLD?
Not yet. .sou is not in the DNS root, so nothing resolves under it. It’s here because .sou is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- .TOP Registry · first recordedICANN
“JBTC2662T-T37661 · Jiangsu Bangning Technology Co., Ltd. · primary”ICANN
“JBTC2662T-T37661 · Jiangsu Bangning Technology Co., Ltd. · replacement string of .sou · Deactivated XL2625T-T82038 · XYZ.COM LLC · primary”ICANN
- Band chosen: 30-49 (usable but limited). The string reads as pinyin for 搜 (search), the root of well-known Chinese search brands, and also as Portuguese 'sou' (I am), so it is short, pronounceable and meaningful in two large language markets; the applicant on the record is .TOP Registry (Jiangsu Bangning Technology Co., Ltd.), a standard (non-brand) application, which informs adoption likelihood toward Chinese-channel distribution. By analogy (flagged as analogy), 2012-round pinyin-word gTLDs such as .wang, .ren and .xin registered at volume through Chinese registrars on promotional pricing, but renewal-driven retention and genuine primary-identity use stayed weak and aftermarket value thin; .top itself is an analogous volume-on-price outcome. That pattern argues against the 50-69 band: there is no sign of sustained, self-explaining primary-identity demand for a 'search' or 'I am' namespace, and the search category in China is dominated by incumbents on their own brands. It is above the 10-29 band because a three-letter dictionary-adjacent string with an experienced volume-distribution channel can plausibly reach meaningful registration counts rather than event-only demand. Main market uncertainty: whether Chinese pinyin TLD demand in the next 5 years converts into real sites and renewals, or remains promotional churn as in the analogy set; secondarily, whether any Lusophone identity use emerges at all. Specific figures for comparable TLDs are unknown here and not asserted.