video-projecteur.be

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

fail

ns61a.haisoft.net, ns61b.haisoft.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns61a.haisoft.net, ns61b.haisoft.net
NS in the zone
ns18a.haisoft.net, ns18b.haisoft.net
NameserverAddressesNetwork (AS)Glue
ns18a.haisoft.net (zone only)185.177.47.18AS49434 FBWNETWORKS - FBW NETWORKS SAS, FR-
ns18b.haisoft.net (zone only)91.212.26.200AS16347 INHERENT - ADISTA SAS, FR-
ns61a.haisoft.net (parent only)185.177.47.18AS49434 FBWNETWORKS - FBW NETWORKS SAS, FR-
ns61b.haisoft.net (parent only)91.212.26.200AS16347 INHERENT - ADISTA SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns61a.haisoft.net, ns61b.haisoft.net.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns61a.haisoft.net, ns61b.haisoft.net; only in the zone: ns18a.haisoft.net, ns18b.haisoft.net. ns18a.haisoft.net, ns18b.haisoft.net, ns61a.haisoft.net, ns61b.haisoft.net report NS ns18a.haisoft.net ns18b.haisoft.net.
    #7
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✗
    Nameserver names are CNAMEs
    Nameserver names must not be aliases (RFC 2181 10.3): ns61a.haisoft.net -> ns18a.haisoft.net.
    #9
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16347 (INHERENT - ADISTA SAS, FR): 2 addresses; AS49434 (FBWNETWORKS - FBW NETWORKS SAS, FR): 2 addresses.
  • i
    All nameserver names under .net
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns18a.haisoft.net 185.177.47.18NOERROR, 14 ms, authoritativenoyes / yesrefusednone
ns18b.haisoft.net 91.212.26.200NOERROR, 16 ms, authoritativenoyes / yesrefused9.11.36-RedHat-9.11.36-16.el8_10.6
ns61a.haisoft.net 185.177.47.18NOERROR, 15 ms, authoritativenoyes / yesrefusednone
ns61b.haisoft.net 91.212.26.200NOERROR, 16 ms, authoritativenoyes / yesrefused9.11.36-RedHat-9.11.36-16.el8_10.6

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: ns18b.haisoft.net: "9.11.36-RedHat-9.11.36-16.el8_10.6"; ns61b.haisoft.net: "9.11.36-RedHat-9.11.36-16.el8_10.6". 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 1788968218 · primary ns18a.haisoft.net

Found

Primary (MNAME)
ns18a.haisoft.net
Contact (RNAME)
andries\.fabrice.hotmail.be
Serial
1788968218
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns18a.haisoft.net (185.177.47.18)1788968218
ns18b.haisoft.net (91.212.26.200)1788968218
ns61a.haisoft.net (185.177.47.18)1788968218
ns61b.haisoft.net (91.212.26.200)1788968218

Checks

  • ✓ Serial 1788968218 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 3h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns18a.haisoft.net is one of the listed nameservers.
  • ✓ Contact andries.fabrice@hotmail.be #25
    The SOA RNAME andries\.fabrice.hotmail.be means andries.fabrice@hotmail.be.
  • ✓ Timestamp serial #26
    The serial 1788968218 is a Unix timestamp (2026-09-09 15:36 UTC).

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

warn

7 records at the apex

Found

Read from
185.177.47.18:53
TypeValueTTL
SOAns18a.haisoft.net. andries\.fabrice.hotmail.be. 1788968218 10800 3600 604800 10800120
NSns18a.haisoft.net.120
NSns18b.haisoft.net.120
A185.177.47.18120
MX10 mail.video-projecteur.be.120
TXT"v=spf1 a mx include:spf.haisoft.net -all"120
TXT"google-site-verification=xRQD3bBWIINwdHCmLFVZbfzIoFr2kNowSWAxgUGrXmM"120

Checks

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