kampc.be

Checked 22 October 2026, 06:41 UTC · via 8.8.8.8
✗Problems found
19 passed 3 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

ns.cipal.be, ns.provant.be, ns2.cipal.be

Found

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

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.cipal.be, ns.provant.be, ns2.cipal.be.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns.provant.be (glue 193.190.154.28, zone 193.53.113.44). Update the glue at your registrar.
    #8
  • ✓ 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 (AS2611 (BELNET - BELNET, BE): 3 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 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.cipal.be 193.190.121.4NOERROR, 21 ms, authoritativenoyes / yesrefused-
ns.provant.be 193.53.113.44no responsenono / no--
ns2.cipal.be 193.190.121.3NOERROR, 20 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns.provant.be (193.53.113.44): read udp 46.225.38.91:39942->193.53.113.44:53: i/o timeout.
    #14
  • ✓ 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 2008013042 · primary ns.provant.be

Found

Primary (MNAME)
ns.provant.be
Contact (RNAME)
please_set_email.absolutely.nowhere
Serial
2008013042
Refresh / retry
10800 s / 3600 s
Expire
2592000 s
Negative TTL
900 s

Serial per nameserver

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

Checks

  • ✓ Serial 2008013042 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 30d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.provant.be is one of the listed nameservers.
  • ✓ Contact please_set_email@absolutely.nowhere #25
    The SOA RNAME please_set_email.absolutely.nowhere means please_set_email@absolutely.nowhere.
  • ✓ Date-based serial #26
    The serial 2008013042 follows the YYYYMMDDnn convention (2008-01-30).

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

16 records at the apex

Found

Read from
193.190.121.4:53
TypeValueTTL
SOAns.provant.be. please_set_email.absolutely.nowhere. 2008013042 10800 3600 2592000 900300
NSns2.cipal.be.300
NSns.provant.be.300
NSns.cipal.be.300
A188.208.37.0300
AAAA2a00:1c98:1000:12a4:0:3:ab35:9b5f300
MX10 d338290.b.ess.de.barracudanetworks.com.300
MX10 d338290.a.ess.de.barracudanetworks.com.300
TXT"d365mktkey=iETlOLfkvXf0QCAHlx9enbMgINpuIGQw4jQIyZo74swx"300
TXT"HARICA-WxLHIeepHH6z66wJ1ut"300
TXT"v=spf1 ip4:213.181.53.220 ip4:213.181.53.221 include:spf.ess.de.barracudanetworks.com include:_spf.createsend.com include:spf.protection.outlook.com include:procurios.cloud include:spf.facilitator.e2e.be include:145439271.spf02.hubspotemail.net ~all"300
TXT"include:customers.clickdimensions.com"300
TXT"P0R4O00328"300
TXT"Demonstration" "of" "domain" "control" "for" "DigiCert" "order" "#___________," "Validation" "e-mail:" "igor.spitters@provincieantwerpen.be"300
TXT"0ed1fe018a49fbe4f640294e2883bb86fb3eb6d480"300
TXT"MS=ms55151449"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, MX 5m, NS 5m. The NS TTL at the parent is 1d and in the zone 5m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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