[ Sending-service guides ]

Shopify sender authentication: protect the address customers recognise

Check Shopify-managed and third-party DNS separately, retain required records and test the customer notifications that matter.

By the EmailAuth research team · 5 min read

On this page

A Shopify store's website domain and its sender identity are related business assets with different technical dependencies. A working storefront does not prove that an order confirmation uses the branded From address or passes aligned authentication.

Start with the sender email configured for the store and the domain that follows the at sign. Establish who controls that domain's active DNS. Then review Shopify's authentication status for the same identity.

Identify the management path

Shopify's current instructions distinguish domains it manages from third-party DNS. Authentication can already be managed for a Shopify-purchased domain, while supported third-party providers can offer an automatic connection. Other configurations use manual changes.

Do not assume that every store needs the same work. Check the store's current state before issuing a DNS request. If authentication is managed, confirm its status and inspect a received notification rather than recreating managed records elsewhere.

For a third-party domain, use the authentication workflow associated with the store's sender email. Review what an automatic connection proposes to change and retain the resulting record names. Automation should leave the owner able to understand and maintain the configuration.

In Shopify admin, open Settings > Notifications > Sender email > Email domain authentication. For supported third-party DNS providers, automatic authentication configures the CNAMEs, not DMARC. Check for an existing applicable DMARC record and add or update it separately when needed.

Use the displayed records, not a historical SPF recipe

Shopify currently directs manual setups to its generated CNAME records and an applicable DMARC record. Publish every required generated record with its exact type and target. A generic instruction to authorise a guessed IP range is not a substitute.

Before manual setup, confirm the store is on an active paid plan. Shopify excludes client transfer stores, development stores and Pause and Build stores from this CNAME setup. The generated CNAMEs handle SPF and DKIM; a separate SPF TXT record is not required for this Shopify sender-email setup.

If the domain already has a DMARC policy, assess that policy in context. Adding Shopify should not silently remove reporting or weaken an operating policy that covers other services.

Use the active authoritative DNS zone. Check whether the editor expects a relative owner name or a full hostname. A correct-looking value in an inactive panel will not help a receiver validate mail.

Keep any CNAME owner conflicts visible in the change request. The same DNS name cannot be casually repurposed while another service depends on it. Resolve the intended configuration before publication.

Treat an update status as a specific maintenance task

Shopify documents an Update recommended state for changed or missing expected CNAMEs. It is not, by itself, evidence that all current sending has stopped.

Compare the displayed requirements with the authoritative answers and follow the applicable update workflow. The current instructions say to retain existing required CNAMEs while adding or correcting the relevant records. Do not delete the old set merely because new values appear.

For managed records, use the supported management or support path. Keep the distinction between a configuration the store can edit and a configuration Shopify controls.

Verify a real customer notification

Use a controlled order or another supported test that exercises the notification route you are assessing. Avoid sending unsolicited tests to customers. Save the received original with appropriate access controls.

Check the visible From address, the signing identity and trusted authentication results. Record whether the expected branded identity is present and whether a passing SPF or DKIM path aligns with it. Reply-To is a separate field; a recognisable reply address does not establish DMARC alignment.

In a synthetic example, a store owner sees successful checkout and assumes email is ready. The received confirmation uses a rewritten sender address. The useful investigation begins with that actual identity and the store's authentication state, then checks the generated DNS requirements. Changing the website's A record would address a different dependency.

Test other important workflows separately if they use different services. An external marketing application or support desk may not use Shopify's notification route at all.

Keep the store ready for the next change

Retain the store reference, sender domain, DNS owner, managed or manual path, required record set and message evidence. Record who checks authentication after a domain transfer, store migration or new sender address.

A successful authentication test supports identity verification. It does not guarantee inbox placement, customer engagement or protection against messages sent from a lookalike domain. Those outcomes need separate controls and evidence.

Use the sender inventory to keep Shopify alongside other authorised services. The setup is complete when the store uses the intended identity and the team can demonstrate and maintain it.

Finish the workflow and read the status

