SurfaceMap › p › privacycommission.be

privacycommission.be

Checked 2026-10-22 07:01 UTC · first added 2026-10-21
!Passed with warnings Score 79 of 100

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA iDNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: elma.ns.cloudflare.com: "2026.10.2"; piers.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for privacycommission.be ›

Mail

warn

28 passed 5 warn 0 failed

Areas

✓SPF !DMARC !DKIM ✓DNSSEC !MX !TLS iBIMI

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: apd-gba-be-1.fortimailcloud.com, apd-gba-be-2.fortimailcloud.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Policy in testing mode
    TLS · With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.
    #33
  • !
    MX hosts missing from policy
    TLS · These MX hosts are not listed in the MTA-STS policy (mx: gw000111-eu.fortimail.com): apd-gba-be-1.fortimailcloud.com, apd-gba-be-2.fortimailcloud.com. This will break delivery once the policy is enforced.
    #34

Recent checks

!

Full report

Mail report for privacycommission.be ›