SurfaceMap › b › bundesrat.de

bundesrat.de

Checked 2026-10-21 22:00 UTC · first added 2026-10-21
!Passed with warnings Score 85 of 100

Domain & DNS

warn

28 passed 1 warn 0 failed

Areas

iRegistration ✓Delegation iNameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 0 iterations and a 32-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 bundesrat.de ›

Mail

warn

26 passed 4 warn 0 failed

Areas

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

Problems

  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.bund.de, mx2.bund.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 bundesrat.de ›