Topic · Transport Security
MTA-STS testing mode
MTA-STS testing mode publishes a policy for observation without instructing senders to block delivery on policy failures.
How it works
Policy-aware senders may report TLS failures under the domain’s reporting configuration while continuing delivery.
What can go wrong
Testing mode does not by itself prevent downgrade attacks or invalid TLS delivery.
What to check or do
Use reports to resolve certificate and MX coverage gaps before enforcing the transport policy.
How to investigate MTA-STS testing mode
- Signal to investigate
- An MTA-STS policy is published in testing mode but an administrator expects recipients to reject insecure delivery.
- Evidence to collect
- Fetch the HTTPS policy text, verify the TXT policy id, and compare the mode and mx patterns with actual MX records.
- Common wrong conclusion
- mode: testing collects signals but does not request strict enforcement.
How to interpret the evidence
MTA-STS senders that support the standard may observe policy failures and generate reports, while continuing delivery according to their local rules. Published HTTPS alone does not prove that policy fetch is working.
What to change and how to verify it
Fix mismatched MX patterns and certificate errors, inspect TLS-RPT evidence, then move to enforce when all legitimate MX endpoints are covered.
Put this into practice
Run a focused check, then explore protection if your domain needs it.