Mail domain report: obi.de

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:84.17.184.240/28 ip4:213.61.69.162 ip4:217.9.112.165 ip4:212.186.193.50 ip4:213.185.164.18 ip4:18.197.251.173 ip4:52.29.201.254 ip4:3.120.167.104 ip4:18.185.195.229 ip4:52.58.235.215 ip4:52.58.48.167 ip4:18.196.84.111 ip4:18.194.214.102 include:spf.sendinblue.com ip4:85.158.196.35 ip4:85.158.196.36 ip4:85.158.196.37 ip4:85.158.196.241 ip4:85.158.196.242 ip4:85.158.196.243 ip4:85.158.196.244 include:_spf.google.com include:mail.zendesk.com include:_spf.salesforce.com ip4:195.200.255.124 include:spf.codepiraten.com a:spf.mas.t-systems-service.com a:mail.datanet.de a:securemail.datanet.de ip4:80.90.150.66 ip4:80.157.1.58 include:spf-a.opntxtdns.com -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

pass

p=reject (_dmarc.obi.de)

Found

Record: v=DMARC1; p=reject; rua=mailto:dmarc_reports@obi.de; adkim=s; aspf=s; fo=1:d:s;
Found at: _dmarc.obi.de

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
rua	mailto:dmarc_reports@obi.de	Aggregate report addresses
adkim	s	DKIM alignment (r = relaxed, s = strict)
aspf	s	SPF alignment (r = relaxed, s = strict)
fo	1:d:s	Failure reporting options

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_reports@obi.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, google, s1, s2

Found

Selectors: mail, google, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits
google	RSA 1024 bits
s1	RSA 2048 bits
s2	RSA 2048 bits

Checks

✓ Keys found: mail, google, s1, s2 #7

DKIM keys found for this domain with selectors: mail, google, s1, s2
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), google (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

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
1	aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
5	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1b	rd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
5	alt2.aspmx.l.google.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
10	alt3.aspmx.l.google.com	A 192.179.20.26 AAAA 2404:6800:4000:1027::1a	ncboms-in-f26.1e100.net ✓ ncboms-in-f26.1e100.net ✓
10	alt4.aspmx.l.google.com	A 192.178.158.26 AAAA 2404:6800:4013:813::1a	lcdels-in-f26.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

✓ 5 MX records #9

Found 5 MX records for this domain.
✓ All hosts resolve #10

All MX records resolve to valid IP addresses.
✓ All hosts have IPv6 #11

All MX records resolve to IPv6 addresses.
✓ Redundant MX hosts #12

Found 5 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 5 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 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
alt3.aspmx.l.google.com	none	-
alt4.aspmx.l.google.com	none	-

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