DMARC, SPF, and DKIM give a small website owner a practical way to reduce domain spoofing and verify that legitimate email is authorized. This guide explains how the three controls work together, how to publish them in DNS, how to troubleshoot newsletters and contact forms, and how to review authentication results on a monthly or quarterly schedule.
Overview
Email authentication does not stop every scam, but it helps receiving mail systems distinguish messages sent through approved services from messages that merely claim to come from your domain. That matters even if your website sends only contact-form notifications, password resets, invoices, or occasional newsletters. Attackers can spoof a visible From address without accessing your website, which may make a fraudulent message appear to come from your business.
SPF, DKIM, and DMARC address different parts of that problem:
- SPF lists the servers and email providers permitted to send mail for your domain.
- DKIM adds a cryptographic signature to outgoing messages so a receiving system can check that the message was authorized and was not altered in transit.
- DMARC tells receiving systems what to do when authentication fails and provides reports that can reveal unknown senders or configuration errors.
These records are published in DNS, usually at the same registrar or DNS host that manages your domain. The exact record values come from your email provider, newsletter platform, website host, or transactional email service. Do not copy a provider's example blindly: a record that is correct for one service may be incomplete or invalid for another.
The safest rollout is staged. First identify every legitimate sender, then publish SPF and DKIM, begin DMARC monitoring with a non-enforcing policy, fix failures, and only then consider a stricter policy. For broader DNS safety, see DNS Security for Website Owners.
What to track
Keep a simple inventory before editing DNS. List the domain and subdomains used for email, the service that sends each type of message, the visible From address, and the person responsible for the account. Include systems that are easy to overlook:
- Business mailboxes and hosted email
- Newsletter and marketing platforms
- Contact forms and website plugins
- Order, booking, help-desk, or customer relationship systems
- Password-reset and transactional email services
- In-house servers, forwarding tools, and automated scripts
Use the following comparison when checking your records:
| Control | DNS location | Primary purpose | What to monitor |
|---|---|---|---|
| SPF | TXT record at the domain root | Identifies approved sending sources | All legitimate providers are included, there is only one SPF policy, and obsolete services are removed |
| DKIM | TXT or provider-specific record at a selector hostname | Lets recipients verify a message signature | The provider's selector exists, signing is enabled, and the signing domain remains aligned with the From domain where required |
| DMARC | TXT record at _dmarc.yourdomain.example | Defines handling and reporting for authentication failures | Policy, alignment, report destinations, failure patterns, and authorized senders |
A basic DMARC monitoring record may look like this:
Host: _dmarc.example.comType: TXTValue: v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
p=none requests reporting without asking recipients to quarantine or reject failing messages. A later policy might use p=quarantine or p=reject, but the correct timing depends on whether all legitimate senders pass authentication and alignment. Use a dedicated reporting mailbox or a reporting service that explains how it handles aggregate data. DMARC reports can contain information about sending sources and may arrive in formats that are difficult to read manually.
SPF often resembles v=spf1 include:mail-provider.example ~all, but the permitted include mechanism must come from the provider. DKIM values are also provider-specific and often include a long public key. Never invent a DKIM key or replace an existing provider record without confirming which service owns the selector.
Cadence and checkpoints
Use a staged setup workflow rather than changing all three controls at once.
- Map senders. Review website settings, plugins, invoices, newsletter accounts, and administrative mailboxes. Record the service used by each sending function.
- Confirm DNS ownership. Identify where the authoritative DNS records are managed. A domain registrar, hosting provider, and email provider may be different companies.
- Publish SPF. Add the provider-approved mechanisms to one SPF TXT record. Multiple separate SPF records at the same hostname can cause an SPF evaluation error. If several services send mail, combine their approved mechanisms according to their documentation rather than creating competing records.
- Enable DKIM. Generate or obtain the selector and public key from each provider, add the requested DNS record, and turn on signing in the provider dashboard. Some services require a custom return-path or branded sending domain as a separate step.
- Start DMARC monitoring. Publish a
p=nonepolicy with an appropriateruadestination. Allow enough time for reports from your normal sending cycle, including newsletters or monthly statements. - Investigate before enforcing. Match report sources to your inventory. Fix legitimate failures, remove retired senders, and confirm that important mail is passing.
- Increase enforcement carefully. Move to a stricter policy only after reviewing results. If your provider supports percentage-based rollout, use it cautiously and document the change.
Review reports monthly for a small site and more frequently during a migration, rebrand, or email-platform change. A quarterly review is a reasonable minimum for a low-volume site that rarely changes its sending tools.
Keep a report-review log with these fields: review date, domain, sending IP or provider, message volume, SPF result, DKIM result, DMARC alignment result, known or unknown sender, action taken, and owner. This turns a technical record into an operational checklist.
How to interpret changes
A new sender in a DMARC report is not automatically an attack. It may be a newly enabled newsletter platform, a website host, a forwarding system, or a third-party service that was not included in the original inventory. Confirm ownership through your internal records and the provider account before changing DNS.
Common symptoms and likely causes include:
- SPF pass but DMARC fail: The sending service may be authorized by SPF, but the authenticated domain does not align with the visible From domain.
- DKIM fail after a DNS change: The selector may be missing, mistyped, truncated, or still waiting for DNS changes to become visible. The provider may also have stopped signing.
- Contact-form messages disappear: The website may be sending directly from a visitor's address or through an unapproved server. Use a fixed address on your domain as the From address and place the visitor's address in Reply-To when the platform supports it.
- Newsletters fail after enforcement: The marketing platform may use a different sending domain, custom DKIM selector, or return-path. Check its domain-authentication setup and alignment instructions.
- Mail forwarding produces failures: Forwarding can change the path or content of a message. DKIM may survive in some cases, while SPF may not. Treat forwarding-related results separately from direct sending.
Do not respond to a failed report by adding every unfamiliar IP address to SPF. That can authorize an unwanted sender and make the record harder to maintain. First determine whether the source is a legitimate provider, an old configuration, a forwarder, or an impersonator. Also avoid deleting a DKIM record merely because the selector looks unfamiliar; selectors belong to specific providers and should be checked against active accounts.
When troubleshooting, test one change at a time and save the previous record. DNS dashboards may automatically append the domain name, add quotation marks, or split long TXT values. Follow the dashboard's format and confirm the published result with an independent DNS lookup tool.
When to revisit
Make email authentication part of your normal domain-safety routine. Revisit the records immediately when you change email providers, launch a newsletter, add a contact-form tool, move hosting, transfer the domain, change the visible From address, or receive reports from an unfamiliar sending source. Domain transfers deserve special care because DNS records may not move automatically; use the domain transfer checklist before changing nameservers.
For routine maintenance, review the following monthly or quarterly:
- Are every SPF mechanism and DKIM selector still tied to an active service?
- Are there new sending sources that the business has not approved?
- Are legitimate messages passing both authentication and alignment?
- Has a provider changed its required DNS syntax or authentication workflow?
- Is the DMARC policy still appropriate for the evidence collected?
- Does the reporting mailbox remain monitored and protected?
As a final action, assign an owner and record the next review date now. Keep a current sender inventory, preserve a copy of working DNS values, and raise enforcement gradually rather than treating DMARC as a one-time installation. If you suspect that an account or mailbox has been compromised, review forwarding rules and recovery settings using this account-takeover checklist as well. Regular review is what turns SPF, DKIM, and DMARC from static DNS entries into an ongoing defense against domain spoofing.