weboke.nl

Checked 22 October 2026, 17:11 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 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/weboke.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/weboke.nl returned HTTP 429
    #3

Delegation

info

ns1.webawere.nl, ns2.webawere.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.webawere.nl, ns2.webawere.nl
NS in the zone
ns1.webawere.nl, ns2.webawere.nl
NameserverAddressesNetwork (AS)Glue
ns1.webawere.nl185.158.165.26 2a07:ae80:100:0:185:158:165:26AS8455 ATOM86-AS - atom86 BV, NL AS8455 ATOM86-AS - atom86 BV, NL185.158.165.26 2a07:ae80:100:0:185:158:165:26
ns2.webawere.nl95.142.98.222 2a00:1188:5:7:95:142:98:222AS8455 ATOM86-AS - atom86 BV, NL AS8455 ATOM86-AS - atom86 BV, NL95.142.98.222 2a00:1188:5:7:95:142:98:222

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.webawere.nl, ns2.webawere.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 (AS8455 (ATOM86-AS - atom86 BV, 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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.webawere.nl 185.158.165.26NOERROR, 9 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)
ns1.webawere.nl 2a07:ae80:100:0:185:158:165:26NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)
ns2.webawere.nl 95.142.98.222NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)
ns2.webawere.nl 2a00:1188:5:7:95:142:98:222NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.webawere.nl: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)"; ns2.webawere.nl: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)". 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 2026101203 · primary ns1.webawere.nl

Found

Primary (MNAME)
ns1.webawere.nl
Contact (RNAME)
hostmaster.weboke.nl
Serial
2026101203
Refresh / retry
3600 s / 3600 s
Expire
1209600 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ns1.webawere.nl (185.158.165.26)2026101203
ns1.webawere.nl (2a07:ae80:100:0:185:158:165:26)2026101203
ns2.webawere.nl (95.142.98.222)2026101203
ns2.webawere.nl (2a00:1188:5:7:95:142:98:222)2026101203

Checks

  • ✓ Serial 2026101203 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 14d, negative TTL 30m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.webawere.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@weboke.nl #25
    The SOA RNAME hostmaster.weboke.nl means hostmaster@weboke.nl.
  • ✓ Date-based serial #26
    The serial 2026101203 follows the YYYYMMDDnn convention (2026-10-12).

DNSSEC

info

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
20345RSASHA256 (8)SHA256 CEB75832D20FE4F8…yes

DNSKEY in the zone

Key tagRoleAlgorithm
33714ZSK (256)RSASHA256 (8)
20345KSK (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 20345 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-16 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-16 11:44 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

warn

10 records at the apex

Found

Read from
185.158.165.26:53
TypeValueTTL
SOAns1.webawere.nl. hostmaster.weboke.nl. 2026101203 3600 3600 1209600 18003600
NSns2.webawere.nl.60
NSns1.webawere.nl.60
A95.142.98.21260
AAAA2a00:1188:5:7:95:142:98:21260
MX10 mail.weboke.nl.60
TXT"google-site-verification=ND3C3yWc6xIclqJm-H_W3LK6jlpODRp2iz2HQXAlJEg"60
TXT"facebook-domain-verification=v5y0pohdhh2xfqre82280hz3r7o04h"60
TXT"v=spf1 a mx ip4:95.142.98.212 ip4:95.142.98.213 ip6:2a00:1188:5:7:95:142:98:212 include:webawere.nl include:_spf.mailrelay.rrpproxy.net -all"60
TXT"tr-claim-record=6fa5b363ab4efb05555c2a0a1c74a8526c392d0a233a90df"60

Checks

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