Free tool

Check your domain's DMARC record

Enter your domain: our DMARC checker reads your DMARC record and tells you, in plain English, whether a fake email from your exact address would be rejected, sent to spam or delivered. With the record to copy into your DNS host.

No sign-up. Your domain is neither stored nor published.

What this DMARC check looks at

DMARC is a short TXT record published at _dmarc.your-domain. It ties the address your customers see in the "From" field to the technical SPF and DKIM checks, and tells mail providers what to do with a message that fails: let it through (p=none), send it to spam (p=quarantine) or reject it (p=reject). The check confirms that the record exists, that there is only one and that it can be read, which policy it sets, whether it's in testing mode and whether it asks for reports. It also looks at your SPF record, because a domain with neither a valid SPF nor a protective DMARC policy can be spoofed with no effort at all. If your domain sends no email, the check makes sure it says so clearly.

How to read the result

Each item has an urgency level. "Broken now": anyone can send an email from your exact address, and it has a good chance of reaching the inbox. "Fix this month": DMARC is missing or has no effect, and the major mail providers now expect it from senders. "In order": your policy protects your address. An item marked "Could not be checked" means DNS didn't answer in time: run the check again a little later, it costs you nothing.

The most common DMARC mistakes

  • No DMARC record at all: it's the most common case, and the easiest to fix.
  • A p=none policy left in place for years: reports come in, but no fake email is ever blocked.
  • Two DMARC records published at the same time: mail providers then ignore both.
  • A record published on the domain itself instead of _dmarc, or with extra quotes copied from a guide.

The fix, step by step

First make sure SPF and DKIM are set up for every service that sends your email (mailbox, website, invoicing tool, newsletter). Then publish DMARC with the p=none policy and a reporting address: for a few weeks you see who sends email in your domain's name without blocking anything. Once your legitimate senders are aligned, move to p=quarantine, then to p=reject. The result above gives you the exact record to copy, in the format of your DNS host's interface when we recognize it.

Frequently asked questions

Can DMARC block my own emails?

Yes, if you jump straight to p=reject while one of your services sends without aligned SPF or DKIM. That's why you start with p=none and reports: they show which senders to fix before you tighten the policy.

Do I need SPF and DKIM before DMARC?

You need at least one of them, aligned with your domain, for every service that sends your email. Both together are stronger: DKIM survives email forwarding, SPF doesn't.

How long before the fix shows up?

As long as DNS takes to update: often a few minutes, sometimes a few hours depending on the old record's time to live. Just run the check again to confirm.