.ber
Is .ber a real TLD? Who’s applying to run it?
.ber is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is dotBerlin GmbH & Co. KG.
A short Berlin abbreviation that mostly lives in the shadow of the full city name; fun for word hacks, rarely a main address.
berlin-based businesses and creators wanting a shorter city tag than the full-name city domain, plus domain-hack buyers for words ending in "-ber" (num.ber, mem.ber, cham.ber, cy.ber)
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 exactly: a three-letter city shorthand offered as the short companion to the same city's full-name namespace, asking local businesses to adopt an abbreviation as their primary identity while the long form carries the recognition.
Same bet of selling a German geo-abbreviation that already circulates in everyday local use, where demand rests on insiders decoding three letters and outsiders needing an explanation, rather than on a self-evident word.
Also a city initialism pitched as the city's own address for resident businesses and creators, but the abbreviation is globally legible and carries no long-form sibling competing for the same buyer, so the bet is less defensive and less explanation-dependent.
What a .ber domain is
.ber 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 .ber domain extension real yet?
.ber 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 .ber domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .ber name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .ber was .bcn, delegated on 8 July 2015.
Is .ber a real TLD?
Not yet. .ber is not in the DNS root, so nothing resolves under it. It’s here because .ber is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- dotBerlin GmbH & Co. KG · first recordedICANN
“DGCK2644T-T19936 · dotBerlin GmbH & Co. KG · primary”ICANN
- Band chosen: 10-29 (vanity/narrow). The verified facts show a single confirmed application from dotBerlin GmbH & Co. KG, with .bln recorded as its replacement string, which reads as an abbreviated-city companion to an existing full-name city namespace. By analogy (flagged as analogy), short-form city abbreviation TLDs launched beside a long-form sibling, such as the Cologne pairing of a full city name with its airport-code abbreviation, have tended to become a secondary or defensive namespace rather than the identity local businesses actually choose; the full name carries the recognition and the abbreviation gets the leftovers. The string's genuine upside is domain hacks, since "-ber" ends many common English words, but hack-driven demand is thin, resale-oriented and rarely becomes a serious primary identity. Not in 30-49 because there is no visible volume driver or price-led registration motive independent of the long-form sibling, and the brand signal of a three-letter abbreviation is weak outside Berlin; not in 1-9 because Berlin is a major city with an established geo-domain buyer base and the hack angle gives the string some real, if shallow, demand. Main market uncertainty: whether the operator positions .ber as a standalone identity or as a bundled alias to existing full-name city registrations, which would inflate counts while hollowing out primary-identity use. Registry pricing and adoption numbers are unknown.