online.be

Checked 22 October 2026, 07:00 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 8 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

dns01.proxi.technology, dns02.proxi.technology

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
dns01.proxi.technology, dns02.proxi.technology
NS in the zone
dns01.proxi.technology, dns02.proxi.technology
NameserverAddressesNetwork (AS)Glue
dns01.proxi.technology5.196.242.179AS16276 OVH - OVH SAS, FR-
dns02.proxi.technology135.125.206.165AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns01.proxi.technology, dns02.proxi.technology.
    #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 (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 .technology
    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
dns01.proxi.technology 5.196.242.179NOERROR, 15 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.4.1
dns02.proxi.technology 135.125.206.165NOERROR, 5 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: dns01.proxi.technology: "PowerDNS Authoritative Server 4.4.1"; dns02.proxi.technology: "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 2019082804 · primary ns.online.be

Found

Primary (MNAME)
ns.online.be
Contact (RNAME)
ns.online.be
Serial
2019082804
Refresh / retry
3600 s / 600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns01.proxi.technology (5.196.242.179)2019082804
dns02.proxi.technology (135.125.206.165)2019082804

Checks

  • ✓ Serial 2019082804 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 14d, negative TTL 1h.
  • i
    Hidden master
    The primary nameserver ns.online.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 ns@online.be #25
    The SOA RNAME ns.online.be means ns@online.be.
  • ✓ Date-based serial #26
    The serial 2019082804 follows the YYYYMMDDnn convention (2019-08-28).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
5 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
10093ECDSAP256SHA256 (13)SHA256 A3D2A0EAE181361F…yes

DNSKEY in the zone

Key tagRoleAlgorithm
10093KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 10093 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

7 records at the apex

Found

Read from
5.196.242.179:53
TypeValueTTL
SOAns.online.be. ns.online.be. 2019082804 3600 600 1209600 360086399
NSdns02.proxi.technology.3599
NSdns01.proxi.technology.3599
A5.196.134.1683600
MX10 in-mx.online.be.3600
TXT"MS=ms98100557"3600
TXT"v=spf1 mx a include:spf.protection.outlook.com ip4:178.33.158.91 ip4:5.135.66.13 ip4:46.105.215.1/26 ip4:176.31.31.139 include:spf.proxi.tools a:mail.proxirepair.be ~all"3600

Checks

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