SurfaceMap › b › bundesarchiv.de

bundesarchiv.de

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

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration iDelegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 1h, expire 7d, negative TTL 1m.
    #23
  • !
    Signatures expire soon
    DNSSEC · The earliest signature expires at 2026-10-26 05:46 UTC (in 104h0m0s). Check that automatic re-signing works.
    #30

Recent checks

!

Full report

Domain & DNS report for bundesarchiv.de ›

Mail

fail

22 passed 5 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
  • !
    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
  • !
    Signatures expire in 104h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-26T05:46:01Z (in 104h0m0s). Check that re-signing works.
    #21
  • !
    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 bundesarchiv.de ›