kit.nl

Checked 21 October 2026, 21:22 UTC · via 8.8.8.8
✗Problems found
26 passed 2 warnings 1 failed 4 info

Registration

info

.nl country-code

Found

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

Delegation

pass

ns3.firstfind.nl, ns4.firstfind.nl, ns5.firstfind.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns3.firstfind.nl, ns4.firstfind.nl, ns5.firstfind.net
NS in the zone
ns3.firstfind.nl, ns4.firstfind.nl, ns5.firstfind.net
NameserverAddressesNetwork (AS)Glue
ns3.firstfind.nl5.157.86.222 2a01:b940:1057::53AS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL-
ns4.firstfind.nl5.157.87.222 2a01:b940:1057::54AS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL-
ns5.firstfind.net178.128.248.2 2a03:b0c0:2:d0::1183:f001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns3.firstfind.nl, ns4.firstfind.nl, ns5.firstfind.net.
  • ✓ 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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 2 addresses; AS48635 (CLDIN-NL - Your Hosting B.V., NL): 4 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .net, .nl.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

5 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.firstfind.nl 5.157.86.222NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns3.firstfind.nl 2a01:b940:1057::53NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns4.firstfind.nl 5.157.87.222NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns4.firstfind.nl 2a01:b940:1057::54NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns5.firstfind.net 178.128.248.2no responsenono / no--
ns5.firstfind.net 2a03:b0c0:2:d0::1183:f001NOERROR, 18 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns5.firstfind.net (178.128.248.2): read udp 46.225.38.91:55671->178.128.248.2: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

pass

serial 2026101501 · primary ns3.firstfind.nl

Found

Primary (MNAME)
ns3.firstfind.nl
Contact (RNAME)
hostmaster.firstfind.nl
Serial
2026101501
Refresh / retry
16384 s / 2048 s
Expire
1048576 s
Negative TTL
14400 s

Serial per nameserver

NameserverSerial
ns3.firstfind.nl (5.157.86.222)2026101501
ns3.firstfind.nl (2a01:b940:1057::53)2026101501
ns4.firstfind.nl (5.157.87.222)2026101501
ns4.firstfind.nl (2a01:b940:1057::54)2026101501
ns5.firstfind.net (2a03:b0c0:2:d0::1183:f001)2026101501

Checks

  • ✓ Serial 2026101501 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h33m4s, retry 34m8s, expire 291h16m16s, negative TTL 4h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns3.firstfind.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@firstfind.nl #25
    The SOA RNAME hostmaster.firstfind.nl means hostmaster@firstfind.nl.
  • ✓ Date-based serial #26
    The serial 2026101501 follows the YYYYMMDDnn convention (2026-10-15).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
1 iterations, 1-byte salt
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
50086RSASHA256 (8)SHA256 80C4A3DDBE53D81A…yes

DNSKEY in the zone

Key tagRoleAlgorithm
52288ZSK (256)RSASHA256 (8)
50086KSK (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 50086 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 1 iteration and a 1-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Records

warn

15 records at the apex

Found

Read from
5.157.86.222:53
TypeValueTTL
SOAns3.firstfind.nl. hostmaster.firstfind.nl. 2026101501 16384 2048 1048576 144003600
NSns4.firstfind.nl.3600
NSns3.firstfind.nl.3600
NSns5.firstfind.net.3600
A84.22.103.11186400
AAAA2a02:2770:8:0:21a:4aff:fe17:9f8586400
MX1 kit-nl.mail.protection.outlook.com.60
TXT"tacklephishing-domain-verification=1328e6e365e04234838cb7a028bc3395"14400
TXT"v=spf1 MX include:spf1.kit.nl include:spf.protection.outlook.com include:spfresh.kit.nl include:spf.mailjet.com ip4:74.125.148.0/22 ip4:74.125.244.0/22 ip4:94.23.26.114 ip6:2a00:1a48:7808:101:be76:4eff:fe08:bdff ~all"14400
TXT"apple-domain-verification=wDKinCsePKDYOSLz"14400
TXT"MS=ms12545800"14400
TXT"_rexcqcn1pa9mm9v1j5ex97ih4ie6x08"14400
TXT"kM1jlNng8dp6vTeIxJ1xT39vZYv7pHmRLe5Q4oaRJB7Gxof+XjO7V3ULz4oRAA9Rs610jGABBhofiR998NwztA=="14400
TXT"adobe-idp-site-verification=a8abadadd9d239a49eca714f6b0f46a12e3bfd873f0f0abf0dddf00ed41bdd80"14400
TXT"google-site-verification=P_K5jhdcCUAKGI57ENn3L45d-bPGhoOcQYha-PZ2IkU"14400

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). 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