radio.nl

Checked 22 October 2026, 15:32 UTC · via 8.8.8.8
iAll checks passed
26 passed 0 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/radio.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/radio.nl returned HTTP 429
    #3

Delegation

info

nodesecure.nl, nodesecure.uk

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
nodesecure.nl, nodesecure.uk
NS in the zone
nodesecure.nl, nodesecure.uk
NameserverAddressesNetwork (AS)Glue
nodesecure.nl192.174.68.102 2001:67c:1bc::102AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT192.174.68.102 2001:67c:1bc::102
nodesecure.uk176.97.158.102 2001:67c:10b8::102AS1921 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: nodesecure.nl, nodesecure.uk.
    #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 .nl, .uk.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
nodesecure.nl 192.174.68.102NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
nodesecure.nl 2001:67c:1bc::102NOERROR, 6 ms, authoritativenoyes / yesrefusedRcodeZero DNS
nodesecure.uk 176.97.158.102NOERROR, 15 ms, authoritativenoyes / yesrefusedreg-wie1
nodesecure.uk 2001:67c:10b8::102NOERROR, 15 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: nodesecure.nl: "RcodeZero DNS"; nodesecure.uk: "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

pass

serial 2024024864 · primary nodesecure.nl

Found

Primary (MNAME)
nodesecure.nl
Contact (RNAME)
hostmaster.interparts.nl
Serial
2024024864
Refresh / retry
43200 s / 7200 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
nodesecure.nl (192.174.68.102)2024024864
nodesecure.nl (2001:67c:1bc::102)2024024864
nodesecure.uk (176.97.158.102)2024024864
nodesecure.uk (2001:67c:10b8::102)2024024864

Checks

  • ✓ Serial 2024024864 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver nodesecure.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@interparts.nl #25
    The SOA RNAME hostmaster.interparts.nl means hostmaster@interparts.nl.
  • ✓ Timestamp serial #26
    The serial 2024024864 is a Unix timestamp (2034-02-20 05:07 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
8032RSASHA256 (8)SHA256 31EE7819B53206B7…yes

DNSKEY in the zone

Key tagRoleAlgorithm
58689ZSK (256)RSASHA256 (8)
8032KSK (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 8032 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ 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

7 records at the apex

Found

Read from
192.174.68.102:53
TypeValueTTL
SOAnodesecure.nl. hostmaster.interparts.nl. 2024024864 43200 7200 1209600 8640086400
NSnodesecure.nl.86400
NSnodesecure.uk.86400
A37.48.79.753600
MX10 forwardmx.autodrs.nl.3600
TXT"v=spf1 include:_spf.google.com include:_spf3.interparts.nl -all"300
TXT"google-site-verification=fa4FTU2jiEgpxswlW4trsdeSqRVSLHwefQJMf0ifkF8"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, 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.
  • 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
  • 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