Folderly Flash Send-readiness test

Fix an MTA-STS and TLS-RPT warning

If Flash reports an MTA-STS or TLS-RPT warning, it did not find both recognized TXT records at the visible From domain. Flash checks DNS presence only; it does not fetch the HTTPS policy, validate MX hosts or certificates, test STARTTLS, verify the report destination or inspect reports.

Why mailbox providers enforce this

MTA-STS is an inbound transport-security policy: it tells supporting senders how to authenticate TLS when delivering mail to your domain. TLS-RPT supplies aggregate reports about policy and TLS failures. They are separate from SPF, DKIM and DMARC, and they do not prove outbound inbox placement. A Flash pass means the two expected DNS record types were present, not that the complete policy or reporting path works.

Primary sources for this guidance

How to fix it

  1. Confirm the visible From domain in the Flash result and identify who owns its DNS, inbound MX hosts, HTTPS service and TLS-report destination. If the domain does not receive mail, confirm the intended inbound-security policy before publishing records.
  2. Read the exact Flash finding. It checks for a TXT value beginning v=STSv1 at _mta-sts.yourdomain and a TXT value beginning v=TLSRPTv1 at _smtp._tls.yourdomain. A temporary DNS lookup is unknown and is not penalized.
  3. Inventory every legitimate inbound MX host and verify that each supports STARTTLS with a publicly trusted certificate whose identity matches the host. Repair that transport path before choosing enforce mode.
  4. Create a monitored TLS-report destination, then publish _smtp._tls.yourdomain with v=TLSRPTv1 and an authorized rua= mailto or HTTPS destination. Treat report payloads as untrusted input and control report volume.
  5. Host the MTA-STS policy as plain text at https://mta-sts.yourdomain/.well-known/mta-sts.txt over HTTPS with a publicly trusted certificate. Include version, mode, max_age and one or more mx fields unless mode is none.
  6. Start with mode testing when you need evidence about legitimate delivery paths. Review TLS reports and correct MX, certificate or STARTTLS failures before moving to enforce; enforce can stop delivery that does not satisfy the policy.
  7. Publish _mta-sts.yourdomain with v=STSv1 and a changed id value whenever the policy changes so supporting senders know to retrieve the new policy.
  8. Validate the DNS records, fetch the exact HTTPS policy URL, compare every policy mx pattern with the live MX set, check certificates and STARTTLS, and confirm reports arrive at the monitored destination. Flash does not perform those checks.
  9. After DNS propagation, run one comparable production-path message through Flash to confirm record presence. Keep the external policy, transport and report checks as the release evidence for MTA-STS itself.

Limitations

Flash checks whether recognized MTA-STS and TLS-RPT TXT records are present for the visible From domain. It does not fetch or parse the HTTPS policy. It does not validate TXT tag completeness, policy MX patterns, live MX records, certificates, STARTTLS, the reporting endpoint or reports. It does not prove secure delivery or measure inbox placement.

Next action Assign the DNS, inbound-mail and report-endpoint owners, complete the policy and transport checks outside Flash, then run one comparable production-path retest after DNS propagation to confirm only the two record-presence findings.
Run a free test →

FAQ

Does a Flash pass prove that MTA-STS is configured correctly?
No. Flash confirms recognized MTA-STS and TLS-RPT TXT records at the visible From domain. It does not fetch or parse the policy file, compare MX hosts, validate HTTPS or SMTP certificates, test STARTTLS, verify the rua destination or inspect reports.
Will MTA-STS improve outbound inbox placement?
MTA-STS protects supported inbound delivery to your domain. It does not replace SPF, DKIM or DMARC and does not prove reputation, recipient response or outbound inbox placement.
What is the difference between testing and enforce mode?
Testing mode lets delivery continue when the MTA-STS policy cannot be satisfied while eligible failures can appear in TLS reports. Enforce mode tells supporting senders not to deliver over a connection that fails the policy, so verify every legitimate MX path first.
Do I need TLS-RPT with MTA-STS?
TLS-RPT is the feedback path for aggregate transport-policy failures. It is separate from enforcement, but without monitored reports you lose evidence needed to find certificate, STARTTLS and MX-policy mismatches.

Related

Content record Owner: Folderly Flash content operations Reviewed: 2026-10-20 Maintenance trigger: Review when Flash expands transport-policy validation, RFC 8461 or RFC 8460 changes, or Google Workspace changes its MTA-STS configuration guidance.
Want a deliverability engineer to fix this for you? Hand it to Folderly →