Mail domain report: deka.de

SPF

fail

SPF record published

Found

Record: v=spf1 mx exists:%{l}.spf.deka.de ip4:91.207.212.9 ip4:62.209.51.6 ip4:92.51.149.51 ip4:217.66.52.20 ip4:217.66.54.189 ip4:89.202.109.2 ip4:50.31.156.96/27 ip4:50.31.205.0/24 ip4:104.245.209.192/26 ip4:84.38.79.0/24 ip4:155.56.221.13 ip4:155.56.221.14 ip4:155.56.220.141 ip4:155.56.220.142 ip4:155.56.221.15 ip4:155.56.221.16 ip4:155.56.222.26 ip4:155.56.222.27 ip4:217.66.54.148 ip4:217.66.54.154 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:194.245.120.202/31 ip4:83.141.11.66 ip4:83.141.11.66 ip4:194.245.120.205 ip4:155.56.208.68 ip4:130.214.193.83 ip4:130.214.193.93 ip4:130.214.193.78 ip4:130.214.193.85 ip4:77.74.232.231 ip4:77.74.232.232 ip4:185.154.148.13 ip4:185.154.150.13 ip4:185.154.148.0/22 ip4:212.6.132.208/28 ip4:2.104.131.31 ip4:172.20.246.72 ip4:172.20.246.77 ip4:2.104.135.52 ip4:2.104.135.51 ip4:83.171.132.152 ip4:83.171.132.153 ip4:83.171.132.154 ip4:83.171.132.147 ip4:83.171.132.135 ip4:83.171.132.136 ip4:20.113.48.156 ip4:9.223.106.210 ip4:52.215.218.128/25 ip4:63.34.31.0/25 ip4:3.122.63.0/25 ip4:3.122.63.128/25 include:_spfa.deka.de -all
DNS lookups: 17 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✗

17 DNS lookups, over the limit of 10

SPF record needs 17 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.deka.de)

Found

Record: v=DMARC1; p=none; rua=mailto:Spoofing-reports@deka.de ; adkim=s; aspf=s
Found at: _dmarc.deka.de

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:Spoofing-reports@deka.de	Aggregate report addresses
adkim	s	DKIM alignment (r = relaxed, s = strict)
aspf	s	SPF alignment (r = relaxed, s = strict)

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.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:Spoofing-reports@deka.de
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

pass

Selectors: selector1, selector2

Found

Selectors: selector1, selector2
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 2048 bits
selector2	RSA 2048 bits

Checks

✓ Keys found: selector1, selector2 #7

DKIM keys found for this domain with selectors: selector1, selector2
✓ Strong keys #23

DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits.
✓ 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

5 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mx.emea.email.fireeyecloud.com	A 3.123.5.7 A 63.34.218.7 A 3.123.5.6 A 63.34.218.8 A 3.123.5.8 A 63.34.218.6	mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓
20	primary.emea.email.fireeyecloud.com	A 3.123.5.7 A 63.34.218.6 A 63.34.218.8 A 3.123.5.6 A 63.34.218.7 A 3.123.5.8	mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓
30	alt1.emea.email.fireeyecloud.com	A 3.123.5.6 A 63.34.218.7 A 63.34.218.6 A 3.123.5.7 A 63.34.218.8 A 3.123.5.8	mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓
40	alt2.emea.email.fireeyecloud.com	A 63.34.218.7 A 63.34.218.8 A 3.123.5.8 A 63.34.218.6 A 3.123.5.6 A 3.123.5.7	mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓
50	alt3.emea.email.fireeyecloud.com	A 63.34.218.7 A 63.34.218.6 A 3.123.5.6 A 3.123.5.8 A 3.123.5.7 A 63.34.218.8	mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓ mx.emea.email.fireeyecloud.com ✓

Checks

✓ 5 MX records #9

Found 5 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: mx.emea.email.fireeyecloud.com, primary.emea.email.fireeyecloud.com, alt1.emea.email.fireeyecloud.com, alt2.emea.email.fireeyecloud.com, alt3.emea.email.fireeyecloud.com

#11
✓ 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 30 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
mx.emea.email.fireeyecloud.com	none	-
primary.emea.email.fireeyecloud.com	none	-
alt1.emea.email.fireeyecloud.com	none	-
alt2.emea.email.fireeyecloud.com	none	-
alt3.emea.email.fireeyecloud.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