hs-anhalt.de

Checked 21 October 2026, 22:51 UTC · via 8.8.8.8
✗Problems found
19 passed 3 warnings 2 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:51.89.73.208/28 ip4:147.135.249.48/28 ip4:54.37.79.226/32 include:spf.mailsupport.dfn.de include:spf.mailjet.com ~all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 2 of 10 DNS lookups #2
    SPF record needs 2 DNS lookups (limit is 10).
  • ✓ Ends with ~all #3
    SPF record properly uses ~all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

No DMARC record found

Checks

  • ✗
    No DMARC record
    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

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
10a1441.mx.srv.dfn.deA 194.95.232.81a1441.mx.srv.dfn.de ✓
10b1441.mx.srv.dfn.deA 194.95.234.81b1441.mx.srv.dfn.de ✓
10c1441.mx.srv.dfn.deA 194.95.238.81c1441.mx.srv.dfn.de ✓

Checks

  • ✓ 3 MX records #9
    Found 3 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: a1441.mx.srv.dfn.de, b1441.mx.srv.dfn.de, c1441.mx.srv.dfn.de
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 3 MX addresss have a PTR record that resolves back to them.

TLS

fail

MTA-STS record without policy · TLS-RPT · DANE on 3 of 3 MX hosts

Found

MTA-STS record
v=STSv1; id=20190326T143500
Policy URL
https://mta-sts.hs-anhalt.de/.well-known/mta-sts.txt
Policy error
Get "https://mta-sts.hs-anhalt.de/.well-known/mta-sts.txt": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
TLS-RPT record
v=TLSRPTv1; rua=mailto:postmaster@hs-anhalt.de

DANE (TLSA records)

MX hostTLSADNSSEC
a1441.mx.srv.dfn.de3 0 1 9bec67f55f2afdb7…Yes
b1441.mx.srv.dfn.de3 0 1 9bec67f55f2afdb7…Yes
c1441.mx.srv.dfn.de3 0 1 9bec67f55f2afdb7…Yes

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20190326T143500.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.hs-anhalt.de/.well-known/mta-sts.txt": context deadline exceeded (Client.Timeout exceeded while awaiting headers).
    #33
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:postmaster@hs-anhalt.de
  • ✓ DANE on all MX hosts #36
    All 3 MX hosts publish DNSSEC-validated TLSA records.

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38