Use the current Shopify authentication workflow, then return to the same sender-email status:

  1. Open Settings > Notifications > Sender email > Email domain authentication.
  2. For a supported automatic connection, complete the provider's approval flow and use its return button to come back to Shopify. Closing the provider window early can leave the check unstarted; use Manual setup and I updated DNS records to start it.
  3. For manual setup, publish every displayed CNAME in the correct DNS zone and trigger the check. Verify third-party DMARC separately; automatic CNAME setup does not create it.
  4. Compare the result with the intended sender identity and a controlled received notification, not just a green website-domain status.

Shopify allows up to 48 hours for DNS changes. Its update workflow distinguishes these maintenance states:

StateNext action
AuthenticatedNo authentication update is required; retain the records.
Update recommendedThe domain remains authenticated. The update is optional with no deadline; add or correct the indicated CNAMEs without deleting required existing ones.
Propagating after an updateAllow time and compare DNS with the displayed values. If records are not found after about a day, the state can return to Update recommended; recheck values and use I updated DNS records.

For Shopify-managed records that remain Update recommended, contact Shopify Support through the supported path. Do not repeatedly replace unrelated website records while waiting for the email check.

[ By role ]

What this means for you

Choose your role for practical next steps.

IT / Mail Admin

Reconcile the store state with public DNS.

Managed records, generated updates and separate applications need their own evidence.

Next steps

  1. Identify the actual authoritative DNS owner.
  2. Retain required CNAMEs during supported updates.
  3. Record From, signing identity and trusted results.

CISO / SecOps

Keep the control boundary clear.

Identity authentication supports a legitimate sending route; it does not eliminate lookalike abuse or all delivery risk.

Next steps

  1. Include external store applications in inventory.
  2. Control automated DNS-change permissions.
  3. Retain scoped configuration and test evidence.

Founder / Non-technical

Protect the customer recognition moment.

Order confirmations should use the expected identity, and somebody should be able to show why they do.

Next steps

  1. Confirm the configured sender domain.
  2. Review a controlled received notification.
  3. Assign ownership after store or domain changes.

[ FAQs ]

Frequently asked questions

Does a working Shopify storefront prove email authentication works?

No. Check the sender identity, active DNS configuration and a received customer notification. Website availability is a different dependency.

Do all Shopify domains require manual DNS setup?

No. Check the management path and authentication state. Shopify documents managed and supported automatic paths as well as manual configuration. Automatic third-party authentication does not create DMARC; check it separately.

Should I add a Shopify IP address to root SPF?

Follow the records generated for the current store configuration. Do not substitute a guessed IP or historical recipe for the displayed authentication requirements.

What does Update recommended mean?

Compare the current required CNAMEs with DNS. Shopify describes a maintenance state that can exist while mail continues to send; it does not establish a complete sending outage.

Can I delete the earlier CNAMEs when new ones appear?

Retain existing required records and follow the applicable update instructions. Deleting an active dependency without checking its role can interrupt verification.

Why is my customer notification using a different From address?

Inspect the actual message and the store sender-authentication status. A rewritten identity calls for that investigation, rather than an unrelated website DNS change.

Does Reply-To determine DMARC alignment?

No. DMARC uses the visible From domain and the relevant authenticated SPF or DKIM identity. Reply-To serves a separate reply-routing purpose.

Does Shopify authentication also cover an outside marketing tool?

Establish the actual sending route for each workflow. A separate application may need its own account, domain authentication and received-message verification.

[ Sources ]

Sources

  1. Shopify: sender email setup and authentication
  2. RFC 9989: DMARC core protocol
  3. RFC 6376: DomainKeys Identified Mail
  4. RFC 1034: DNS concepts and facilities

[ Glossary ]

Glossary

DMARC
Domain-based Message Authentication, Reporting, and Conformance connects aligned authentication with domain-owner policy and feedback. It does not certify message content or guarantee delivery.
DMARC alignment
The required relationship between the visible From domain and a passing SPF or DKIM identity. Strict alignment requires an exact domain match; relaxed alignment uses the applicable organisational-domain relationship.
Authoritative DNS
The delegated servers responsible for the relevant public zone. An edit in a different provider's inactive panel does not change their answers.
DKIM
DomainKeys Identified Mail associates a verifiable signature over covered message content with a signing domain. Signature verification and DMARC alignment are separate tests.
DKIM selector
The s= value in a DKIM-Signature. Together with that signature's d= domain, it locates verification material under _domainkey.

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

Knowledge Base