DMARC checker

Your DMARC record,
read the way receivers read it.

A DMARC checker looks up the TXT record at _dmarc.yourdomain.com and tells you what it asks receivers to do with mail that fails, where the reports go and whether anything in it makes receivers ignore it. Type your domain. If a subdomain has no record, it walks up the name the way the standard describes, and it checks that a report address at another domain has agreed to receive your reports.

It runs in your browser. The domain you check goes to public DNS, Google’s first and Cloudflare’s if Google’s does not answer, and never to us. The DMARC record generator builds the record and a dated rollout plan, the SPF record generator (or the SPF lookup counter, for a record that is already live) and the DKIM checker cover the other two, and the setup guide shows how all three fit.

RFC 9989 · RFC 9990 Tree walk · report check Checked 21 Nov 2026

By the Builderify team

DMARC checker Reads public DNS from your browser

Nothing is looked up in this mode. Paste the value your DNS host shows, with or without the quotes around it. Add the domain if you want report addresses at another domain flagged.

Example results · nothing has been looked up yet
Monitoring _dmarc.yourbrand.com

Monitoring only: p=none

Sample: a first record that only monitors

v=DMARC1; p=none; rua=mailto:dmarc@yourbrand.com
Policy (p)
none
Subdomains (sp)
none (same as p)
Aggregate reports (rua)
mailto:dmarc@yourbrand.com
DKIM alignment
relaxed (default)
SPF alignment
relaxed (default)
  • i p=none asks receivers to change nothing for mail that fails. RFC 9989 calls p=none with reports coming in monitoring mode, and says a p=none policy must not modify how mail is handled. It is the right first stage: the reports show which senders fail before you enforce. It does not stop anyone from spoofing your domain.
Enforcing _dmarc.yourbrand.com

Enforcing: p=reject

Sample: an enforcing record with a report service and a retired tag

v=DMARC1; p=reject; sp=reject; rua=mailto:reports@dmarc-service.example; pct=50; adkim=s
Policy (p)
reject
Subdomains (sp)
reject
Aggregate reports (rua)
mailto:reports@dmarc-service.example
DKIM alignment
strict
SPF alignment
relaxed (default)
  • i RFC 9989 (section 7.4) says a domain that publishes p=reject must not rely on SPF alone and must sign its mail with valid DKIM, because forwarded mail usually fails SPF. It also says domains whose users post to mailing lists should not publish p=reject.
  • i Reports for yourbrand.com go to an address at dmarc-service.example, which is a different domain. RFC 9990 (section 4) says receivers send them only if dmarc-service.example publishes a TXT record at yourbrand.com._report._dmarc.dmarc-service.example that starts with v=DMARC1.
  • i Strict alignment is requested by adkim=s: the domain that passed must be identical to the From domain (RFC 9989, section 3.2.10.2). Under the default, relaxed alignment, sharing the same Organizational Domain is enough, so mail signed for bounce.yourbrand.com lines up with yourbrand.com.
  • i pct is a retired tag. RFC 9989 (appendix A.6) says it was usually not applied accurately unless it was 0 or 100, and IANA now lists it as historic. Do not rely on it to phase in enforcement: step p from none to quarantine to reject, or test with t=y.
Problem _dmarc.yourbrand.com

p=quarantined is not a valid policy

Sample: two typos that switch the record off

v=DMARC1; p=quarantined; rua=dmarc@yourbrand.com
Policy (p)
not applied
Subdomains (sp)
—
Aggregate reports (rua)
dmarc@yourbrand.com
DKIM alignment
relaxed (default)
SPF alignment
relaxed (default)
  • ! RFC 9989 allows p=none, p=quarantine or p=reject. RFC 9989 (section 4.10.1) says a record without a valid policy is treated as p=none only when it has a valid rua address. This one has none, so receivers apply no DMARC processing at all.
  • ! “dmarc@yourbrand.com” has no mailto: in front of it. rua takes URIs, so write rua=mailto:dmarc@yourbrand.com. RFC 9989 says a part of the record that breaks the syntax is discarded or ignored, so do not count on reports reaching it.

Names asked

Answered by . DNS answers are cached, so a record you published a few minutes ago may not show yet.

Pasted record

The checker reads the record; it cannot tell you whether your mail passes. To see DMARC pass or fail on a real message, read the Authentication-Results header, and use the aggregate reports for the rest.

01 / What each tag does

The tags in a DMARC record,
and what a missing one does.

A record is a list of tag=value pairs separated by semicolons. RFC 9989 defines these, says unknown tags must be ignored, and gives each a default. Most of what the checker reports is one of these rules.

