SurfaceMap › m › mivb.be

mivb.be

Checked 2026-10-22 06:51 UTC · first added 2026-10-21
✗Problems found Score 69 of 100

Domain & DNS

warn

20 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.clf.proximus.be: "2026.10.2"; ns2.clf.proximus.be: "2026.10.2"; ns3.clf.proximus.be: "2026.10.2". Hide or replace the version string.
    #17
  • !
    Not signed
    DNSSEC · 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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for mivb.be ›

Mail

fail

26 passed 3 warn 1 failed

Areas

✓SPF ✓DMARC ✗DKIM !DNSSEC !MX iTLS iBIMI

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.mivb.be does not exist (SERVFAIL), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mail.mivb.be
    #11
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 195.13.2.29 -> mail.brodwear.com.
    #30

Recent checks

✗

Full report

Mail report for mivb.be ›