Make Klaviyo DMARC-compliant
How to authenticate Klaviyo as a sender on your domain - so its mail passes SPF, DKIM and DMARC, and you can safely reach enforcement.
Three steps to authenticate Klaviyo
Klaviyo needs to pass SPF and DKIM, and align with your domain so DMARC passes. Here’s how – confirm the exact values against Klaviyo’s current documentation as you go.
How Klaviyo authenticates
Klaviyo sets up SPF and DKIM for you through the CNAME / NS records you add when you configure a branded sending domain - there is no SPF include to paste in by hand.
So there’s no SPF include to paste in for Klaviyo – DKIM (next step) is what carries DMARC alignment. Hosted SPF still helps keep your overall record under the 10-lookup limit.
No SPF include to add
Klaviyo authenticates through the CNAME records you publish during its domain-setup flow – follow Step 2.
Turn on DKIM signing
DKIM cryptographically signs each message so receivers can prove it really came from you and wasn’t tampered with. Configured automatically via the branded-domain CNAME/NS records Klaviyo provides during setup (three CNAMEs plus a verification TXT).
DKIM is what keeps you authenticated even when a message is forwarded – so it’s worth getting right. More on how DKIM works →
- Enable DKIM inside Klaviyo
- Publish the DNS records it gives you
- Wait for it to verify, then send a test
Confirm alignment, then enforce
With SPF and DKIM set up, check that Klaviyo aligns – that the authenticated domain matches your visible From address. Once every legitimate sender aligns, you can move DMARC to p=reject safely.
DMARCER’s enforcement journey shows you exactly when it’s safe to advance – no guesswork.
Good to know
You still publish your DMARC record yourself at your DNS provider - Klaviyo doesn't do that part.
Check you got it right
Look up your records instantly, or run a full free check to confirm Klaviyo passes SPF, DKIM and DMARC – and get your score out of 100.
Check SPF Full free check