bmu.de

Checked 21 October 2026, 21:50 UTC · via 8.8.8.8
✗Problems found
15 passed 7 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:85.220.144.8 ip4:85.220.144.9 ip4:149.13.94.44 ~all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

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

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.bund.deA 77.87.224.131mx1.bund.de ✓
15mx2.bund.deA 77.87.228.115mx2.bund.de ✓
20mailer-bonn.ivbb.bund.de(does not resolve)
25mailer-berlin.ivbb.bund.de(does not resolve)

Checks

  • ✓ 4 MX records #9
    Found 4 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: mailer-bonn.ivbb.bund.de, mailer-berlin.ivbb.bund.de
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx1.bund.de, mx2.bund.de, mailer-bonn.ivbb.bund.de, mailer-berlin.ivbb.bund.de
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 2 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.bund.de3 0 1 5ae2cc8699e165de…Yes
mx2.bund.de3 0 1 5ae2cc8699e165de…Yes
mailer-bonn.ivbb.bund.denone-
mailer-berlin.ivbb.bund.denone-

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
  • !
    Not all MX hosts use DANE
    These MX hosts publish no TLSA records, so mail to them is not protected by DANE: mailer-bonn.ivbb.bund.de, mailer-berlin.ivbb.bund.de.
    #36

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