Skip to content
DMARC Pulse
Guides

Klaviyo

Klaviyo DMARC setup: SPF, DKIM and a branded sending domain

Klaviyo DMARC setup: add a branded sending domain with NS or CNAME records, check your DKIM selectors and publish one DMARC record on your root domain.

Klaviyo DMARC setup starts with a branded sending domain: a subdomain of your own domain, such as send.example.com, that Klaviyo sends from. DMARC is the record that tells receivers how to treat mail that fails authentication, and it needs a domain it can match to your From address. This guide covers that subdomain, the Klaviyo DKIM selectors, the Klaviyo SPF record and the DMARC record you publish yourself.

How Klaviyo authenticates your mail

New accounts usually start on a shared Klaviyo domain such as klaviyomail.com. Klaviyo has already set up authentication there, so those messages carry passing results for Klaviyo's domain. Your From address is on your own domain, so those results do not align and DMARC cannot pass for you. In Gmail, recipients also see via klaviyomail.com beside your address.

A message passes DMARC when SPF or DKIM passes and the authenticated domain aligns with the From domain. Alignment is relaxed by default, so the two only need to share an organizational domain, the domain you registered, which Klaviyo calls the root domain: sales@example.com aligns with send.example.com. RFC 9989, the current DMARC standard, defines this in sections 3.2.10 and 4.4.

Klaviyo DKIM selectors

DKIM adds a signature that receivers check against a public key in DNS. Once your branded domain is set up, Klaviyo signs your mail with your own domain and also with a shared Klaviyo domain. One aligned signature is enough for DMARC (RFC 9989, section 4.4.1), and Klaviyo describes DKIM as the way its branded domains meet alignment.

A DKIM selector is the name that locates the public key. With Static routing, the CNAME records use these selectors by send type:

  • Marketing: km1 and km2
  • Transactional: kt1 and kt2
  • Service: ks1 and ks2

A second domain of the same type takes the next pair, such as km3 and km4 for marketing. Static domains set up before send types existed can keep kl and kl2 or kl1 and kl2. Leave those records unchanged. With Dynamic routing you add no selector-named CNAMEs, because Klaviyo serves the DKIM records for you. These domains can use other selectors, such as mtd, so read the selector from a real message when you check one.

Klaviyo SPF record

SPF lists the servers allowed to send for a domain. Receivers check it on the Return-Path, the hidden address that collects bounces. On a branded setup, the Return-Path can be your branded sending domain or one of its subdomains.

Klaviyo documents no include: for you to add, and it says you do not need to add Klaviyo to your root domain's SPF record. The NS or CNAME records from setup connect the branded domain to SPF records that Klaviyo manages. SPF can pass without aligning, and DMARC can still pass through an aligned DKIM signature.

Step 1: Add the domain in Klaviyo

You need the Owner, Admin, Manager or Campaign Coordinator role, and someone with access to your DNS.

  1. Click your company name at the bottom left, then open Settings and Domains. Klaviyo's help pages show this path as Settings > Domains and as Settings > General > Domains.
  2. Select Add domain and choose the Email type: Marketing, Transactional or Service. Each type can have one active domain.
  3. Confirm the root domain. Klaviyo fills it in from your account, and every branded sending domain in the account must use it.
  4. Enter an unused subdomain under Sending domain, such as send.
  5. Choose the Routing type. Klaviyo recommends Dynamic, which delegates the subdomain to Klaviyo with NS records (records that name the servers answering for a host). Choose Static, which uses CNAME records (aliases to another host), if your DNS provider does not support NS records.
  6. If your domain has no DMARC record, decide whether to turn on Add DMARC record.

Step 2: Publish the DNS records

Choose Connect with Entri or Set up manually. Entri appears only for eligible domains and publishes the records after you log in to your DNS provider. For manual setup, copy what Klaviyo generates. The values in its help pages are examples, and yours will differ.

  • Dynamic: up to 4 NS records for the subdomain, plus 1 TXT record on the root domain that proves ownership.
  • Static: up to 3 CNAME records, plus that TXT record. For a first marketing domain, the hosts are send.example.com, km1._domainkey.example.com and km2._domainkey.example.com.

You do not create the subdomain yourself. Copy the TXT value exactly, including capitalization. If your root domain already has TXT records, add Klaviyo's as a separate TXT record at the same hostname and leave the others alone.

Step 3: Publish your DMARC record

Your DMARC record is a TXT record named _dmarc on the root domain. Check for an existing one first.

If your domain has none, Add DMARC record generates v=DMARC1; p=none;. This meets the DMARC policy requirement for bulk senders and asks receivers for no action on failures. Other sender requirements still apply. It also requests no reports, because it has no rua tag, the address that receives aggregate reports. Publish this instead of the generated record, never alongside it. If Klaviyo's v=DMARC1; p=none; is already published, add the rua tag to that record. A domain with two _dmarc TXT records has no usable DMARC policy.

To get reports, the record needs that tag:

Use this starter value only if no DMARC policy exists at this name. Otherwise edit the existing record, preserving its p=, alignment settings and report addresses; add your monitored rua destination there. Never create a second policy record.

TXT
v=DMARC1; p=none; rua=mailto:dmarc@example.com

Replace the address with your DMARC Pulse reporting address. An address on another domain needs that domain's permission, given through a TXT record (RFC 9990, section 4), so follow your report service's instructions.

If your domain already has a DMARC record, Klaviyo says to review it instead of adding a second record or replacing its policy with p=none. Keep a single record.

Step 4: Verify and activate

