Mail domain report: ping.de

SPF

pass

SPF record published

Found

Record: v=spf1 mx ip4:89.238.69.84 ip4:138.201.142.202 ip6:2a01:4f8:171:413:66ea::42 ip4:89.58.28.183 ip4:85.214.25.206 ip4:89.238.65.246 ip6:2a00:1828:2000:833::2 ip4:89.238.65.208 ip6:2a00:1828:2000:824::3 ip4:85.22.138.154 ip6:2001:470:9d7f::1 ip4:162.19.143.17 ip4:167.235.0.46 ip6:2a01:4f8:262:445e:100::4 -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

pass

p=reject (_dmarc.ping.de)

Found

Record: v=DMARC1;p=reject;sp=reject;rua=mailto:dmarc@ping.de;ruf=mailto:dmarc@ping.de;adkim=r;aspf=r;
Found at: _dmarc.ping.de

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	reject	Subdomain policy
rua	mailto:dmarc@ping.de	Aggregate report addresses
ruf	mailto:dmarc@ping.de	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)

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@ping.de
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
✓ 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 2048 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 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
0	mail.ping.ruhr	A 167.235.0.46 AAAA 2a01:4f8:262:445e:100::4	mail.ping.ruhr ✓ mail.ping.ruhr ✓

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 testing · TLS-RPT · DANE on 1 of 1 MX hosts

Found

MTA-STS record: v=STSv1; id=20250914092600Z;
Policy URL: https://mta-sts.ping.de/.well-known/mta-sts.txt
Mode: testing
Allowed MX: mail.ping.ruhr
Max age: 86400 seconds
TLS-RPT record: v=TLSRPTv1;rua=mailto:postmaster@ping.de

DANE (TLSA records)

MX host	TLSA	DNSSEC
mail.ping.ruhr	3 1 1 75c9adbe3b62524f…	No

Checks

✓ Record published #32

MTA-STS record found with id 20250914092600Z.
!

Policy in testing mode

With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.

#33
✓ 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:postmaster@ping.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.ping.ruhr.

#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