# SPF record for Klaviyo

URL: https://iblockspam.com/spf/klaviyo
Last updated: 2026-10-09

Include: None needed
Where it goes: Not needed
DNS lookups: 0 on your domain

You usually don't need to add an SPF record for Klaviyo. Klaviyo uses its own Return-Path domain on every email, so SPF passes by default. With a branded sending domain, the CNAME or NS records you add during setup handle SPF and DKIM. You only set up DMARC yourself, at your DNS host.

## Example records

- Your main domain on Microsoft 365 stays as it is (TXT, host @): `v=spf1 include:spf.protection.outlook.com -all`
- Your main domain on Google Workspace stays as it is (TXT, host @): `v=spf1 include:_spf.google.com ~all`

## Notes

- With dynamic routing, Klaviyo hosts the DNS for the sending subdomain, so you add any extra records there in Klaviyo, not at your DNS host.
- If you do add or edit an SPF record for a sending subdomain, put it on that subdomain's host (for example `send`), not on `@`, and keep one SPF record per host.

## How to add it

- In Klaviyo, set up a branded sending domain, usually a subdomain such as `send.example.com`.
- Add the records Klaviyo shows: CNAME records plus a TXT verification record for static routing, or NS records for dynamic routing.
- Publish a DMARC record on your root domain (`_dmarc.example.com`) at your DNS host: Klaviyo doesn't do this for you.
- If your DNS host offers a proxy (Cloudflare in particular), turn it off for Klaviyo's records so Klaviyo can verify them.

## DKIM and DMARC

With a branded sending domain, Klaviyo's records enable DKIM signing with your domain, which aligns with your From address. DMARC is a separate step you complete at your DNS host; see our [DMARC record examples](https://iblockspam.com/blog/dmarc-record-examples).

## Common mistakes

- Creating a second `v=spf1` record on the same host. Klaviyo says to combine values into a single SPF record for that host.
- Proxying Klaviyo's CNAME records behind a CDN, which blocks verification.

**Q: Do I need to add Klaviyo to my SPF record?**
Usually not. Klaviyo uses its own Return-Path domain on every email, so SPF passes by default. With a branded sending domain, the CNAME or NS records from setup handle SPF and DKIM for you.

**Q: What DNS records does Klaviyo need?**
For a branded sending domain: CNAME records and a TXT verification record (static routing), or NS records (dynamic routing), as Klaviyo shows during setup. Add a DMARC TXT record on your root domain yourself.

**Q: Where do I put an SPF record for a Klaviyo sending subdomain?**
On the subdomain's host, for example `send` for `send.example.com`, not on `@`. If one already exists, edit it instead of adding a second `v=spf1` record.

Sources:
- Klaviyo Help: DNS and SPF setup troubleshooting in Klaviyo: https://help.klaviyo.com/hc/en-us/articles/50941715515675
- Klaviyo Help: Understanding email authentication: https://help.klaviyo.com/hc/en-us/articles/4402601857307

---

Source: iBlockSpam, https://iblockspam.com/spf/klaviyo (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt