What DMARC does for your domain, in plain English
Without DMARC, anyone can send email that looks like it came from you. Here is how SPF, DKIM and DMARC fit together.

Email was designed in a more trusting age. By default, nothing stops a stranger from sending a message that says it comes from your domain. Three public DNS records change that: SPF, DKIM and DMARC. You do not need to understand the technology to use them, only what each one does.
SPF: who may send
SPF is a list, published in your DNS, of the servers allowed to send email for your domain: your email provider, your newsletter tool, your invoicing system. A receiving server checks the list. If the sender is not on it, the message is suspicious. SPF has limits, such as a cap on how many lookups the list may need, and it breaks when email is forwarded, which is why it is not enough alone.
DKIM: a signature on every message
DKIM adds a digital signature to each email your systems send. The matching public key sits in your DNS. If the message was changed in transit, or did not come from a system that holds your private key, the signature fails. Each service that sends email for you needs its own DKIM setup.
DMARC: what to do when checks fail
DMARC ties the two together and tells receiving servers what to do with messages that fail: deliver them anyway, send them to spam or reject them. It also asks those servers to send you reports, so you can see who is sending email in your name, legitimate or not.
A DMARC policy of "none" only collects reports. "Quarantine" sends failing messages to spam. "Reject" blocks them. Real protection comes from quarantine or reject.
Why most small domains are exposed
Many domains have an SPF record that is out of date, no DKIM for some of the services that send email, and either no DMARC record or one set to "none" forever. Since 2024 Google and Yahoo require bulk senders to publish DMARC, so more domains have a record, but far fewer enforce it.
A safe way to get to "reject"
- List every service that sends email for you.
- Fix SPF so it includes them all and stays within the lookup limit.
- Set up DKIM for each service.
- Publish DMARC with a "none" policy and read the reports for a few weeks.
- Move to "quarantine", then to "reject", once legitimate mail passes.
Check yours
All of these records are public, so a check needs nothing from you except the domain name. Our Email Domain Security Check reads them, rates how easy your domain is to spoof and gives you the exact records to paste into your DNS, plus a rollout plan.
Pick what you need.
16 fixed-price deliverables from €39. Pay once, answer a short questionnaire or download straight away, and get plain-English documents by email.
See the Email Domain Security Check