<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: DNSFix</title>
    <description>The latest articles on DEV Community by DNSFix (@dnsfix).</description>
    <link>https://dev.to/dnsfix</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4251477%2Fe8d86175-dbc5-4e1d-ba62-292198f282c4.png</url>
      <title>DEV Community: DNSFix</title>
      <link>https://dev.to/dnsfix</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dnsfix"/>
    <language>en</language>
    <item>
      <title>How to set up DMARC (and fix "No DMARC record found")</title>
      <dc:creator>DNSFix</dc:creator>
      <pubDate>Wed, 18 Nov 2026 09:13:14 +0000</pubDate>
      <link>https://dev.to/dnsfix/how-to-set-up-dmarc-and-fix-no-dmarc-record-found-28nd</link>
      <guid>https://dev.to/dnsfix/how-to-set-up-dmarc-and-fix-no-dmarc-record-found-28nd</guid>
      <description>&lt;p&gt;DMARC is one TXT record at _dmarc.yourdomain that tells inboxes what to do with fakes and sends you reports.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start here
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;v=DMARC1; p=none; rua=mailto:&lt;a href="mailto:reports@dnsfix.com"&gt;reports@dnsfix.com&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Add it as a TXT record with host &lt;code&gt;_dmarc&lt;/code&gt;. &lt;code&gt;p=none&lt;/code&gt; blocks nothing; it only turns on reports so you can see who sends as you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Every DMARC tag
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Tag v:&lt;/strong&gt; the version, always &lt;code&gt;DMARC1&lt;/code&gt;, and it must come first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag p:&lt;/strong&gt; the policy for your domain: &lt;code&gt;none&lt;/code&gt; (only report), &lt;code&gt;quarantine&lt;/code&gt; (spam folder) or &lt;code&gt;reject&lt;/code&gt; (refuse).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag sp:&lt;/strong&gt; the policy for subdomains. Without it, subdomains follow &lt;code&gt;p&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag np:&lt;/strong&gt; the policy for subdomains that don't exist at all. Set it to &lt;code&gt;reject&lt;/code&gt; once you can.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag rua:&lt;/strong&gt; where daily summary reports go (&lt;code&gt;mailto:&lt;/code&gt; addresses). An address at another domain needs that domain's permission record.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag ruf:&lt;/strong&gt; where failure samples go. Few providers send them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag adkim:&lt;/strong&gt; DKIM alignment: &lt;code&gt;r&lt;/code&gt; (relaxed, the default) lets a subdomain match; &lt;code&gt;s&lt;/code&gt; (strict) needs the exact domain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag aspf:&lt;/strong&gt; SPF alignment, same idea as adkim.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag fo:&lt;/strong&gt; when failure samples are sent: &lt;code&gt;0&lt;/code&gt; (default), &lt;code&gt;1&lt;/code&gt;, &lt;code&gt;d&lt;/code&gt; or &lt;code&gt;s&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag t:&lt;/strong&gt; test mode. With &lt;code&gt;t=y&lt;/code&gt;, inboxes apply your policy one step softer: &lt;code&gt;reject&lt;/code&gt; is handled as &lt;code&gt;quarantine&lt;/code&gt;, and &lt;code&gt;quarantine&lt;/code&gt; as &lt;code&gt;none&lt;/code&gt;. Reports still arrive. The default is &lt;code&gt;n&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag psd:&lt;/strong&gt; marks a public suffix domain. Leave it out.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Retired tags.&lt;/strong&gt; The current DMARC standard (RFC 9989, May 2026) dropped &lt;code&gt;pct&lt;/code&gt;, &lt;code&gt;rf&lt;/code&gt; and &lt;code&gt;ri&lt;/code&gt;, and inboxes ignore tags they don't know. Remove them when you next edit your record; to step up gently, use &lt;code&gt;t=y&lt;/code&gt; instead of a low &lt;code&gt;pct&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The safe plan
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Week 1 to 2: &lt;code&gt;p=none&lt;/code&gt;. Read the reports. Make sure every real service passes SPF or DKIM.&lt;/li&gt;
&lt;li&gt;Week 3: &lt;code&gt;p=quarantine&lt;/code&gt;. Fakes go to spam.&lt;/li&gt;
&lt;li&gt;Week 4 or later: &lt;code&gt;p=reject&lt;/code&gt;. Fakes are refused. To try it first, publish &lt;code&gt;p=reject; t=y&lt;/code&gt; for a week: inboxes handle it as quarantine while you check the reports, then remove &lt;code&gt;t=y&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Fix common mistakes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Only one DMARC record, at &lt;code&gt;_dmarc&lt;/code&gt;, not at the root.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;v=DMARC1&lt;/code&gt; must come first.&lt;/li&gt;
&lt;li&gt;If reports go to another domain, that domain must allow it (we handle that for &lt;a href="mailto:reports@dnsfix.com"&gt;reports@dnsfix.com&lt;/a&gt;).&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;First published on &lt;a href="https://dnsfix.com/help/set-up-dmarc" rel="noopener noreferrer"&gt;DNSFix&lt;/a&gt;. Check your own domain free at &lt;a href="https://dnsfix.com" rel="noopener noreferrer"&gt;dnsfix.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>email</category>
      <category>dns</category>
      <category>security</category>
      <category>webdev</category>
    </item>
    <item>
      <title>DKIM passes but DMARC still fails: the alignment trap</title>
      <dc:creator>DNSFix</dc:creator>
      <pubDate>Wed, 18 Nov 2026 09:12:52 +0000</pubDate>
      <link>https://dev.to/dnsfix/dkim-passes-but-dmarc-still-fails-the-alignment-trap-5a4j</link>
      <guid>https://dev.to/dnsfix/dkim-passes-but-dmarc-still-fails-the-alignment-trap-5a4j</guid>
      <description>&lt;p&gt;DMARC needs the domain that passed to match your From address. Many tools sign with their own domain, so DKIM passes but DMARC still fails.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;DMARC asks one question: did SPF or DKIM pass &lt;strong&gt;for the same domain that's in the From line&lt;/strong&gt;? That match is called alignment.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A newsletter or CRM tool often signs mail with its own domain, like &lt;code&gt;sendgrid.net&lt;/code&gt;. DKIM passes, for them, not for you.&lt;/li&gt;
&lt;li&gt;SPF checks the hidden "return path" address, which is usually the tool's domain too.
So both pass, neither matches &lt;code&gt;yourbusiness.com&lt;/code&gt;, and DMARC fails.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open the email's full headers ("Show original" or "View source") and look for the &lt;code&gt;d=&lt;/code&gt; value in the DKIM signature. If it isn't your domain, alignment fails.&lt;/li&gt;
&lt;li&gt;In the sending tool, find "domain authentication", "custom DKIM" or "branded sending domain" and follow its steps. It gives you one to three CNAME or TXT records to add.&lt;/li&gt;
&lt;li&gt;Send another test. The &lt;code&gt;d=&lt;/code&gt; value should now be your domain and DMARC should pass.&lt;/li&gt;
&lt;li&gt;Do this for every tool that sends as you. Your DMARC reports list them.&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;em&gt;First published on &lt;a href="https://dnsfix.com/help/dkim-pass-dmarc-fail" rel="noopener noreferrer"&gt;DNSFix&lt;/a&gt;. Check your own domain free at &lt;a href="https://dnsfix.com" rel="noopener noreferrer"&gt;dnsfix.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>email</category>
      <category>dns</category>
      <category>security</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
