Skip to content

DMARC record checker

Enter your domain: the checker finds the DMARC record that applies to it, at the domain itself or above it as RFC 9989 walks the DNS, reads its policy and its reports, and checks SPF and DKIM alongside.

Check a domain

What the check reads
  • DMARC

    The DMARC record that applies to your domain, its policy, its reports and where it comes from.

  • SPF

    Your SPF record and every record it includes, its DNS lookups against the limit of 10, and its policy for other servers.

  • DKIM

    Your DKIM keys, under your selectors or 12 common ones, with the type and size of each key.

DMARC

What a DMARC record does

DMARC tells receivers what to do with mail that shows your domain in its From address but passes neither SPF nor DKIM for that same domain: deliver it anyway (p=none), send it to spam (p=quarantine) or refuse it (p=reject). It also asks them to send you reports, through rua, of who sends mail as your domain.

It is a TXT record at _dmarc.yourdomain, starting with v=DMARC1. A subdomain without a record of its own falls under the record of its organizational domain, which RFC 9989 finds by walking up the DNS rather than from a list of public suffixes; sp sets the policy of its subdomains, and np the policy of names that do not exist.

RFC 9989 replaced RFC 7489 in May 2026: pct, rf and ri are gone, t=y replaces a partial rollout, and np and psd arrive. Gmail, Yahoo and Outlook ask bulk senders for at least p=none, but only quarantine or reject keeps others from sending as you.

Method

How the check reads your domain

  • Every query goes through PricklyMails' own resolver, never a public one, with at most 32 queries and 8 seconds per check; a section the budget cut short says so.
  • SPF follows RFC 7208: one record at the domain, every include and redirect followed, the lookups counted against 10 and the lookups that find nothing against 2, as receivers count them.
  • DMARC follows RFC 9989, which replaced RFC 7489 in May 2026: the record at the domain or, without one, the record the DNS walk finds above it, the obsolete pct, rf and ri tags noted, and each report address on another domain checked for the authorization RFC 9990 asks for.
  • DKIM follows RFC 6376, with the key rules of RFC 8301 and RFC 8463: the type of each key, its RSA size, and its flags. Selectors cannot be listed from the DNS, so without yours the check tries 12 common ones.
  • The answer is kept 4 minutes, so a second check of the same domain costs no query, then forgotten: no domain is stored, logged or sent to analytics.

Frequently asked questions

Which DMARC policy should I publish?

Start with p=none and a rua address, read the reports until every service that sends as your domain passes SPF or DKIM for it, then move to p=quarantine and to p=reject. RFC 9989 advises against p=reject for a domain whose users post to mailing lists, which often break the check.

What happened to pct in DMARC?

RFC 9989 removed it, with rf and ri, and receivers ignore it now. To roll a policy out step by step, publish it with t=y, which asks receivers to apply the policy one level lower: quarantine as none, reject as quarantine. Remove t=y once the reports are clean.

Why are my DMARC reports not arriving?

Receivers send aggregate reports to the mailto: addresses in rua. When an address is on another domain than yours, they first check that this domain accepts your reports, through a TXT record naming your domain under _report._dmarc on its side, starting with v=DMARC1; without it, they drop the reports. The checker looks that record up for you.

Do Gmail, Yahoo and Outlook require DMARC?

From bulk senders, yes: Gmail and Yahoo since February 2024, Outlook.com since May 2025, each with at least p=none and mail that passes SPF or DKIM for the domain in its From address. Gmail has been enforcing these rules more strictly since November 2025.

Check your list before your next send.

1,000 tokens free when you sign up, no credit card. After that, you only pay for answers.