sleutelstad.nl

Checked 22 October 2026, 15:51 UTC · via 8.8.8.8
✗Problems found
18 passed 2 warnings 1 failed 8 info

Registration

info

.nl country-code

Found

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

Delegation

warn

ns1.sleutelstad.nl, ns2.sleutelstad.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.sleutelstad.nl, ns2.sleutelstad.nl
NS in the zone
ns1.sleutelstad.nl, ns2.sleutelstad.nl
NameserverAddressesNetwork (AS)Glue
ns1.sleutelstad.nl185.10.50.96 2a01:7c8:aaaf:ae:5054:ff:fec4:eebbAS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL185.10.50.96 2a01:7c8:aaaf:ae:5054:ff:fec4:eebb
ns2.sleutelstad.nl185.10.50.104AS20857 TRANSIP-AS - Signet B.V., NL185.10.50.104

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.sleutelstad.nl, ns2.sleutelstad.nl.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.sleutelstad.nl, ns2.sleutelstad.nl.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 185.10.50.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS20857 (TRANSIP-AS - Signet B.V., NL): 3 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 .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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns2.sleutelstad.nl.
    #13

Nameservers

fail

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.sleutelstad.nl 185.10.50.96NOERROR, 12 ms, authoritativenoyes / yesrefusednone
ns1.sleutelstad.nl 2a01:7c8:aaaf:ae:5054:ff:fec4:eebbNOERROR, 14 ms, authoritativenoyes / yesrefusednone
ns2.sleutelstad.nl 185.10.50.104NOERROR, 11 ms, authoritativenono / yesrefusednone

Checks

  • ✓ All respond #14
    All 3 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: ns1.sleutelstad.nl: "none"; ns2.sleutelstad.nl: "none".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns2.sleutelstad.nl (185.10.50.104): dial tcp 185.10.50.104:53: connect: connection refused.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026101504 · primary ns2.sleutelstad.nl

Found

Primary (MNAME)
ns2.sleutelstad.nl
Contact (RNAME)
chris.sleutelstad.nl
Serial
2026101504
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns1.sleutelstad.nl (185.10.50.96)2026101504
ns1.sleutelstad.nl (2a01:7c8:aaaf:ae:5054:ff:fec4:eebb)2026101504
ns2.sleutelstad.nl (185.10.50.104)2026101504

Checks

  • ✓ Serial 2026101504 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 3h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns2.sleutelstad.nl is one of the listed nameservers.
  • ✓ Contact chris@sleutelstad.nl #25
    The SOA RNAME chris.sleutelstad.nl means chris@sleutelstad.nl.
  • ✓ Date-based serial #26
    The serial 2026101504 follows the YYYYMMDDnn convention (2026-10-15).

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

6 records at the apex

Found

Read from
185.10.50.96:53
TypeValueTTL
SOAns2.sleutelstad.nl. chris.sleutelstad.nl. 2026101504 10800 3600 1209600 1080086400
NSns1.sleutelstad.nl.86400
NSns2.sleutelstad.nl.86400
A195.66.134.17486400
MX10 mail.sleutelstad.nl.86400
TXT"v=spf1 +a +mx +a:plsk3.hostingkw.nl include:_spf.mijnwefact.nl -all"86400

Checks

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