SurfaceMap › h › hannover-stadt.de

hannover-stadt.de

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

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA ✓DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns01.hannover-stadt.de: "9.18.39-0ubuntu0.22.04.7-Ubuntu"; ns02.hannover-stadt.de: "9.18.39-0ubuntu0.24.04.8-Ubuntu". 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 hannover-stadt.de ›

Mail

fail

26 passed 3 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: dmzmailgw03.hannover-stadt.de, dmzmailgw04.hannover-stadt.de
    #11
  • !
    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
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35

Recent checks

✗

Full report

Mail report for hannover-stadt.de ›