lefred.be

Checked 22 October 2026, 06:42 UTC · via 8.8.8.8
✗Problems found
16 passed 5 warnings 2 failed 6 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.lefred.be, ns2.lefred.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.lefred.be, ns2.lefred.be
NS in the zone
ns1.lefred.be
NameserverAddressesNetwork (AS)Glue
ns1.lefred.be162.19.248.192AS16276 OVH - OVH SAS, FR162.19.248.192
ns2.lefred.be (parent only)188.165.239.85AS16276 OVH - OVH SAS, FR188.165.239.85

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.lefred.be, ns2.lefred.be.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns2.lefred.be. ns1.lefred.be, ns2.lefred.be report NS ns1.lefred.be.
    #7
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.lefred.be, ns2.lefred.be.
  • ✓ 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

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.lefred.be 162.19.248.192NOERROR, 4 ms, authoritativeOPENyes / yesALLOWED (48 records)9.16.23-RH
ns2.lefred.be 188.165.239.85NOERROR, 21 ms, authoritativeOPENyes / yesALLOWED (48 records)9.16.23-RH

Checks

  • ✓ All respond #14
    All 2 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✗
    Open recursion
    These nameservers resolve names for anyone, which makes them usable for DNS amplification attacks and cache poisoning: ns1.lefred.be (162.19.248.192), ns2.lefred.be (188.165.239.85). Disable recursion on authoritative servers.
    #16
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.lefred.be: "9.16.23-RH"; ns2.lefred.be: "9.16.23-RH". 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: ns1.lefred.be (162.19.248.192): 48 records; ns2.lefred.be (188.165.239.85): 48 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

warn

serial 2026092301 · primary ns1.lefred.be

Found

Primary (MNAME)
ns1.lefred.be
Contact (RNAME)
root.lefred.be
Serial
2026092301
Refresh / retry
7200 s / 7200 s
Expire
86400 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.lefred.be (162.19.248.192)2026092301
ns2.lefred.be (188.165.239.85)2026092301

Checks

  • ✓ Serial 2026092301 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 2h should be shorter than refresh 2h; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 2h, retry 2h, expire 1d, negative TTL 1d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.lefred.be is one of the listed nameservers.
  • ✓ Contact root@lefred.be #25
    The SOA RNAME root.lefred.be means root@lefred.be.
  • ✓ Date-based serial #26
    The serial 2026092301 follows the YYYYMMDDnn convention (2026-09-23).

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
162.19.248.192:53
TypeValueTTL
SOAns1.lefred.be. root.lefred.be. 2026092301 7200 7200 86400 86400604800
NSns1.lefred.be.604800
A188.165.239.85604800
MX2 mail2.lefred.be.604800
MX1 mail.lefred.be.604800
TXT"v=spf1 a mx ~all"604800

Checks

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