.helsinki
Generic top-level domain
- Register
- —first year
- Renew
- —a year
- Transfer
- —to move it
- Registrars
- —quoting it
- Lookup
- RDAP + WHOISanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.helsinki
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld helsinkiAdd --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
No registrar in the price table bundled with ds quotes .helsinki, so the CLI prints no figure beside it — one of 927 such TLDs. That is a gap in the table as often as it is a TLD nobody sells. See Prices for supplying your own table with --pricing-file.
Who can register
No eligibility rule is on file for .helsinki, 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. .helsinki has both, so RDAP answers and WHOIS is the fallback if it does not.
- RDAP
https://rdap.identitydigital.services/rdapFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://rdap.identitydigital.services/rdap/domain/mybrand.helsinki— a 404 means the name is free.- WHOIS
whois.nic.helsinkiQueried on port 43, from the bundled whois.json. The name is called free when the reply containsdomain not found— text matching, which is why RDAP is preferred where it exists.
ds mybrand --tld helsinki --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .helsinki today. See Accuracy notes.
The registry
From IANA's delegation record for .helsinki. .helsinki is a generic TLD.
- Run by
- City of HelsinkiBased in Finland. Delegated 2015-12-10, record last updated 2025-08-27.
- Registry site
- www.hel.fiWhere the registry documents .helsinki — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.identitydigital.services · whois.nic.helsinkiWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
a0.nic.helsinkia2.nic.helsinkib0.nic.helsinkic0.nic.helsinkiThe 4 authoritative servers for the .helsinki zone — what the root delegates to. Nothingdsqueries 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.
genericIANA Root Zone Database types it "generic"new-gtldICANN delegated it on or after 2013-10-23, when the 2013 round opened — seedelegated
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 .helsinki was delegated to; this is what the root actually answers with when a resolver asks it where .helsinki lives.
- Delegated to
a0.nic.helsinki65.22.220.332a01:8840:d6::33a2.nic.helsinki65.22.223.332a01:8840:d9::33b0.nic.helsinki65.22.221.332a01:8840:d7::33c0.nic.helsinki65.22.222.332a01:8840:d8::33
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 31639RSA/SHA-256 · SHA-256
069A71EF4B12265A44802FCF51B4531DC3835F8FBB68874FBF3565144A12770D
- key 31639RSA/SHA-256 · SHA-256
Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net helsinki. NS and dig +norec @a.root-servers.net helsinki. DS.