DMARC Record Checker
Can someone send fake email as you?
Check your DMARC record to see what receivers do with mail that uses your domain but fails SPF or DKIM, where reports are sent and which step of protection you're on.
Create a DMARC Record
Setting it up for the first time? Start with none and a report address; once reports show every legitimate sender passing, move to quarantine and then reject.
DMARC Problems and How to Fix Them
Most DMARC complaints come from having no record, sitting on p=none for years, or having no report address and so no idea who sends with your domain. Pick the symptom you see.
Gmail and Yahoo require a DMARC record
Since February 2024, Gmail and Yahoo require anyone sending more than 5,000 emails a day to have a DMARC record with at least p=none, plus SPF and DKIM. Start with v=DMARC1; p=none; rua=mailto:dmarc@example.com; even smaller senders get better delivery with it.
Spoofed email is being sent with my domain
p=none doesn't block spoofed mail; it only reports it. First use the reports to confirm all your legitimate senders pass SPF or DKIM, then move the policy to quarantine and reject. With reject, fake email using your domain never reaches the inbox.
I've been on p=none for ages — how do I move on?
Read the reports for 2–4 weeks and list your legitimate senders; add the failing ones to SPF or enable their DKIM. Then start with p=quarantine; pct=25, raise it to 100 while nothing breaks, and finally switch to p=reject.
I'm not getting DMARC reports
Make sure the record contains rua=mailto:…. If the report address is on another domain, that domain must publish a v=DMARC1 TXT record at example.com._report._dmarc.reportdomain.com. Reports arrive once a day as compressed XML files.
My legitimate email started going to spam
After tightening the policy, a sender (CRM, invoicing, newsletter tool) isn't passing SPF or DKIM for your domain. Find that source in the reports, then add it to your SPF or enable DKIM signing with your domain in that service. You can loosen the policy one step until it's fixed.
SPF Record CheckerAre my subdomains protected?
If a subdomain has no record of its own, the main domain's record applies: its sp= if set, otherwise p=. Setting sp=reject shuts spoofing down for subdomains that never send mail. Look up a subdomain here to see which record applies.
What Is DMARC?
DMARC (Domain-based Message Authentication, Reporting and Conformance) is a TXT record telling receiving servers what to do with email that uses your domain but fails SPF or DKIM: deliver anyway (none), send to spam (quarantine) or reject it.
The record lives at _dmarc.example.com and requests daily reports through the rua tag. The reports show who sends email with your domain, so you can confirm your legitimate senders before tightening the policy.
- SPF and DKIMVerify the message
- DMARC policySays what to do with the result
- Deliver, spam or rejectYou get a daily report
How to Read a DMARC Record
v=DMARC1Version: Marks the record as DMARC; it must be the first tag.p=quarantinePolicy:nonemonitors,quarantinesends to spam,rejectrejects.rua=mailto:dmarc@example.comReport address: Where daily aggregate reports go; an address on another domain needs that domain's permission.pct=100Percentage: The share of messages the policy applies to; 100 if not set.adkim=rAlignment:rrelaxed: subdomains match too;sstrict: the exact same domain is required.
The result explains every tag, shows which step your policy is on and also checks whether external report addresses are authorised.
A Safe DMARC Rollout Plan
Jumping straight to p=reject also rejects legitimate mail from any sender with incomplete SPF or DKIM. Tighten the policy one step at a time, guided by the reports.
| Step | Record | When |
|---|---|---|
| 1 | v=DMARC1; p=none; rua=mailto:dmarc@example.com | First 2–4 weeks: collect reports and list your legitimate senders. |
| 2 | v=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc@example.com | Once no legitimate sender fails in the reports: apply to a quarter of messages first. |
| 3 | v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com | If nothing breaks for a week or two: apply to all messages. |
| 4 | v=DMARC1; p=reject; rua=mailto:dmarc@example.com | Final step: spoofed email using your domain is never delivered. |
Use a separate mailbox as the report address; reports are compressed XML files that arrive once a day.
Frequently Asked Questions
The most common questions about DMARC policy, reports and the Gmail/Yahoo requirements.
- DMARC decides what receivers do when mail using your domain fails SPF or DKIM, and reports to you who sends in your name. It's the record that stops spoofing.
-
p=noneis monitoring only: mail that fails verification is still delivered and reported to you. It meets Gmail's and Yahoo's minimum but doesn't block spoofing; protection starts with quarantine and reject. - Start with
quarantine: if a legitimate sender is misconfigured, its messages end up in spam rather than lost. Once reports are clean, move toreject, the strongest setting, which keeps spoofed mail out entirely. - It has been required since February 2024 for anyone sending more than 5,000 emails a day to Gmail or Yahoo (at least p=none). For smaller senders it isn't required, but it still improves delivery and stops your domain from being used in fake email.
- A compressed XML file arrives at the
ruaaddress every day, listing the IP addresses that sent mail with your domain, message counts and SPF/DKIM results. Upload it to a DMARC report analyser to read it as a table. - No; a subdomain without its own record uses the main domain's record (its
sp=policy, if set). If a subdomain needs a different policy, add a separate record at_dmarc.sub.example.com.
Rather not deal with email DNS records?
Atak Domain Business Email adds the MX, SPF and DKIM records for you, with support every day; from $0.99 a month.