SurfaceMap › l › leuven.be

leuven.be

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

Domain & DNS

warn

23 passed 5 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: nsmaster.belnet.be. ns1.belnet.be, ns2.belnet.be, ns3.belnet.be, nsmaster.belnet.be report NS ns1.belnet.be ns2.belnet.be ns3.belnet.be nsmaster.belnet.be.
    #7
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2026101501 on ns1.belnet.be (193.190.198.14), ns1.belnet.be (2001:6a8:3c80::14), ns3.belnet.be (194.58.196.32), ns3.belnet.be (2a01:3f1:832::53), nsmaster.belnet.be (193.190.198.14), nsmaster.belnet.be (2001:6a8:3c80::14); 2026102201 on ns2.belnet.be (193.190.182.40), ns2.belnet.be (2001:6a8:3c80:c000::40). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    SOA · retry 2h should be shorter than refresh 2h. Current values: refresh 2h, retry 2h, expire 14d, negative TTL 15m.
    #23
  • !
    Signatures expire soon
    DNSSEC · The earliest signature expires at 2026-10-29 00:00 UTC (in 161h0m0s). Check that automatic re-signing works.
    #30
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 1 iteration and a 4-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Recent checks

!

Full report

Domain & DNS report for leuven.be ›

Mail

fail

25 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    Weak DKIM key
    DKIM · RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): pm (768 bits). Rotate to a 2048-bit key.
    #23
  • !
    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: smtp1.leuven.be
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

✗

Full report

Mail report for leuven.be ›