zwaneberg.be

Checked 22 October 2026, 07:31 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 warnings 0 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

ns.cipal.be, ns2.cipal.be

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns.cipal.be, ns2.cipal.be
NS in the zone
ns.cipal.be, ns2.cipal.be
NameserverAddressesNetwork (AS)Glue
ns.cipal.be193.190.121.4AS2611 BELNET - BELNET, BE193.190.121.4
ns2.cipal.be193.190.121.3AS2611 BELNET - BELNET, BE193.190.121.3

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.cipal.be, ns2.cipal.be.
    #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 193.190.121.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 (AS2611 (BELNET - BELNET, 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 .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

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.cipal.be 193.190.121.4NOERROR, 20 ms, authoritativenoyes / yesrefused-
ns2.cipal.be 193.190.121.3NOERROR, 20 ms, authoritativenoyes / yesrefused-

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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2023041951 · primary ns.cipal.be

Found

Primary (MNAME)
ns.cipal.be
Contact (RNAME)
hostmaster.cipal.be
Serial
2023041951
Refresh / retry
25200 s / 3600 s
Expire
2592000 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns.cipal.be (193.190.121.4)2023041951
ns2.cipal.be (193.190.121.3)2023041951

Checks

  • ✓ Serial 2023041951 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 7h, retry 1h, expire 30d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.cipal.be is one of the listed nameservers.
  • ✓ Contact hostmaster@cipal.be #25
    The SOA RNAME hostmaster.cipal.be means hostmaster@cipal.be.
  • ✓ Date-based serial #26
    The serial 2023041951 follows the YYYYMMDDnn convention (2023-04-19).

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

12 records at the apex

Found

Read from
193.190.121.4:53
TypeValueTTL
SOAns.cipal.be. hostmaster.cipal.be. 2023041951 25200 3600 2592000 9003600
NSns2.cipal.be.900
NSns.cipal.be.900
A185.3.217.1233600
AAAA2a02:5b40:4:228::4e900
MX0 zwaneberg-be.mail.protection.outlook.com.3600
TXT"google-site-verification=fCo_uGysUIxv_cwmlWp9ZZgN6KYXba9I8cn07kzkYhI"900
TXT"brevo-code:361eca44c96f0ac84fb025c4d83f50ea"3600
TXT"MS=ms17939807"3600
TXT"google-site-verification=9bbHTbH3kHLJftnj8Qpo6hoa8dzar_h3FPoHsO_b9Ng"900
TXT"sophos-domain-verification=4abf61ee5a4ba36a31b834a3ee00055b80f1dad61a96a814a31bacd5ec493170"900
TXT"v=spf1 ip4:62.148.163.157 ip4:62.148.163.134 ip4:194.78.224.212 include:spf.protection.outlook.com include:_spf_eucentral1.prod.hydra.sophos.com include:sendgrid.net -all"3600

Checks

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