TLD Health: .fi — DNS Lister

Our answer rate

Not enough data Country

Answer rate: 100.0% of attempted checks returned a definitive answer
Check volume: Minimal (coarse band, not a count)
Mostly answered by: DNS
Still available: 97.7% of answered .fi candidates were unregistered
Last definitive answer: 2026-09-21

Servers we query for .fi

Public registry infrastructure — a whois, a dig NS fi, and one read of IANA’s bootstrap file return the same three values. Listed here for convenience.

WHOIS host: not yet discovered
Authoritative nameservers: g.fi 204.61.216.98

i.fi 194.0.25.30

j.fi 185.159.199.190

k.fi 213.186.229.226

a.fi 193.166.4.1

b.fi 194.146.106.26

c.fi 194.0.11.104

d.fi 77.72.229.253

e.fi 194.0.1.14

f.fi 80.248.170.230
RDAP endpoint: https://rdap.fi/rdap/rdap/

What this measures: the share of our own availability checks that came back with a definitive answer. Nobody else publishes this, because nobody else is running bulk registry lookups at this scale and recording what came back.

What it does not measure: a registry’s uptime or quality. A low rate here can just as easily mean our requests are being rate-limited as it can mean anything about the registry itself.

These are current-state figures, not a history. We keep one record per domain, holding its most recent check — so a TLD that failed hundreds of times and then recovered reads as healthy here. A low rate means checks are failing now; a high one does not mean they always have.

Figures count domains checked, not queries — a domain checked six times counts once. Candidates we generated but never checked are excluded entirely; they are not failures. Snapshot rebuilt 2026-09-27 02:19:47.