.vienna
Is .vienna a real TLD? Who’s applying to run it?
.vienna is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is domainworx Service & Management GmbH.
A city-name address for Vienna's international-facing businesses and tourism; useful locally, but a thin market beyond that.
tourism operators, hotels, venues, and internationally marketed businesses in Vienna that want an English-language city identity, plus city-branded projects and a small cohort of place-name collectors
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 — a city-geo registry for the exact same city, sold to the same Viennese businesses, institutions and residents who want local identity in the address bar, differing only in which language's name for the city is on the label.
Same structural bet as .vienna: the English exonym of a German-speaking city, wagering that an international-facing spelling is worth owning alongside the native-language string rather than being a mere redirect.
The same city-as-identity bet at capital scale — a municipal/regional registry depending on local civic and commercial buy-in — though as the city's own native name it carries none of the exonym-versus-endonym split that defines .vienna.
What a .vienna domain is
.vienna 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 .vienna domain extension real yet?
.vienna 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 .vienna domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .vienna name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .vienna was .wien, delegated on 3 January 2014.
Is .vienna a real TLD?
Not yet. .vienna is not in the DNS root, so nothing resolves under it. It’s here because .vienna is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- domainworx Service & Management GmbH · first recordedICANN
“DSMG2627T-T95981 · domainworx Service & Management GmbH · primary”ICANN
- Band chosen: 30-49, usable but limited. .vienna is a geographic city string, and by analogy with existing city TLDs (.london, .berlin, .nyc, .paris, .tokyo), city namespaces attract real but bounded registration from local businesses, tourism, and civic projects, with weak aftermarket depth; that inference is from analogy, with no figures asserted. It is not in the 50-69 band because the English exonym competes with the local-language city string (.wien, by analogy an already-delegated namespace serving the same city) and with the national ccTLD, so primary-identity use is likely split and needs explaining to a Viennese buyer; the English name also collides with other places called Vienna, which dilutes the brand signal rather than strengthening it. It is not in the 10-29 band because Vienna is a globally recognized capital with a large tourism and conference economy, so a sustained, non-event-driven trickle of serious hotel, venue, and city-marketing registrations is plausible over five years, which is more than vanity or joke demand. The record shows one confirmed applicant (domainworx Service & Management GmbH) filing it as a geographic name, which, stated neutrally, implies a city-endorsed launch path and likely tourism- or city-aligned positioning; that supports adoption likelihood but does not change the ceiling. Main market uncertainty: whether internationally facing Viennese businesses prefer an English city string over the German one and the ccTLD they already use, which decides whether this is a modest complement or largely redundant.