Skip to main content
wp-config.org

Search tools

Email tools

DMARC record generator and checker

Build a DMARC record that tells receivers what to do with mail that fails SPF and DKIM, and where to send reports. Then test the record you publish, and whether mail from each of your services can pass it.

  • Up to date with RFC 9989
  • Rollout guide to p=reject
  • Report address checks

Free, no sign-up. Results are not saved.

This tool needs JavaScript. Turn JavaScript on and reload the page.

Email DNS

What gets your email delivered in 2026

  • Gmail and Yahoo ask every sender for SPF or DKIM. Bulk senders (for Gmail, about 5,000 or more messages a day to Gmail accounts) also need both SPF and DKIM, a DMARC record (p=none at least) aligned with SPF or DKIM, and one-click unsubscribe for marketing mail. Since November 2025 Gmail has been stepping up enforcement, including rejecting mail that does not comply.
  • Outlook.com, Hotmail and Live ask domains that send more than 5,000 messages a day for passing SPF and DKIM and DMARC p=none or stronger, aligned with one of them. Since 5 May 2025 mail that fails goes to Junk.
  • Mail from your WordPress site (password resets, orders, contact forms) counts too: send it through an SMTP plugin and an email service that is in your SPF and DKIM records.

What you can do

  • Build a DMARC record with p, sp, np, reports and alignment

  • Follow a rollout guide from p=none to p=reject

  • Find the record that applies, through the DNS tree walk

  • Check that report addresses at other domains are authorised

  • See whether each of your services' mail can pass DMARC

  • Spot old tags like pct, and tags DMARC does not know

How to set up and check DMARC

  1. Build the record

    Start with p=none and an address for daily reports. The builder writes the TXT record to publish at _dmarc.yourdomain.

  2. Test what is published

    After a quick Cloudflare security check, the test reads your record, explains each tag, checks your report addresses and says whether mail from the services you picked can pass.

  3. Tighten the policy step by step

    Read the reports for a few weeks and fix every real sender. Then move to p=quarantine and finally p=reject, testing again after each change.

DMARC in 2026: what it does and what changed

DMARC is a TXT record at _dmarc.yourdomain, such as v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com. A message passes when SPF or DKIM passes for a domain that matches (aligns with) the From address. The policy says what receivers should do with mail that fails: none (deliver and report), quarantine (spam folder) or reject (refuse).

The new standard: RFC 9989

In May 2026 DMARC became a Proposed Standard, RFC 9989, replacing RFC 7489. For your record, the changes are:

  • pct is gone. To step up gently, add t=y (test mode): receivers then apply one step less than your policy, none instead of quarantine and quarantine instead of reject.
  • np sets a policy for subdomains that do not exist, such as invoices.yourdomain, which only forgers use. np=reject is a safe choice.
  • Receivers find the record that applies by walking up the DNS tree instead of using the Public Suffix List.
  • rf and ri are gone too. Receivers ignore tags they do not know.

Roll out in steps

Start with p=none and a rua address, and read the daily reports for two to four weeks. List every service that sends as your domain, including your WordPress site's contact forms and order emails, and set up DKIM with your domain for each. Then move to p=quarantine, with t=y for a week or two if you want, and then to p=reject. BIMI logos need p=quarantine or p=reject.

Reports

rua receives daily aggregate reports, XML files listing who sent mail as your domain. A DMARC reporting service makes them readable. ruf asks for failure reports, which few receivers send and which can contain parts of real messages. If a report address is at another organisation's domain, that domain must publish a TXT record at yourdomain._report._dmarc.theirdomain containing v=DMARC1, or receivers drop the reports. Reporting services publish it for their customers.

Alignment

Relaxed alignment (the default) accepts any subdomain of yours, such as the bounce subdomain a sending service uses. Strict (adkim=s, aspf=s) needs the exact domain, which breaks most services' return paths, so keep relaxed unless you have a reason.

WordPress mail sent by the web server rarely aligns. Send it through an SMTP plugin and an email service that signs with your domain before you move past p=none.

Frequently asked questions

Which DMARC policy should I start with?

Start with p=none and a report address. Nothing changes for your mail, and the reports show every service that sends as your domain. Move to p=quarantine once your real mail passes, and to p=reject after that.

What happened to the pct tag?

RFC 9989, published in May 2026, removed it, because receivers rarely applied it accurately. Use t=y instead while you step up: receivers apply one step less than your policy. Remove t=y once the reports look right.

Is p=none enough for Gmail, Yahoo and Outlook.com?

For their bulk sender rules, yes: they ask for a DMARC record of at least p=none, aligned with SPF or DKIM. But p=none does not stop anyone sending as you, and BIMI needs p=quarantine or p=reject, so keep going.

Why are my DMARC reports not arriving?

Check that rua starts with mailto: and the address is spelt correctly. If the address is at another domain, that domain must publish a record at yourdomain._report._dmarc.theirdomain with v=DMARC1, or receivers drop the reports. The test checks this for you.

What is the difference between sp and np?

sp is the policy for subdomains that exist but have no DMARC record of their own. np, new in RFC 9989, is for subdomains that do not exist at all. If np is missing, receivers use sp, and if sp is missing, p.

Should I use strict alignment?

Usually not. Strict alignment needs the exact domain in SPF or DKIM, while many sending services use a subdomain of yours for bounces. Relaxed alignment still stops other domains, and is the default.

Is the domain I check stored?

The result is not saved. The MTA-STS policy, BIMI logo and certificate the test downloads are read once and not kept. To count how the tool is used, this site keeps the domain you tested for 12 months, with the time, the outcome, your approximate location (country, region and city), the site you came from and your type of device and browser, but no IP address, and never the services or DKIM selectors you picked. The privacy policy has the details.

Related tools

  • Look up DNS records and check SPF, DMARC, DKIM and DNSSEC.

  • Email header decoder

    New (added recently)

    Paste an email’s full headers to see its delivery path, delays, SPF, DKIM, DMARC and ARC results, alignment and spam scores, decoded in your browser.

  • Blacklist checker

    New (added recently)

    Check whether an IP address or a domain’s website and mail servers are on spam blocklists, with what each listing means and how to get removed.

  • DNS propagation checker

    New (added recently)

    Check whether a DNS change has reached Google, Cloudflare, Quad9 and other public resolvers, and when each one refreshes.