kaapsebrouwers.nl

Checked 22 October 2026, 14:01 UTC · via 8.8.8.8
!Passed with warnings
26 passed 3 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/kaapsebrouwers.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/kaapsebrouwers.nl returned HTTP 429
    #3

Delegation

info

ns1.yourdomainprovider.net, ns2.yourdomainprovider.net, ns3.yourdomainprovider.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.yourdomainprovider.net, ns2.yourdomainprovider.net, ns3.yourdomainprovider.net
NS in the zone
ns1.yourdomainprovider.net, ns2.yourdomainprovider.net, ns3.yourdomainprovider.net
NameserverAddressesNetwork (AS)Glue
ns1.yourdomainprovider.net185.88.143.183 2a00:c6c0:0:150:1::1AS47172 Greenhost - Greenhost BV, NL AS47172 Greenhost - Greenhost BV, NL-
ns2.yourdomainprovider.net46.101.153.24 2a03:b0c0:3:d0::124:5001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-
ns3.yourdomainprovider.net104.236.29.251 2604:a880:800:10::9a1:2001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.yourdomainprovider.net, ns2.yourdomainprovider.net, ns3.yourdomainprovider.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 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 4 addresses; AS47172 (Greenhost - Greenhost BV, NL): 2 addresses.
  • i
    All nameserver names under .net
    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

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.yourdomainprovider.net 185.88.143.183NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns1.yourdomainprovider.net 2a00:c6c0:0:150:1::1NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.yourdomainprovider.net 46.101.153.24NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.yourdomainprovider.net 2a03:b0c0:3:d0::124:5001NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3.yourdomainprovider.net 104.236.29.251NOERROR, 93 ms, authoritativenoyes / yesrefused-
ns3.yourdomainprovider.net 2604:a880:800:10::9a1:2001NOERROR, 88 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 2026102001 · primary ns1.yourdomainprovider.net

Found

Primary (MNAME)
ns1.yourdomainprovider.net
Contact (RNAME)
hostmaster.metaregistrar.com
Serial
2026102001
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
120 s

Serial per nameserver

NameserverSerial
ns1.yourdomainprovider.net (185.88.143.183)2026102001
ns1.yourdomainprovider.net (2a00:c6c0:0:150:1::1)2026102001
ns2.yourdomainprovider.net (46.101.153.24)2026102001
ns2.yourdomainprovider.net (2a03:b0c0:3:d0::124:5001)2026102001
ns3.yourdomainprovider.net (104.236.29.251)2026102001
ns3.yourdomainprovider.net (2604:a880:800:10::9a1:2001)2026102001

Checks

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

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
5 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
63928ECDSAP256SHA256 (13)SHA256 22CE2243421AA908…yes

DNSKEY in the zone

Key tagRoleAlgorithm
63928KSK (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 63928 (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.
  • !
    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

12 records at the apex

Found

Read from
185.88.143.183:53
TypeValueTTL
SOAns1.yourdomainprovider.net. hostmaster.metaregistrar.com. 2026102001 3600 3600 1209600 120120
NSns3.yourdomainprovider.net.120
NSns1.yourdomainprovider.net.120
NSns2.yourdomainprovider.net.120
A23.227.38.65120
MX10 filter01.yourdomainprovider.net.120
MX10 filter02.yourdomainprovider.net.120
TXT"google-site-verification=w5Sa4t_aMg-pz67e54sTMPrFkc4Ekxd9DyajF6QFXGM"120
TXT"v=spf1 a mx include:servers.mcsv.net ?all"120
TXT"google-site-verification=do9gy-ndxwr_aojYCXdPQADBlzy5gz3T7jwKOq377wo"120
TXT"brevo-code:0965b5b329796411b02cdad93fcc2fb3"120
TXT"google-site-verification=ZuG6bIN_QzkKtIU3jl2qQEGpGfyV4bkh8DJrQPHmKBQ"120

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (2m), MX (2m), NS (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 2m; resolvers may use either.
    #32
  • ✓ 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