Mail domain report: dmea.de

SPF

fail

No SPF record found

warn

p=quarantine (_dmarc.dmea.de)

Record: v=DMARC1;p=quarantine;rua=mailto:dmarc@Messe-Muenchen.de;ruf=mailto:dmarc@Messe-Muenchen.de;sp=none;fo=1
Found at: _dmarc.dmea.de
External report address: mailto:dmarc@Messe-Muenchen.de (not authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
rua	mailto:dmarc@Messe-Muenchen.de	Aggregate report addresses
ruf	mailto:dmarc@Messe-Muenchen.de	Failure report addresses
fo	1	Failure reporting options

!

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:dmarc@Messe-Muenchen.de
!

Subdomains unprotected (sp=none)

DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

#20
!

Report address not authorized

These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc@Messe-Muenchen.de (needs dmea.de._report._dmarc.messe-muenchen.de). Ask the report provider to publish the record, or check the address.

#29

fail

No keys found under the checked selectors

warn

Not signed

pass

2 mail servers

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

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

warn

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

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

!

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.

info

No BIMI record