Mail domain report: bayern-evangelisch.de

SPF

pass

SPF record published

Found

Record: v=spf1 a:mail.bayern-evangelisch.de a:www.bayern-evangelisch.de include:cmail1.com include:spf.crsend.com ~all
DNS lookups: 4 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 4 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.bayern-evangelisch.de)

Found

Record: v=DMARC1; p=none; rua=mailto:bev_dmarc@kerygma.de; ruf=mailto:bev_dmarc@kerygma.de; sp=none; fo=1; adkim=r; aspf=r
Found at: _dmarc.bayern-evangelisch.de
External report address: mailto:bev_dmarc@kerygma.de (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
sp	none	Subdomain policy
rua	mailto:bev_dmarc@kerygma.de	Aggregate report addresses
ruf	mailto:bev_dmarc@kerygma.de	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
fo	1	Failure reporting options

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:bev_dmarc@kerygma.de
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

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

pass

2 mail servers

Found

Priority	Host	Records	Reverse DNS
100	gatekeeper.space.net	A 195.30.114.130 A 194.97.132.2 A 194.97.132.16 AAAA 2001:608:3:84::2 AAAA 2001:608:2:84::130 AAAA 2001:608:3:84::16	gatekeeper2.space.net ✓ gatekeeper1.space.net ✓ gatekeeper3.space.net ✓ gatekeeper1.space.net ✓ gatekeeper2.space.net ✓ gatekeeper3.space.net ✓
100	gatekeeper.spacenet.de	A 195.30.114.135 A 194.97.132.15 A 194.97.132.6 AAAA 2001:608:3:84::15 AAAA 2001:608:2:84::135 AAAA 2001:608:3:84::6	gatekeeper2.spacenet.de ✓ gatekeeper3.spacenet.de ✓ gatekeeper1.spacenet.de ✓ gatekeeper3.spacenet.de ✓ gatekeeper2.spacenet.de ✓ gatekeeper1.spacenet.de ✓

Checks

✓ 2 MX records #9

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
gatekeeper.space.net	3 1 1 2da870224ea7666d…	Yes
gatekeeper.spacenet.de	3 1 1 c68d7e7d8b26e6f6…	Yes

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
!

Not configured

MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

#35
✓ DANE on all MX hosts #36

All 2 MX hosts publish DNSSEC-validated TLSA records.

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