centraalbeheer.nl

Checked 21 October 2026, 21:00 UTC · via 8.8.8.8
iAll checks passed
27 passed 0 warnings 0 failed 6 info

Registration

info

.nl country-code

Found

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

Delegation

info

ns01.brandshelter.com, ns02.brandshelter.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns01.brandshelter.com, ns02.brandshelter.net
NS in the zone
ns01.brandshelter.com, ns02.brandshelter.net
NameserverAddressesNetwork (AS)Glue
ns01.brandshelter.com193.227.117.15 2a04:2b00:14cc::15AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns02.brandshelter.net194.50.187.16 2a04:2b00:14dd::16AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.brandshelter.com, ns02.brandshelter.net.
    #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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 4 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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01.brandshelter.com 193.227.117.15NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns01.brandshelter.com 2a04:2b00:14cc::15NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns02.brandshelter.net 194.50.187.16NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1
ns02.brandshelter.net 2a04:2b00:14dd::16NOERROR, 12 ms, authoritativenoyes / yesrefusedreg-wie1

Checks

  • ✓ All respond #14
    All 4 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.brandshelter.com: "RcodeZero DNS"; ns02.brandshelter.net: "reg-wie1".
    #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

pass

serial 2026104464 · primary ns01.brandshelter.com

Found

Primary (MNAME)
ns01.brandshelter.com
Contact (RNAME)
tech.brandshelter.com
Serial
2026104464
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns01.brandshelter.com (193.227.117.15)2026104464
ns01.brandshelter.com (2a04:2b00:14cc::15)2026104464
ns02.brandshelter.net (194.50.187.16)2026104464
ns02.brandshelter.net (2a04:2b00:14dd::16)2026104464

Checks

  • ✓ Serial 2026104464 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.brandshelter.com is one of the listed nameservers.
  • ✓ Contact tech@brandshelter.com #25
    The SOA RNAME tech.brandshelter.com means tech@brandshelter.com.
  • ✓ Timestamp serial #26
    The serial 2026104464 is a Unix timestamp (2034-03-16 06:47 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
31504ECDSAP256SHA256 (13)SHA256 B4159874D8A91846…yes

DNSKEY in the zone

Key tagRoleAlgorithm
31910ZSK (256)ECDSAP256SHA256 (13)
31504KSK (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 31504 (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.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

15 records at the apex

Found

Read from
193.227.117.15:53
TypeValueTTL
SOAns01.brandshelter.com. tech.brandshelter.com. 2026104464 10800 3600 604800 3003600
NSns01.brandshelter.com.3600
NSns02.brandshelter.net.3600
A145.219.28.113600
AAAA2a04:b0c0:13::113600
MX0 centraalbeheer-nl.d-v1.mx.microsoft.3600
TXT"airtable-verification=9dd1fc21e5a42160c45f75ce4346cf17"3600
TXT"miro-verification=68617f6bb90380222729f4853889a984b0956a89"3600
TXT"sitecore-domain-verification=93ba7bf091bb4e469f4e79bbc2272bd5"3600
TXT"google-site-verification=FwYtrxhtcC-UA-ybY9wm205iQyMj6DcznUpTcNKOk_A"3600
TXT"google-site-verification=bpmjAKSg-mL8TNg53GFMpGPcI6ZT2RBSjYiswfvxbms"3600
TXT"Jcckydhk/1GadUZvcToU/2pjW0zRRTsog31gUeBD+3mPcuxu5c7+T5AOo8u58CfFA4gmXhBIDN/LZwV8vE3oBQ=="3600
TXT"v=spf1 include:spf.mailrelay.achmea.nl ip4:77.222.78.0/28 ip4:87.249.96.110 include:spf.protection.outlook.com include:_spf.zivver.com ip4:46.17.10.160/27 -all"3600
CAA0 iodef "mailto:domeinnamen@achmea.nl"3600
CAA0 issue "digicert.com"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 1h, MX 1h, NS 1h.
  • ✓ 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com.