.bau
Is .bau a real TLD? Who’s applying to run it?
Nobody has applied for .bau in its own right, as of 7 October 2026. Krischenowski GmbH named .bau as the replacement string of its .frankfurt application.
German for construction: a clear niche for building trades in German-speaking markets, but most firms will stay on country domains.
construction companies, trades, architects and building-materials suppliers in German-speaking markets wanting a short sector-specific address
No applications recorded for this TLD yet.
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 short, everyday German common noun from the built-environment vocabulary, sold to German-speaking trades and property businesses who would put their primary identity on their own language's word rather than an English one.
Same bet in the other language: the construction industry's own category noun as a namespace, bought by contractors and building firms who want the sector word itself, with the whole thesis resting on a trade adopting its generic.
Also a German-language industry generic aimed at the same German commercial buyer in the adjacent property vertical, but it is a long, formal sector term for brokers rather than a short trade word a builder would wear.
What a .bau domain is
.bau is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. Nobody has applied for .bau in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .bau domain extension real yet?
.bau 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 .bau domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .bau name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .bau was .haus, delegated on 31 March 2014.
Is .bau a real TLD?
Not yet. .bau is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .bau as part of an application for another string. Every entry on this page links to its source.
- Krischenowski GmbH · first recordedICANN
“KG2621T-T78385 · Krischenowski GmbH · replacement string of .frankfurt”ICANN
- Band chosen: 30-49, usable but limited. 'Bau' is the everyday German word for construction and building, so the string reads instantly to its target buyer and the construction sector in Germany, Austria and Switzerland is a large, fragmented population of small firms, which is the classic registration base for a sector TLD. The record shows one application, by Krischenowski GmbH, filed as a replacement string for .frankfurt (ICANN Reveal Day list, 7 October 2026); contention on the record is 0 and no category tag is recorded. By analogy (flagged as analogy), the closest precedents are the English-language .build and .construction from the 2012 round and the German-language sector strings .haus and .immo: all found genuine but modest uptake, with registrations driven more by promotional pricing and defensive holds than by primary-identity use, and thin aftermarkets. It is not in the 50-69 band because sustained primary-identity use is unproven for this pattern: DACH businesses lean heavily on their country-code domains, and a .bau address would still need explaining to customers and in print. It is not in the 10-29 band because the string is short, a real industry vocabulary word rather than a joke or event, and names like a surname or town plus .bau are plausible, durable identities for small trade firms, which supports volume registrations rather than shallow event-driven demand. Main market uncertainty: whether German-speaking construction firms treat .bau as a credible primary identity or only as a redirect alongside their existing country-code domain, which decides whether the TLD settles at the top or bottom of this band.