How it worksSample reportPricingGuidesHelpSign inRun free Gap Check

DMARC p=none on a Klaviyo store: what it does, what it does not, and the next step

Updated October 19, 2026. Every fact on this page comes from Klaviyo's Help Center, Google's Gmail and Workspace help pages, or the SPF standard, all linked under Sources. It has no statistics and no customer results, because we do not have any of our own to share yet.

On this page (8 sections)

What p=none means

DMARC is a TXT record at _dmarc.yourstore.com. It tells receiving mail servers what to do with mail that claims to come from your domain but fails the SPF and DKIM alignment checks. The p tag is the policy. Klaviyo's Help Center lists the three values like this:

  • p=none: accept the email normally, despite the misalignment.
  • p=quarantine: accept the email but place it in spam.
  • p=reject: block the misaligned email.

A typical record looks like v=DMARC1; p=none; rua=mailto:dmarc-reports@yourstore.com. The rua tag is where daily DMARC reports are sent. Klaviyo calls it recommended, not required. If sp is left out, subdomains follow the p value.

Why so many stores sit at p=none

Because it is the record Klaviyo and Google point new senders to, and it is enough to meet the sender requirements:

  • When you set up a branded sending domain, Klaviyo can generate a DMARC record for you, and the one it generates is v=DMARC1; p=none;. Klaviyo says this satisfies inbox provider sender requirements without affecting the delivery of your emails.
  • Google's Email sender guidelines require all senders to Gmail accounts to set up SPF or DKIM. Senders of 5,000 or more messages a day to Gmail accounts must set up SPF, DKIM and DMARC, and Google says the DMARC enforcement policy can be set to none.
  • Google counts every message from the same primary domain toward that 5,000 a day threshold, subdomains included, and a sender who reaches it once is treated as a bulk sender from then on. Klaviyo adds that all traffic counts, including transactional email.

So p=none is a sensible first step. It is not a finished setup.

What p=none does not do

Klaviyo is direct about this: p=none does not affect inbox placement when an email is sent from a misaligned domain, so recipients can still receive email from someone impersonating your brand. A customer who opens a spoofed "order problem" email that looks like it came from you has a reason to trust your real emails less.

With p=quarantine or p=reject, misaligned mail goes to spam or is blocked, so spoofed email does not reach the main inbox.

Check these before you tighten anything

DMARC applies to every email sent from your domain, not just Klaviyo. Klaviyo warns that stricter policies can stop your own mail from being delivered if your domains are not aligned across all of your sending. Check these first:

  1. Klaviyo is on a branded sending domain. On Klaviyo's shared sending domain, your from address (for example hello@yourstore.com) never aligns with the sending domain (a klaviyomail.com address), so DMARC alignment fails. With a branded sending domain such as send.yourstore.com that matches your from address, Klaviyo says DMARC checks pass. The Klaviyo records added during that setup also handle SPF and DKIM for Klaviyo mail, so you do not add your own for Klaviyo.
  2. Everything else that sends as you is authenticated. Your mailbox provider, your store's order and shipping emails, your help desk and any other tool that sends from your domain. This is what the DMARC reports show you.
  3. You have exactly one SPF record. Under the SPF standard (RFC 7208, section 4.5), if a domain publishes more than one SPF record, the check returns a permanent error (permerror). This can happen when two tools each ask you to add an SPF record. Merge them into one.
  4. Reports have somewhere to go. Klaviyo says the raw reports are XML files that are hard to read and recommends a DMARC service provider to process them. The rua address must be on your own root domain, unless the other domain publishes a TXT record that authorizes it.

The rollout Google recommends

Google's Workspace help center lays out a gradual rollout:

  1. Set up SPF and DKIM at least 48 hours before DMARC.
  2. Start at p=none for one week and review the DMARC reports daily. Google says a week is usually enough for the reports to cover all of your mail streams.
  3. If the reports show no problems with your own mail, move to p=quarantine for a small percentage of messages with the pct tag, for example v=DMARC1; p=quarantine; pct=5; rua=mailto:dmarc@yourstore.com. Google gives 10% as a possible start for a small organization and 1% for a large one.
  4. Raise the percentage over time until it covers 100% of messages. p=reject is the strictest option: failing messages are never delivered.

Klaviyo recommends doing this with your IT team, a DMARC service provider or another professional, and notes that Klaviyo cannot set DMARC for you, because it lives in your DNS.

Check your own record

  1. Look up the TXT record for _dmarc.yourstore.com with any DNS lookup tool, or use the DMARC checker that Klaviyo points to (EasyDMARC). Klaviyo says a status of Warning or Valid meets inbox provider sender requirements.
  2. Look up the TXT records for yourstore.com and count the ones that start with v=spf1. There should be one.
  3. Send yourself a Klaviyo test email and open the message headers. Klaviyo's Help Center explains how to read SPF, DKIM and DMARC results there.

Step 1 of our free Gap Check also reads your public SPF and DMARC records as soon as you enter your store domain.

A five minute checklist

  1. One DMARC record at _dmarc on your root domain.
  2. Exactly one SPF record on your root domain.
  3. Klaviyo sending from a branded sending domain that matches your from address.
  4. An rua address on your own domain, or a DMARC service provider, and someone who reads the reports.
  5. After at least a week of clean reports, a plan to move to quarantine at a small pct.

Where FlowsFixed fits

Every flow fix includes a sending domain check: we send you the exact SPF and DMARC records for your DNS host and check that they pass afterwards. You add the records yourself, so we never need access to your domain account. Moving your policy to quarantine or reject is your call, made from your own reports. We are taking requests now and not accepting payments yet.

Sources

Read on October 19, 2026. Klaviyo and Google may change their menus and advice. FlowsFixed is not affiliated with Klaviyo or Google.

Related guides

BenchmarkKlaviyo abandoned cart benchmarkWhat a good abandoned cart flow earns in 2026, and why most underperform.Read the guide BenchmarkKlaviyo welcome flow benchmarkThe widest gap between average and top 10% of any core flow.Read the guide BenchmarkKlaviyo browse abandonment benchmarkWhat the flow earns, from Klaviyo's own published data.Read the guide

All guides