wbets.nl

Checked 22 October 2026, 17:11 UTC · via 8.8.8.8
!Passed with warnings
19 passed 3 warnings 0 failed 7 info

Registration

info

.nl country-code

Found

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

Delegation

warn

user-with-problem01.nominus.com, user-with-problem02.nominus.com, user-with-problem03.nominus.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
user-with-problem01.nominus.com, user-with-problem02.nominus.com, user-with-problem03.nominus.com
NS in the zone
ns01.nominus.com, ns02.nominus.com, ns03.nominus.com
NameserverAddressesNetwork (AS)Glue
ns01.nominus.com (zone only)162.159.26.143 2400:cb00:2049:1::a29f:1a8fAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
ns02.nominus.com (zone only)162.159.27.22 2400:cb00:2049:1::a29f:1b16AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
ns03.nominus.com (zone only)162.159.26.101 2400:cb00:2049:1::a29f:1a65AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
user-with-problem01.nominus.com (parent only)162.159.26.143AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
user-with-problem02.nominus.com (parent only)162.159.27.22AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
user-with-problem03.nominus.com (parent only)162.159.26.101AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • ✓ 3 nameservers #6
    Delegated to user-with-problem01.nominus.com, user-with-problem02.nominus.com, user-with-problem03.nominus.com.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: user-with-problem01.nominus.com, user-with-problem02.nominus.com, user-with-problem03.nominus.com; only in the zone: ns01.nominus.com, ns02.nominus.com, ns03.nominus.com. ns01.nominus.com, ns02.nominus.com, ns03.nominus.com, user-with-problem01.nominus.com, user-with-problem02.nominus.com, user-with-problem03.nominus.com report NS ns01.nominus.com ns02.nominus.com ns03.nominus.com.
    #7
  • ✓ 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 2400:cb00:2049::/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 (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 9 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 .com
    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: user-with-problem01.nominus.com, user-with-problem02.nominus.com, user-with-problem03.nominus.com.
    #13

Nameservers

warn

9 of 9 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01.nominus.com 162.159.26.143NOERROR, 26 ms, authoritativenoyes / yesrefused2026.10.8
ns01.nominus.com 2400:cb00:2049:1::a29f:1a8fNOERROR, 111 ms, authoritativenoyes / yesrefused2026.10.8
ns02.nominus.com 162.159.27.22NOERROR, 35 ms, authoritativenoyes / yesrefused2026.10.8
ns02.nominus.com 2400:cb00:2049:1::a29f:1b16NOERROR, 110 ms, authoritativenoyes / yesrefused2026.10.8
ns03.nominus.com 162.159.26.101NOERROR, 29 ms, authoritativenoyes / yesrefused2026.10.8
ns03.nominus.com 2400:cb00:2049:1::a29f:1a65NOERROR, 27 ms, authoritativenoyes / yesrefused2026.10.8
user-with-problem01.nominus.com 162.159.26.143NOERROR, 106 ms, authoritativenoyes / yesrefused2026.10.8
user-with-problem02.nominus.com 162.159.27.22NOERROR, 22 ms, authoritativenoyes / yesrefused2026.10.8
user-with-problem03.nominus.com 162.159.26.101NOERROR, 29 ms, authoritativenoyes / yesrefused2026.10.8

Checks

  • ✓ All respond #14
    All 9 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: ns01.nominus.com: "2026.10.8"; ns02.nominus.com: "2026.10.8"; ns03.nominus.com: "2026.10.8"; user-with-problem01.nominus.com: "2026.10.8"; user-with-problem02.nominus.com: "2026.10.8"; user-with-problem03.nominus.com: "2026.10.8". 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

pass

serial 2025022503 · primary ns01.nominus.com

Found

Primary (MNAME)
ns01.nominus.com
Contact (RNAME)
it.nominus.com
Serial
2025022503
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns01.nominus.com (162.159.26.143)2025022503
ns01.nominus.com (2400:cb00:2049:1::a29f:1a8f)2025022503
ns02.nominus.com (162.159.27.22)2025022503
ns02.nominus.com (2400:cb00:2049:1::a29f:1b16)2025022503
ns03.nominus.com (162.159.26.101)2025022503
ns03.nominus.com (2400:cb00:2049:1::a29f:1a65)2025022503
user-with-problem01.nominus.com (162.159.26.143)2025022503
user-with-problem02.nominus.com (162.159.27.22)2025022503
user-with-problem03.nominus.com (162.159.26.101)2025022503

Checks

  • ✓ Serial 2025022503 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.nominus.com is one of the listed nameservers.
  • ✓ Contact it@nominus.com #25
    The SOA RNAME it.nominus.com means it@nominus.com.
  • ✓ Date-based serial #26
    The serial 2025022503 follows the YYYYMMDDnn convention (2025-02-25).

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

4 records at the apex

Found

Read from
162.159.26.143:53
TypeValueTTL
SOAns01.nominus.com. it.nominus.com. 2025022503 10800 3600 1209600 36003600
NSns03.nominus.com.3600
NSns02.nominus.com.3600
NSns01.nominus.com.3600

Checks

  • ✓ TTLs within range #32
    TTLs: NS 1h.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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