Mail domain report: datenschutz-mv.de

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.dvz-mv.de -all
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).
✓ 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.datenschutz-mv.de)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:it@datenschutz-mv.de; ruf=mailto:it@datenschutz-mv.de; aspf=s; adkim=s; fo=1;
Found at: _dmarc.datenschutz-mv.de

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:it@datenschutz-mv.de	Aggregate report addresses
ruf	mailto:it@datenschutz-mv.de	Failure report addresses
adkim	s	DKIM alignment (r = relaxed, s = strict)
aspf	s	SPF alignment (r = relaxed, s = strict)
fo	1	Failure reporting options

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:it@datenschutz-mv.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

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

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: RSASHA256 (8)
Key tags: 24014, 38178
Signatures valid until: 3 November 2026, 17:13 UTC

Checks

✓ Signed, DS published at parent #8

DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
✓ Signatures valid until 2026-11-03 #21

DNSKEY signatures are valid until 2026-11-03T17:13:05Z.

MX

warn

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mx03.mvnet.de	A 85.208.248.81 AAAA 2a02:1006:c000:0:194:25:109:19	mx03.mvnet.de ✓ no PTR
10	mx04.mvnet.de	A 85.208.250.82 AAAA 2a02:1006:c000:0:194:25:109:20	mx04.mvnet.de ✓ 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.
✓ 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.
!

Addresses without reverse DNS

These MX addresses have no PTR record, which many receivers treat as a spam signal: 2a02:1006:c000:0:194:25:109:19 (mx03.mvnet.de), 2a02:1006:c000:0:194:25:109:20 (mx04.mvnet.de). Ask your hosting provider to set one.

#30

TLS

fail

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

Found

MTA-STS record: v=STSv1; id=20240912000001Z
Policy URL: https://mta-sts.datenschutz-mv.de/.well-known/mta-sts.txt
Policy error: https://mta-sts.datenschutz-mv.de/.well-known/mta-sts.txt returned HTTP 403
TLS-RPT record: v=TLSRPTv1; rua=mailto:it@datenschutz-mv.de

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx03.mvnet.de	3 0 1 63947a05cfac69ee…	Yes
mx04.mvnet.de	3 0 1 08e03bf18bf95916…	Yes

Checks

✓ Record published #32

MTA-STS record found with id 20240912000001Z.
✗

Policy not reachable

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

#33
✓ Reports enabled #35

TLS reports are sent to: mailto:it@datenschutz-mv.de
✓ 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