groningen.nl

ns1.qsp.nl, ns2.qsp.nl

Found

Parent zone

nl

Delegation from

ns1.dns.nl (194.0.28.53)

NS at the parent

ns1.qsp.nl, ns2.qsp.nl

NS in the zone

ns1.qsp.nl, ns2.qsp.nl

Checks

• i

  2 nameservers

  Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.qsp.nl, ns2.qsp.nl.

  #6
• ✓ Parent and zone agree #7

  The parent delegation and the zone's NS records list the same nameservers.
• !

  Glue differs from the zone

  The addresses at the parent (glue) differ from the addresses in the zone: ns1.qsp.nl (glue 193.254.215.240, zone 193.254.215.240, 2a04:c580:0:f0::1); ns2.qsp.nl (glue 193.254.215.241, zone 193.254.215.241, 2a04:c580:0:f1::1). Update the glue at your registrar.

  #8
• ✓ All names resolve #9

  Every nameserver name has an address and is not an alias.
• !

  Nameservers in one network

  all IPv4 addresses are in 193.254.215.0/24; all IPv6 addresses are in 2a04:c580::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).

  #10
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS12315 (QSP-AS - Quality Service Provider BV, NL): 4 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.

serial 2026102001 · primary ns1.qsp.nl

Found

Primary (MNAME)

ns1.qsp.nl

Contact (RNAME)

domain.qsp.nl

Serial

2026102001

Refresh / retry

3600 s / 3600 s

Expire

604800 s

Negative TTL

3600 s

Serial per nameserver

Checks

• ✓ Serial 2026102001 everywhere #22

  All nameservers serve the same version of the zone.
• !

  Unusual SOA timers

  retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 7d, negative TTL 1h.

  #23
• ✓ Primary is a public nameserver #24

  The primary nameserver ns1.qsp.nl is one of the listed nameservers.
• ✓ Contact domain@qsp.nl #25

  The SOA RNAME domain.qsp.nl means domain@qsp.nl.
• ✓ Date-based serial #26

  The serial 2026102001 follows the YYYYMMDDnn convention (2026-10-20).

Signed, DS published at parent

Found

Validated by resolver

yes

Denial of existence

NSEC3

NSEC3

33 iterations, 8-byte salt

Signatures valid until

19 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 57918 (SHA256), key tag 52952 (SHA256).
• ✓ Modern algorithms #29

  Key algorithms: RSASHA512 (10).
• ✓ Signatures valid until 2026-11-19 #30

  The earliest DNSKEY/SOA signature expires at 2026-11-19 07:02 UTC.
• !

  NSEC3 with extra iterations or salt

  NSEC3 uses 33 iterations and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.

  #31