Can you see prosperity in domain names?
A first look at domains per 1,000 inhabitants around the Baltic Sea reveals an intriguing pattern — and an important warning about what our data can and cannot tell us yet.
HostProbe Team
Data notes
4 min read
As HostProbe expands beyond Finland, we are starting to have enough data to ask questions that are a little more interesting than simply: how many domains did we find?
Here is one of them:
How many country-code domain names do we see per 1,000 inhabitants?
We recently assembled datasets for countries around the Baltic Sea and nearby Nordic markets. Comparing those domain counts with population produces a surprisingly wide spread.
| Country | Domains in our dataset | Population (approx.) | Domains / 1,000 people | GDP per capita (approx. USD) |
|---|---|---|---|---|
| Denmark | 1,256,529 | 6.03m | 208.3 | $71,200 |
| Germany | 12,131,292 | 83.47m | 145.3 | $56,100 |
| Sweden | 921,904 | 10.61m | 86.9 | $57,000 |
| Estonia | 116,443 | 1.36m | 85.6 | $31,400 |
| Norway | 386,354 | 5.63m | 68.7 | $86,600 |
| Poland | 2,477,240 | 37.35m | 66.3 | $25,000 |
| Finland | 365,164 | 5.65m | 64.6 | $53,300 |
| Lithuania | 177,780 | 2.89m | 61.6 | $29,400 |
| Latvia | 102,247 | 1.85m | 55.4 | $23,200 |
The first thing that jumps out is Denmark. In the dataset we currently have, there are more than 208 .dk names for every 1,000 Danish inhabitants — roughly one domain for every five people.
Germany is also remarkably domain-dense in our data at about 145 .de names per 1,000 inhabitants.
At the other end of this small sample, Latvia has about 55 .lv names per 1,000 people.
An important warning about these numbers
These are not counts of all registered domains in these countries.
They are counts of unique domain names present in the dataset currently being processed by HostProbe. Right now, we cannot reliably say how complete or representative that source dataset is for every national top-level domain.
That distinction matters enormously.
For example, our source contains 386,354 .no names, while Norway’s registry, Norid, currently reports more than 880,000 registered .no domains. Our present dataset therefore clearly does not represent the complete Norwegian domain universe.
So this table should not be read as authoritative national registry statistics. It is an experiment with the data HostProbe currently has.
And, in a way, discovering the weaknesses of the dataset is part of the experiment too.
Does domain density follow prosperity?
Even with that large caveat, there is an interesting pattern worth watching.
Countries with higher GDP per capita often appear toward the upper end of the domain-density table, while several lower-income countries appear toward the bottom. Denmark is the clearest example. Germany is another.
It would be premature to claim that domains per inhabitant are an economic indicator. Our sample is small, our domain coverage is not yet known well enough, and national domain policies differ.
But the relationship is interesting enough that we want to revisit it as the HostProbe dataset improves.
And then there is Norway
Norway is particularly interesting because it demonstrates another variable: registry policy.
Norway is by far one of the wealthiest countries in this group, yet it does not sit near Denmark at the top of our domain-density ranking.
The .no registry is also unusually restrictive compared with many country-code domains. To register directly under .no, organizations must be registered in Norway and have a Norwegian postal address. An organization may hold at most 100 domains directly under .no. Private individuals must meet Norwegian eligibility requirements and may hold only five.
That does not prove how much those rules reduce Norway’s domain density. Our own incomplete .no coverage makes such a conclusion impossible at this stage.
But it gives us a very good reason not to expect domain counts to follow GDP alone.
Economics matters. Population matters. Registration price probably matters. Registry rules matter. Local Internet culture matters. The popularity of alternatives such as .com matters.
And the quality of our source data certainly matters.
This is why we are building the dataset
This is exactly the sort of question HostProbe should eventually be able to answer properly.
Today these numbers are raw. We have only recently begun processing most of these national datasets, and we are still learning what our source material contains and where its blind spots are.
As coverage improves, we can compare HostProbe observations against registry totals, measure coverage by country, separate second-level domains from deeper hostnames, look at active versus inactive domains, and see whether relationships such as domain density and economic activity survive better data.
So consider this table a snapshot from 20 August 2026, not a finished result.
The interesting part will be coming back to it later and seeing how wrong — or surprisingly right — these first numbers were.