Mail domain report: evangelisch.de

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.mailjet.com a mx ip4:92.204.71.0/23 ip4:92.205.237.203 ip4:46.163.91.24 ip4:46.163.91.25 ip4:46.163.91.26 ip4:46.163.91.29 ip4:46.163.91.30 ip4:185.86.158.68 ip4:217.110.237.37 ip4:217.110.237.40 -all
DNS lookups: 3 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 3 of 10 DNS lookups #2

SPF record needs 3 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

p=none (_dmarc.evangelisch.de)

Found

Record: v=DMARC1; p=none; rua=mailto:webmaster@evangelisch.de; ruf=mailto:webmaster@evangelisch.de;
Found at: _dmarc.evangelisch.de

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:webmaster@evangelisch.de	Aggregate report addresses
ruf	mailto:webmaster@evangelisch.de	Failure report addresses

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:webmaster@evangelisch.de
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

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

3 mail servers

Found

Priority	Host	Records	Reverse DNS
10	gep-ffm.in.tmes.trendmicro.eu	A 18.185.115.145 A 18.185.115.147 A 18.185.115.146	in.tmes.trendmicro.eu ✓ in.tmes.trendmicro.eu ✓ in.tmes.trendmicro.eu ✓
20	mx-m1.bisping.de	A 91.99.178.218	wms-m1.bisping.net (does not resolve back)
30	mx-l2.bisping.de	A 62.91.92.21	mx-l2.bisping.de ✓

Checks

✓ 3 MX records #9

Found 3 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: gep-ffm.in.tmes.trendmicro.eu, mx-m1.bisping.de, mx-l2.bisping.de

#11
✓ Redundant MX hosts #12

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

Found 3 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 does not match

The PTR name of these addresses does not resolve back to the same address: 91.99.178.218 -> wms-m1.bisping.net.

#30

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
gep-ffm.in.tmes.trendmicro.eu	none	-
mx-m1.bisping.de	none	-
mx-l2.bisping.de	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