With manual setup, select Verify after adding the records. With Entri, verification starts on its own. Select Finish to return to Domains while Klaviyo checks the records, which can take up to 48 hours.

When the status shows Verified, select Activate on the domain's row, because Klaviyo does not activate a domain on its own. For a first marketing domain, Klaviyo recommends pausing flows and campaigns before you activate. New qualifying accounts, and domains registered in the last 30 days, should warm up marketing sending over the first 2 to 4 weeks. Warming means raising volume gradually. Existing customers activating a first marketing domain can skip it if the domain is at least 30 days old and has already sent email.

Send from an address on your root domain, such as name@example.com. For marketing and transactional mail, keep the sending subdomain out of the From address, because you would not receive replies. Service domains work differently.

Step 5: Confirm it and tighten the policy

Send yourself a test and paste the headers into the Email Header Analyzer. Look for dkim=pass for your own domain and dmarc=pass. In the DKIM-Signature header, d= is the signing domain and s= is the selector. Expect two signatures, one from your domain and one from Klaviyo's. The DMARC Checker confirms that your record is published, but a DNS lookup cannot show that messages pass.

Preserve any existing policy and report destinations. For a first deployment, monitor at p=none. After every legitimate sender passes with alignment, assess p=quarantine. Consider p=reject separately, including mailing-list and forwarding risks; it is optional. Receivers decide how to handle individual messages.

Common problems

  • dmarc=fail on mail from a branded domain. Check that the domain is active and that your From address uses the same root domain. A From address on a different root domain does not align.
  • Strict alignment. Klaviyo's example of send.example.com aligning with example.com applies to relaxed mode. If your record sets adkim=s or aspf=s, the authenticated domain must match your From domain exactly. Both tags default to relaxed (RFC 9989, section 4.7), so check whether your record sets them.
  • Cloudflare proxy. Proxying can hide the CNAME target Klaviyo needs to verify. Set Klaviyo's CNAME records to DNS only and keep them that way after setup.
  • Record not found. Some DNS providers add your root domain to the host automatically, which produces send.example.com.example.com. Enter only send in the host field.
  • A CNAME target that ends in your own domain. Some panels append your domain to the value you paste. Add a final period to the value.
  • A panel that rejects underscores. Static DKIM hosts such as km1._domainkey need them. Ask your DNS provider to create the records. If it cannot and it supports NS records, use Dynamic routing.
  • Duplicate SPF. A host can have only one v=spf1 record. Combine the mechanisms into one record with a single ending such as ~all or -all, as our page on multiple SPF records explains. Klaviyo itself needs no change to this record.
  • TXT records on the sending subdomain. With Static routing, do not add a TXT record at a host that has a Klaviyo CNAME. With Dynamic routing, records you add at your DNS provider for the subdomain have no effect, so add them in Klaviyo under Manage DNS zone.
  • A domain shows Action required or Failed during setup. Open View records, correct what is wrong and select Verify. DNS changes can take up to 48 hours to update.
  • A domain shows Failed after it was already sending. There is no Verify button in that state. Fix the records at your DNS provider, wait a few minutes and refresh the page.
  • A disconnected domain. Klaviyo marks a branded domain as disconnected when its required DNS records are removed, and it alerts users who can configure domains. Its documentation does not say how mail is handled while the domain is disconnected, so restore the records as soon as you can.
  • Internal mail flagged on a shared domain. Inbox providers may show a warning or place the message in spam when the recipient has the same domain as your From address and you send from a shared domain. An aligned branded domain can help, though it does not ensure inbox placement.
  • BigCommerce Domains. Use Static routing, because that DNS provider does not support the NS records Dynamic needs.

Frequently asked questions

Do I need to add Klaviyo to my SPF record?
No. Klaviyo says you do not need to add it to your root domain's SPF record, and it documents no include: for customers. The NS or CNAME records from the branded sending domain setup connect that domain to SPF records Klaviyo manages.
What are Klaviyo's DKIM selectors?
With Static routing, marketing domains use km1 and km2, transactional domains use kt1 and kt2, and service domains use ks1 and ks2. A second domain of the same type uses the next pair, such as km3 and km4. Older static domains can keep kl and kl2 or kl1 and kl2. With Dynamic routing, Klaviyo serves the DKIM records and you add no selector-named CNAMEs. Those domains can use other selectors, such as mtd.
Can I pass DMARC on Klaviyo's shared sending domain?
Not for your own domain. On a shared domain such as klaviyomail.com, the Return-Path and DKIM domains do not align with your From address. Klaviyo advises against the shared domain if your domain uses p=quarantine or p=reject, because that mail can be placed in spam or rejected.
Do I need a branded sending domain in Klaviyo?
If you are a bulk sender, yes. Klaviyo says to set one up to meet inbox providers' authentication requirements. Google applies its bulk sender rules at 5,000 or more messages a day to personal Gmail accounts. Klaviyo also says to use a shared domain only if you are not required to use a branded one and your domain does not use p=quarantine or p=reject. A branded domain does not ensure inbox placement.
Should I choose Dynamic or Static routing?
Klaviyo recommends Dynamic, which uses NS records and lets Klaviyo choose a sending provider for each message. Choose Static, which uses CNAME records, if your DNS provider does not support NS records.
Does Klaviyo create a DMARC record for me?
It can. During setup, if your domain has no DMARC record, the Add DMARC record option generates v=DMARC1; p=none;. If you already have a record, Klaviyo says to review it with your IT team or DMARC service instead of adding a second one or replacing its policy with p=none. To receive reports, the record needs a rua tag.

Sources consulted

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.