.muenchen
Is .muenchen a real TLD? Who’s applying to run it?
.muenchen is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Krischenowski GmbH.
A Munich city address in its everyday web spelling: real local appeal for Munich businesses, but .de stays the default and resale is thin.
Munich-based businesses, venues, clubs and local services that want a visibly local address, plus a smaller group of city-pride and regional-brand projects in Bavaria
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.
Identical bet: the German-language endonym of a large German city run as a civic namespace for local businesses and residents who already carry that name, so demand is bounded by the local economy rather than any global audience.
Same bet of one German city's own name as a municipally blessed geographic registry whose pitch is 'we are from here' to small local businesses, not a category word or a company mark.
Same local-language city-name bet aimed at a German-speaking metro's own businesses, differing in that it is a national capital in another country, so the civic authority and market behind it are not quite the same shape.
What a .muenchen domain is
.muenchen is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Places. One application for it is on ICANN’s Reveal Day list.
Is the .muenchen domain extension real yet?
.muenchen 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 .muenchen domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .muenchen name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .muenchen was .koeln, delegated on 5 March 2014.
Is .muenchen a real TLD?
Not yet. .muenchen is not in the DNS root, so nothing resolves under it. It’s here because .muenchen is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Krischenowski GmbH · first recordedICANN
- Band chosen: 30-49, usable but limited. The string is the ASCII ue-transliteration of München, the spelling German speakers already use for the city in URLs and email, so there is no translation gap for the local buyer and the TLD reads instantly as Munich. By analogy (flagged as analogy) to existing German city TLDs such as .berlin, .hamburg and .koeln/.köln, a Munich city TLD should see sustained local registrations from small businesses, hospitality, clubs and local services, and some city-identity use. Those analogues also show the ceiling: in Germany .de remains the primary identity for nearly all serious local businesses, city TLDs are often registered alongside a .de rather than instead of it, and their aftermarkets are thin and mostly limited to a handful of generic local terms. That is why it is not in the 50-69 band: adoption needs explaining relative to .de and primary-identity use is the exception. It is not in the 10-29 band because Munich is a large, affluent city with strong local identity, so demand would be steady and genuinely local rather than event-driven or joke-like. On the record there is one applicant, Krischenowski GmbH, with a confirmed standard-type application (not brand, community or geographic), and the same applicant has .pflege recorded as a replacement string naming this one as primary; no category tag or city-endorsement fact is recorded. A standard application type for a city name leaves the question of institutional backing open, which matters mainly for how fast local adoption follows. Main market uncertainty: whether Munich businesses and institutions treat the city TLD as a real primary identity, or as a secondary defensive add-on to .de, and whether the ue spelling is accepted as the natural form versus a native-script alternative. Registration volumes for the analogues are unknown to me under the rules, so the comparison is qualitative.