<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Email Authentication on Secure Techies</title><link>https://securetechie.com/tags/email-authentication/</link><description>Recent content in Email Authentication on Secure Techies</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 18 Sep 2026 00:00:00 -0700</lastBuildDate><atom:link href="https://securetechie.com/tags/email-authentication/index.xml" rel="self" type="application/rss+xml"/><item><title>DMARC for Small Business: From Monitor to Reject</title><link>https://securetechie.com/blog/dmarc-for-small-business/</link><pubDate>Fri, 18 Sep 2026 00:00:00 -0700</pubDate><guid>https://securetechie.com/blog/dmarc-for-small-business/</guid><description>&lt;p&gt;Here&amp;rsquo;s the short version: &lt;strong&gt;DMARC for small business is a DNS policy you tighten in public, not a checkbox you set to reject on day one.&lt;/strong&gt; SPF and DKIM have to work first. Then &lt;code&gt;p=none&lt;/code&gt;, then quarantine, then reject. Skip the ladder and you will block your own invoices.&lt;/p&gt;</description></item><item><title>A Close Call With a Fake Wire Instruction</title><link>https://securetechie.com/case-studies/wire-fraud-email-close-call/</link><pubDate>Thu, 13 Aug 2026 00:00:00 -0700</pubDate><guid>https://securetechie.com/case-studies/wire-fraud-email-close-call/</guid><description>A San Fernando Valley law firm almost sent a settlement wire after a lookalike email used a partner&amp;rsquo;s display name. Staff called the partner on a known number first. The partner had not sent it. Secure Techies reviewed the mailboxes, closed identity gaps, set email authentication on a path to enforcement, and left a written call-back that is now a rule, not a suggestion.</description></item></channel></rss>