hetnieuweinstituut.nl

Checked 21 October 2026, 21:21 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/hetnieuweinstituut.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/hetnieuweinstituut.nl returned HTTP 429
    #3

Delegation

warn

ns01.on.ek.co, ns02.on.ek.co

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns01.on.ek.co, ns02.on.ek.co
NS in the zone
ns01.on.ek.co, ns02.on.ek.co
NameserverAddressesNetwork (AS)Glue
ns01.on.ek.co194.180.219.10AS199816 AS-Ekco-GAS - Ekco B.V., NL-
ns02.on.ek.co217.77.129.10AS12902 LUNA - Ekco B.V., NL-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.on.ek.co, ns02.on.ek.co.
    #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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12902 (LUNA - Ekco B.V., NL): 1 address; AS199816 (AS-Ekco-GAS - Ekco B.V., NL): 1 address.
  • i
    All nameserver names under .co
    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
ns01.on.ek.co 194.180.219.10NOERROR, 11 ms, authoritativenoyes / yesrefusedEkco Distributed DNS NL-AMS
ns02.on.ek.co 217.77.129.10NOERROR, 12 ms, authoritativenoyes / yesrefused-

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: ns01.on.ek.co: "Ekco Distributed DNS NL-AMS".
    #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 2026040501 · primary ns01.on.ek.co

Found

Primary (MNAME)
ns01.on.ek.co
Contact (RNAME)
hostmaster.on.ek.co
Serial
2026040501
Refresh / retry
10800 s / 3600 s
Expire
3600 s
Negative TTL
604800 s

Serial per nameserver

NameserverSerial
ns01.on.ek.co (194.180.219.10)2026040501
ns02.on.ek.co (217.77.129.10)2026040501

Checks

  • ✓ Serial 2026040501 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    expire 1h is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 1h must be longer than refresh + retry; negative caching TTL (minimum) 7d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 1h, expire 1h, negative TTL 7d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.on.ek.co is one of the listed nameservers.
  • ✓ Contact hostmaster@on.ek.co #25
    The SOA RNAME hostmaster.on.ek.co means hostmaster@on.ek.co.
  • ✓ Date-based serial #26
    The serial 2026040501 follows the YYYYMMDDnn convention (2026-04-05).

DNSSEC

info

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
19912ECDSAP256SHA256 (13)SHA256 FF5D94B6F6DC228F…yes

DNSKEY in the zone

Key tagRoleAlgorithm
19912KSK (257)ECDSAP256SHA256 (13)

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 19912 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 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

warn

9 records at the apex

Found

Read from
194.180.219.10:53
TypeValueTTL
SOAns01.on.ek.co. hostmaster.on.ek.co. 2026040501 10800 3600 3600 6048003600
NSns02.on.ek.co.3600
NSns01.on.ek.co.3600
A75.2.60.530
MX10 hetnieuweinstituut-nl.mail.protection.outlook.com.3600
TXT"v=spf1 a mx ip4:31.3.101.87 ip4:141.138.193.31 ip4:141.138.192.15 ip4:195.93.224.251 ip4:141.138.197.120 ip4:141.138.204.89 include:spf.protection.outlook.com include:spf.jewellabs.net include:relay.mailchannels.net include:servers.mcsv.net -all"60
TXT"MS=ms46222780"60
TXT"apple-domain-verification=fBLbAeN247r3D0B0"60
TXT"google-site-verification=ahvmIg4juBI3s9YIK3U37xf4pGy6JnMTjgVVYHooKqo"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (30s). Low TTLs are useful just before a planned change.
    #32
  • ✓ 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