nwz.nl

Checked 22 October 2026, 15:01 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 warnings 0 failed 8 info

Registration

info

.nl country-code

Found

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

Delegation

warn

ns1.zorgring.nl, ns2.zorgring.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.zorgring.nl, ns2.zorgring.nl
NS in the zone
ns1.zorgring.nl, ns2.zorgring.nl
NameserverAddressesNetwork (AS)Glue
ns1.zorgring.nl195.88.136.33AS48997 Zorgring-AS - Stichting Zorgring Noord Holland Noord, NL195.88.136.33
ns2.zorgring.nl195.88.136.34AS48997 Zorgring-AS - Stichting Zorgring Noord Holland Noord, NL195.88.136.34

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.zorgring.nl, ns2.zorgring.nl.
    #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 one network
    all IPv4 addresses are in 195.88.136.0/24. 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 (AS48997 (Zorgring-AS - Stichting Zorgring Noord Holland Noord, NL): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.zorgring.nl 195.88.136.33NOERROR, 10 ms, authoritativenoyes / yesrefusednone
ns2.zorgring.nl 195.88.136.34NOERROR, 10 ms, authoritativenoyes / yesrefusednone

Checks

  • ✓ All respond #14
    All 2 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.zorgring.nl: "none"; ns2.zorgring.nl: "none".
    #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 2026102102 · primary ns1.zorgring.nl

Found

Primary (MNAME)
ns1.zorgring.nl
Contact (RNAME)
postmaster.zorgring.nl
Serial
2026102102
Refresh / retry
300 s / 3600 s
Expire
720000 s
Negative TTL
120 s

Serial per nameserver

NameserverSerial
ns1.zorgring.nl (195.88.136.33)2026102102
ns2.zorgring.nl (195.88.136.34)2026102102

Checks

  • ✓ Serial 2026102102 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 5m is outside 20m–1d; retry 1h should be shorter than refresh 5m; negative caching TTL (minimum) 2m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 5m, retry 1h, expire 200h, negative TTL 2m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.zorgring.nl is one of the listed nameservers.
  • ✓ Contact postmaster@zorgring.nl #25
    The SOA RNAME postmaster.zorgring.nl means postmaster@zorgring.nl.
  • ✓ Date-based serial #26
    The serial 2026102102 follows the YYYYMMDDnn convention (2026-10-21).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
17 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
21364RSASHA256 (8)SHA256 6DA9D08D0AF54DFF…yes

DNSKEY in the zone

Key tagRoleAlgorithm
30210ZSK (256)RSASHA256 (8)
21364KSK (257)RSASHA256 (8)

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 21364 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-17 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-17 16:54 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

Records

info

9 records at the apex

Found

Read from
195.88.136.33:53
TypeValueTTL
SOAns1.zorgring.nl. postmaster.zorgring.nl. 2026102102 300 3600 720000 120300
NSns1.zorgring.nl.300
NSns2.zorgring.nl.300
A20.50.2.25300
MX0 nwz-nl.r-v1.mx.microsoft.300
TXT"v=spf1 ip4:194.13.145.20 ip4:195.88.136.0/23 ip4:31.14.96.33 include:spf.afas.online a:malengo.exception.mx include:_spf.mailplus.nl include:_spf.ezorg.nl include:spf.protection.outlook.com include:spf.use-cocoon.com include:spf2.nwz.nl -all"300
TXT"faxination=fen84647808"300
TXT"MS=ms49995582"300
TXT"l0WX0N1RzcicpwFWgFbNgnPvrrYL70Yi1ebsm5j4BKWd54fFdSjfi1JAUikfiP9oD/PtdHqHgrx6I8PXzit+kw=="300

Checks

  • ✓ TTLs within range #32
    TTLs: A 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