horus.be

Checked 22 October 2026, 06:32 UTC · via 8.8.8.8
!Passed with warnings
18 passed 4 warnings 0 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.horus.be, ns2.horus.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.horus.be, ns2.horus.be
NS in the zone
ns1.horus.be, ns2.horus.be
NameserverAddressesNetwork (AS)Glue
ns1.horus.be5.196.242.179AS16276 OVH - OVH SAS, FR5.196.242.179
ns2.horus.be135.125.206.165AS16276 OVH - OVH SAS, FR51.254.96.58

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.horus.be, ns2.horus.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: ns2.horus.be (glue 51.254.96.58, zone 135.125.206.165). 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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.horus.be 5.196.242.179NOERROR, 17 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
ns2.horus.be 135.125.206.165NOERROR, 9 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1

Checks

  • ✓ All respond #14
    All 2 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.horus.be: "PowerDNS Authoritative Server 4.4.1"; ns2.horus.be: "PowerDNS Authoritative Server 4.4.1". 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

info

serial 2014061800 · primary horus.be

Found

Primary (MNAME)
horus.be
Contact (RNAME)
root.horus.be
Serial
2014061800
Refresh / retry
10800 s / 3600 s
Expire
2419200 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.horus.be (5.196.242.179)2014061800
ns2.horus.be (135.125.206.165)2014061800

Checks

  • ✓ Serial 2014061800 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 28d, negative TTL 1d.
  • i
    Hidden master
    The primary nameserver horus.be is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact root@horus.be #25
    The SOA RNAME root.horus.be means root@horus.be.
  • ✓ Date-based serial #26
    The serial 2014061800 follows the YYYYMMDDnn convention (2014-06-18).

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

6 records at the apex

Found

Read from
5.196.242.179:53
TypeValueTTL
SOAhorus.be. root.horus.be. 2014061800 10800 3600 2419200 8640086400
NSns1.horus.be.86400
NSns2.horus.be.86400
A151.80.199.1733600
MX10 mail.globulebleu.com.3600
TXT"v=spf1 mx a include:spf.proxi.tools ?all"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.
  • ✓ 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