corendon.nl

.nl country-code · Registrar.eu

Found

TLD

.nl (country-code)

ICANN policies apply

no

Registrar

Registrar.eu

Registered

10 November 1999

Last changed

21 July 2026

Status

locked

Registry nameservers

ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info

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
• ✓ Transfer locked #4

  Registry status: locked.
• ✓ Registry and delegation match #5

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

ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info

Found

Parent zone

nl

Delegation from

ns1.dns.nl (194.0.28.53)

NS at the parent

ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info

NS in the zone

ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info

Checks

• ✓ 4 nameservers #6

  Delegated to ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info.
• ✓ Parent and zone agree #7

  The parent delegation and the zone's NS records list the same nameservers.
• ✓ No glue needed #8

  All nameservers are outside the zone, so no glue records are needed.
• ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

  #11
• ✓ Nameserver names under 4 TLDs #12

  Nameserver names use the TLDs .com, .info, .net, .org.
• ✓ All reachable over IPv6 #13

  Every nameserver has an IPv6 address.

Signed, DS published at parent

Found

Validated by resolver

yes

Denial of existence

NSEC

Signatures valid until

22 October 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 52181 (SHA256).
• ✓ Modern algorithms #29

  Key algorithms: ECDSAP256SHA256 (13).
• ✓ Short-lived signatures (online signing) #30

  Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-20 20:00 UTC and expires at 2026-10-22 22:00 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

24 records at the apex

Found

Read from

13.107.236.9:53

Checks

• ✓ TTLs within range #32

  TTLs: A 15m, MX 15m, NS 2d. The NS TTL at the parent is 1h and in the zone 2d; resolvers may use either.
• ✓ No CNAME at the apex #33

  The zone apex has no CNAME record.
• ✓ No wildcard #34

  Names that don't exist return NXDOMAIN.
• i

  No CAA records

  Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.

  #35