Business email · Practical guide
SPF, DKIM and DMARC: a practical business email setup guide
SPF, DKIM and DMARC answer different questions. A working MX record does not prove outbound mail is authenticated.
First published · OlaCheap technical reference · Check current provider instructions before changing production services
Know what each record proves
SPF tells receiving servers which hosts are permitted to send using a domain in the SMTP envelope. DKIM adds a cryptographic signature that can be verified through a DNS public key. DMARC checks alignment between the visible From domain and an authenticated SPF or DKIM domain, then communicates a requested policy.
An SPF pass alone may not satisfy DMARC when the authenticated envelope domain differs from the visible From address. Similarly, a DKIM signature can be valid but not aligned. Look at authentication results from a received message rather than trusting only a DNS checker.
Inventory every legitimate sender
List the business mailbox provider, transactional email API, marketing platform, helpdesk, invoicing service and any device that sends mail as your domain. For each one, confirm the vendor's documented SPF and DKIM setup. Do not simply copy a record from another website: the allowed services and selectors are domain-specific.
Keep only one SPF TXT record at the domain name used for SPF. Multiple separate SPF policies can invalidate evaluation. Stay within the protocol's DNS lookup limits and avoid permissive +all policies. An old sender can continue working after migration if its DKIM and envelope configuration are preserved during a measured overlap.
Verification checklist
- Map every provider that sends email as your domain
- Check each sender's DKIM selector and actual From alignment
- Test replies, forwarding and bounce-handling flows
Roll out DMARC by measuring before enforcement
A cautious rollout usually starts by publishing a DMARC record at _dmarc.example.com with a monitoring policy and an aggregate-report destination that you control. Examine reports to identify legitimate senders that are not aligned, then fix them before applying quarantine or reject.
A DMARC report address can receive detailed operational metadata. Use a trusted mailbox or reporting service that is designed to process it. Forwarders and mailing lists may behave differently, so exercise representative mail flows before changing policy.
Verify mail in the receiving inbox
Send a real message from each provider to at least two unrelated receiving providers. Inspect the Authentication-Results headers and confirm SPF, DKIM and DMARC evaluation. A green DNS status cannot guarantee inbox placement; message quality, sender reputation, volume and recipient signals also matter.
Repeat after DNS migrations or onboarding a new sender. Treat mail authentication as an ongoing inventory, not a once-only setup wizard. Record the owner of each sender and the date its DNS records were checked.
Next practical step
This article is an educational checklist, not a claim of live product availability or a substitute for current documentation from your provider.
Explore business email hosting →References and official documentation
These materials help verify procedures. Provider requirements may change, and this guide does not claim first-hand security certification or independent testing of third-party products.