MTA-STS (Mail Transfer Agent Strict Transport Security)
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://tldfyi.com/iframe/glossary/mta-sts/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>
Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://tldfyi.com/glossary/mta-sts/
Add a dynamic SVG badge to your README or docs.
[](https://tldfyi.com/glossary/mta-sts/)
Use the native HTML custom element.
MTA-STS (RFC 8461) is a mechanism that allows email domains to declare a policy requiring that inbound SMTP connections to their mail servers use TLS and present a valid [[ssl-tls|certificate]]. The policy is published via a DNS TXT record pointing to an HTTPS-served policy file, and sending mail servers that support MTA-STS will fetch and cache the policy before delivering mail. MTA-STS prevents opportunistic TLS downgrade attacks — where attackers intercept SMTP traffic and strip encryption — and complements [[dane|DANE]] as an alternative that does not require [[dnssec|DNSSEC]]. Implementing MTA-STS alongside [[dmarc|DMARC]] and [[spf-record|SPF]] significantly hardens an organization's email security posture.
Example
Google publishes an MTA-STS policy for gmail.com; external mail servers that support MTA-STS will refuse to deliver email to Gmail over a plaintext or self-signed TLS connection.