siteffect.be

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

warn

ns1.siteffect.be, ns2.siteffect.be, ns3.siteffect.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.siteffect.be, ns2.siteffect.be, ns3.siteffect.be
NS in the zone
ns1.siteffect.be, ns2.siteffect.be, ns3.siteffect.be
NameserverAddressesNetwork (AS)Glue
ns1.siteffect.be77.73.98.232 2a03:a800:12:1:3267::232AS34762 COMBELL-AS - Combell NV, BE AS34762 COMBELL-AS - Combell NV, BE77.73.98.232 2a03:a800:12:1:3267::232
ns2.siteffect.be78.110.196.99 2a02:1807:3930:3600::1AS8368 DSTNY-BACKBONE - Dstny BE N.V., BE AS6848 TELENET-AS - Telenet BV, BE78.110.196.99 2a02:1807:3930:100::1
ns3.siteffect.be77.73.98.238 2a03:a800:12:1:1::8230AS34762 COMBELL-AS - Combell NV, BE AS34762 COMBELL-AS - Combell NV, BE77.73.98.238 2a03:a800:12:1:1::8230

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.siteffect.be, ns2.siteffect.be, ns3.siteffect.be.
  • ✓ 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: ns2.siteffect.be (glue 78.110.196.99, 2a02:1807:3930:100::1, zone 78.110.196.99, 2a02:1807:3930:3600::1). Update the glue at your registrar.
    #8
  • ✓ 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.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS34762 (COMBELL-AS - Combell NV, BE): 4 addresses; AS6848 (TELENET-AS - Telenet BV, BE): 1 address; AS8368 (DSTNY-BACKBONE - Dstny BE N.V., BE): 1 address.
  • 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

5 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.siteffect.be 77.73.98.232NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns1.siteffect.be 2a03:a800:12:1:3267::232NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns2.siteffect.be 78.110.196.99NOERROR, 24 ms, authoritativenoyes / yesrefusedunknown
ns2.siteffect.be 2a02:1807:3930:3600::1no responsenono / no--
ns3.siteffect.be 77.73.98.238NOERROR, 14 ms, authoritativenoyes / yesrefused9.18.28-0ubuntu0.24.04.1-Ubuntu
ns3.siteffect.be 2a03:a800:12:1:1::8230NOERROR, 14 ms, authoritativenoyes / yesrefused9.18.28-0ubuntu0.24.04.1-Ubuntu

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns2.siteffect.be (2a02:1807:3930:3600::1): read udp [2a01:4f8:1c1c:eebf::1]:46678->[2a02:1807:3930:3600::1]:53: i/o timeout.
    #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: ns3.siteffect.be: "9.18.28-0ubuntu0.24.04.1-Ubuntu". 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 2026020302 · primary ns1.siteffect.be

Found

Primary (MNAME)
ns1.siteffect.be
Contact (RNAME)
register.smp-europe.com
Serial
2026020302
Refresh / retry
21600 s / 3600 s
Expire
1209600 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns1.siteffect.be (77.73.98.232)2026020302
ns1.siteffect.be (2a03:a800:12:1:3267::232)2026020302
ns2.siteffect.be (78.110.196.99)2026020302
ns3.siteffect.be (77.73.98.238)2026020302
ns3.siteffect.be (2a03:a800:12:1:1::8230)2026020302

Checks

  • ✓ Serial 2026020302 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 14d, negative TTL 3h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.siteffect.be is one of the listed nameservers.
  • ✓ Contact register@smp-europe.com #25
    The SOA RNAME register.smp-europe.com means register@smp-europe.com.
  • ✓ Date-based serial #26
    The serial 2026020302 follows the YYYYMMDDnn convention (2026-02-03).

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

9 records at the apex

Found

Read from
77.73.98.232:53
TypeValueTTL
SOAns1.siteffect.be. register.smp-europe.com. 2026020302 21600 3600 1209600 108003600
NSns3.siteffect.be.86400
NSns2.siteffect.be.86400
NSns1.siteffect.be.86400
A31.24.250.33600
MX10 siteffect-be.mail.protection.outlook.com.3600
TXT"v=spf1 mx a include:spf.protection.outlook.com include:servers.mcsv.net include:_spf.siteffect.be -all"3600
CAA0 issue "godaddy.com"3600
CAA0 issue "letsencrypt.org"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 1d.
  • ✓ 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: godaddy.com, letsencrypt.org.