.berlin

Generic top-level domain

RDAP + WHOISsold by 2 registrarsPlaces

Register: $77.99first year
Renew: $80.24a year
Transfer: $82.99to move it
Registrars: 2quoting it
Lookup: RDAP + WHOISanswers for it
DNSSEC: Signed3 DS records in the root
Level: Secondmybrand.berlin

Check a name

One command, straight against the registry — no account, no page to load.

Name

Fills the command and the registrar links below in with your own name. The page is static — nothing is looked up here, and nothing you type leaves the browser.

ds mybrand --tld berlin

Add --where for the registrars and the registry's rules, --registry for the server that answered, or --all-info for everything at once.

What it costs

Every published quote in the bundled table, cheapest registration first. The figure ds prints beside .berlin is the mean of the registration column — $77.99, which undercuts 23% of the 881 priced TLDs.

Registrar	Register	Renew	Transfer
101domain.comcheapest	$75.99	$70.49	$82.99
namecheap.com	$79.98	$89.98	—
Mean — what `ds` prints	$77.99	$80.24	$82.99

List prices in US dollars, bundled with the binary and last regenerated 2026-09-09. Promotions, ICANN fees, taxes and premium names all move the real number, and a registry may decline to sell you the name at all. See Prices.

Where to register

2 registrars in the bundled table publish a registration price for .berlin, which is evidence they sell it — nobody prices what they cannot sell. Cheapest first, exactly as ds mybrand --tld berlin --where prints them.

Put a name in the box above and each link becomes that registrar's search for mybrand.berlin, where it publishes one. This list is what the price table knows, not the whole market — see Where to register.

Who can register

No eligibility rule is on file for .berlin, which is not the same as a promise that it is open: the list is hand-maintained and covers the restricted TLDs a registrar is likely to offer you. Check the registry's own page before counting on a name. 81 TLDs do carry a rule — see Who can register.

How `ds` answers for it

RDAP first, WHOIS second — the same order for every TLD. .berlin has both, so RDAP answers and WHOIS is the fallback if it does not.

RDAP: https://rdap.nic.berlin/v1From IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.nic.berlin/v1/domain/mybrand.berlin — a 404 means the name is free.
WHOIS: whois.nic.berlinQueried on port 43, from the bundled whois.json. The name is called free when the reply contains object does not exist — text matching, which is why RDAP is preferred where it exists.

ds mybrand --tld berlin --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .berlin today. See Accuracy notes.

The registry

From IANA's delegation record for .berlin. .berlin is a generic TLD.

Run by: dotBERLIN GmbH & Co. KGBased in Germany. Delegated 2013-12-19, record last updated 2026-05-07.
Registry site: nic.berlinWhere the registry documents .berlin — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: rdap.nic.berlin · whois.nic.berlinWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: a.dns.nic.berlinm.dns.nic.berlinn.dns.nic.berlinThe 3 authoritative servers for the .berlin zone — what the root delegates to. Nothing ds queries directly; they are what makes a registered name resolve.

What it is

Derived from the root zone and ICANN's registry list — each one is a fact with a source.

generic IANA Root Zone Database types it "generic"
new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — see delegated

What it is for

Our reading, not a fact — nothing in the root zone says what a TLD means. Hand-maintained in tld-categories.json.

Places Cities, regions, and parts of the world.

In the root zone

The delegation itself, read out of the root zone — serial 2026090900, on 2026-09-09. The registry section above is IANA's record of what .berlin was delegated to; this is what the root actually answers with when a resolver asks it where .berlin lives.

Delegated to: a.dns.nic.berlin194.0.25.162001:678:20::16
m.dns.nic.berlin194.0.26.52001:67c:10e0::5
n.dns.nic.berlin194.0.24.52001:678:24::5
The 3 name servers the root hands out for .berlin, with the glue addresses that come with them — every one of them answers over IPv6. None of this is what ds queries: these servers know which names exist, not who registered them.
DNSSEC: Signed — 3 DS records in the root
key 7669RSA/SHA-256 · SHA-256169700D66838FC2A4FE16098924C9DA5F3D167DA2697461C144C50D47ED123B0
key 30464RSA/SHA-256 · SHA-2567D53C720E3BFC56F260C98235E5A8CC86565CAE370FE4E24692D3C134208CA94
key 47974RSA/SHA-256 · SHA-256B1DDC962A9293CDA1C2AE8F951C86A8F391248C50751AD61F642D46D0F644B41
Each one is a fingerprint of .berlin's own signing key, published by the root and signed with the root's key — which is how a resolver that trusts only one key can prove an answer under .berlin came from its registry and was not tampered with in transit. It says nothing about who owns a name or whether one is free.

Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net berlin. NS and dig +norec @a.root-servers.net berlin. DS.