bdo.de

Checked 21 October 2026, 21:36 UTC · via 8.8.8.8
!Passed with warnings
25 passed 4 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spfv4.sosafe.de include:spfv6.sosafe.de exists:%{i}.spf.hc697-83.eu.iphmx.com include:spf.protection.outlook.com include:_spf.jpberlin.de include:_spf.qp-mail.eu include:spf.mailjet.com include:_spf.salesforce.com ip4:23.90.102.228/32 ip4:23.90.102.231/32 ip4:23.90.105.137/32 ip4:23.90.105.144/32 ip4:23.253.182.0/23 ip4:69.72.32.0/20 ip4:87.253.232.0/21 ip4:104.130.96.0/28 ip4:104.130.122.0/23 ip4:141.193.32.0/23 ip4:143.55.224.0/21 ip4:143.55.232.0/22 ip4:143.55.236.0/22 ip4:146.20.112.0/26 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.112.240.0/20 ip4:159.135.132.128/25 ip4:159.135.140.80/29 ip4:159.135.224.0/20 ip4:161.38.192.0/20 ip4:161.38.204.0/22 ip4:166.78.68.0/22 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:192.237.158.0/23 ip4:198.61.254.0/23 ip4:198.244.48.0/20 ip4:198.244.60.0/22 ip4:204.220.160.0/21 ip4:204.220.168.0/21 ip4:204.220.176.0/20 ip4:207.54.71.200/32 ip4:209.61.151.0/24 -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

pass

p=reject (_dmarc.bdo.de)

Found

Record
v=DMARC1; p=reject; rua=mailto:dmarc_aggregate@bdo.de;
Found at
_dmarc.bdo.de
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:dmarc_aggregate@bdo.deAggregate report addresses

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc_aggregate@bdo.de
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, s1, s2

Found

Selectors
mail, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: mail, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.hc697-83.eu.iphmx.comA 23.90.105.144 A 23.90.105.137 A 23.90.102.228 A 207.54.71.200esa4.hc697-83.eu.iphmx.com ✓ esa3.hc697-83.eu.iphmx.com ✓ esa1.hc697-83.eu.iphmx.com ✓ esa2.hc697-83.eu.iphmx.com ✓
10mx2.hc697-83.eu.iphmx.comA 23.90.105.137 A 23.90.102.228 A 207.54.71.200 A 23.90.105.144esa3.hc697-83.eu.iphmx.com ✓ esa1.hc697-83.eu.iphmx.com ✓ esa2.hc697-83.eu.iphmx.com ✓ esa4.hc697-83.eu.iphmx.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: mx1.hc697-83.eu.iphmx.com, mx2.hc697-83.eu.iphmx.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.hc697-83.eu.iphmx.comnone-
mx2.hc697-83.eu.iphmx.comnone-

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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #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