<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Authentication on Sender Audit Blog</title><link>https://senderaudit.com/blog/en/tags/authentication/</link><description>Recent content in Authentication on Sender Audit Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://senderaudit.com/blog/en/tags/authentication/index.xml" rel="self" type="application/rss+xml"/><item><title>DMARCbis Explained: Changes, Implications for Senders and Receivers</title><link>https://senderaudit.com/blog/en/dmarcbis-explained/</link><pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate><guid>https://senderaudit.com/blog/en/dmarcbis-explained/</guid><description>&lt;p&gt;In May 2026, the IETF officially published &lt;strong&gt;DMARCbis&lt;/strong&gt; — the new version of the DMARC (Domain-based Message Authentication, Reporting, and Conformance) standard. This update replaces RFC 7489 from 2015 with three new documents: &lt;strong&gt;RFC 9989&lt;/strong&gt;, &lt;strong&gt;RFC 9990&lt;/strong&gt;, and &lt;strong&gt;RFC 9991&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;But what actually changes? Is this a revolution or an evolution? What are the concrete implications for you — whether you&amp;rsquo;re a &lt;strong&gt;domain administrator&lt;/strong&gt;, &lt;strong&gt;email service provider&lt;/strong&gt;, or &lt;strong&gt;email security specialist&lt;/strong&gt;?&lt;/p&gt;</description></item></channel></rss>