Mail domain report: uni-bonn.de

SPF

info

SPF record published

Found

Record: v=spf1 redirect=_spf.uni-bonn.de
DNS lookups: 1 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 1 DNS lookups (limit is 10).
i

Delegated via redirect

SPF record has no 'all' mechanism but redirects to _spf.uni-bonn.de, whose policy applies.

#3
✓ 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.uni-bonn.de)

Found

Record: v=DMARC1; p=none; sp=none; adkim=s; aspf=s; rua=mailto:dmarc@uni-bonn.de
Found at: _dmarc.uni-bonn.de

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
sp	none	Subdomain policy
rua	mailto:dmarc@uni-bonn.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:dmarc@uni-bonn.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

pass

3 mail servers

Found

Priority	Host	Records	Reverse DNS
10	esa1.rhrz.uni-bonn.de	A 131.220.18.241 AAAA 2a00:5ba0:0:102c::a	esa1.rhrz.uni-bonn.de ✓ esa1.rhrz.uni-bonn.de ✓
10	esa2.rhrz.uni-bonn.de	A 131.220.18.242 AAAA 2a00:5ba0:0:102d::b	esa2.rhrz.uni-bonn.de ✓ esa2.rhrz.uni-bonn.de ✓
10	esa3.rhrz.uni-bonn.de	A 131.220.18.243 AAAA 2a00:5ba0:0:102e::c	esa3.rhrz.uni-bonn.de ✓ esa3.rhrz.uni-bonn.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.
✓ All hosts have IPv6 #11

All MX records resolve to IPv6 addresses.
✓ 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 confirmed #30

All 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

TLS-RPT record: v=TLSRPTv1; rua=mailto:tlsrpt@uni-bonn.uriports.com

DANE (TLSA records)

MX host	TLSA	DNSSEC
esa1.rhrz.uni-bonn.de	none	-
esa2.rhrz.uni-bonn.de	none	-
esa3.rhrz.uni-bonn.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
✓ Reports enabled #35

TLS reports are sent to: mailto:tlsrpt@uni-bonn.uriports.com
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