tno.nl

.nl country-code · SURF B.V.

Found

TLD

.nl (country-code)

ICANN policies apply

no

Registrar

SURF B.V.

Registered

1 June 1987

Last changed

20 March 2026

Status

active

Registry nameservers

app-dns01.tno.nl, app-dns02.tno.nl, ns1.surfnet.nl

RDAP server

https://rdap.sidn.nl/

Checks

• i

  .nl is a country-code TLD (ccTLD)

  Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.

  #1
• ✓ TLD delegated and signed #2

  .nl is delegated in the root zone and DNSSEC-signed.
• i

  Expiry date not published

  The registry does not publish the expiry date in RDAP. Check it with your registrar.

  #3
• i

  No transfer lock

  The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.

  #4
• ✓ Registry and delegation match #5

  The nameservers registered at the registry are the ones published in DNS.

app-dns01.tno.nl, app-dns02.tno.nl, ns1.surfnet.nl

Found

Parent zone

nl

Delegation from

ns1.dns.nl (194.0.28.53)

NS at the parent

app-dns01.tno.nl, app-dns02.tno.nl, ns1.surfnet.nl

NS in the zone

app-dns01.tno.nl, app-dns02.tno.nl, ns1.surfnet.nl

Checks

• ✓ 3 nameservers #6

  Delegated to app-dns01.tno.nl, app-dns02.tno.nl, ns1.surfnet.nl.
• ✓ Parent and zone agree #7

  The parent delegation and the zone's NS records list the same nameservers.
• ✓ Glue present and correct #8

  Glue is published for the nameservers inside the zone: app-dns01.tno.nl, app-dns02.tno.nl.
• ✓ All names resolve #9

  Every nameserver name has an address and is not an alias.
• ✓ Nameservers in different networks #10

  The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS1103 (SURFNET-NL - SURF B.V., NL): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

  #11
• i

  All nameserver names under .nl

  All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.

  #12
• ✓ All reachable over IPv6 #13

  Every nameserver has an IPv6 address.

6 of 6 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 6 nameserver addresses answered.
• ✓ All authoritative #15

  Every responding nameserver answers authoritatively for the zone.
• ✓ No recursion #16

  The nameservers do not answer recursive queries for other domains.
• i

  Identifying string disclosed

  These nameservers answer version queries with a string that is not a version number: ns1.surfnet.nl: "This is a SURFnet nameserver - dns-beheer@surfnet.nl".

  #17
• ✓ Zone transfers refused #18

  No nameserver allows a zone transfer to the public.
• ✓ TCP supported #19

  All nameservers answer over TCP.
• ✓ EDNS supported #20

  All nameservers support EDNS(0).
• ✓ Public addresses #21

  All nameserver addresses are publicly routable.

Signed, DS published at parent

Found

Validated by resolver

yes

Denial of existence

NSEC

Signatures valid until

1 November 2026

DS at the parent

DNSKEY in the zone

Checks

• ✓ Signed and validated #27

  The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
• ✓ DS matches a key #28

  The DS record at the parent matches a key in the zone: key tag 49157 (SHA256).
• ✓ Modern algorithms #29

  Key algorithms: RSASHA256 (8).
• ✓ Signatures valid until 2026-11-01 #30

  The earliest DNSKEY/SOA signature expires at 2026-11-01 22:15 UTC.
• i

  NSEC

  The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.

  #31