Skip to content
Glossary · Security

REQUIRETLS

An SMTP extension (RFC 8689) by which a sender requires that one message travel only over validated TLS on every hop, or bounce.

What it means

MTA-STS and DANE are set by the receiving domain. REQUIRETLS lets the sender decide per message. A client adds REQUIRETLS to the MAIL FROM command, and every hop must then use TLS, validate the next server's name through MTA-STS or DNSSEC, verify its certificate, and see REQUIRETLS advertised by the next server. If no path meets that, the message is returned with 5.7.30 (REQUIRETLS not supported) or 5.7.10 (encryption needed).

The same RFC defines a TLS-Required: No header, the opposite request: deliver even if the recipient's MTA-STS or DANE policy would block it, for example a security alert about a broken certificate.

Example

MAIL FROM:<alerts@example.com> REQUIRETLS

On this site

Sources

What this definition rests on. The wording is ours; the facts are theirs.

All 432 terms in the glossaryThe wiki: blocklists and bounce codes

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 25 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 25

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer