Does your domain have a DMARC record, and is it actually doing anything? In the Mailwarm network study, about a quarter of sending domains had no DMARC record, and another 45% sat at p=none. Only about one in three enforced a policy. Here's how to check yours, and how to move to enforcement without blocking your own
email. DMARC is a TXT record at _dmarc.yourdomain.com. It tells Gmail and Outlook what to do when an email claiming to be from you fails SPF and DKIM: deliver it, send it to spam, or reject it. And it sends you reports on who is sending as your domain.
Open the free DMARC checker from Mailwarm, the email warmup and deliverability monitoring tool built by a Y Combinator team. Type a domain and click Check DMARC. Here's google.com.
Valid and enforced. Policy: reject. Mail that fails DMARC is refused outright. That's the strongest protection against spoofing. And rua is the address that receives your daily aggregate reports.
Now a domain at p=none. The checker flags it: not enforced. p=none only monitors. Failing mail is still delivered, so anyone can still spoof this domain. It's the right place to start, not to stay.
And no record at all: not found. Since 2024, Gmail and Yahoo require bulk senders to publish DMARC. p=none is enough to meet that rule, but you need the record.
So how do you get to reject without blocking your own email? Start with p=none and a rua address. Read the reports for a week or two, and fix SPF and DKIM for every service that sends as you. Then move to quarantine, and to reject once nothing legitimate fails.
DMARC proves an email is really yours. It doesn't make Gmail trust you. A new domain still needs a sending history. That's what Mailwarm builds, with email warmup. Check your DMARC record free. The link is in the description. And check again every time you add a new sending tool.