infobel.be

Checked 22 October 2026, 06:40 UTC · via 8.8.8.8
!Passed with warnings
19 passed 3 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.infobel.net, ns2.infobel.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.infobel.net, ns2.infobel.net
NS in the zone
ns1.infobel.net, ns2.infobel.net
NameserverAddressesNetwork (AS)Glue
ns1.infobel.net185.55.93.25AS42160 LCPDCO - DC STAR nv, BE-
ns2.infobel.net185.55.93.26AS42160 LCPDCO - DC STAR nv, BE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.infobel.net, ns2.infobel.net.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 185.55.93.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS42160 (LCPDCO - DC STAR nv, BE): 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 .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

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.infobel.net 185.55.93.25NOERROR, 17 ms, authoritativenoyes / yesrefusednot currently available
ns2.infobel.net 185.55.93.26NOERROR, 17 ms, authoritativenoyes / yesrefusednot currently available

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.infobel.net: "not currently available"; ns2.infobel.net: "not currently available".
    #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 2026092900 · primary ns1.infobel.net

Found

Primary (MNAME)
ns1.infobel.net
Contact (RNAME)
postmaster.kapitol.com
Serial
2026092900
Refresh / retry
3600 s / 1800 s
Expire
1209600 s
Negative TTL
38400 s

Serial per nameserver

NameserverSerial
ns1.infobel.net (185.55.93.25)2026092900
ns2.infobel.net (185.55.93.26)2026092900

Checks

  • ✓ Serial 2026092900 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 30m, expire 14d, negative TTL 640m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.infobel.net is one of the listed nameservers.
  • ✓ Contact postmaster@kapitol.com #25
    The SOA RNAME postmaster.kapitol.com means postmaster@kapitol.com.
  • ✓ Date-based serial #26
    The serial 2026092900 follows the YYYYMMDDnn convention (2026-09-29).

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

7 records at the apex

Found

Read from
185.55.93.25:53
TypeValueTTL
SOAns1.infobel.net. postmaster.kapitol.com. 2026092900 3600 1800 1209600 3840038400
NSns1.infobel.net.38400
NSns2.infobel.net.38400
A185.55.93.4038400
MX1 smtp.google.com.300
TXT"google-site-verification=IzccBMUy9cpuEzFHS8KQDgHHAUVlogxqP4lSqf16LQc"38400
TXT"v=spf1 ip4:185.55.93.23 ip4:185.55.93.24 include:_spf.google.com ~all"38400

Checks

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