IP addresses in Netherlands
What an IP address located in Netherlands carries: the registries that allocated its space and how much, the privacy regime, sanctions programmes and FATF list a lookup answers for it, the clock it keeps, and how well free geolocation places a city here. Read from the registries’ statistics and the curated facts files, never from a person.
What the registries record for Netherlands
The five regional Internet registries publish daily statistics of every block they have allocated or assigned, each with the country they recorded for it. These are the rows that name Netherlands as of the statistics dated 2026-09-12. A registry country is what the registrant declared, and it can differ from where an address is used.
| registries | ARIN, RIPE NCC, APNIC |
|---|---|
| ipv4 addresses | 47,947,552 in 6,247 blocks |
| ipv6 ranges | 1,931 |
| autonomous systems | 1,606 |
| allocated between | 1970 and 2026 |
| statistics dated | 2026-09-12 |
| continent | EU |
| is_eu / is_eea | true / true |
| privacy_regime | gdpr |
| sanctions | [] |
| fatf_list | null |
| calling_code | +31 |
| currency | EUR |
| timezone | Europe/Amsterdam |
What a lookup answers for an address here
Every IP lookup that places an address in Netherlands carries the same country facts beside the network: is_eu true, is_eea true, currency EUR and calling_code 31. The three below are facts about the place from curated files that name their sources and dates; none of them is advice and none carries a risk weight.
- Privacy law. the General Data Protection Regulation: a lookup here answers privacy_regime: gdpr.
- Sanctions. No country-related US (OFAC) sanctions programme names Netherlands; a lookup answers sanctions: [].
- FATF. Netherlands is on neither FATF list; a lookup answers fatf_list: null.
- Clock. Europe/Amsterdam — the whole country keeps one clock, so every address here answers that zone.
How well free geolocation places a city in Netherlands
59 of 120 compared addresses in Netherlands were placed in the same city by the database and by the network operator’s own declaration: 49.2 % agreement. That is agreement between two data sources, never ground truth of a person’s location, and it is what grades location_confidence for database-located addresses here.
Measured weekly by re-locating addresses whose operators publish their own location — clouds, relays, VPN servers and RFC 8805 geofeeds — and comparing the database’s city with the declared one. Country-level agreement is far higher everywhere; city-level precision from free data is approximate and should never carry a compliance or identity decision on its own.
Run the lookup
The same fields, with the network, the operator and every flag beside them, for any address:
curl https://spaw.co/api/v1/ip \
-H "Authorization: Bearer sk_live_…" \
-H "Content-Type: application/json" \
-d '{"ip": "203.0.113.9"}'Or try one without a key on the free IP lookup, and read every field in the IP intelligence guide.
Other countries
More free tools
All free toolsNeed this at scale?
The Spaw API runs the same checks plus mailbox-level SMTP verification, batch and bulk endpoints, and list monitoring — 10 free lookups a month, no card required.