smallingerland.nl

Checked 22 October 2026, 16:00 UTC · via 8.8.8.8
!Passed with warnings
27 passed 2 warnings 0 failed 4 info

Registration

info

.nl country-code

Found

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

Delegation

info

ns0.claranet.com, ns1.clara.net, ns2.claranet.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns0.claranet.com, ns1.clara.net, ns2.claranet.com
NS in the zone
ns0.claranet.com, ns1.clara.net, ns2.claranet.com
NameserverAddressesNetwork (AS)Glue
ns0.claranet.com185.77.72.50 2001:67c:1088::50AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns1.clara.net185.77.72.11 2001:67c:1088::11AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns2.claranet.com195.245.201.50 2001:a88:0:fffa::50AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns0.claranet.com, ns1.clara.net, ns2.claranet.com.
  • ✓ 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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8426 (CLARANET-AS - Claranet Limited, GB): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.claranet.com 185.77.72.50NOERROR, 6 ms, authoritativenoyes / yesrefused-
ns0.claranet.com 2001:67c:1088::50NOERROR, 7 ms, authoritativenoyes / yesrefused-
ns1.clara.net 185.77.72.11NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns1.clara.net 2001:67c:1088::11NOERROR, 7 ms, authoritativenoyes / yesrefused-
ns2.claranet.com 195.245.201.50NOERROR, 7 ms, authoritativenoyes / yesrefused-
ns2.claranet.com 2001:a88:0:fffa::50NOERROR, 5 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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.
  • ✓ 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 2026100602 · primary ns0.claranet.com

Found

Primary (MNAME)
ns0.claranet.com
Contact (RNAME)
hostmaster.clara.net
Serial
2026100602
Refresh / retry
14400 s / 3600 s
Expire
1728000 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
ns0.claranet.com (185.77.72.50)2026100602
ns0.claranet.com (2001:67c:1088::50)2026100602
ns1.clara.net (185.77.72.11)2026100602
ns1.clara.net (2001:67c:1088::11)2026100602
ns2.claranet.com (195.245.201.50)2026100602
ns2.claranet.com (2001:a88:0:fffa::50)2026100602

Checks

  • ✓ Serial 2026100602 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 4h, retry 1h, expire 20d, negative TTL 2d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns0.claranet.com is one of the listed nameservers.
  • ✓ Contact hostmaster@clara.net #25
    The SOA RNAME hostmaster.clara.net means hostmaster@clara.net.
  • ✓ Date-based serial #26
    The serial 2026100602 follows the YYYYMMDDnn convention (2026-10-06).

DNSSEC

info

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
45191ECDSAP256SHA256 (13)SHA256 1D2AA66BB76EA7E3…yes

DNSKEY in the zone

Key tagRoleAlgorithm
40827ZSK (256)ECDSAP256SHA256 (13)
45191KSK (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 45191 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 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

17 records at the apex

Found

Read from
185.77.72.50:53
TypeValueTTL
SOAns0.claranet.com. hostmaster.clara.net. 2026100602 14400 3600 1728000 1728003600
NSns0.claranet.com.3600
NSns1.clara.net.3600
NSns2.claranet.com.3600
A37.200.85.24120
AAAA2a07:5201:1::3:2120
MX0 smallingerland-nl.w-v1.mx.microsoft.120
TXT"wKpCbwFP9Lq7cSFRDjCIxFEUN36lCjXtCUtIcVVdYUYcOuAtMjCpRQFkNuXNPDjL"120
TXT"MS=ms59197609"120
TXT"google-site-verification=IvknnGwTeWl11ZWXNAj_Du4IB0-jT1elb8XgZETYuA0"120
TXT"apple-domain-verification=W8QICcN3Qe6itaLm"120
TXT"v=spf1 mx a ip4:87.249.113.147 ip4:95.97.105.170 ip4:87.249.113.154 ip4:212.178.158.2 ip4:80.113.70.194 ip4:195.28.22.134 ip4:195.28.22.97 ip4:80.247.174.68/32 ip4:91.230.244.106 include:spf.protection.outlook.com include:spf.topdesk.net include:spf.eprov" ".nl include:_spf.zivver.com include:spf.pinkprivate.cloud include:spf.simgroephosting.nl include:_spf01.rxfront.nl -all"120
CAA0 issue "sectigo.com"120
CAA0 issue "kpn.com"120
CAA0 issue "thawte.com"120
CAA0 issue "certsign.ro"120
CAA0 issue "digicert.com"120

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (2m), AAAA (2m), MX (2m). Low TTLs are useful just before a planned change.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: sectigo.com, kpn.com, thawte.com, certsign.ro, digicert.com.