Skip to content
DMARC Pulse

Email errors

No DMARC record found: what it means and how to fix it

No DMARC record found means no usable TXT record exists at _dmarc on your domain. See why a lookup misses it and how to publish one safely.

What this means

No DMARC record found means a DNS lookup for _dmarc. plus your domain returned no TXT record (a text entry in DNS) that the tool could read as DMARC. DMARC is the DNS record that tells receiving servers how to treat mail that fails authentication.

With no record to read, receiving servers run no DMARC check, so a message cannot fail DMARC for this reason. DMARC policy not enabled is a different finding: the record exists but requests neither quarantine nor reject.

Gmail can still limit or block bulk senders. Its bulk sender rules require DMARC from anyone sending more than 5,000 messages a day to Gmail accounts. Its errors for a missing record are 421 4.7.40 (rate limited) and 550 5.7.40 (blocked). The 550 text reads:

Your message was blocked because the sending domain doesn't have a DMARC record or the DMARC record doesn't specify a DMARC policy.

DMARC record not found and similar wordings

The words come from the tool, because the DMARC standard, RFC 9989, defines no such message. DMARC record not found and its variants mean the same thing.

DMARC record published failed in MXToolbox

DMARC Record Published is an MXToolbox check. For a domain with no record it shows DMARC Record Published Failed, explained as No DMARC Record found.

Why it happens

  • Nobody published one. DMARC is opt-in, and a domain with no record does not take part.
  • The name is wrong. It belongs at _dmarc under your domain, underscore included. Some DNS hosts add your domain automatically, so typing the full name can double it.
  • The value is discarded. It does not start with the v tag set to DMARC1 in uppercase.
  • There are two records. When a lookup returns more than one DMARC record for a name, receivers discard them all.
  • You checked a subdomain. Receivers fall back to parent domains, so _dmarc.news.example.com can be empty while _dmarc.example.com covers that mail.

How to fix it

  1. Note the domain after @ in the From address of the affected mail and query it on a public DNS server. For a subdomain, check every parent up to the main domain too. A nonexistent-domain reply or no TXT answer means no record exists. After a timeout or server failure, run it again.

    nslookup -type=TXT _dmarc.example.com 1.1.1.1

  2. If one v=DMARC1 record with p= answers, at the domain or any parent, DMARC is published: change nothing and stop. If two answer, or the record is misspelled, misnamed or has no p=, repair it so one remains. Caution: repairing a record activates its policy. First set p, sp and np, where present, to none.

  3. Set up SPF and DKIM before you publish. A message passes DMARC only when one of them validates a domain aligned with From, usually the same registered domain. Caution: keep one SPF record per domain. If v=spf1 already exists, edit it, because a second record makes SPF return permerror.

  4. If no DMARC record exists, create one TXT record named _dmarc at your DNS host (some ask for _dmarc.example.com), then check the saved name. For a subdomain sender, publish at the main domain. Use this value with a mailbox you control in rua=, or build one with the DMARC generator:

    TXT
    v=DMARC1; p=none; rua=mailto:dmarc@example.com

    p=none leaves mail handling unchanged. rua= sets where aggregate reports go (summaries of who sends as your domain). An address outside your domain needs authorization in that domain's DNS, or receivers ignore it: see how the rua tag works.

  5. Stay on p=none for now. Caution: p=quarantine or p=reject can send legitimate mail to spam or get it refused. Move up only when reports show every legitimate sender passing.

Confirm the fix

  1. Repeat the lookup or use the DMARC checker. You want one answer starting with v=DMARC1. If it is still empty, retry later: DNS servers may hold the earlier answer.

  2. Send a test message to a mailbox at another provider and read its Authentication-Results header. dmarc=pass or dmarc=fail shows a record was found. dmarc=none means none was found, and Microsoft 365 can also write dmarc=bestguesspass in that case. A dmarc=fail with p=none means a sender still needs alignment: see DMARC fail with p=none.

Check it now

Create a correct DMARC record

Open the DMARC Generator

Frequently asked questions

Is this error stopping my email from being delivered?
On its own, no. Receivers skip DMARC when no record exists. Large mailbox providers add their own rules, though. Gmail requires DMARC, along with both SPF and DKIM, from senders of more than 5,000 messages a day to Gmail accounts. Yahoo requires bulk senders to publish at least p=none. Microsoft asks the same of domains sending over 5,000 messages a day to its consumer addresses (Outlook.com, Hotmail and Live.com).
What is the shortest DMARC record I can publish?
v=DMARC1; p=none is valid and states a policy. Add rua= if you want reports, because receivers must not send aggregate reports without it. Keep the p tag: Gmail's error also covers a record that specifies no policy.
Does every subdomain need its own DMARC record?
No. A subdomain without a record uses the record at its organizational domain, usually the domain you registered. For a subdomain that exists, the policy comes from sp, or from p if sp is absent. For a subdomain that does not exist, np applies first, then sp, then p. Publish a record at the subdomain only when you want different settings there.
Why does it still say not found after I added the record?
Check the saved name first, because some DNS hosts add your domain automatically. If the name is right, DNS servers may still hold the earlier empty answer until its cache time runs out. Try again later.
Is p=none enough to clear this error?
Yes. The error is about whether a record exists, and p=none is a valid policy. It only monitors, so it makes no request about failing mail. MXToolbox can then show a separate warning, DMARC Policy Not Enabled, because p=none requests neither quarantine nor reject. Tightening it later is a separate decision that you make from your reports. RFC 9989 warns domains whose users post to mailing lists against p=reject.

Sources consulted

Google: Set up DMARC
checked 2026-11-08

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.