The DMARC tags defined in RFC 9989, what each does and what happens when it is missing
Tag What it does If it is missing
v The version. It must be the first tag, and the value is case sensitive: DMARC1 is the only possible value. Required. If it is missing, not first or not DMARC1, the entire record is ignored.
p What the domain owner asks receivers to do with mail that fails DMARC: none, quarantine or reject. It covers the domain and, unless sp or np say otherwise, its subdomains. Recommended. Without a valid p, the record counts as p=none if it has a valid rua, and receivers apply no DMARC processing if it does not.
sp The policy for existing subdomains that have no record of their own. Existing subdomains follow p.
np The policy for subdomains that do not exist in DNS. Receivers use sp if it is set, and p if it is not.
rua Where to send aggregate reports: a comma-separated list of URIs, such as mailto:dmarc@yourbrand.com. Receivers that send them must support mailto. Optional. Without it, receivers must not send aggregate reports.
ruf Where to send failure reports about single messages. Most receivers refuse to send them, for privacy reasons. Optional. Without it, receivers must not send failure reports.
adkim, aspf Whether the DKIM or SPF domain must match the From domain exactly (s, strict) or only share its Organizational Domain (r, relaxed). Relaxed.
fo Which failures should produce failure reports: 0, 1, d or s, joined by colons. 0 and 1 are mutually exclusive. 0. Ignored unless there is a ruf tag.
t Test mode. t=y asks receivers to apply the policy one step softer than p. It has no effect on p=none. n: apply the policy as written.
psd For operators of public suffixes: y marks a public suffix domain, and n marks a domain that is its own Organizational Domain. u: neither.
pct, rf, ri Older tags from RFC 7489. The IANA registry in RFC 9989 lists all three as historic. Not among the tags RFC 9989 defines.

From RFC 9989 (sections 4.7, 4.10.1 and 9.3 and appendix A.6), read on 21 November 2026. To build a record with these tags and a dated rollout, use the DMARC record generator.

02 / Subdomains

Which record applies
to a subdomain.

A subdomain does not need its own DMARC record. If _dmarc.news.yourbrand.com has none, receivers look further up the name and use the record of the domain that owns it. The checker does the same walk and tells you which record it found.

That is why a record on your main domain also covers a sending subdomain such as news.yourbrand.com, which the setup guide recommends for newsletters. RFC 9989 replaced the public suffix list with this walk, so the checker needs no list.

The names asked for a.mail.example.com, per RFC 9989
_dmarc.a.mail.example.com
_dmarc.mail.example.com
_dmarc.example.com
_dmarc.com

The standard’s own example: with records at mail.example.com and example.com but not at the other two names, the Organizational Domain is example.com.

01The exact name comes first

Receivers ask for _dmarc followed by the domain in the From address. If a valid record is there, it applies and nothing else is read.

02No record? They walk up

They take the left-most label off, ask again, and repeat until they run out of labels. RFC 9989 limits this to eight queries, however long the name is.

03The parent’s sp decides

For a subdomain, the policy comes from the parent record’s sp if the subdomain exists, from np if it does not, and from p if neither is set.

04Two records cancel out

If a name returns more than one DMARC record, RFC 9989 says they are all discarded. On a subdomain, that sends receivers on up to the parent.

05psd is not for you

The psd tag lets the operator of a public suffix mark where an organisation’s domain begins. An ordinary business domain should not set it to y.

From RFC 9989 (sections 4.7, 4.10, 4.10.1 and 4.10.2), read on 21 November 2026.

03 / Report addresses

Who may receive
your DMARC reports.

An address at your own domain just works. An address at a different domain, such as a report service’s, only receives reports if that domain has said it agrees.

Why the rule exists

RFC 9990 explains that without a check, anyone could publish a record that sends reports to a victim’s address and then send failing mail to many receivers, flooding the victim with reports. So when the address is outside your domain, receivers must verify it before they send anything.

RFC 9990’s own example
_dmarc.blue.example.com TXT
v=DMARC1; p=none; rua=mailto:reports@red.example.net

Receivers then ask for
blue.example.com._report._dmarc.red.example.net
What has to be there

A TXT record at that name that starts with v=DMARC1. If a receiver finds one, the arrangement is confirmed. If it does not, the standard says the address must be ignored, and you get no reports there, with no error to tell you.

The domain that receives the reports publishes it, for its customers: a report service for the domains it serves, or a wildcard at *._report._dmarc to accept any domain. Your report service’s setup page says whether it already has. The checker asks for the record and tells you.

RFC 9989 adds that, where possible, it is simpler to send reports to a mailbox on a domain that can receive mail and forward them from there. And an address in ruf gets more private data than one in rua, since failure reports can contain parts of real messages.

From RFC 9990 (section 4) and RFC 9989 (sections 10.2 and 11.6), read on 21 November 2026.

04 / Read the result

What the checker says,
and what to do about it.

Each card quotes the rule behind its verdict. These are the six findings you are most likely to meet.

01

Two records at _dmarc

RFC 9989 says that when several DMARC records are returned for one name, they are all discarded. A domain with two is the same as a domain with none. Keep one record and put every tag in it.

02

v=DMARC1 is not first

The v tag must be the first tag, and its value is case sensitive. If it is missing, later in the record or spelled differently, the entire record is ignored. A stray space or a quote character in front of it is a common cause.

03

p= is not a valid policy

A typo such as p=quarantined, or an invalid sp or np, makes receivers treat the record as p=none if it has a valid rua, and apply no DMARC at all if it does not. The record looks live and does nothing.

04

rua without mailto:

The reporting tags take URIs. rua=dmarc@yourbrand.com has no scheme, so it is a syntax error that receivers discard. Write rua=mailto:dmarc@yourbrand.com.

05

p=none is monitoring

Not a fault. RFC 9989 says a p=none policy must not change how mail is handled, and calls it monitoring mode when reports come in. Use the reports to find every sender that fails, then move to quarantine and reject. It stops nobody from spoofing your domain while it stays at none.

06

p=reject needs DKIM

RFC 9989 says a domain that publishes p=reject must not rely on SPF alone and must sign its mail with DKIM, because forwarded mail usually fails SPF while its DKIM signature survives. Check your senders with the DKIM checker first.

From RFC 9989 (sections 3.2.12, 4.7, 4.8, 4.10 and 7.4), read on 21 November 2026.

05 / Nothing found?

Why the checker says
“no DMARC record.”

It means no TXT record that starts with v=DMARC1 exists at _dmarc on your domain or any name above it. RFC 9989 says receivers then do not apply DMARC to the message. Work through these in order.

If the record is fine and mail still lands in spam, the guide to business emails going to spam ranks the other causes, and the Gmail and Yahoo bulk sender guide says when DMARC is required.

01Check the name

The record belongs at _dmarc.yourdomain.com, for the domain in your From address. A record at www or at the bare domain is a different name and receivers do not read it.

02Read the name your host saved

Some DNS hosts add your domain to whatever you type. If the host shows _dmarc.yourdomain.com.yourdomain.com after you save, enter only _dmarc.

03Use a TXT record

RFC 9989 says DMARC records are stored as DNS TXT records at a name that starts with _dmarc. A record of any other type is not read.

04Give DNS time

Public resolvers cache answers for the record’s time to live, so a record you added minutes ago may not show yet. The checker shows what resolvers return, not what your DNS host holds.

05Mind the subdomain

Mail from news.yourdomain.com uses the record at _dmarc.news.yourdomain.com if it is valid, and otherwise the one on yourdomain.com. Two records on the subdomain send receivers to the parent.

06Spell the policy right

A policy that is not none, quarantine or reject switches the record off, as chapter 04 shows. The checker puts that first when it finds it.

Where does the lookup go?

Your browser asks Google Public DNS for the record, using its JSON API, and asks Cloudflare’s if that fails. Nothing goes to Builderify’s servers, but those resolvers see the names you ask about, as any DNS resolver would. To keep a domain to yourself, use the “Paste a record” tab, which looks nothing up.

Sending newsletters from Builderify?

Broadcast and Sequences send from your own domain. The Domains page lists a recommended DMARC record, v=DMARC1; p=none;, and accepts any valid record you already publish. That record has no rua, so it works but sends you no reports: add one, as the generator does, and check it here. Sending costs 0.5 credit per email, and the 250 free credits every month cover 500 emails. See pricing.

Questions

DMARC checks, before you ask.

Type the domain you send email from into the checker. It asks public DNS for the TXT record at _dmarc.yourdomain.com, reads each tag against RFC 9989 and tells you what the record asks receivers to do, where reports go and what is wrong with it. The Paste a record tab reads a record before you publish it and looks nothing up.

No TXT record that starts with v=DMARC1 exists at _dmarc.yourdomain.com or at any parent name receivers would walk up to. RFC 9989 says receivers must not apply DMARC to a message when they find no record. Build one with the DMARC record generator, start with p=none and a rua address, and check it here again once it has had time to reach public DNS.

It is not an error. RFC 9989 calls p=none with reports coming in monitoring mode: receivers deliver mail as they would anyway and you read the aggregate reports to find senders that fail. It also says a p=none policy must not change how mail is handled, so it does not stop anyone spoofing your domain. The checker shows it as monitoring and warns only when there is no usable rua address, because then you would get no reports.

No. If _dmarc.news.yourbrand.com has no valid record, receivers walk up to _dmarc.yourbrand.com and use that one, taking the policy for the subdomain from sp if it is set, from np if the subdomain does not exist in DNS, and from p otherwise. Publish a record on the subdomain only if you want a different policy or its own report address. The checker does the same walk and shows which record applied.

Check four things in order: the record has a rua tag, the address starts with mailto:, the mailbox exists, and, if the address is at a different domain from the one that publishes the record, that domain publishes a TXT record at yourdomain.com._report._dmarc.theirdomain.com starting with v=DMARC1. RFC 9990 says receivers must ignore an address at another domain without it. The checker looks that record up for you and says if it is missing.

Receivers discard both. RFC 9989 says that when several DMARC records are returned for one name, they are all discarded, so the name has no valid record. On a subdomain that sends receivers on to the parent domain's record. Keep one record with every tag in it. The checker lists every record it finds and says when there is more than one.

No. Your browser asks Google Public DNS for the record, and Cloudflare's resolver if Google's does not answer, so nothing reaches Builderify's servers. Those resolvers do see the names you ask about, as any DNS resolver would. The Paste a record tab looks nothing up, so use it to keep a domain private.

Stop losing the visitors
you already paid for.

More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.