Mail domain report: lz.de

SPF

fail

SPF record published

Found

Record: v=spf1 mx include:spf.teuto.net include:spf.protection.outlook.com ip4:212.8.209.192/29 ip4:212.8.197.0/24 ip4:195.140.184.0/22 ip4:91.192.40.0/22 ip4:213.157.3.185/32 ip4:212.227.126.0/25 include:_spfi.evolver.de include:spf.gutenberg-rz.de include:_spf.perfora.net include:_spf.kundenserver.de ip4:46.16.79.196/32 ip4:78.137.98.203/32 ip4:46.16.73.103/32 ip4:46.16.79.67/32 ip4:46.16.79.107/32 ip4:46.16.74.38/32 ip4:78.137.101.53/32 ip4:78.137.100.58 ip4:46.16.76.3/32 include:turbo-smtp.com include:25356209.spf05.hubspotemail.net -all
DNS lookups: 12 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✗

12 DNS lookups, over the limit of 10

SPF record needs 12 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.

#2
✓ 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

p=none (_dmarc.lz.de)

Found

Record: v=DMARC1; p=none;
Found at: _dmarc.lz.de

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy

Checks

✗

Policy: none (monitoring only)

DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
!

No aggregate reports (rua)

DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19

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

1 mail server

Found

Priority	Host	Records	Reverse DNS
10	lz-de.mail.protection.outlook.com	A 52.101.170.0 A 52.101.170.1 A 52.101.168.0 A 52.101.170.2 AAAA 2a01:111:f403:c967::a AAAA 2a01:111:f403:ca48::c AAAA 2a01:111:f403:ca48::12 AAAA 2a01:111:f403:ca09::a	mail-fr5p281cu00500.inbound.protection.outlook.com ✓ mail-fr4p281cu03101.inbound.protection.outlook.com ✓ mail-beup281cu00100.inbound.protection.outlook.com ✓ mail-fr6p281cu00202.inbound.protection.outlook.com ✓ mail-cpjpr05cu00102.inbound.protection.outlook.com ✓ mail-miypr03cu00104.inbound.protection.outlook.com ✓ mail-miypr05cu00202.inbound.protection.outlook.com ✓ mail-am7pr02cu00202.inbound.protection.outlook.com ✓

Checks

✓ 1 MX record #9

Found 1 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.
!

Single MX host, no backup

Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
✓ At most 5 MX records #13

Found 1 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 1 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
lz-de.mail.protection.outlook.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