Mail domain report: braun.de

SPF

fail

SPF record published

Found

Record: v=spf1 include ns3-01.azure-dns.org ns2-01.azure-dns.net ns1-01.azure-dns.com ~all
DNS lookups: 1 of 10
Void lookups: 0 of 2
Problem: include without a domain

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
!

1 of 10 DNS lookups, with problems

SPF record needs 1 DNS lookups (limit is 10). Problems found: include without a domain.

#2
✓ 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.
✗

Syntax errors

Receivers reject the whole SPF record (permerror) because of: "include": include needs a value; unknown mechanism "ns3-01.azure-dns.org"; unknown mechanism "ns2-01.azure-dns.net"; unknown mechanism "ns1-01.azure-dns.com".

#25
✓ 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=reject (_dmarc.braun.de)

Found

Record: v=DMARC1; p=reject; sp=none; fo=1; ri=3600; rua=mailto:dmarc_agg@vali.email;
Found at: _dmarc.braun.de
External report address: mailto:dmarc_agg@vali.email (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	none	Subdomain policy
rua	mailto:dmarc_agg@vali.email	Aggregate report addresses
fo	1	Failure reporting options
ri	3600	Report interval (seconds)

Checks

✓ Policy: reject #4

DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
✓ 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_agg@vali.email
!

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
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: s1

Found

Selectors: s1
_domainkey: NOERROR

Selector	Key	Flags
s1	RSA 2048 bits

Checks

✓ Keys found: s1 #7

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

DKIM keys are strong enough: s1: RSA 2048 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	parse.mailjet.com	A 35.205.202.134	134.202.205.35.bc.googleusercontent.com ✓

Checks

✓ 1 MX record #9

Found 1 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: parse.mailjet.com

#11
!

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
parse.mailjet.com	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
i

Not configured

TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.

#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