kinderombudsman.nl

Checked 22 October 2026, 14:02 UTC · via 8.8.8.8
✗Problems found
24 passed 2 warnings 1 failed 7 info

Registration

info

.nl country-code · Bizway B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
Bizway B.V.
Registered
21 January 2012
Last changed
1 April 2020
Status
active
Registry nameservers
ns01.nexthost.nl, ns02.nexthost.nl
RDAP server
https://rdap.sidn.nl/

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
    Expiry date not published
    The registry does not publish the expiry date in RDAP. Check it with your registrar.
    #3
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns01.nexthost.nl, ns02.nexthost.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns01.nexthost.nl, ns02.nexthost.nl
NS in the zone
ns01.nexthost.nl, ns02.nexthost.nl
NameserverAddressesNetwork (AS)Glue
ns01.nexthost.nl185.138.80.142 2a00:1ac1:812:0:185:138:80:1420AS203318 asbizwaynl - Bizway BV, NL AS203318 asbizwaynl - Bizway BV, NL185.138.80.142 2a00:1ac1:812:0:185:138:80:1420
ns02.nexthost.nl217.26.119.170 45.153.84.16 2a05:b000:2000:0:45:153:84:160 2a00:1ac0:1104:0:217:26:119:1700AS35260 IU-Net - Bizway BV, NL AS203318 asbizwaynl - Bizway BV, NL AS203318 asbizwaynl - Bizway BV, NL AS35260 IU-Net - Bizway BV, NL-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.nexthost.nl, ns02.nexthost.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 different networks #10
    The nameservers are spread over 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS203318 (asbizwaynl - Bizway BV, NL): 4 addresses; AS35260 (IU-Net - Bizway BV, NL): 2 addresses.
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

5 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01.nexthost.nl 185.138.80.142NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns01.nexthost.nl 2a00:1ac1:812:0:185:138:80:1420no responsenono / no--
ns02.nexthost.nl 217.26.119.170NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns02.nexthost.nl 45.153.84.16NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns02.nexthost.nl 2a05:b000:2000:0:45:153:84:160NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns02.nexthost.nl 2a00:1ac0:1104:0:217:26:119:1700NOERROR, 13 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns01.nexthost.nl (2a00:1ac1:812:0:185:138:80:1420): read udp [2a01:4f8:1c1c:eebf::1]:42205->[2a00:1ac1:812:0:185:138:80:1420]:53: i/o timeout.
    #14
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2026100101 · primary ns01.nexthost.nl

Found

Primary (MNAME)
ns01.nexthost.nl
Contact (RNAME)
hostmaster.kinderombudsman.nl
Serial
2026100101
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ns01.nexthost.nl (185.138.80.142)2026100101
ns02.nexthost.nl (217.26.119.170)2026100101
ns02.nexthost.nl (45.153.84.16)2026100101
ns02.nexthost.nl (2a05:b000:2000:0:45:153:84:160)2026100101
ns02.nexthost.nl (2a00:1ac0:1104:0:217:26:119:1700)2026100101

Checks

  • ✓ Serial 2026100101 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 30m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.nexthost.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@kinderombudsman.nl #25
    The SOA RNAME hostmaster.kinderombudsman.nl means hostmaster@kinderombudsman.nl.
  • ✓ Date-based serial #26
    The serial 2026100101 follows the YYYYMMDDnn convention (2026-10-01).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC
Signatures valid until
5 November 2026

DNSKEY in the zone

Key tagRoleAlgorithm
3795KSK (257)ECDSAP256SHA256 (13)
16747ZSK (256)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 01:20 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
185.138.80.142:53
TypeValueTTL
SOAns01.nexthost.nl. hostmaster.kinderombudsman.nl. 2026100101 3600 3600 1209600 18003600
NSns02.nexthost.nl.600
NSns01.nexthost.nl.600
A87.233.198.7600
AAAA2001:9a8:a6:0:87:233:198:7600
MX0 kinderombudsman-nl.v-v1.mx.microsoft.600
TXT"MS=ms80255234"600
TXT"v=spf1 redirect=_scb98eg03.sdmarc.net"600
TXT"fUIGsFzrgzteHRqJTFik85OSlY/C8t6WtsEEEr2gBBKfIOduMsRooTH8bHUq6S58hyjtLaFGHYO0c6SwVbsmCA=="600

Checks

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