Mail domain report: koeln.de

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf1.snafu.de include:_spf2.snafu.de include:netcologne.de ~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.koeln.de)

Found

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

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
sp	none	Subdomain 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

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mailin.koeln.de	A 84.23.254.54	mailin.koeln.de ✓
50	secondary.snafu.de	A 84.23.254.17	no PTR

Checks

✓ 2 MX records #9

Found 2 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: mailin.koeln.de, secondary.snafu.de

#11
✓ 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.
!

Addresses without reverse DNS

These MX addresses have no PTR record, which many receivers treat as a spam signal: 84.23.254.17 (secondary.snafu.de). Ask your hosting provider to set one.

#30

TLS

fail

MTA-STS record without policy · no TLS-RPT · DANE on 0 of 2 MX hosts

Found

MTA-STS record: v=STSv1; id=2026100501
Policy URL: https://mta-sts.koeln.de/.well-known/mta-sts.txt
Policy error: https://mta-sts.koeln.de/.well-known/mta-sts.txt returned HTTP 503

DANE (TLSA records)

MX host	TLSA	DNSSEC
mailin.koeln.de	none	-
secondary.snafu.de	none	-

Checks

✓ Record published #32

MTA-STS record found with id 2026100501.
✗

Policy not reachable

The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: https://mta-sts.koeln.de/.well-known/mta-sts.txt returned HTTP 503.

#33
!

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
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