DMARC, SPF and DKIM for Shopify
Updated 2026-11-14
Shopify sends your store's notification emails, order confirmations and marketing emails from the Sender email you set in the admin. To send them as your own domain, you authenticate that domain with CNAME records that Shopify shows you. DMARC is a record you publish, unless you bought the domain through Shopify. This guide follows Shopify's help center article on setting up your email. For background on each standard, see SPF explained, DKIM explained and DMARC explained.
What Shopify sends from
The visible From address is your Sender email, for example [email protected]. Shopify lists it in Settings > Notifications and uses it "as the From email address when your customers receive automatic notification emails, order confirmation emails, and any marketing emails sent from your store". The Store email in Settings > General is a different address: it is where Shopify contacts you.
The fallback: as of November 2026, if your domain is not authenticated, Shopify rewrites the sender to [email protected], where the number "is unique to your store". Shopify says this happens when authentication records are not configured, when you remove the CNAME records ("Shopify Email will automatically reset your sender address"), and possibly when your domain has more than one DMARC record. Without the newer recommended records, mail "might temporarily be sent from" that address during a delivery disruption.
The envelope sender (Return-Path, also called MAIL FROM) and the DKIM d= domain are not documented. Shopify only says the CNAME records connect your domain "to the Shopify SPF and DKIM records". It also says mail sent through Shopify passes DMARC even with strict alignment. Strict alignment for both SPF and DKIM requires an identical domain, so in our reading at least one of the two is exactly your Sender email domain once the domain is authenticated. Send a test notification to yourself and read the Return-Path and DKIM-Signature headers to see which names are used.
SPF
Shopify does not ask for an SPF include. As of November 2026 its article says: "The CNAME records you add during domain authentication handle SPF automatically for your sender email address. You don't need to add a separate SPF TXT record for this purpose." It also says "You don't need to add any IP addresses to your domain".
SPF is checked on the Return-Path domain. Shopify does not say which name that is, so the SPF record that covers Shopify mail sits behind one of the CNAMEs, in our reading, not in a record you edit. A name with a CNAME cannot also hold a TXT record, so never put your own SPF record on a name that Shopify gave you as a CNAME.
Your root domain still needs SPF for services that use example.com itself as Return-Path, such as your mailbox provider. A typical record looks like this, where include:_spf.example.net is a placeholder for "another service":
example.com TXT v=spf1 include:_spf.example.net ~all
This record uses 1 DNS lookup in the record itself. The include adds its own nested lookups, which depend on that service and are not documented here. The limit is 10 lookups for the whole tree (RFC 7208); the SPF lookup counter counts it. See also too many SPF lookups. One name may only have one SPF record, so merge includes rather than adding a second record (multiple SPF records).
DKIM
DKIM for Shopify is set up through the same CNAME records. Shopify does not publish the names or values in its help article; the admin shows them. As of November 2026 the documented manual steps are:
- From your Shopify admin, go to Settings > Notifications.
- In the Sender email section, click Email domain authentication (one step in the article calls the link "authenticate your domain").
- Enter "all CNAME records displayed" at your DNS host. Shopify says: "The number of records may vary, so you must add all records displayed in the modal."
- Wait: Shopify says changes can take up to 48 hours.
Shopify's Manual setup and update instructions then have you click I updated DNS records to start the check.
The CNAMEs go on the domain of your Sender email. Shopify's example: if the sender is [email protected], add them to the johns-apparel.com domain.
Automatic setup: if your domain was bought through Shopify, "your DKIM, SPF, and DMARC records are configured for you". For domains on Cloudflare, GoDaddy or IONOS, you can click Authenticate automatically and approve the change at the provider. The article says both "hosted on" and "purchased your domain from" these providers, so it is unclear which one counts. It is also not consistent about DMARC: one sentence says these providers' domains get their "DNS records" configured, while a note says automatic authentication "doesn't configure a DMARC record". Plan to add DMARC yourself in that case.
Status: Authenticated means nothing to do. Update recommended means "new CNAME records are available for your domain, or your CNAME records don't match the expected value". The update is optional; add the missing records and keep the ones you have, "because they're still required".
Selectors, key length and rotation are not documented. Because the records are CNAMEs, the key data sits on Shopify's side, in our reading. Shopify does not support this step on every store: adding CNAME records "isn't possible for client transfer stores, dev stores, or for stores on the Pause and Build plan".
DMARC alignment
DMARC passes when SPF or DKIM passes and that result aligns with the From domain. SPF alignment compares the Return-Path domain with the From domain. DKIM alignment compares the signature's d= domain with the From domain. Relaxed alignment means both are in the same organisational domain. Strict alignment (aspf=s, adkim=s) means the domains must be identical.
Shopify does not say which of the two identifiers aligns. It does state that "Emails sent through Shopify pass DMARC when one or both of these settings are strict", so you can keep a strict record. As a general DMARC rule, not a Shopify statement: if the Return-Path is a subdomain of yours, SPF aligns only in relaxed mode, because aspf=s needs an identical domain. Mail rewritten to shopifyemail.com is outside your domain's DMARC.
Shopify warns: "Your domain must have only one DMARC record. Having multiple DMARC TXT records causes DMARC validation to fail" (multiple DMARC records). Update your existing record instead of adding one.
Step by step to p=reject
- Set the Sender email. In Settings > Notifications, enter an address on your domain in the Sender email section, such as
[email protected], and click Save. Check that your store is on an active paid plan, because adding CNAME records is not possible on some store types. - Authenticate the domain. Click Email domain authentication and choose Authenticate automatically (Cloudflare, GoDaddy or IONOS) or add every CNAME record the admin displays at your DNS host; Shopify's Manual setup instructions then have you click I updated DNS records.
- Wait for Authenticated. Changes can take up to 48 hours; if verification fails, compare your DNS records with the values in the admin and send a test notification to read its headers.
- Check SPF on the root domain. Keep one SPF record on
example.comfor your other services, with no Shopify include, and stay under 10 DNS lookups in total. - Publish DMARC with p=none and a report address. Shopify's default record is
v=DMARC1; p=nonewith no report address; addruaso receivers send aggregate reports, as in the record below. - Read the reports and fix other senders. Watch the reports for a few weeks, confirm that Shopify mail passes with your domain, and give every other legitimate sender aligned DKIM or SPF.
- Move to p=quarantine. Change the policy to
p=quarantineand keep reading reports, because failing mail now goes to spam and any sender you missed shows up quickly. - Move to p=reject. When the reports show only legitimate mail passing and nothing legitimate failing, change the policy to
p=reject.
The record for step 5:
_dmarc.example.com TXT v=DMARC1; p=none; rua=mailto:[email protected]
That record triggers our DMARC policy none note on purpose; it is the monitoring stage. The final record:
_dmarc.example.com TXT v=DMARC1; p=reject; rua=mailto:[email protected]
Some receivers support pct (RFC 7489) or t=y (RFC 9989), but RFC 7489 says unknown tags are ignored, so a receiver may apply p=reject; t=y as a full reject. Do not treat either tag as a safety net.
Common mistakes
- Adding only some CNAME records. Shopify says the number varies and you must add all records displayed.
- Removing the CNAME records. Shopify warns this "can cause deliverability issues, including bounces", and your sender is reset to
shopifyemail.comuntil you restore them. - Adding a Shopify SPF TXT record or IP addresses. The CNAMEs handle SPF; Shopify says no separate SPF TXT record or IP addresses are needed.
- A second DMARC record. Two DMARC TXT records make DMARC fail and may trigger the rewrite. Edit the one you have.
- Domain added twice. Entering the full
_dmarc.example.comat a host that appends the domain produces_dmarc.example.com.example.com. Shopify notes that "Some domain hosts automatically add the domain portion", so enter_dmarcthere and check the result after saving. - No report address. Shopify's default DMARC record has no
rua, so you cannot see what fails (DMARC without rua).
How to check it
Run the email security check on example.com to read SPF, DKIM and DMARC together. Use the SPF lookup counter on your root domain to count the full lookup tree. Shopify does not document its DKIM selector; read the s= value from the DKIM-Signature header of a test notification and enter it in the DKIM selector finder. Build your policy with the DMARC record generator. In the Shopify admin, Email domain authentication should show Authenticated.
Frequently asked questions
Do I need to add Shopify to my SPF record?
No. As of November 2026 Shopify says the CNAME records you add during domain authentication "handle SPF automatically for your sender email address" and that you don't need to add a separate SPF TXT record for this purpose. Keep your existing SPF record for your other services.
Why are my store emails sent from [email protected]?
Shopify rewrites the sender email to an address of the form [email protected] when your domain is not authenticated, when you remove the CNAME records, and possibly when your domain has more than one DMARC record. The number is unique to your store. Authenticate the domain under Settings > Notifications to send from your own address again.
What are the exact CNAME records for Shopify?
Shopify's help pages do not print them. The admin shows them under Settings > Notifications, Email domain authentication. Shopify says the number of records may vary and that you must add all records displayed. Do not remove them later.
Can I keep adkim=s or aspf=s in my DMARC record?
Yes. Shopify says that if your existing DMARC record uses strict alignment, you don't need to change it, because emails sent through Shopify pass DMARC when one or both of these settings are strict.
Sources
- Setting up your email, Shopify documentation, fetched 2026-11-14.
- RFC 7208: Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, RFC Editor, fetched 2026-11-14.
- RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC), RFC Editor, fetched 2026-11-14.
- RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC), RFC Editor, fetched 2026-11-14.