Mail domain report: haufe.de

SPF

pass

SPF record published

Found

Record: v=spf1 +mx include:adns.haufe.de ip4:185.150.244.238 ip4:20.52.209.98 ip4:217.31.84.77 ip4:217.31.86.164 ip4:217.31.84.34 ip4:84.17.184.240/28 ip4:18.196.4.250 ~all
DNS lookups: 3 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 3 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.haufe.de)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:dmarc+aggregated@reports.nicmanager.net;
Found at: _dmarc.haufe.de
External report address: mailto:dmarc+aggregated@reports.nicmanager.net (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:dmarc+aggregated@reports.nicmanager.net	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:dmarc+aggregated@reports.nicmanager.net
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: k1

Found

Selectors: k1
_domainkey: NOERROR

Selector	Key	Flags
k1	RSA 1024 bits

Checks

✓ Keys found: k1 #7

DKIM keys found for this domain with selectors: k1
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits). Rotate to a 2048-bit key.

#23
✓ No problematic flags #24

No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 56333, 29825
Signatures valid until: 29 October 2026, 00:00 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-10-29 #21

DNSKEY signatures are valid until 2026-10-29T00:00:00Z.

MX

warn

3 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mail.haufe.de	A 185.150.247.40	mail.haufe.de ✓
20	mail2.haufe.de	A 185.150.247.41	mail2.haufe.de ✓
30	mail3.haufe.de	A 185.150.247.42	mail3.haufe.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.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: mail.haufe.de, mail2.haufe.de, mail3.haufe.de

#11
✓ 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 3 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@reports.nicmanager.net;

DANE (TLSA records)

MX host	TLSA	DNSSEC
mail.haufe.de	none	-
mail2.haufe.de	none	-
mail3.haufe.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@reports.nicmanager.net
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