Mail domain report: rechtslupe.de

SPF

pass

SPF record published

Found

Record: v=spf1 a mx ~all
DNS lookups: 2 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

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

warn

p=quarantine (_dmarc.rechtslupe.de)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:admin@rechtslupe.de
Found at: _dmarc.rechtslupe.de

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:admin@rechtslupe.de	Aggregate report addresses

Checks

!

Policy: quarantine

DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Applies to 100% of mail #18

DMARC policy applies to all failing mail.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:admin@rechtslupe.de
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

pass

Selectors: dkim

Found

Selectors: dkim
_domainkey: NOERROR

Selector	Key	Flags
dkim	RSA 4096 bits

Checks

✓ Keys found: dkim #7

DKIM keys found for this domain with selectors: dkim
✓ Strong keys #23

DKIM keys are strong enough: dkim: RSA 4096 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

1 mail server

Found

Priority	Host	Records	Reverse DNS
10	mail.praetormail.de	A 51.75.146.109 AAAA 2001:41d0:700:1f6d::1	mail.praetormail.de ✓ mail.praetormail.de ✓

Checks

✓ 1 MX record #9

Found 1 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.
!

Single MX host, no backup

Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
✓ At most 5 MX records #13

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

TLS

fail

MTA-STS enforce · TLS-RPT · DANE on 1 of 1 MX hosts

Found

MTA-STS record: v=STSv1; id=20260426014900Z;
Policy URL: https://mta-sts.rechtslupe.de/.well-known/mta-sts.txt
Mode: enforce
Allowed MX: mail.praetormail.de
Max age: 86400 seconds
TLS-RPT record: v=TLSRPTv1; rua=mailto:report@rechtslupe.de

DANE (TLSA records)

MX host	TLSA	DNSSEC
mail.praetormail.de	3 1 1 4d5bc2d164184979…	No

Checks

✓ Record published #32

MTA-STS record found with id 20260426014900Z.
✓ Policy enforced #33

The MTA-STS policy is enforced and cached for 24h0m0s.
✓ All MX hosts covered #34

Every MX host matches an mx: line of the MTA-STS policy.
✓ Reports enabled #35

TLS reports are sent to: mailto:report@rechtslupe.de
✗

TLSA records not DNSSEC-validated

These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: mail.praetormail.de.

#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