<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TLS on PeteMahon.net</title><link>https://petemahon.net/tags/tls/</link><description>Recent content in TLS on PeteMahon.net</description><generator>Hugo</generator><language>en</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Fri, 15 May 2026 11:00:00 +0400</lastBuildDate><atom:link href="https://petemahon.net/tags/tls/index.xml" rel="self" type="application/rss+xml"/><item><title>You've Done DMARC. You Haven't Done Email Security. An MTA-STS Walkthrough.</title><link>https://petemahon.net/posts/2026/05/youve-done-dmarc.-you-havent-done-email-security.-an-mta-sts-walkthrough./</link><pubDate>Fri, 15 May 2026 11:00:00 +0400</pubDate><guid>https://petemahon.net/posts/2026/05/youve-done-dmarc.-you-havent-done-email-security.-an-mta-sts-walkthrough./</guid><description>&lt;h2 id="the-gap"&gt;The gap&lt;/h2&gt;
&lt;p&gt;Most domains have SPF, DKIM and DMARC sorted. If yours does, that&amp;rsquo;s good work. It also has nothing to do with whether the email arriving at your domain is actually encrypted in transit.&lt;/p&gt;
&lt;p&gt;SPF, DKIM and DMARC are &lt;em&gt;outbound&lt;/em&gt; authentication. They prove to receiving servers that mail claiming to be from your domain is legitimate. They protect your sending reputation.&lt;/p&gt;
&lt;p&gt;MTA-STS is &lt;em&gt;inbound&lt;/em&gt; transport security. It enforces that mail sent &lt;em&gt;to&lt;/em&gt; your domain is encrypted, refuses delivery if it can&amp;rsquo;t be, and pins which MX hosts are allowed to receive it. Different problem, different protocol, and as of the date of posting this, almost completely missing.&lt;/p&gt;</description></item></channel></rss>