www.be

Checked 22 October 2026, 07:30 UTC · via 8.8.8.8
✗Problems found
18 passed 3 warnings 1 failed 7 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

warn

ns1.sunhost.be, ns2.sunhost.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.sunhost.be, ns2.sunhost.be
NS in the zone
ns1.sunhost.be, ns2.sunhost.be
NameserverAddressesNetwork (AS)Glue
ns1.sunhost.be84.22.115.32 2a02:2770:15:0:21a:4aff:fe4a:ab40AS196752 TILAA - Tilaa B.V., NL AS196752 TILAA - Tilaa B.V., NL84.22.115.32
ns2.sunhost.be84.22.110.118 2a02:2770:15:0:21a:4aff:feaf:ff51AS196752 TILAA - Tilaa B.V., NL AS196752 TILAA - Tilaa B.V., NL84.22.110.118

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.sunhost.be, ns2.sunhost.be.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns1.sunhost.be (glue 84.22.115.32, zone 84.22.115.32, 2a02:2770:15:0:21a:4aff:fe4a:ab40); ns2.sunhost.be (glue 84.22.110.118, zone 84.22.110.118, 2a02:2770:15:0:21a:4aff:feaf:ff51). Update the glue at your registrar.
    #8
  • ✓ 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 2a02:2770:15::/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 (AS196752 (TILAA - Tilaa B.V., 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 .be
    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

fail

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.sunhost.be 84.22.115.32NOERROR, 16 ms, authoritativenoyes / yesrefused9.9.5-9+deb8u19-Debian
ns1.sunhost.be 2a02:2770:15:0:21a:4aff:fe4a:ab40NOERROR, 10 ms, authoritativenoyes / yesrefused9.9.5-9+deb8u19-Debian
ns2.sunhost.be 84.22.110.118NOERROR, 9 ms, authoritativenoyes / yesALLOWED (43 records)9.9.5-9+deb8u19-Debian
ns2.sunhost.be 2a02:2770:15:0:21a:4aff:feaf:ff51NOERROR, 13 ms, authoritativenoyes / yesALLOWED (43 records)9.9.5-9+deb8u19-Debian

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.sunhost.be: "9.9.5-9+deb8u19-Debian"; ns2.sunhost.be: "9.9.5-9+deb8u19-Debian". Hide or replace the version string.
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns2.sunhost.be (84.22.110.118): 43 records; ns2.sunhost.be (2a02:2770:15:0:21a:4aff:feaf:ff51): 43 records. Restrict zone transfers to your secondary servers.
    #18
  • ✓ 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 2016091502 · primary ns1.sunhost.be

Found

Primary (MNAME)
ns1.sunhost.be
Contact (RNAME)
root.sunhost.be
Serial
2016091502
Refresh / retry
3600 s / 600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.sunhost.be (84.22.115.32)2016091502
ns1.sunhost.be (2a02:2770:15:0:21a:4aff:fe4a:ab40)2016091502
ns2.sunhost.be (84.22.110.118)2016091502
ns2.sunhost.be (2a02:2770:15:0:21a:4aff:feaf:ff51)2016091502

Checks

  • ✓ Serial 2016091502 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.sunhost.be is one of the listed nameservers.
  • ✓ Contact root@sunhost.be #25
    The SOA RNAME root.sunhost.be means root@sunhost.be.
  • ✓ Date-based serial #26
    The serial 2016091502 follows the YYYYMMDDnn convention (2016-09-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

12 records at the apex

Found

Read from
84.22.115.32:53
TypeValueTTL
SOAns1.sunhost.be. root.sunhost.be. 2016091502 3600 600 604800 86400300
NSns2.sunhost.be.300
NSns1.sunhost.be.300
A84.22.115.32300
MX30 aspmx3.googlemail.com.300
MX30 aspmx2.googlemail.com.300
MX20 alt1.aspmx.l.google.com.300
MX10 aspmx.l.google.com.300
MX20 alt2.aspmx.l.google.com.300
MX30 aspmx4.googlemail.com.300
MX30 aspmx5.googlemail.com.300
TXT"v=spf1 include:_spf.google.com ~all"300

Checks

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