SurfaceMap › h › hs-ansbach.de

hs-ansbach.de

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

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration !Delegation iNameservers iSOA !DNSSEC ✓Records

Problems

  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 193.174.75.0/24; all IPv6 addresses are in 2001:638:d::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 10 iterations and a 14-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 hs-ansbach.de ›

Mail

fail

22 passed 3 warn 1 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • !
    Signatures expire in 37h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-23T11:26:02Z (in 37h0m0s). 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 hs-ansbach.de ›