RFC 8461: SMTP MTA Strict Transport Security (MTA-STS)
In plain English — editorial summary, not part of the RFC
SMTP MTA Strict Transport Security (MTA-STS) is a mechanism enabling mail service providers (SPs) to declare their ability to receive Transport Layer Security (TLS) secure SMTP connections and to specify whether sending SMTP servers should refuse to deliver to MX hosts that do not offer TLS with a trusted server certificate.
Document record
- Document ID
- RFC8461
- Published
- September 2018
- Authors
- D. Margolis; M. Risher; B. Ramakrishnan; A. Brotman; J. Jones
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8460SMTP TLS ReportingCurrent
September 2018
- RFC 8471The Token Binding Protocol Version 1.0Current
October 2018
- RFC 8472Transport Layer Security (TLS) Extension for Token Binding Protocol NegotiationCurrent
October 2018
- RFC 8449Record Size Limit Extension for TLSCurrent
August 2018
- RFC 8473Token Binding over HTTPCurrent
October 2018
- RFC 8448Example Handshake Traces for TLS 1.3Current
January 2019
- RFC 8447IANA Registry Updates for TLS and DTLSUpdated
August 2018
- RFC 8446The Transport Layer Security (TLS) Protocol Version 1.3Obsoleted
August 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?