SPF, DKIM, and DMARC help receiving mail systems distinguish authorized messages from spoofed or poorly configured email. This reusable checklist explains how to inventory senders, publish the right DNS records, test authentication, review DMARC reports, and increase enforcement without blocking legitimate mail.
Overview
Domain email authentication is a DNS and mail-configuration task, not a setting controlled by your website hosting plan alone. It applies to every service that sends mail using your domain, including employee mailboxes, newsletters, contact forms, customer relationship management systems, support desks, invoicing tools, and transactional applications.
The three controls have different jobs:
- SPF (Sender Policy Framework) publishes which sending services are allowed to send mail for your domain. It is checked against the envelope sender, sometimes called the return-path.
- DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing messages. The receiving system checks the public key published in DNS.
- DMARC (Domain-based Message Authentication, Reporting, and Conformance) tells receiving systems how to handle messages that fail authentication and can send you reports about observed mail.
Authentication does not guarantee inbox placement. Message content, recipient engagement, sending reputation, list quality, and provider-specific filtering also matter. However, a correctly configured domain gives legitimate mail a stronger identity and makes unauthorized use easier to detect.
Before editing DNS, record the current values and confirm where your DNS is managed. Your registrar, website host, email provider, and DNS provider may be different companies. Changes should be made in the authoritative DNS zone, not automatically in the hosting control panel.
Checklist by scenario
1. Prepare an inventory of legitimate senders
- List every service that sends as your domain or a subdomain.
- Separate ordinary employee email from newsletters, support tickets, web forms, receipts, alerts, and marketing automation.
- Ask each provider for its current SPF guidance, DKIM selector and public key, recommended return-path or custom sending domain, and DMARC alignment requirements.
- Include forgotten systems such as an old website contact form, an accounting application, or a staging environment that may still send messages.
Do not build authentication records from memory. Provider instructions can change, and a service may require a specific DNS name or a custom subdomain.
2. Create or review SPF
Add one SPF TXT record for the domain used in the envelope sender. A typical record begins with v=spf1, followed by authorized mechanisms, and ends with an enforcement qualifier such as ~all or -all, according to your provider's instructions and rollout stage.
- Maintain one SPF policy per exact domain. Multiple separate SPF records can cause a permanent error.
- Use the provider's official
include:value rather than guessing an IP address. - Review nested DNS lookups. SPF has a limit of 10 DNS-based lookups during evaluation, so adding many providers can make an otherwise reasonable record fail.
- Remove services that no longer send mail, but keep a change log before deleting an entry.
SPF alone does not prove that the visible From address is authorized. DMARC alignment and DKIM are needed for a more complete setup.
3. Enable DKIM for every sending platform
In each email provider, locate the domain-authentication or DKIM section. The provider will normally give you a selector and a DNS record, often a TXT record or a CNAME that points to a hosted public key. Add the record exactly as supplied, including the selector and any trailing punctuation required by the DNS interface.
After the DNS record is visible, return to the provider and select the option to verify or activate DKIM. Send a test message and inspect its authentication results. DKIM keys can be rotated, so document the selector and note which service owns it before changing or removing a record.
4. Publish DMARC in monitoring mode
Start with a DMARC TXT record at _dmarc.example.com. A basic monitoring policy might look like this:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
Replace the reporting address with a mailbox or reporting service that you actively monitor. Aggregate reports can reveal legitimate senders, alignment failures, forwarding behavior, and possible spoofing. Avoid publishing a reporting address that you cannot access or that is not prepared to receive automated reports.
Once legitimate sources are authenticated and unexplained failures have been investigated, consider moving gradually to p=quarantine and eventually p=reject. Use provider guidance and your own report history to decide the timing. A strict policy introduced before every legitimate sender is identified can interrupt business mail.
5. Use a simple troubleshooting decision tree
- SPF fails: Check the envelope-from domain, confirm the sender's include or IP, and review the DNS lookup count.
- DKIM fails: Check the selector, public key, signing status, and whether the message was altered by a relay or forwarding process.
- SPF and DKIM pass but DMARC fails: Check alignment. The authenticated domain must align with the visible From domain according to the DMARC mode in use.
- DMARC reports show an unknown sender: Identify the source before allowing it. It may be a forgotten vendor, a forwarded message, or unauthorized use.
- Mail is authenticated but still goes to spam: Investigate content, list consent, bounce rates, sending volume, recipient engagement, and provider-specific diagnostic tools.
What to double-check
| Item | Check |
|---|---|
| DNS location | Confirm you are editing the authoritative DNS provider for the domain. |
| Record type | Use TXT, CNAME, or another type exactly as the mail provider specifies. |
| Host name | Check whether your DNS panel automatically appends the domain name; avoid duplicating it. |
| SPF count | Keep one SPF record and review DNS-based lookup limits after every provider change. |
| DKIM selector | Verify the selector in the message matches the selector published in DNS. |
| DMARC address | Confirm aggregate reports go to a monitored mailbox or reporting service. |
| Alignment | Compare the visible From domain with the authenticated SPF and DKIM domains. |
DNS updates may take time to appear because resolvers cache records. Test from more than one tool or network, and allow for the time-to-live set on the record. Keep a dated copy of each change so you can reverse an error without reconstructing the previous configuration.
Common mistakes
- Adding a second SPF record: Combine authorized mechanisms into one policy instead of publishing separate SPF TXT records.
- Copying a provider record to the wrong host: A DKIM record usually belongs at a selector-based name, while DMARC belongs at
_dmarc. - Forgetting non-marketing mail: Transactional and operational messages often come from different systems than newsletters.
- Publishing strict DMARC immediately: Monitor first and investigate reports before enforcing quarantine or rejection.
- Assuming forwarding means spoofing: Forwarding can affect SPF and DKIM results. Review the complete report and message headers before changing policy.
- Leaving old vendor access in place: Remove obsolete sending services and their DNS records after confirming they are no longer needed.
- Confusing website and email DNS: An A record or website hosting change is separate from SPF, DKIM, and DMARC, although all are managed in DNS.
For broader DNS diagnosis, see DNS Troubleshooting by Symptom and DNS Records Explained.
When to revisit
Keep this checklist with your domain and vendor records. Revisit authentication before seasonal planning cycles, after a domain or email migration, and whenever workflows or tools change. It should also be part of the launch checklist when you add a newsletter platform, CRM, support mailbox, payment system, contact form, or transactional sender.
At each review:
- Export or review recent DMARC aggregate reports.
- Compare observed senders with your current vendor inventory.
- Confirm SPF still contains only active services and has sufficient lookup capacity.
- Verify DKIM for each active sender and document key selectors.
- Investigate new failures before changing enforcement.
- Record the date, DNS changes, owner, and next review date.
When you change registrars, DNS providers, or hosting arrangements, preserve email records separately from website records. A domain transfer or website migration should not silently remove authentication settings. For related domain controls, use the Domain Security Checklist and keep ownership, renewal, and DNS details in a central portfolio record.
The practical goal is not to publish the most restrictive policy on day one. It is to know who sends mail for your domain, authenticate those sources consistently, review evidence from real traffic, and increase protection only when the evidence supports it.