rdw.nl

Checked 21 October 2026, 21:24 UTC · via 8.8.8.8
!Passed with warnings
23 passed 1 warning 0 failed 9 info

Registration

info

.nl country-code

Found

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

Delegation

info

ns0067.secondary.cloudflare.com, ns0142.secondary.cloudflare.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns0067.secondary.cloudflare.com, ns0142.secondary.cloudflare.com
NS in the zone
ns0067.secondary.cloudflare.com, ns0142.secondary.cloudflare.com
NameserverAddressesNetwork (AS)Glue
ns0067.secondary.cloudflare.com162.159.32.68 2606:4700:51::a29f:2044AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
ns0142.secondary.cloudflare.com162.159.33.17 2606:4700:59::a29f:2111AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns0067.secondary.cloudflare.com, ns0142.secondary.cloudflare.com.
    #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 (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 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 .com
    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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0067.secondary.cloudflare.com 162.159.32.68NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
ns0067.secondary.cloudflare.com 2606:4700:51::a29f:2044NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
ns0142.secondary.cloudflare.com 162.159.33.17NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
ns0142.secondary.cloudflare.com 2606:4700:59::a29f:2111NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns0067.secondary.cloudflare.com: "2026.10.2"; ns0142.secondary.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #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

info

serial 385666 · primary ns.rdw.nl

Found

Primary (MNAME)
ns.rdw.nl
Contact (RNAME)
domain-registry.rdw.nl
Serial
385666
Refresh / retry
10800 s / 1080 s
Expire
1814400 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns0067.secondary.cloudflare.com (162.159.32.68)385666
ns0067.secondary.cloudflare.com (2606:4700:51::a29f:2044)385666
ns0142.secondary.cloudflare.com (162.159.33.17)385666
ns0142.secondary.cloudflare.com (2606:4700:59::a29f:2111)385666

Checks

  • ✓ Serial 385666 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 18m, expire 21d, negative TTL 5m.
  • i
    Hidden master (not resolvable)
    The primary nameserver ns.rdw.nl is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✓ Contact domain-registry@rdw.nl #25
    The SOA RNAME domain-registry.rdw.nl means domain-registry@rdw.nl.
  • ✓ Counter serial #26
    The serial 385666 is a plain counter.

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
24 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
44474RSASHA256 (8)SHA256 DBC8CE1ADAAEBC59…yes
48169RSASHA256 (8)SHA256 61CA5882D1A1DC37…NO

DNSKEY in the zone

Key tagRoleAlgorithm
2355ZSK (256)RSASHA256 (8)
44474KSK (257)RSASHA256 (8)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • i
    Unused DS records
    These DS records match no key in the zone: key tag 48169 (SHA256). That is normal during a key rollover; otherwise remove them.
    #28
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 96h0m0s and created on demand; the current one was made at 2026-10-20 23:26 UTC and expires at 2026-10-24 23:52 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

15 records at the apex

Found

Read from
162.159.32.68:53
TypeValueTTL
SOAns.rdw.nl. domain-registry.rdw.nl. 385666 10800 1080 1814400 300300
NSns0067.secondary.cloudflare.com.3600
NSns0142.secondary.cloudflare.com.3600
A104.40.151.59300
AAAA2a01:111:f100:9001::1761:91b3300
MX0 rdw-nl.f-v1.mx.microsoft.3600
TXT"bastion365-domain-validation=5de5ee1a53209"3600
TXT"infoblox-domain-mastery=7d150a30f8a23012c44cd16908012b2fa3eab6749924c020a4ad8398a25e3918e3"3600
TXT"v=NTA7516-1;startdate=2019-06;enddate=2029-09;provider=bastionic;ntamx=10 mx.bastion365.net"3600
TXT"v=spf1 ip4:91.213.37.0/24 ip4:81.18.1.6 ip4:81.18.5.116 ip4:168.245.36.241 ip4:168.245.124.147 ip4:46.22.189.51 ip4:80.95.173.197 include:mailplus.nl include:spf.protection.outlook.com include:_spf.mail.services.bastion365.net -all"3600
CAA0 iodef "mailto:serviceteam_sed@rdw.nl"300
CAA0 issue "digicert.com"300
CAA0 issue "entrust.net"300
CAA0 issue "quovadisglobal.com"300
CAA0 issue "sectigo.com"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, MX 1h, NS 1h.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, entrust.net, quovadisglobal.com, sectigo.com.