sro.nl

Checked 22 October 2026, 16:11 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 7 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/sro.nl returned HTTP 429

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
    Could not be checked
    The RDAP lookup failed, so this could not be checked: https://rdap.sidn.nl/domain/sro.nl returned HTTP 429
    #3

Delegation

warn

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
NameserverAddressesNetwork (AS)Glue
ns1.qsp.nl193.254.215.240 2a04:c580:0:f0::1AS12315 QSP-AS - Quality Service Provider BV, NL AS12315 QSP-AS - Quality Service Provider BV, NL193.254.215.240
ns2.qsp.nl193.254.215.241 2a04:c580:0:f1::1AS12315 QSP-AS - Quality Service Provider BV, NL AS12315 QSP-AS - Quality Service Provider BV, NL193.254.215.241

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.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.qsp.nl 193.254.215.240NOERROR, 35 ms, authoritativenoyes / yesrefusedundisclosed
ns1.qsp.nl 2a04:c580:0:f0::1NOERROR, 15 ms, authoritativenoyes / yesrefusedundisclosed
ns2.qsp.nl 193.254.215.241NOERROR, 35 ms, authoritativenoyes / yesrefusedundisclosed
ns2.qsp.nl 2a04:c580:0:f1::1NOERROR, 15 ms, authoritativenoyes / yesrefusedundisclosed

Checks

  • ✓ All respond #14
    All 4 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.qsp.nl: "undisclosed"; ns2.qsp.nl: "undisclosed".
    #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.

SOA

pass

serial 2026091602 · primary ns1.qsp.nl

Found

Primary (MNAME)
ns1.qsp.nl
Contact (RNAME)
domain.qsp.nl
Serial
2026091602
Refresh / retry
14400 s / 1800 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.qsp.nl (193.254.215.240)2026091602
ns1.qsp.nl (2a04:c580:0:f0::1)2026091602
ns2.qsp.nl (193.254.215.241)2026091602
ns2.qsp.nl (2a04:c580:0:f1::1)2026091602

Checks

  • ✓ Serial 2026091602 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 30m, expire 7d, negative TTL 1d.
  • ✓ 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 2026091602 follows the YYYYMMDDnn convention (2026-09-16).

DNSSEC

warn

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

Key tagAlgorithmDigestMatches a key
19446RSASHA512 (10)SHA256 6FEDF7B6DAAF9601…yes
21413RSASHA512 (10)SHA256 69F3898D2A08BB61…yes

DNSKEY in the zone

Key tagRoleAlgorithm
21413ZSK (256)RSASHA512 (10)
19446KSK (257)RSASHA512 (10)

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 19446 (SHA256), key tag 21413 (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 17:03 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

Records

info

10 records at the apex

Found

Read from
193.254.215.240:53
TypeValueTTL
SOAns1.qsp.nl. domain.qsp.nl. 2026091602 14400 1800 604800 8640086400
NSns1.qsp.nl.86400
NSns2.qsp.nl.86400
A212.57.57.24286400
AAAA2a02:690:4000::24286400
MX40 d316232.b.ess.de.barracudanetworks.com.86400
MX30 d316232.a.ess.de.barracudanetworks.com.86400
TXT"mandrill_verify.rVADKwCmZBm6c7HO3ApkYg"86400
TXT"v=spf1 ip4:212.57.57.242 ip4:45.139.160.33 ip6:2a02:690:4000::242 ip4:212.57.57.70 include:spf.ess.de.barracudanetworks.com include:spf.afas.online include:spf.mailjet.com include:windows.ppibv.nl include:_spf.axxerion.com include:smtp.dat" "aim.nl include:spf.EU.exclaimer.net include:spf1.serasoft.com include:spf.protection.outlook.com -all"86400
TXT"cisco-ci-domain-verification=3a8a910b9623bfb532c698af459b72621e5bfbb613b1fa9e070775400477b317"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, AAAA 1d, MX 1d, NS 1d. The NS TTL at the parent is 1h and in the zone 1d; 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