.congee
Is .congee a real TLD? Who’s applying to run it?
Nobody is chasing .congee, as of 7 October 2026. One applicant claimed it and is out. We keep the entry on the record either way.
- Journey To The West
A single-dish web address; a few porridge shops and food bloggers might enjoy it, but almost no business needs it.
congee restaurants and chains, Asian-food bloggers, and recipe or delivery brands wanting a novelty dish-specific identity, mostly in East/Southeast Asian and diaspora food markets
In Journey To The West's published portfolio of 323 strings submitted in the ICANN 2026 round. Their catalog line: “A humble rice porridge loved across generations.”
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: a single dish noun that a fragmented base of independent restaurants, delivery shops and recipe publishers would hang their primary identity on, with no single owner able to claim the word.
Same shape of bet — one consumable item that doubles as a shopfront identity for small merchants and enthusiast content — but with a far broader, global registrant pool than a regionally concentrated dish.
The nearest 2012 example of a hyper-narrow single-foodstuff noun where the addressable base of anyone wanting that word as their identity is thin enough that the string works only as a curiosity or a category-capture play, not as a volume registry.
What a .congee domain is
.congee is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Culture. Nobody is chasing .congee today. The applicants that claimed it are out.
Is the .congee domain extension real yet?
.congee 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 .congee domain?
You can’t yet. A .congee name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .congee was .pizza, delegated on 27 August 2014.
Is .congee a real TLD?
Not yet. .congee is not in the DNS root, so nothing resolves under it. It’s here because an applicant claimed .congee and is no longer in it. We keep the entry, and every entry on this page links to its source.
- Journey To The West · now abandonedICANN
- Journey To The West · first recordedJourney To The West Corporation
“.congee · Cuisine · “A humble rice porridge loved across generations.””Journey To The West Corporation
- I place .congee in the 10-29 vanity/narrow band. It is above the 1-9 band because congee is a genuine dish category with real restaurants and food-media brands worldwide, so a small pool of memorable registrations (shop names, blogs, campaign microsites) is plausible over 5 years. It is below the 30-49 band because, by analogy (flagged as analogy) with existing single-food TLDs like .pizza and .coffee — which serve vastly larger merchant categories yet remain modest, price-driven namespaces with thin aftermarkets — a dish far smaller than pizza is unlikely to sustain volume registrations or any brand signal; serious food businesses default to .com or a country code. A further drag: much of the dish's natural market is Chinese-speaking, where the Latin word 'congee' competes with native-script naming, an adoption headwind I infer by analogy from IDN-market dynamics. The applicant is a Beijing portfolio applicant with 323 submitted strings (per the facts block), which suggests broad catalog economics rather than a dedicated adoption push — a neutral fact I use only to temper expectations of category marketing. Main market uncertainty: whether pan-Asian comfort-food branding in Western markets grows enough that dish-name domain hacks (e.g. a chain using a .congee identity) become a fashionable niche.