Looking up MTA-STS DNS record, fetching policy file, and checking TLS-RPT...
Looking up MTA-STS DNS record, fetching policy file, and checking TLS-RPT...
MTA-STS + TLS-RPT for
Checked 5/14/2026, 10:53:04 PM · 141ms
No MTA-STS at all. Mail in transit is not enforced.
looked up: _mta-sts.sap.com
https://mta-sts.sap.com/.well-known/mta-sts.txt
v=TLSRPTv1; rua=mailto:[email protected]
for sap.com
The id is an opaque string. Bump it whenever you change the policy file, otherwise receivers will keep using the cached version.
_mta-stsv=STSv1; id=20260514225304Host the file below at https://mta-sts.sap.com/.well-known/mta-sts.txt with a trusted TLS cert (no self-signed). Replace the mx: line(s) with each of your real mail servers. Start with mode: testing to collect TLS-RPT failure reports before raising to mode: enforce.
version: STSv1 mode: testing mx: mail.sap.com max_age: 86400
Cloudflare Workers, Pages, or any static host with HTTPS can serve this. The well-known path needs a Content-Type of text/plain.
AI-assisted remediation
Wiredepth Pro sends this report to our AI engine and streams back a 30-day rollout plan tailored to sap.com, with provider-specific tips when we can infer them from the data. 10 playbooks per month on Pro, 100 on MSP.
Or share this URL with the team that owns the records.