keurslager.nl

Checked 22 October 2026, 14:02 UTC · via 8.8.8.8
!Passed with warnings
23 passed 1 warning 0 failed 11 info

Registration

info

.nl country-code · team.blue nl B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
team.blue nl B.V.
Registered
1 January 1997
Last changed
30 September 2026
Status
active
Registry nameservers
pns31.cloudns.net, pns32.cloudns.net
RDAP server
https://rdap.sidn.nl/

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
    Expiry date not published
    The registry does not publish the expiry date in RDAP. Check it with your registrar.
    #3
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

pns31.cloudns.net, pns32.cloudns.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
pns31.cloudns.net, pns32.cloudns.net
NS in the zone
pns31.cloudns.net, pns32.cloudns.net
NameserverAddressesNetwork (AS)Glue
pns31.cloudns.net185.136.96.66 2a06:fb00:1::1:66AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-
pns32.cloudns.net185.136.97.66 2a06:fb00:1::2:66AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: pns31.cloudns.net, pns32.cloudns.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a06:fb00:1::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS203391 (CLOUDNSNET - Cloud DNS Ltd, BG): 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 .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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
pns31.cloudns.net 185.136.96.66NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-1
pns31.cloudns.net 2a06:fb00:1::1:66NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-1
pns32.cloudns.net 185.136.97.66NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-1
pns32.cloudns.net 2a06:fb00:1::2:66NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-1

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: pns31.cloudns.net: "de3-1"; pns32.cloudns.net: "de3-1".
    #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

info

serial 2026102103 · primary ns31.cloudns.net

Found

Primary (MNAME)
ns31.cloudns.net
Contact (RNAME)
support.cloudns.net
Serial
2026102103
Refresh / retry
7200 s / 1800 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
pns31.cloudns.net (185.136.96.66)2026102103
pns31.cloudns.net (2a06:fb00:1::1:66)2026102103
pns32.cloudns.net (185.136.97.66)2026102103
pns32.cloudns.net (2a06:fb00:1::2:66)2026102103

Checks

  • ✓ Serial 2026102103 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 30m, expire 14d, negative TTL 1h.
  • i
    Hidden master
    The primary nameserver ns31.cloudns.net 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 support@cloudns.net #25
    The SOA RNAME support.cloudns.net means support@cloudns.net.
  • ✓ Date-based serial #26
    The serial 2026102103 follows the YYYYMMDDnn convention (2026-10-21).

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

DS at the parent

Key tagAlgorithmDigestMatches a key
25938ECDSAP256SHA256 (13)SHA256 10DB8CBBBCE55698…yes

DNSKEY in the zone

Key tagRoleAlgorithm
25938KSK (257)ECDSAP256SHA256 (13)
36385ZSK (256)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 25938 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-20 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-20 11:58 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

warn

12 records at the apex

Found

Read from
185.136.96.66:53
TypeValueTTL
SOAns31.cloudns.net. support.cloudns.net. 2026102103 7200 1800 1209600 36003600
NSpns31.cloudns.net.300
NSpns32.cloudns.net.300
A213.207.85.7300
AAAA2001:4018:8800:3::4660
MX20 filter02.cloudet.nl.300
MX10 filter01.cloudet.nl.300
TXT"v=spf1 a ip4:92.64.36.73/29 ip4:213.207.89.75 ip4:92.67.55.205 include:spf.routit.net include:spf.afas.online include:spf.protection.outlook.com include:spf.mandrillapp.com include:spf.interconnect.nl ip4:213.206.225.107 ip6:2001:4018:8800:3::30 include:s" "pf.flowmailer.net -all"300
TXT"MS=ms24703002"300
TXT"atlassian-sending-domain-verification=6cc1557b-3a2f-4a1e-8e60-0a8fc5c0eace"300
TXT"mandrill_verify.oAL2xtl1FLmowcmA_MUIyA"300
TXT"google-site-verification=t13oNxdXFHt7yQErWx4ApLBzo9psC-Hm7RwPV7samg4"300

Checks

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