How do you make Klaviyo pass DMARC?
Klaviyo passes DMARC only once you set up a branded sending domain. On the default shared domain, Klaviyo signs and bounces mail through klaviyomail.com, which never aligns with your From address. A branded domain such as send.example.com, published with Klaviyo's CNAME or NS records, makes SPF and DKIM authenticate on your own root domain, so DMARC aligns.
Klaviyo appears in many e-commerce DMARC rollouts, especially for online stores, and it is often the source that blocks the move to enforcement. This guide covers the difference between shared and branded sending, the DNS records Klaviyo asks for, what happens at p=quarantine and p=reject, how to verify with dig and message headers, a failure table and a checklist for MSPs (managed service providers). All Klaviyo details are taken from Klaviyo's own help centre as of November 2026.
Key takeaways
- On a shared Klaviyo domain, the Return-Path and DKIM domains belong to Klaviyo, so neither aligns with a From address at
example.com. DMARC then depends on your policy. - Klaviyo warns that stricter DMARC policies (
p=quarantine,p=reject) can send shared-domain mail to spam or get it rejected. - A branded sending domain uses static routing (three CNAMEs) or dynamic routing (four NS records), plus a TXT verification record on the root domain.
- The From address must share the root domain of the branded sending domain.
sales@example.comaligns withsend.example.comunder relaxed alignment. - Klaviyo can generate
v=DMARC1; p=none;. If the client already has a DMARC record, keep one record and do not add a second.
What is the difference between a shared and a branded sending domain in Klaviyo?
A shared sending domain is Klaviyo's default: mail goes out from a Klaviyo-owned domain and shared IPs, so Gmail shows "via klaviyomail.com". A branded sending domain is a subdomain of your own domain, delegated or pointed to Klaviyo, so the technical sending identity becomes yours and the "via" label disappears.
Klaviyo describes both in Understanding branded vs. shared sending domains. The key points for DMARC (Domain-based Message Authentication, Reporting and Conformance) are summarised below.
| Domain role | Shared sending domain | Branded sending domain |
|---|---|---|
From address (header.from) |
Your address, e.g. news@example.com |
Your address, e.g. news@example.com |
| Return-Path (envelope sender, SPF domain) | A Klaviyo domain such as klaviyomail.com |
Your branded domain or a subdomain of it |
DKIM signing domain (d=) |
A Klaviyo domain such as klaviyomail.com |
Your own domain, in addition to Klaviyo's |
| "via" label in Gmail | "via klaviyomail.com" | Removed when the From domain aligns |
DMARC alignment with example.com |
No | Yes, under relaxed alignment |
| Sending IP | Shared | Still shared unless the account has a dedicated IP |
Two points are easy to miss. First, Klaviyo states that "A branded sending domain does not give you a dedicated IP", so a branded domain fixes authentication, not IP reputation. Second, Klaviyo's domains overview says branded mail is signed by your own domain in addition to the shared Klaviyo domain. Only the signature from your domain matters for DMARC.
Why does Klaviyo mail fail DMARC on the shared domain?
Because neither authenticated domain matches the From domain. SPF (Sender Policy Framework) passes for Klaviyo's Return-Path, and DKIM (DomainKeys Identified Mail) passes for Klaviyo's signing domain. Both are real passes, but DMARC also needs the passing domain to align with the visible From address. Neither klaviyomail.com result aligns with example.com, so DMARC fails.
RFC 9989, the current DMARC standard, defines a pass as SPF or DKIM passing and aligning with the From domain. Klaviyo's authentication overview says the same, and adds that relaxed alignment, the default, accepts domains with a shared root. For the mechanics, see DMARC alignment explained and why DMARC fails when SPF passes.
At p=none, that failure is only visible in aggregate reports. Once the client moves to a stricter policy, the receiver acts on it.
What happens to shared-domain Klaviyo mail at p=quarantine or p=reject?
It is likely to land in spam or be refused. Klaviyo says directly that "stricter DMARC policies can cause email from a shared sending domain to be placed in spam or rejected", naming p=quarantine and p=reject. Klaviyo's guidance is to use a shared domain only if you are not required to use a branded one.
Klaviyo's deliverability FAQs add a second effect. Internal recipients at the client's own domain may block shared-domain mail, because inbox providers "may view this as a spoofing attempt". That shows up as staff never receiving test campaigns, which is often the first symptom an MSP hears about.
The order of work therefore matters:
- Set up and activate the branded sending domain in Klaviyo.
- Confirm in aggregate reports that Klaviyo mail passes DMARC through your domain.
- Only then move the client's policy from
p=nonetop=quarantine, and later top=reject.
RFC 9989 removed the percentage tag, so there is no partial ramp. Each policy step applies to all failing mail, which is why the Klaviyo fix must come first. Our guide to moving from monitoring to enforcement covers the wider sequence.
Which DNS records does a Klaviyo branded sending domain need?
Klaviyo asks for up to three CNAME records or four NS records, depending on the routing you choose, plus one TXT record on the root domain to prove ownership. The exact names and values are generated per account in Settings > Domains, so always copy them from there. Klaviyo's setup guide shows these examples.
Static routing (CNAME records)
send.example.com. CNAME 1.klaviyodns.com.
km1._domainkey.example.com. CNAME km1._domainkey.1.klaviyodns.com.
km2._domainkey.example.com. CNAME km2._domainkey.1.klaviyodns.com.
example.com. TXT "klaviyo-site-verification=PUBLIC_API_KEY"
The target number (1.klaviyodns.com here) comes from your account. Note that the DKIM records sit under the root domain, not under send..
Dynamic routing (NS records)
send.example.com. NS ns1.klaviyo.com.
send.example.com. NS ns2.klaviyo.com.
send.example.com. NS ns3.klaviyo.com.
send.example.com. NS ns4.klaviyo.com.
example.com. TXT "klaviyo-site-verification=PUBLIC_API_KEY"
Klaviyo recommends dynamic routing for performance and suggests static routing when the DNS provider does not support NS records. With dynamic routing, Klaviyo answers DNS for the subdomain. Klaviyo's guide on managing DNS for a dynamic domain says records added at your DNS provider for that subdomain "won't take effect"; extra records go in Klaviyo's Manage DNS zone panel.
Which DKIM selectors does Klaviyo use?
Klaviyo uses different selectors for each email type on static domains. Record them in the client's DNS documentation, so nobody later deletes them as unknown CNAMEs.
| Email type | Selectors | Suggested subdomain in Klaviyo's examples |
|---|---|---|
| Marketing | km1, km2 (a second marketing domain uses km3, km4) |
send |
| Transactional | kt1, kt2 |
updates |
| Service | ks1, ks2 |
support |
| Legacy static domains | kl1, kl2 |
Existing setups keep working |
Klaviyo notes that dynamically routed domains can use other selectors, such as mtd. All branded sending domains in one Klaviyo account must share one root domain. See DKIM selectors explained for background.
What about the DMARC record Klaviyo offers?
Klaviyo's setup has an Add DMARC record option that generates v=DMARC1; p=none;. Klaviyo says this meets the bulk sender DMARC requirement, while you still need to meet the other sender requirements. For a managed client, the MSP usually already runs a DMARC record with reporting. In that case, do not let a second record be created: two TXT records at _dmarc.example.com mean receivers apply no policy at all.
A good client record during the Klaviyo project looks like this:
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"
Should the branded domain be a subdomain such as send.example.com?
Yes. Klaviyo requires a subdomain that is "unique and unused", and its examples use send for marketing. The subdomain carries the Return-Path and routing, while the From address stays on the main brand, for example hello@example.com. Relaxed alignment treats send.example.com and example.com as the same organisational domain.
Under RFC 9989, the organisational domain is found by a DNS tree walk rather than the Public Suffix List. For send.example.com, the walk finds example.com, so alignment works as expected. If the client ever sends with a From address at send.example.com itself, the policy lookup also starts there. Without its own record, the tree walk falls back to the example.com record and its sp= value. Our article on subdomain or separate domain for bulk email explains why a subdomain beats a lookalike domain such as example-mail.com, and DMARC for subdomains covers sp= and the np= tag for non-existent subdomains.
Do not use strict alignment (adkim=s or aspf=s) without checking. Klaviyo notes that strict alignment requires an exact domain match, and the Return-Path on send.example.com will not match a From at example.com exactly.
How does this tie in with Gmail and Yahoo sender rules?
Bulk senders to Gmail must authenticate with SPF and DKIM, publish a DMARC policy (which can be p=none), align the From domain with SPF or DKIM, support one-click unsubscribe and keep spam rates at or below 0.3%. Google's sender guidelines define a bulk sender as one sending 5,000 or more messages a day to personal Gmail accounts.
Yahoo sets similar rules in its sender best practices. Klaviyo's FAQ adds three points that matter for retail clients:
- All traffic from the same root domain counts towards Google's threshold, including transactional mail and subdomain mail.
- Once Google classifies a sender as bulk, Klaviyo says "that status is permanent".
- Klaviyo adds one-click unsubscribe headers to marketing email automatically, and recommends Google Postmaster Tools for spam rate data.
A seasonal store that crosses 5,000 messages a day once, at a peak sale, is in scope from then on. See Google and Yahoo sender requirements and one-click unsubscribe requirements.
How does Klaviyo fit into a Shopify or e-commerce client?
Klaviyo is usually one of several senders for an online store. A typical retail client sends order confirmations from the store platform, marketing from Klaviyo, and support, review and shipping mail from other tools. Each needs aligned DKIM before the brand domain can reach p=reject.
For Shopify stores, Klaviyo and Shopify's own notifications are separate sources with separate DNS records. Authenticate both, and follow DMARC and Shopify for the store side. The wider sender map is in DMARC for e-commerce, and handling third-party senders covers the project approach.
Klaviyo's separate email types help here. A client can route marketing through send.example.com and order or service mail through updates.example.com, each with its own selectors. Aggregate reports then show each stream on its own line. For a UK retailer on example.co.uk, the same records apply with the UK domain in place of example.com.
How do you verify Klaviyo DMARC alignment?
Check DNS first, then a real message. DNS tells you the records exist; the headers tell you which domain actually signed and bounced the mail. Klaviyo's verification guide says the key information sits in the Authentication-Results header, and asks you to test one message per sending domain.
Which dig commands should you run?
# Static routing: the subdomain CNAME and both DKIM CNAMEs
dig +short CNAME send.example.com
dig +short CNAME km1._domainkey.example.com
dig +short CNAME km2._domainkey.example.com
# Dynamic routing: the delegation
dig +short NS send.example.com
# Ownership TXT and the DMARC record (exactly one v=DMARC1 line)
dig +short TXT example.com
dig +short TXT _dmarc.example.com
On Windows, Resolve-DnsName -Type CNAME km1._domainkey.example.com and Resolve-DnsName -Type TXT _dmarc.example.com give the same answers. The DKIM validator checks the public key behind each selector, and the DMARC checker parses the policy.
What should the headers show?
Send a test campaign to a Gmail mailbox, open Show original and read Authentication-Results. Before and after branding, the result should change roughly like this (illustrative values):
Before (shared domain):
spf=pass smtp.mailfrom=klaviyomail.com
dkim=pass header.d=klaviyomail.com
dmarc=fail header.from=example.com
After (branded domain):
spf=pass smtp.mailfrom=send.example.com
dkim=pass header.d=example.com header.s=km1
dmarc=pass header.from=example.com
Exact Klaviyo host names vary, and a branded message may carry a second, Klaviyo-domain signature. What matters is one passing DKIM or SPF result on a domain that shares the root of header.from. Paste the full header into the email header analyzer if it is hard to read.
What are the common Klaviyo DMARC failures and fixes?
Most failures come from DNS entry mistakes or from a From address that does not match the branded root domain. The table combines Klaviyo's troubleshooting guide with what aggregate reports typically show.
| Symptom | Likely cause | Fix |
|---|---|---|
DMARC fails, SPF and DKIM pass on klaviyomail.com |
Still on the shared domain | Set up, verify and activate a branded sending domain |
| Domain stuck on verifying or failed | Host doubled, e.g. send.example.com.example.com |
Enter only the subdomain part in the host field |
| CNAME looks right but verification fails | Cloudflare proxy enabled on the Klaviyo records | Turn proxying off for those records and keep it off |
| Target resolves under your own domain | Provider appends the root to values without a trailing dot | Add the trailing period where the provider requires it |
| DKIM records cannot be created | DNS host rejects underscores | Ask the provider, switch to dynamic routing, or move DNS |
| TXT verification fails | Value retyped or changed case | Copy TXT values exactly, including capitalisation |
| Branded domain active, DMARC still fails | From address on a different root, e.g. @example-shop.com |
Use a From address on the branded root domain |
| Reports show two DMARC records | Klaviyo's DMARC option added next to an existing record | Merge into one record at _dmarc |
| Changes in DNS have no effect | Records added at the DNS host for a delegated subdomain | Add them in Klaviyo's Manage DNS zone panel instead |
Klaviyo allows up to 48 hours for DNS changes to verify. If a domain shows as incomplete, select Verify again from the action menu after propagation.
MSP checklist for Klaviyo clients
The marketing team or agency usually owns the Klaviyo account, while the MSP owns DNS and the DMARC policy. Agree that split in writing, then work through each client:
- Find Klaviyo in the reports. Search aggregate data for
klaviyomail.comin SPF and DKIM results. Several brands or agencies may run separate accounts. Client discovery covers the method. - Confirm the From addresses use the client's root domain, for every account and email type.
- Choose routing. Dynamic if the DNS host supports NS delegation, static otherwise. Record which one, because it changes where future records live.
- Publish the records yourself rather than handing DNS credentials to an agency. Klaviyo offers an Entri connection, but manual entry keeps the change in your own log.
- Keep one DMARC record. Skip or remove Klaviyo's generated record if a managed record with
ruareporting already exists. - Coordinate activation. Klaviyo asks the marketing team to pause flows and campaigns before activating a first marketing domain, and new accounts should warm up over two to four weeks.
- Verify with
digand a header check, then watch aggregate reports for at least one full sending cycle. - Tighten policy from
p=nonetop=quarantinetop=reject, without percentage steps. RFC 9989 offerst=yas a testing flag if a receiver needs it. - Offboarding: when a client leaves Klaviyo, remove the CNAMEs or NS delegation and the verification TXT record, and update the documented selector list.
DMARC AI processes aggregate reports for every client domain in one place and classifies sending sources, so a Klaviyo account still on the shared domain shows up as a failing source for that client.
FAQ
Does Klaviyo require a DMARC record?
Klaviyo recommends one and can generate v=DMARC1; p=none; during branded domain setup. Gmail and Yahoo require a DMARC record from bulk senders, and Klaviyo says a valid p=none record meets that policy requirement. Alignment through a branded sending domain is still needed for messages to pass DMARC.
Can I use p=reject with Klaviyo?
Yes, once a branded sending domain is active and reports show Klaviyo mail passing DMARC through your own domain. On the shared domain, Klaviyo warns that p=quarantine or p=reject can push mail to spam or get it rejected. Fix Klaviyo and every other sender before tightening the policy.
Does a Klaviyo branded sending domain give me a dedicated IP?
No. Klaviyo states that a branded sending domain does not give you a dedicated IP. It changes the authenticated domains so DMARC aligns and the "via klaviyomail.com" label disappears. Dedicated IPs are a separate Klaviyo option, and not every account qualifies for one.
Do I need a Klaviyo include in my root SPF record?
Klaviyo's setup does not ask for one. SPF for branded sending is enabled through the subdomain's CNAME or NS records, because the Return-Path uses your branded subdomain. The root SPF record keeps its lookup budget for the client's main mail platform. Check the current Klaviyo setup page before changing anything.
Why does Gmail show "via klaviyomail.com"?
The message was sent from Klaviyo's shared domain, so the authenticated domain differs from your From address. Setting up a branded sending domain on the same root as the From address removes the label, according to Klaviyo. It also gives you the aligned DKIM signature DMARC needs.