th-rosenheim.de

Checked 22 October 2026, 00:40 UTC · via 8.8.8.8
✗Problems found
19 passed 4 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:141.60.0.0/16 ip4:195.200.70.64/26 ip4:46.29.101.1/32 ip4:46.29.101.2/32 ip4:62.67.226.167/32 ip4:217.150.155.10/32 ip4:217.150.155.12/32 include:_spf.o261.mx.srv.dfn.de include:_spf.kdv-fh-bayern.de a:bvbvxmail.bib-bvb.de include:spf.protection.outlook.com a:mail.sop-at.com include:_spf.salesforce.com a:rp.send.cnds.io include:spf.send.cnds.io -all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 10 of 10 DNS lookups #2
    SPF record needs 10 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

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
3454, 35365
Signatures valid until
1 November 2026, 09:53 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-11-01 #21
    DNSKEY signatures are valid until 2026-11-01T09:53:39Z.

MX

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
10a2611.mx.srv.dfn.deA 194.95.233.28a2611.mx.srv.dfn.de ✓
10b2611.mx.srv.dfn.deA 194.95.235.28b2611.mx.srv.dfn.de ✓
10c2611.mx.srv.dfn.deA 194.95.239.28c2611.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: a2611.mx.srv.dfn.de, b2611.mx.srv.dfn.de, c2611.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

warn

no MTA-STS · no TLS-RPT · DANE on 3 of 3 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
a2611.mx.srv.dfn.de3 0 1 9bec67f55f2afdb7…Yes
b2611.mx.srv.dfn.de3 0 1 9bec67f55f2afdb7…Yes
c2611.mx.srv.dfn.de3 0 1 9bec67f55f2afdb7…Yes

Checks

  • !
    Not configured
    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
    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
  • ✓ 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