.nl WHOIS Lookup
.nl is the country-code extension of the Netherlands, administered by SIDN. Look up a .nl address and see what the record contains.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.nl WHOIS Lookup: SIDN Records and Their Fields
.nl is the country code extension of the Netherlands, delegated into the root zone on 25 April 1986 and operated by SIDN, a foundation. Queries are answered by whois.domain-registry.nl. In our measurement on 12 August 2026 the reply carried nine fields, and its layout departs from generic practice: the registrar arrives not on one line but as a block complete with address lines. The zone holds a DS record in the root.
The most striking part of the reply is the field that is missing: there is no expiry date. A creation date and a last-updated date are given to the day, yet no line says when the registration ends — and the registry's RDAP endpoint behaves the same way, listing only registration and last-change events. The reply also carries the DNSSEC status of the domain and a line naming who maintains the record.
Lines belonging to the holder never appear in the port 43 reply. On the RDAP side the registrant, admin and technical roles are listed as entities, but their name fields come back closed for privacy — so you see the role structure, not the identities. At the end of the reply sits a note for holders based outside the Netherlands: such registrations use the registry's own address as a domicile address. To compare neighbouring markets, see the .be WHOIS lookup and .de WHOIS lookup pages.
About the .nl extension
- Extension
- .nl
- WHOIS server
- whois.domain-registry.nl
- RDAP endpoint
- https://rdap.sidn.nl
- Registry
- SIDN — Stichting Internet Domeinregistratie Nederland
- Delegated
- 25 April 1986
- Fields measured
- 9 fields (12 August 2026)
- Withheld
- The expiry date and holder details are opened on no channel
- RDAP
- rdap.sidn.nl — roles are listed, name fields come back closed
WHOIS FAQ
Why is there no expiry date in a .nl WHOIS record?
Because SIDN does not publish that field at all. In the 12 August 2026 measurement the reply held a creation date and a last-updated date but no expiry date, and the registry's RDAP endpoint matched it, listing only registration and last-change events. The practical consequence is direct: when a .nl address runs out has to come from your registrar's own record, because WHOIS does not answer that question.
Does a .nl record show the name of the holder?
It does not. The port 43 reply has no line set aside for the registrant at all. On the RDAP endpoint the registrant, admin and technical roles are listed as separate entities, yet their name fields come back closed for privacy. You learn which roles the record carries, not who fills them. For contact, the registrar named plainly in the reply is the address that works.
Why does the registrar span several lines in .nl output?
Because SIDN writes the registrar as an address block rather than a single field: organisation, street, postal code, city and country each arrive on their own line. Generic extensions keep the same information in one field on one line. The difference matters to anyone writing a parser: a reader that assumes one field per line loses the rest of the block in .nl output.
What does the DNSSEC line in a .nl record describe?
It describes whether the domain you queried is signed with DNSSEC, and it carries a short yes or no; in the record we measured the value was no. The extension itself is a separate matter: the .nl zone holds a DS record in the root and is signed. Whether an individual address is signed depends on a setting made at the registrar managing it, and can be checked through DNS.
What changes in the record for holders outside the Netherlands?
A note at the end of the reply covers exactly that: where the holder's address is not in the Netherlands, the registration terms have the registry's own address serve as a domicile address. So the address in such a record is not the person's real one but an institutional point of service. Read without that context the record misleads; here the address line marks a legal service point, not a location.
Why does the .nl result screen show only a few fields?
Because SIDN's block layout differs from generic templates, the parsed panel carries the domain name and the status line. The registrar block, the creation and update dates, the name server list and the DNSSEC line all stand complete in the raw reply tab. No data is lost — it simply does not arrive split into fields, so use the raw output tab on the result screen to read the whole record.
What values does the status line take in a .nl record?
In the record we measured the status read active. SIDN uses a status vocabulary of its own, and its values do not map one to one onto the EPP codes of generic extensions. So do not look for something like clientTransferProhibited in .nl output. The status has to be read in the context of the record itself; transfer or deletion locks are not separately published on this channel.
What does the .nl RDAP endpoint add over WHOIS?
Structure. The rdap.sidn.nl endpoint returns the same record as JSON and lists registrant, admin and technical roles as separate entities, none of which appear in the port 43 reply. Because the name fields come back closed, however, the two channels end up equal on identity. There is no difference on dates either: no expiry appears among the RDAP events, since the registry does not publish that field.