ruuda.nl

Checked 22 October 2026, 15:50 UTC · via 8.8.8.8
✗Problems found
19 passed 3 warnings 1 failed 6 info

Registration

info

.nl country-code

Found

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

Delegation

info

ns1.ruuda.nl, ns2.ruuda.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.ruuda.nl, ns2.ruuda.nl
NS in the zone
ns1.ruuda.nl, ns2.ruuda.nl
NameserverAddressesNetwork (AS)Glue
ns1.ruuda.nl91.92.117.2 2a04:c46:e00:fce6:404:26ff:fe00:82eAS61098 exoscale - Akenes SA, CH AS61098 exoscale - Akenes SA, CH91.92.117.2 2a04:c46:e00:fce6:404:26ff:fe00:82e
ns2.ruuda.nl84.32.96.247AS59642 CHERRYSERVERS2-AS - UAB _Cherry Servers_, LT84.32.96.247

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.ruuda.nl, ns2.ruuda.nl.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.ruuda.nl, ns2.ruuda.nl.
  • ✓ 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 1 IPv6 /48.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS59642 (CHERRYSERVERS2-AS - UAB _Cherry Servers_, LT): 1 address; AS61098 (exoscale - Akenes SA, CH): 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns2.ruuda.nl.
    #13

Nameservers

fail

2 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ruuda.nl 91.92.117.2NOERROR, 4 ms, authoritativenoyes / yesrefusedNSD 4.15.2
ns1.ruuda.nl 2a04:c46:e00:fce6:404:26ff:fe00:82eno responsenono / no--
ns2.ruuda.nl 84.32.96.247NOERROR, 744 ms, authoritativenoyes / yesrefusedNSD 4.15.2

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns1.ruuda.nl (2a04:c46:e00:fce6:404:26ff:fe00:82e): read udp [2a01:4f8:1c1c:eebf::1]:58693->[2a04:c46:e00:fce6:404:26ff:fe00:82e]:53: read: connection refused.
    #14
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.ruuda.nl: "NSD 4.15.2"; ns2.ruuda.nl: "NSD 4.15.2". Hide or replace the version string.
    #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

warn

serial 2026041501 · primary ns1.ruuda.nl

Found

Primary (MNAME)
ns1.ruuda.nl
Contact (RNAME)
webmaster.ruuda.nl
Serial
2026041501
Refresh / retry
1209600 s / 1209600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.ruuda.nl (91.92.117.2)2026041501
ns2.ruuda.nl (84.32.96.247)2026041501

Checks

  • ✓ Serial 2026041501 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 14d is outside 20m–1d; retry 14d should be shorter than refresh 14d; expire 14d must be longer than refresh + retry. Current values: refresh 14d, retry 14d, expire 14d, negative TTL 1h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.ruuda.nl is one of the listed nameservers.
  • ✓ Contact webmaster@ruuda.nl #25
    The SOA RNAME webmaster.ruuda.nl means webmaster@ruuda.nl.
  • ✓ Date-based serial #26
    The serial 2026041501 follows the YYYYMMDDnn convention (2026-04-15).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

8 records at the apex

Found

Read from
91.92.117.2:53
TypeValueTTL
SOAns1.ruuda.nl. webmaster.ruuda.nl. 2026041501 1209600 1209600 1209600 360010800
NSns1.ruuda.nl.28800
NSns2.ruuda.nl.28800
A91.92.117.210800
AAAA2a04:c46:e00:fce6:404:26ff:fe00:82e10800
MX10 mx.soverin.net.10800
TXT"v=spf1 include:soverin.net ~all"10800
CAA0 issue "letsencrypt.org"180

Checks

  • ✓ TTLs within range #32
    TTLs: A 3h, AAAA 3h, MX 3h, NS 8h. The NS TTL at the parent is 1h and in the zone 8h; 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: letsencrypt.org.