nhmmaastricht.nl

Checked 22 October 2026, 14:42 UTC · via 8.8.8.8
!Passed with warnings
26 passed 1 warning 0 failed 6 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/nhmmaastricht.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/nhmmaastricht.nl returned HTTP 429
    #3

Delegation

info

sec1.rcode0.eu, sec2.rcode0.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
sec1.rcode0.eu, sec2.rcode0.net
NS in the zone
sec1.rcode0.eu, sec2.rcode0.net
NameserverAddressesNetwork (AS)Glue
sec1.rcode0.eu192.174.68.100 2001:67c:1bc::100AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
sec2.rcode0.net176.97.158.100 2001:67c:10b8::100AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: sec1.rcode0.eu, sec2.rcode0.net.
    #6
  • ✓ 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 2 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 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
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .eu, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
sec1.rcode0.eu 192.174.68.100NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
sec1.rcode0.eu 2001:67c:1bc::100NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
sec2.rcode0.net 176.97.158.100NOERROR, 19 ms, authoritativenoyes / yesrefusedreg-wie1
sec2.rcode0.net 2001:67c:10b8::100NOERROR, 19 ms, authoritativenoyes / yesrefusedreg-wie1

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: sec1.rcode0.eu: "RcodeZero DNS"; sec2.rcode0.net: "reg-wie1".
    #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

warn

serial 2026084868 · primary sec1.rcode0.eu

Found

Primary (MNAME)
sec1.rcode0.eu
Contact (RNAME)
hostmaster.spzl.nl
Serial
2026084868
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
30 s

Serial per nameserver

NameserverSerial
sec1.rcode0.eu (192.174.68.100)2026084868
sec1.rcode0.eu (2001:67c:1bc::100)2026084868
sec2.rcode0.net (176.97.158.100)2026084868
sec2.rcode0.net (2001:67c:10b8::100)2026084868

Checks

  • ✓ Serial 2026084868 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 30s is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 1h, expire 7d, negative TTL 30s.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver sec1.rcode0.eu is one of the listed nameservers.
  • ✓ Contact hostmaster@spzl.nl #25
    The SOA RNAME hostmaster.spzl.nl means hostmaster@spzl.nl.
  • ✓ Timestamp serial #26
    The serial 2026084868 is a Unix timestamp (2034-03-16 01:21 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
5 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
40829ECDSAP256SHA256 (13)SHA256 F3911506D59BB4DD…yes

DNSKEY in the zone

Key tagRoleAlgorithm
3889ZSK (256)ECDSAP256SHA256 (13)
53326ZSK (256)ECDSAP256SHA256 (13)
40829KSK (257)ECDSAP256SHA256 (13)

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 40829 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

10 records at the apex

Found

Read from
192.174.68.100:53
TypeValueTTL
SOAsec1.rcode0.eu. hostmaster.spzl.nl. 2026084868 10800 3600 604800 303600
NSsec1.rcode0.eu.300
NSsec2.rcode0.net.300
A178.104.58.30300
AAAA2a01:4f8:1c19:fa2e::1300
MX10 smtp1.spzl.nl.300
MX20 smtp2.spzl.nl.300
TXT"v=spf1 -all"300
TXT"QuoVadis=e008405d-20bb-4106-9320-aa5ce305252b"300
TXT"google-site-verification=ODNlLOTi1nIWeKo9c8MgEwmH38mCZoRII14SIszswBQ"300

Checks

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