hoppenbrouwerstechniek.nl

.nl country-code

Found

TLD

.nl (country-code)

ICANN policies apply

no

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/hoppenbrouwerstechniek.nl returned HTTP 429

  #3

ns1.zxcs.nl, ns2.zxcs.nl, ns3.zxcs.nl

Found

Parent zone

nl

Delegation from

ns1.dns.nl (194.0.28.53)

NS at the parent

ns1.zxcs.nl, ns2.zxcs.nl, ns3.zxcs.nl

NS in the zone

ns1.zxcs.nl, ns2.zxcs.nl, ns3.zxcs.nl

Checks

• ✓ 3 nameservers #6

  Delegated to ns1.zxcs.nl, ns2.zxcs.nl, ns3.zxcs.nl.
• ✓ 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; AS206281 (AS-ZXCS - Stichting DIGI NL, NL): 2 addresses.
• 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
• ✓ All reachable over IPv6 #13

  Every nameserver has an IPv6 address.

6 of 6 addresses answer authoritatively

Found

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.
• i

  Identifying string disclosed

  These nameservers answer version queries with a string that is not a version number: ns1.zxcs.nl: "Unknown"; ns2.zxcs.nl: "Unknown"; ns3.zxcs.nl: "Unknown".

  #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.

serial 2026102104 · primary ns.zxcs.nl

Found

Primary (MNAME)

ns.zxcs.nl

Contact (RNAME)

hostmaster.zxcs.nl

Serial

2026102104

Refresh / retry

10800 s / 3600 s

Expire

604800 s

Negative TTL

3600 s

Serial per nameserver

Checks

• ✓ Serial 2026102104 everywhere #22

  All nameservers serve the same version of the zone.
• ✓ Timers within recommendations #23

  SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
• i

  Hidden master

  The primary nameserver ns.zxcs.nl is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.

  #24
• ✓ Contact hostmaster@zxcs.nl #25

  The SOA RNAME hostmaster.zxcs.nl means hostmaster@zxcs.nl.
• ✓ Date-based serial #26

  The serial 2026102104 follows the YYYYMMDDnn convention (2026-10-21).

Signed, DS published at parent

Found

Validated by resolver

yes

Denial of existence

NSEC

Signatures valid until

5 November 2026

DS at the parent

DNSKEY in the zone

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 21366 (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

12 records at the apex

Found

Read from

185.104.28.19:53

Checks

• ✓ TTLs within range #32

  TTLs: A 5m, MX 5m, 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.
• 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