Skip to content
DMARC Pulse

DMARC lookup

DMARC Checker & Tester

Enter a domain to test its DMARC record: we look it up, check it for errors and show what each tag means for your email.

We query _dmarc.<domain> over DNS and explain the result.

Example result

Sample data, not a live check. Run the tool above to see your own result.

Result for

acme.example

Looks good

p=reject rua ✓

Published record

_dmarc.acme.exampleTXT
v=DMARC1; p=reject; rua=mailto:d-acme01@rua.dmarcpulse.com; adkim=r; aspf=r; fo=1

What we found

  • Fake e-mail is refused (p=reject)

    Messages that fail DMARC are rejected. This is the strongest protection against someone sending as your domain.

  • Reports go to DMARC Pulse

    Aggregate reports are delivered to your DMARC Pulse dashboard.

Details

v
DMARC1 Version. Must be DMARC1 and come first.
p
reject Policy for mail that fails DMARC: none (just report), quarantine (spam folder) or reject (refuse).
sp
— default: same as p Policy for subdomains. If absent, subdomains use p.
np
— default: same as sp Policy for subdomains that don’t exist (DMARCbis). Blocks spoofing of made-up subdomains.
pct
— default: 100 Historic percentage tag, removed by RFC 9989. Do not rely on it: your policy may affect all failing mail immediately.
rua
mailto:d-acme01@rua.dmarcpulse.com Where daily aggregate reports are sent. This is how you see who sends as you.
ruf
— default: none Where failure (forensic) reports go. Rarely sent by providers.
adkim
r DKIM alignment: r (relaxed, subdomains allowed) or s (strict, exact match).
aspf
r SPF alignment: r (relaxed) or s (strict).
fo
1 When to send failure reports: 0 (both fail), 1 (either fails), d (DKIM), s (SPF).
ri
— default: 86400 Historic requested report interval in seconds, removed by RFC 9989. Current receivers choose their reporting schedule.
rf
— default: afrf Historic failure-report format tag, removed by RFC 9989. RFC 9991 defines current failure reporting.

What to do with the result

No DMARC record was found

No TXT record starting with v=DMARC1 exists at _dmarc.example.com, or at its organizational domain (the domain its owner registered, such as example.com) when you check a subdomain. Receiving mail servers have no policy of yours to apply.

  1. Confirm that SPF (the servers allowed to send for you) and DKIM (a signature on each message) work.
  2. Create a mailbox for aggregate reports, the XML summaries receivers send, usually daily.
  3. Publish one TXT record at that name. Some DNS panels need only _dmarc as the host.

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

Start at p=none, which leaves mail handling unchanged. The DMARC Generator can build the record for you.

There are two records, or the policy is missing or invalid

With two or more records at the same name, receivers discard them all. This check shows only the first, so open your DNS zone to see the others. With a missing or invalid p, or an invalid sp or np, receivers act as if you published p=none when the record has a valid rua address. Without one, they apply no DMARC.

Keep a single TXT record and separate the rua addresses with commas. Policy tags accept none, quarantine or reject.

Caution: the fix puts your policy into effect. Publish p=none unless reports already show all your senders passing.

The record works, but the policy is p=none

The domain is in monitoring mode. Receivers handle mail as before, so DMARC does not hold back forged mail yet. Use this stage to find every service that sends as your domain.

  1. Read the aggregate reports. You need a working rua address for this.
  2. For each legitimate sender, fix SPF or DKIM until it aligns: by default, the authenticated domain must share the registered domain of your From address.
  3. Move to p=quarantine once those senders pass.

Enforcing too early can keep legitimate mail out of the inbox. If you send rarely, collecting enough reports can take months.

There is no report address, or receivers will ignore it

Without a rua tag, receivers must not send aggregate reports, so you cannot see who sends as your domain. Add one with the mailto: prefix: rua=mailto:dmarc@example.com. The rua ✓ badge only confirms that the tag exists.

An address on another organizational domain (the domain its owner registered, such as example.net) needs that owner’s permission, or receivers ignore it. The owner publishes a TXT record starting with v=DMARC1 at the name in the finding, such as example.com._report._dmarc.example.net. If a service collects your reports, ask it to publish this record. RFC 9990, section 4, describes the check.

The policy is p=quarantine or p=reject

Receivers that honor your policy keep failing mail out of the inbox. Each receiver still makes the final decision. This check reads DNS only, so keep reading reports to confirm your mail passes.

  • Before p=reject, sign all mail with DKIM, because forwarded mail usually fails SPF. RFC 9989, section 7.4, advises domains whose users post to mailing lists against p=reject. If you go ahead, compare reports from at least a month at p=none and as long at p=quarantine.
  • RFC 9989 removed pct, so do not count on percentages. The new t=y test mode asks for one level below your policy. Receivers still on RFC 7489 ignore it.

Explained

What a DMARC lookup tells you

A DMARC lookup reads the TXT record at _dmarc.yourdomain.com. That record tells mailbox providers what to do when a message claims to be from your domain but fails authentication, and where to send reports about it. A message passes DMARC when SPF or DKIM passes and is aligned with the domain in the From header.

A safe DMARC rollout

  1. Inspect your existing DMARC record. Keep its policy and add a reporting address; create one record at p=none only if none exists.
  2. Use reports to fix every legitimate sender and enable aligned DKIM.
  3. Consider p=quarantine only after legitimate mail passes. RFC 9989 removed pct: assume the policy affects all failing mail immediately.
  4. Evaluate whether p=reject suits your domain. RFC 9989 advises domains whose users post to mailing lists against it; remaining at quarantine can be appropriate.

Frequently asked questions

How do I check if my domain has DMARC?
Enter your domain above. We look up the TXT record at _dmarc.yourdomain.com; if there is none, your domain has no DMARC protection.
What is the best DMARC policy?
Choose based on your mail flows. Start a new record at p=none, then consider quarantine after legitimate senders pass. RFC 9989 advises domains whose users post to mailing lists against p=reject.
Why does my DMARC record show an error?
The most common causes are two records published at once, a missing p= tag, typos in tag names and reporting addresses on another domain without authorization.
Do I need a rua address?
It’s technically optional, but without it you are blind: reports are the only way to see who is sending as your domain before you enforce a policy.
How long does a DMARC change take to apply?
As long as your DNS TTL, usually minutes to a few hours. Run the check again to confirm the new record is visible.

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.

Related tools