relaxy.be

Checked 22 October 2026, 07:02 UTC · via 8.8.8.8
!Passed with warnings
25 passed 3 warnings 0 failed 4 info

Registration

info

.be country-code

Found

TLD
.be (country-code)
ICANN policies apply
no

Checks

  • i
    .be 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
    .be is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .be offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

pass

ns.bnamed.eu, ns.bnamed.uk, ns.bnamed.us, ns.nscluster.pw, ns.nscluster.si

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns.bnamed.eu, ns.bnamed.uk, ns.bnamed.us, ns.nscluster.pw, ns.nscluster.si
NS in the zone
ns.bnamed.eu, ns.bnamed.uk, ns.bnamed.us, ns.nscluster.pw, ns.nscluster.si
NameserverAddressesNetwork (AS)Glue
ns.bnamed.eu188.166.70.123 2a03:b0c0:2:d0::79d:4001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-
ns.bnamed.uk13.248.156.209 2600:9000:a51d:1c55:a63e:443d:ec03:df01AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns.bnamed.us198.251.86.156 2605:6400:10:5c1:84ee:85fb:b2b:8b37AS53667 PONYNET - FranTech Solutions, US AS53667 PONYNET - FranTech Solutions, US-
ns.nscluster.pw137.74.111.240 2001:41d0:305:2100::1:597dAS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns.nscluster.si192.99.182.47 2607:5300:201:3100::92afAS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-

Checks

  • ✓ 5 nameservers #6
    Delegated to ns.bnamed.eu, ns.bnamed.uk, ns.bnamed.us, ns.nscluster.pw, ns.nscluster.si.
  • ✓ 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 5 IPv4 /24s and 5 IPv6 /48s.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 2 addresses; AS16276 (OVH - OVH SAS, FR): 4 addresses; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 2 addresses; AS53667 (PONYNET - FranTech Solutions, US): 2 addresses.
  • ✓ Nameserver names under 5 TLDs #12
    Nameserver names use the TLDs .eu, .pw, .si, .uk, .us.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

10 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.bnamed.eu 188.166.70.123NOERROR, 32 ms, authoritativenoyes / yesrefusednscluster
ns.bnamed.eu 2a03:b0c0:2:d0::79d:4001NOERROR, 27 ms, authoritativenoyes / yesrefusednscluster
ns.bnamed.uk 13.248.156.209NOERROR, 5 ms, authoritativenoyes / yesrefusedKnot DNS 3.5.3
ns.bnamed.uk 2600:9000:a51d:1c55:a63e:443d:ec03:df01NOERROR, 5 ms, authoritativenoyes / yesrefusedKnot DNS 3.5.3
ns.bnamed.us 198.251.86.156NOERROR, 21 ms, authoritativenoyes / yesrefusednscluster
ns.bnamed.us 2605:6400:10:5c1:84ee:85fb:b2b:8b37NOERROR, 109 ms, authoritativenoyes / yesrefusednscluster
ns.nscluster.pw 137.74.111.240NOERROR, 7 ms, authoritativenoyes / yesrefusednscluster
ns.nscluster.pw 2001:41d0:305:2100::1:597dNOERROR, 16 ms, authoritativenoyes / yesrefused-
ns.nscluster.si 192.99.182.47NOERROR, 95 ms, authoritativenoyes / yesrefused-
ns.nscluster.si 2607:5300:201:3100::92afNOERROR, 96 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 10 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: ns.bnamed.uk: "Knot DNS 3.5.3". 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 2026102201 · primary ns.bnamed.eu

Found

Primary (MNAME)
ns.bnamed.eu
Contact (RNAME)
hostmaster.bnamed.eu
Serial
2026102201
Refresh / retry
7200 s / 3600 s
Expire
1209600 s
Negative TTL
901 s

Serial per nameserver

NameserverSerial
ns.bnamed.eu (188.166.70.123)2026102201
ns.bnamed.eu (2a03:b0c0:2:d0::79d:4001)2026102201
ns.bnamed.uk (13.248.156.209)2026102201
ns.bnamed.uk (2600:9000:a51d:1c55:a63e:443d:ec03:df01)2026102201
ns.bnamed.us (198.251.86.156)2026102201
ns.bnamed.us (2605:6400:10:5c1:84ee:85fb:b2b:8b37)2026102201
ns.nscluster.pw (137.74.111.240)2026102201
ns.nscluster.pw (2001:41d0:305:2100::1:597d)2026102201
ns.nscluster.si (192.99.182.47)2026102201
ns.nscluster.si (2607:5300:201:3100::92af)2026102201

Checks

  • ✓ Serial 2026102201 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 1h, expire 14d, negative TTL 15m1s.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.bnamed.eu is one of the listed nameservers.
  • ✓ Contact hostmaster@bnamed.eu #25
    The SOA RNAME hostmaster.bnamed.eu means hostmaster@bnamed.eu.
  • ✓ Date-based serial #26
    The serial 2026102201 follows the YYYYMMDDnn convention (2026-10-22).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC3
NSEC3
10 iterations, 3-byte salt
Signatures valid until
5 November 2026

DNSKEY in the zone

Key tagRoleAlgorithm
39859KSK (257)RSASHA256 (8)
10866ZSK (256)RSASHA256 (8)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 10 iterations and a 3-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Records

info

20 records at the apex

Found

Read from
188.166.70.123:53
TypeValueTTL
SOAns.bnamed.eu. hostmaster.bnamed.eu. 2026102201 7200 3600 1209600 901901
NSns.bnamed.us.901
NSns.nscluster.pw.901
NSns.bnamed.uk.901
NSns.bnamed.eu.901
NSns.nscluster.si.901
A134.209.139.162901
MX10 ALT4.ASPMX.L.GOOGLE.COM.901
MX1 ASPMX.L.GOOGLE.COM.901
MX10 ALT3.ASPMX.L.GOOGLE.COM.901
MX5 ALT1.ASPMX.L.GOOGLE.COM.901
MX5 ALT2.ASPMX.L.GOOGLE.COM.901
TXT"v=spf1 include:_spf.google.com include:servers.mcsv.net include:spf.mtasv.net include:_spf.createsend.com include:helpscoutemail.com include:_spf.relay.mailprotect.be include:47850483.spf06.hubspotemail.net include:_spf.odoo.com ~all"901
TXT"google-site-verification=xFbRwGcDMb19msQHoT4kQzivOqRqdjzPwLnHJgHM_eo"901
TXT"MS=ms43529211"901
TXT"ppkey-14f0a462b98552d66d7607b7393dc5ae"901
TXT"ppkey-fcadc5f868ff11bf1945ebb14629dc3a"901
TXT"anthropic-domain-verification-traygj=bqWoSxbKJtfvZwIolcZLh9rep"901
TXT"google-site-verification=SUM6o1KTNJxLwBp_hHAiBhNOXo8SyvR1kQXTbp-VE7E"901
TXT"domain-verification:43676fa5e8d0978232d1c1cba73f6910ce404869"901

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m1s, MX 15m1s, NS 15m1s. The NS TTL at the parent is 1d and in the zone 15m1s; 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
  • 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