Configure MX, SPF, DKIM, DMARC, forwarding, and verification for domains used with Outlio.
This is the core authentication checklist every sending domain should pass before campaign launch.
Your registrar is not always your active DNS host. If nameservers point to Cloudflare, edit Cloudflare. If they point to Namecheap or GoDaddy, edit there. Editing the wrong place is the most common reason records never show up.
SPF is a TXT record at the root host, usually @. You should only have one SPF record for a domain. If you use more than one legitimate sender, merge the include mechanisms into one record.
DKIM values are generated by the mailbox provider, not by Outlio. Google often gives a TXT record. Microsoft often gives two CNAME selector records. Use the record type and host exactly as the provider gives them.
Add DMARC as a TXT record at _dmarc. Start with monitoring while you confirm legitimate mail passes SPF and DKIM. Tighten the policy only after you know normal business mail is aligned.
Host/name: _dmarc
Example starting value: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
Replace the report email with an inbox you control or a DMARC reporting provider.
Open Email Accounts.
Click Test Domain Setup.
Review which domains and records are missing.
Fix DNS at the active DNS host.
Wait for propagation and test again.
A cleaner Outlio setup, fewer avoidable campaign issues, and a more reliable path from setup to replies.
Use Outlio to verify email authentication.
Add and verify records when Cloudflare manages DNS.
Set up branded tracking for opens and links.
Diagnose missing MX, SPF, DKIM, or DMARC records.
Was this article helpful?
Need more help? Contact Support