onderdelenlijn.nl

Checked 22 October 2026, 15:01 UTC · via 8.8.8.8
!Passed with warnings
20 passed 2 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/onderdelenlijn.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/onderdelenlijn.nl returned HTTP 429
    #3

Delegation

info

mia.ns.cloudflare.com, sevki.ns.cloudflare.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
mia.ns.cloudflare.com, sevki.ns.cloudflare.com
NS in the zone
mia.ns.cloudflare.com, sevki.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
mia.ns.cloudflare.com173.245.58.200 172.64.32.200 108.162.192.200 2803:f800:50::6ca2:c0c8 2a06:98c1:50::ac40:20c8 2606:4700:50::adf5:3ac8AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
sevki.ns.cloudflare.com162.159.44.164 108.162.195.164 172.64.35.164 2606:4700:58::a29f:2ca4 2a06:98c1:50::ac40:23a4 2803:f800:50::6ca2:c3a4AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 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: mia.ns.cloudflare.com, sevki.ns.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 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 12 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

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
mia.ns.cloudflare.com 173.245.58.200NOERROR, 24 ms, authoritativenoyes / yesrefused2026.10.2
mia.ns.cloudflare.com 172.64.32.200NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
mia.ns.cloudflare.com 108.162.192.200NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
mia.ns.cloudflare.com 2803:f800:50::6ca2:c0c8NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
mia.ns.cloudflare.com 2a06:98c1:50::ac40:20c8NOERROR, 20 ms, authoritativenoyes / yesrefused2026.10.2
mia.ns.cloudflare.com 2606:4700:50::adf5:3ac8NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 162.159.44.164NOERROR, 33 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 108.162.195.164NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 172.64.35.164NOERROR, 20 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 2606:4700:58::a29f:2ca4NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 2a06:98c1:50::ac40:23a4NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
sevki.ns.cloudflare.com 2803:f800:50::6ca2:c3a4NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2

Checks

  • ✓ All respond #14
    All 12 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: mia.ns.cloudflare.com: "2026.10.2"; sevki.ns.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

pass

serial 2418138152 · primary mia.ns.cloudflare.com

Found

Primary (MNAME)
mia.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2418138152
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
mia.ns.cloudflare.com (173.245.58.200)2418138152
mia.ns.cloudflare.com (172.64.32.200)2418138152
mia.ns.cloudflare.com (108.162.192.200)2418138152
mia.ns.cloudflare.com (2803:f800:50::6ca2:c0c8)2418138152
mia.ns.cloudflare.com (2a06:98c1:50::ac40:20c8)2418138152
mia.ns.cloudflare.com (2606:4700:50::adf5:3ac8)2418138152
sevki.ns.cloudflare.com (162.159.44.164)2418138152
sevki.ns.cloudflare.com (108.162.195.164)2418138152
sevki.ns.cloudflare.com (172.64.35.164)2418138152
sevki.ns.cloudflare.com (2606:4700:58::a29f:2ca4)2418138152
sevki.ns.cloudflare.com (2a06:98c1:50::ac40:23a4)2418138152
sevki.ns.cloudflare.com (2803:f800:50::6ca2:c3a4)2418138152

Checks

  • ✓ Serial 2418138152 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver mia.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2418138152 is a Unix timestamp (2046-08-17 17:02 UTC).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

13 records at the apex

Found

Read from
173.245.58.200:53
TypeValueTTL
SOAmia.ns.cloudflare.com. dns.cloudflare.com. 2418138152 10000 2400 604800 18001800
NSmia.ns.cloudflare.com.86400
NSsevki.ns.cloudflare.com.86400
A104.18.26.48300
A104.18.27.48300
MX0 onderdelenlijn-nl.mail.protection.outlook.com.300
TXT"MS=ms90975907"300
TXT"google-site-verification=6M00N_BcsHV4LlaSp0t666PSv56ABL7nsI9iCx48TGg"300
TXT"google-site-verification=9sLtc2GDB-YvB6-Apwsh2OmYWfx1rhOp0ByVDz3DJf0"300
TXT"google-site-verification=K-hUU6puYRFu1ySAonBv5-_WDdARsoHxymjfgaGqfdg"300
TXT"google-site-verification=zr2AxR3pTtJjPd1dyzD4j46kByky6MuxfgcUe_1cceM"300
TXT"v=spf1 ip4:87.233.253.128/28 ip4:87.233.133.64/28 ip4:185.22.13.13 ip6:2001:9a8:e9::/64 include:spf.protection.outlook.com -all"300
TXT"yandex-verification: 84f422fb46294487"300

Checks

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