be2concept.be

Checked 22 October 2026, 06:10 UTC · via 8.8.8.8
✗Problems found
18 passed 4 warnings 1 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.o2switch.net, ns2.o2switch.net

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns1.o2switch.net, ns2.o2switch.net
NS in the zone
ns1.o2switch.net, ns2.o2switch.net
NameserverAddressesNetwork (AS)Glue
ns1.o2switch.net109.234.160.5AS50474 O2SWITCH - O2SWITCH SAS, FR-
ns2.o2switch.net109.234.161.5AS50474 O2SWITCH - O2SWITCH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.o2switch.net, ns2.o2switch.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 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 (AS50474 (O2SWITCH - O2SWITCH 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 .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

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.o2switch.net 109.234.160.5NOERROR, 24 ms, authoritativenono / yesrefusedPowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)
ns2.o2switch.net 109.234.161.5NOERROR, 20 ms, authoritativenono / yesrefusedPowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)

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.o2switch.net: "PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)"; ns2.o2switch.net: "PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.o2switch.net (109.234.160.5): dial tcp 109.234.160.5:53: i/o timeout; ns2.o2switch.net (109.234.161.5): dial tcp 109.234.161.5:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2023021500 · primary ns1.o2switch.net

Found

Primary (MNAME)
ns1.o2switch.net
Contact (RNAME)
systemshl.o2switch.fr
Serial
2023021500
Refresh / retry
3600 s / 7200 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.o2switch.net (109.234.160.5)2023021500
ns2.o2switch.net (109.234.161.5)2023021500

Checks

  • ✓ Serial 2023021500 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 2h should be shorter than refresh 1h. Current values: refresh 1h, retry 2h, expire 14d, negative TTL 1d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.o2switch.net is one of the listed nameservers.
  • ✓ Contact systemshl@o2switch.fr #25
    The SOA RNAME systemshl.o2switch.fr means systemshl@o2switch.fr.
  • ✓ Date-based serial #26
    The serial 2023021500 follows the YYYYMMDDnn convention (2023-02-15).

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
109.234.160.5:53
TypeValueTTL
SOAns1.o2switch.net. systemshl.o2switch.fr. 2023021500 3600 7200 1209600 8640086400
NSns1.o2switch.net.86400
NSns2.o2switch.net.86400
A109.234.161.1914400
MX0 be2concept.be.14400
TXT"v=spf1 ip4:109.234.161.19 +a +mx +include:spf.jabatus.fr ~all"14400

Checks

  • ✓ TTLs within range #32
    TTLs: A 4h, MX 4h, 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