zwemwater.nl

Checked 22 October 2026, 17:31 UTC · via 8.8.8.8
iAll checks passed
25 passed 0 warnings 0 failed 8 info

Registration

info

.nl country-code

Found

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

Delegation

info

ns1.aralto.nl, ns2.aralto.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.aralto.nl, ns2.aralto.nl
NS in the zone
ns1.aralto.nl, ns2.aralto.nl
NameserverAddressesNetwork (AS)Glue
ns1.aralto.nl5.61.248.164 2a01:7860::db:1152:a:1AS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL5.61.248.164 2a01:7860::db:1152:a:1
ns2.aralto.nl93.119.13.218 2a01:7c8:bb09:15e:5054:ff:fed2:6901AS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL93.119.13.218 2a01:7c8:bb09:15e:5054:ff:fed2:6901

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.aralto.nl, ns2.aralto.nl.
    #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 (AS20857 (TRANSIP-AS - Signet B.V., NL): 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
  • 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.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.aralto.nl 5.61.248.164NOERROR, 11 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns1.aralto.nl 2a01:7860::db:1152:a:1NOERROR, 11 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.aralto.nl 93.119.13.218NOERROR, 12 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.aralto.nl 2a01:7c8:bb09:15e:5054:ff:fed2:6901NOERROR, 12 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

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: ns1.aralto.nl: "Served by PowerDNS - https://www.powerdns.com/"; ns2.aralto.nl: "Served by PowerDNS - https://www.powerdns.com/".
    #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 2026100926 · primary ns1.aralto.nl

Found

Primary (MNAME)
ns1.aralto.nl
Contact (RNAME)
bij12.aralto.nl
Serial
2026100926
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns1.aralto.nl (5.61.248.164)2026100926
ns1.aralto.nl (2a01:7860::db:1152:a:1)2026100926
ns2.aralto.nl (93.119.13.218)2026100926
ns2.aralto.nl (2a01:7c8:bb09:15e:5054:ff:fed2:6901)2026100926

Checks

  • ✓ Serial 2026100926 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 ns1.aralto.nl is one of the listed nameservers.
  • ✓ Contact bij12@aralto.nl #25
    The SOA RNAME bij12.aralto.nl means bij12@aralto.nl.
  • ✓ Date-based serial #26
    The serial 2026100926 follows the YYYYMMDDnn convention (2026-10-09).

DNSSEC

info

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
8051RSASHA256 (8)SHA256 DD602C532A0E52CB…yes
47324RSASHA256 (8)SHA256 312793182D259457…yes

DNSKEY in the zone

Key tagRoleAlgorithm
51195ZSK (256)RSASHA256 (8)
8051KSK (257)RSASHA256 (8)
47324KSK (257)RSASHA256 (8)

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 8051 (SHA256), key tag 47324 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-13 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-13 12:13 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

info

13 records at the apex

Found

Read from
5.61.248.164:53
TypeValueTTL
SOAns1.aralto.nl. bij12.aralto.nl. 2026100926 10800 3600 1209600 10800600
NSns1.aralto.nl.600
NSns2.aralto.nl.600
A162.159.135.42600
AAAA2606:4700:7::a29f:872a600
MX10 mail.zwemwater.nl.600
TXT"v=spf1 +a +mx +a:vm23363.proserve.nl -all"600
CAA0 issuewild "digicert.com"600
CAA0 issue "digicert.com"600
CAA0 issuewild "sectigo.com"600
CAA0 issue "letsencrypt.org"600
CAA0 issuewild "letsencrypt.org"600
CAA0 issue "sectigo.com"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 10m, MX 10m, NS 10m. The NS TTL at the parent is 1h and in the zone 10m; 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, sectigo.com, letsencrypt.org.