A brand domain can load while customer notifications land in spam. Keep the verified website result, but leave the sending work pending. Different systems handle domain access and email: this lesson checks domain control, DNS, the primary domain, redirects, and TLS first, then mailbox hosting, Shopify's sending identity, and the route customer replies take.
9 parts · 3 checkpoints
Show all 9 parts
- 01Separate registration, DNS, the primary domain, and TLS
- 02Establish control and keep the starting configuration
- 03Connect, verify, and set up email in order
- 04Keep sending, mailbox, and recovery identities distinct
- 05Read SPF, DKIM, and DMARC results carefully
- 06Follow a failed result back to the responsible system
- 07Practise a partial result: website works, sending is pending, has a checkpoint
- 08Keep a domain and email handover record, has a checkpoint
- 09Work it out: which sender is least trustworthy
Key point Verify website access and email separately
Connected, a visible sender address, and one received message each establish only part of the result. Keep evidence for the primary domain and redirects, HTTPS, mailbox send/receive, sending authentication, renewal, and recovery. A tutorial checkbox does not connect a domain, edit DNS, or authenticate an email address.
The main admin paths are Settings > Domains and Settings > Notifications. Use this lesson when connecting a brand domain or taking over domain and email work from staff or an agency. Identify the current store, page title, and complete settings section before inspecting fields, save responses, and actual test results. If an entry is missing, check permissions, plan, and the current interface before editing a similarly named page.
Questions this lesson answers
- After Connected appears, how do you verify DNS, TLS, and redirects?
- How should Primary domain, www, and myshopify.com work together?
- How does email forwarding differ from full mailbox hosting?
- Why inspect From, Reply-To, receiving, and sending separately?
- What do SPF, DKIM, and DMARC each do?
- Can a working website pass while messages land in spam?
- Who controls registrar, DNS, and mailbox billing when someone leaves?
- What redacted results and recovery records should you keep before launch?
Separate registration, DNS, the primary domain, and TLS
Buying a domain establishes its registration and renewal arrangements; DNS determines where its names point. The registrar and the service hosting its active DNS can be different companies. A domain appearing in a registrar account does not establish that this account controls the records currently being published. Identify the active nameservers, DNS manager, and authorized custodian first.
The apex, or bare domain, is example.com; www.example.com is a subdomain. A and AAAA records point names to IPv4 and IPv6 addresses. A CNAME points one name to another. These website records have a different job from the MX records used for incoming mail and the TXT or CNAME records used for email authentication. A website change should not erase working mail records.
Primary domain is the address customers ultimately see; redirects send other entry points to their intended destination. Shopify initially uses the generated myshopify.com domain. After connecting a brand domain, you can make it primary. A redirect domain sends visitors to the primary domain; an alias keeps its own address in the browser. A simple single-market store normally chooses either apex or www as its public primary domain, then verifies the other entry and myshopify.com. Existing Markets domains and aliases need checks against their intended targets rather than a blanket rule that every domain must show the same address.
TLS provides the secure connection used by HTTPS. It encrypts the connection between browser and store; it does not establish domain custody, correct redirects, or email authentication. Shopify supplies automatic TLS for added domains, but certificate issuance after connecting a third-party domain can take time. A homepage loading is only the start: inspect the address bar, certificate warnings, and other pages too.
The series example is a desk-organization store planning a United States launch, USD, and an English storefront. Here, example.com and [email protected] stand for a domain and support address. They are examples, not configuration values. The business entity, payment eligibility, market, and completion of earlier lessons still require the store's own checks.
Suppose the team bought its domain from registrar A, hosts DNS with service B, plans to connect the website to Shopify, and uses service C for email. Saving records in A's old DNS screen might have no effect on active DNS. Deleting B's zone could stop C's mail. Map these responsibilities before deciding which record needs a change.
Establish control and keep the starting configuration
Prepare a brand domain under long-term business control. Check registrar and DNS access, 2FA, renewal payment, and recovery methods. Give the daily custodian and an authorized backup appropriate ways to restore management, using individual access rather than a shared password. This does not create two legal registrants. An agency can configure the service, but account control and handover should survive a particular contact leaving.
Assign responsibility for the domain, mailbox hosting, and sending tools separately. Arrange durable addresses and handlers for owner, support, and finance functions. These roles do not each require a separately purchased mailbox. Record customer-service addresses separately from the owner's login and recovery identity. After changing a support address, check the Shopify owner's login email and recovery methods separately. Also check whether a domain-mail outage would disable the only route to recover the services needed to repair it.
Export or retain a controlled backup of the existing DNS zone before connecting. Record each relevant name, type, value, TTL, purpose, change time, and owner. Include the old primary domain, mail routing, approved changes, and recovery contact. Actual DNS values belong in your controlled documents. Public captures and tutorial notes should contain redacted summaries, excluding real domains, addresses, DNS verification values, account IDs, and recovery codes.
Give the four domain and email decisions an owner and a check
Primary domain
- Decision and actual value
- Choose the brand primary domain and list intended destinations for apex, www, myshopify.com, and existing markets.
- Reason and verification
- Public links and canonical URLs should follow that domain strategy. Explain separate market or alias uses rather than leaving accidental duplicates.
Mailbox hosting
- Decision and actual value
- Choose a third-party host and assign support receiving, sending, and billing responsibility.
- Reason and verification
- Shopify does not provide full mailbox hosting. A forwarding address receiving a message does not establish that the team can reply from it.
Sender email
- Decision and actual value
- Use a monitored support address that customers can reply to, and record From and Reply-To separately.
- Reason and verification
- Both notifications and customer replies need a traceable support process. Changing a display name does not create that process.
DNS custody
- Decision and actual value
- Name the daily custodian, authorized recovery backup, and renewal, change, and handover responsibilities.
- Reason and verification
- Avoid single-person or agency lock-in. Verify the available recovery methods and set a review date.
Check each row against your actual store values. Mark a row passed only when the value fits the intended setup and has a saved or tested result. Missing access, results, or ownership sends you back to the relevant step. Planned values and example addresses are not completion evidence.

Historical development-store example: Settings → Domains shows Connect existing, Buy new domain, and the default domain. It does not show a connected brand domain, DNS records, or mail authentication and cannot establish that your settings passed.
Connect, verify, and set up email in order
An authorized custodian can follow these steps in the intended store. Identify the store and complete target section each time, refresh after saving, and test what a shopper or recipient actually sees. Domain purchases, DNS edits, and mail-service activation are business actions that need the agreed owner and change arrangements. The tutorial controls do not perform them.
Connect or purchase the domain
Where in the UI: SettingsDomains
For an existing domain, choose
Connect existing domain, enter the apex domain, and continue. If you have not purchased one, settle business control and renewal arrangements before consideringBuy new domain. Apply the records shown by the current Shopify connection flow at the service publishing active DNS. Compare type, name, and target individually. Resolve only the conflicting A, AAAA, or www CNAME records involved in the connection, retaining other business and mail records. Do not change nameservers just to find a DNS screen. If another service already hosts DNS, establish that it is publishing the required records there.You should see
Have the domain source, connection save response, DNS-change summary, original-record backup, and recoverable account ownership.How to confirm
Reopen this domain's details. Confirm that the connection targets this store and matches Shopify's instructions. Seeing the purchase or connection button is not completion.If it goes wrong
If connection fails, check the store, domain, active DNS provider, required fields, and save response. Ask the authorized custodian to resolve access rather than deleting the entire zone and guessing.Keep as evidence
Keep registrar, DNS provider, backup location, change time, non-sensitive record summary, and owner.Wait for and verify connection and TLS
Where in the UI: SettingsDomainscurrent domain
Return to Domains for connection details and TLS state. Shopify allows up to 48 hours for third-party connection, DNS propagation, and certificate issuance. This is a troubleshooting window, not a promise that every region changes at the same moment. Use a private window to visit apex, www, and the original
myshopify.comentry. Inspect HTTP-to-HTTPS behavior, final address, page response, and certificate warnings. A private window reduces some browser-state effects but does not remove every DNS cache.
This historical example is still the default-domain list, with no DNS details or independent TLS result. Use it to identify Domains; keep your connection details, certificate, and apex, www, and myshopify.com tests separately.
You should see
Have actual responses for each entry, connection and TLS states, and timed propagation observations.How to confirm
Recheck HTTPS and pages on target devices and, where appropriate, another network. Match the Connected admin state with actual access results; do not describe it as proof of completed global propagation.If it goes wrong
If still disconnected, compare records, TTL, same-name conflicts, and change time, then wait and recheck instead of repeatedly switching values. If Connected but access fails, investigate DNS, TLS, and redirects separately. Beyond the documented window, use Shopify's current DNS, CAA, and DNSSEC troubleshooting with the custodian or support team. Do not bypass certificate warnings or arbitrarily delete security records.Keep as evidence
Record entry URL, HTTP/HTTPS response, final address, TLS state, device or network, time, and owner.Set Primary domain and test redirects
Where in the UI: SettingsDomainscurrent domainType
Once the brand domain is connected, open it and use
Type > Changeto selectPrimary domain, then save withChange domain type. In an ordinary primary-domain change, the previous primary becomes a redirect domain. Record the starting setup and intended destinations first. Test apex, www, myshopify.com, and a valid old link containing a path and query parameters; the homepage alone is insufficient.A domain assigned to Markets may show
Market domain forandView market settings, requiring a review of market assignment first. Aliases have a separate purpose too. With international domains, verify each market's URL and language strategy and the effect on market subfolders before forcing domains to a single address.
The historical Primary label belongs to the default myshopify.com domain. No change-domain-type dialog is shown. This is not Notifications and does not establish a configured brand primary domain or working redirects.
You should see
Have the primary-domain setting, final destinations, and path/parameter results. Public links and canonical URLs should fit the same documented domain strategy.How to confirm
Use a real product or page link and confirm that old links are not all sent to the homepage. An invalid original link and a redirect losing its path are different failures; record them separately.If it goes wrong
If paths or parameters disappear, inspect domain type, redirect settings, and theme or app rewrites. For recovery, use the starting record to make the still-connected original domain primary again, then retest every entry and market path. Do not troubleshoot by deleting the domain.Keep as evidence
Keep old and new primary domains, types, three entry results, a path/parameter test, canonical or public-link observations, time, and owner.Establish a business mailbox that can send and receive
Where in the UI: Selected email hostdomain and mailbox settings
Verify the domain with the chosen email host, create support and other needed role addresses, and follow its inbound and outbound setup. MX records route incoming messages to the host. Verify domain-verification TXT records, sending authentication, and SMTP or webmail setup as separate requirements. For a Shopify-managed domain, use the applicable hosting entry in its Domains details. With third-party DNS, follow the email host's instructions at the active DNS service.
You should see
The support mailbox has a host and handler, receives external messages, and can send replies from the formal mail tool.How to confirm
Send from an independent test inbox to support, then reply from support and inspect the actual sending address. Adding MX can affect existing Shopify forwarding. Confirm its destination and a replacement arrangement before switching, then observe behavior during propagation.If it goes wrong
If mail receives but cannot send, check whether it is forwarding-only, then inspect outbound settings, SMTP, or webmail with the email host. For failed receipt, check account activation, MX, and the host's requirements. Contact the mail host if problems continue beyond its propagation window; the website's Connected label cannot establish working mail.Keep as evidence
Record mailbox role, host, receiving/sending/reply tests, effects on old forwarding, billing owner, and recovery custodian using redacted summaries.Set Shopify sender email and test the customer reply
Where in the UI: SettingsNotificationsSender email
Save a Sender email that customers can reply to and the team monitors. Avoid an unattended no-reply address. Send a test notification and inspect the received message's original details for From, Reply-To, placement, and reply destination. Ask the assigned support handler to confirm receipt of the reply. The visible notification identity should agree with actual delivery and reply behavior.

Historical English development-store example: Settings → Notifications → Sender email. It shows a public-email and shopifyemail.com rewrite notice plus notification entries, not passed SPF, DKIM, DMARC, or renewal records.
You should see
Shopify notifications use the intended customer-facing identity, the test arrives, and a named handler receives customer replies.How to confirm
Record notification type, receiving provider, time, From, Reply-To, and inbox or spam placement. Complete a reply test too. Neither a display name nor a template preview establishes working mail.If it goes wrong
For an unexpected From or missing delivery, check the saved sender, recipient, and mailbox hosting before authentication and bounce information. A display-name change cannot repair authentication. A shopifyemail.com rewrite calls for checking the public-domain or authentication notice. Test the reply route of each relevant notification later in the notifications lesson.Keep as evidence
Keep notification type, redacted From/Reply-To, receiving provider, placement, reply handler, test time, and result.Check authentication, renewal, and handover
Where in the UI: SettingsNotificationsSender emailEmail domain authentication
Identify whether the domain was purchased or is managed through Shopify or is a third-party domain, then inspect the relevant authentication flow. Third-party setup may offer automatic or manual methods. Before a change, have the DNS custodian compare every name, type, and target. Shopify's sending CNAME records and the mailbox host's records serve different purposes; do not overwrite one with the other.
You should see
Have Shopify and mail-host authentication states, send/receive results, domain expiry, registrar renewal, mailbox billing, and DNS-change ownership.How to confirm
Compare each record with current admin instructions, allow propagation, and read back the authentication result. Record when Authenticated appears and what remains pending. A DNS screenshot or a single message cannot establish every result.If it goes wrong
For pending DKIM, check duplicated domain suffixes in record names, the active DNS manager, target values, TTL, and change time. Keep authentication CNAMEs that remain required. If the website works but authentication is pending/failed or messages land in spam, retain the website result and keep sending pending.Keep as evidence
Keep authentication state, redacted record-type/name summaries, the controlled location of original values, test and review times, payment and daily/backup custodians, and expiry or departure handover arrangements.
Keep sending, mailbox, and recovery identities distinct
Mailbox hosting lets the team receive, send, and reply using a brand address. Forwarding passes incoming mail to another existing inbox. Shopify's domain forwarding alone does not provide full hosting or manual replies from the brand address. A forwarding address on a Shopify-managed domain can be used as the store sender, with customer replies forwarded to the selected inbox. That does not give the team a branded address for manually replying. The classroom setup uses a hosted support mailbox so both directions of customer communication have a clear tool and handler.
Sender email is the customer-facing address in Settings > Notifications. From is the sending identity shown to a recipient; Reply-To specifies the destination when they reply. Receiving a notification does not establish that its reply reaches support. A working support inbox also does not establish that Shopify is authorized to send notifications for its domain. Test notification receipt, the customer's reply, and support's outbound mail separately.
Store email in Settings > General handles store contact and some exports. The owner's login email and recovery methods belong to account settings. They are separate from the Notifications sender. Before changing a domain or email host, check owner recovery, support coverage, billing, and retention of the old mailbox. Resolve a recovery design that depends entirely on the same failing domain before relying on it.
Read SPF, DKIM, and DMARC results carefully
SPF identifies systems authorized to use the relevant mail-sending domain. DKIM uses a domain signature to help a recipient verify a message. DMARC aligns the visible From domain with an identity that passes SPF or DKIM and publishes a handling policy. These checks reduce impersonation and authentication problems; they do not guarantee inbox placement. Content, domain reputation, list quality, and the receiving service's decisions still matter.
Domains purchased through Shopify get DKIM, SPF, and DMARC automatically. For third-party domains, automatic authentication handles DKIM/SPF CNAMEs while DMARC needs a separate check. Manual setup likewise needs every CNAME currently shown and the required DMARC record. Shopify's authentication CNAMEs already handle its sender SPF, so do not add a separate SPF TXT for that purpose. Follow the mailbox host's own sending requirements separately.
The third-party sending-CNAME flow requires an active paid plan; dev stores, client transfer stores, and Pause and Build are excluded. Historical dev-store images do not establish availability. Begin with Email domain authentication in Notifications. Return to Shopify after an available automatic flow, or confirm the DNS update in the manual flow. Allow up to 48 hours for propagation.
Do not label Update recommended an authentication failure: current guidance says the domain remains authenticated and sending can continue while the recommended records are reviewed. Actual pending/failed states remain unresolved. Read your complete current status and instructions, as labels and buttons can change.
The SPF duplication check concerns policies selectable for the same name, not a ban on other TXT records. More than one selectable v=spf1 record causes permerror. Have the mail custodian consolidate requirements from all actual sending services rather than adding another policy. Avoid duplicate DMARC policies at the same name too. Review an existing policy with its owner instead of overwriting stricter settings to obtain a passing screenshot.
Follow a failed result back to the responsible system
Retain verified results and assign each failure to the custodian of the system involved. The table gives the checks and follow-up for each problem. One save confirmation cannot establish all of these results.
| Symptom | Check first | Action and result to retain |
|---|---|---|
| Domain remains disconnected | Current store, active DNS service, A/AAAA/www CNAME, TTL, conflicts, and change time | Compare current Shopify instructions, wait, and recheck. Record the error and owner rather than repeatedly changing values back. |
| Connected but access fails or the certificate warns | DNS resolution, HTTPS, TLS, page response, and redirects separately | Investigate each result. Beyond the official window, follow current TLS troubleshooting and retain timed observations. |
| Old links lose their path or parameters | Domain type, market target, redirects, and theme/app rewrites | Reproduce with a valid old link. Restore the known configuration from the record and retest; do not send everything to the homepage. |
| Support receives but cannot send | Forwarding versus hosting, mailbox activation, SMTP, or webmail | Return to the email host. Test receiving, sending, and replies individually, keeping results and handler. |
| Notifications enter spam or DKIM stays pending | Sender, From domain, authentication records, content, propagation, and receiving provider | Test with services such as Gmail and Outlook and inspect bounces and original message details. Keep the website result while sending remains pending. |
| One person or an agency controls the account | Registrar, DNS, mailbox host, billing, 2FA, and recovery access | Pause launch and restore business control and authorized backup access. Record handover, renewal, and the next review. |
If a change breaks service, use the backup to restore only the affected records with the DNS and mail custodians, then retest both website and mail. Restoring DNS or a primary domain does not instantly clear every cache or recall messages already sent. Retain available old services, an alternative support route, and a recheck plan during a transition. Do not wipe the zone, treat forwarding as hosting, or publish unredacted records.
Practise a partial result: website works, sending is pending
Return to the classroom store. Its primary domain loads, but the support test lands in spam and DKIM is pending. The website observation can be retained; sending still needs work. Choose before reading each explanation. This practice does not run DNS or mail tests.
Decide whether both paths are complete
Self-check not answered
Even with all three checked, confirm test-notification From and Reply-To, required sending authentication, and responsibility for the domain, DNS, mailbox, and renewal. Leave unsupported items pending with an owner and review time.
Actual conditions for continuing
| Done when | Stop if |
|---|---|
The primary domain and planned redirects are stable, registrar/DNS are controlled, TLS is healthy, support sends, receives, and handles replies, the Shopify sending domain passes required authentication, and renewal, billing, and recovery are transferable. | Connection is incomplete, TLS is unhealthy, DKIM or other required authentication is pending/failed, mail only receives, or domain/mail control depends on a non-transferable third-party account or lacks a recovery owner. |
| Evidence Current domain and authentication states, three entry and path/parameter tests, notification From/Reply-To and send/receive/reply results, DNS backup location, and redacted renewal/recovery responsibilities. | |
Keep a domain and email handover record
Keep registrar, renewal owner, expiry, active DNS service and backup, primary domain, domain types, redirects, TLS, mailbox host, support send/receive, Shopify sender, authentication state, test times, blockers, owners, and evidence locations in your asset record. Write separate conclusions for website access and sending. Mark untested items unverified rather than copying a pass from the example.
The form saves automatically in this browser and reuses the decision and checks above. Enter redacted summaries, roles, and locations of controlled evidence. Keep longer working records separately, and export or copy before changing devices. Resetting this lesson record does not undo Shopify, DNS, or email settings.
What this record establishes
Hold
Make the scenario decision
Correct the pass decision
Some checks remain
Decision and checks recorded
Once both paths and their responsibilities are clear, build the first product across price, variants, inventory, weight, and channels. Return to real notifications and test orders before launch to recheck domain, email, and recovery arrangements.
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
FAQ
- Is domain setup complete when it says Connected?
Match current DNS with actual access and check TLS, apex, www, myshopify.com, the primary domain, and a valid old URL's path and parameters. Connected does not establish updated caches everywhere or authenticated, delivered email.
- Can Shopify forwarding replace mailbox hosting?
No. Forwarding mainly sends incoming mail to an existing inbox. A Shopify-managed domain's forwarding address can be the notification sender, but manual replies from the brand address still require third-party hosting. This lesson checks receiving, sending, and replies separately.
- Why check for duplicate SPF records?
Multiple policies selected for the same name produce permerror. Have the mail owner maintain a valid policy covering the actual sending services while retaining unrelated TXT records. Shopify authentication CNAMEs already handle its sender SPF; do not add another SPF TXT for that purpose.
- Does automatic Shopify authentication configure DMARC?
It depends on the domain. Shopify-purchased domains get DKIM, SPF, and DMARC automatically. Automatic third-party authentication handles the required DKIM/SPF CNAMEs while DMARC needs a separate check. This is not a reason to overwrite an existing policy or promise inbox placement.
- Does Shopify provide full business email hosting?
Shopify provides domain features and applicable email forwarding, not full hosting. Choose a third-party email service and verify domain setup, send/receive, and recovery responsibility. Paying for a domain does not establish that a complete mailbox service is active.
- Must both www and the apex be public versions?
A simple store can choose one as primary and redirect the other as planned, avoiding accidental duplicate versions. Existing aliases and international domains need checks against their target and market purpose before any blanket consolidation.
- Why can mail still enter spam after SPF and DKIM are configured?
They help verify authorized sending, but delivery also involves DMARC, content, domain reputation, list quality, and recipient-service decisions. Inspect original messages and bounces and test different services. Website access cannot substitute for mail results.
Continue with the gap you have now
Work it out: which sender is least trustworthy
Four setups (example data). Rule: customers only see the sender address and the authentication behind it — with either SPF or DKIM missing, the receiving side cannot fully verify that the mail came from your domain.
How much each setup can be trusted
| Item | Domain | Sender address | Authentication |
|---|---|---|---|
| Setup A | Connected | Free mailbox address | Not applicable |
| Setup B | Connected | Your own domain | SPF and DKIM both pass |
| Setup C | Connected | Your own domain | SPF missing, DKIM fine |
| Setup D | Not connected | Falls back to the platform address | Not applicable |
Decide before you read on. Say which sender is least trustworthy, and why A, on a free mailbox, is not the worst of the four.
Commit to an answer before reading the key below.Answer key: C is least trustworthy — it sends under your own domain with DKIM working but SPF missing, so the receiving side cannot fully confirm the mail came from you, which is the fastest route into spam or a straight rejection. D is a different case: with the domain unconnected the sender falls back to the platform address, so the mail still goes out but no longer looks like your brand — its problem is recognition, not trust. A uses a free mailbox and looks just as unbranded, yet that domain carries complete authentication, and complete authentication affects delivery more than a prettier domain does. C is the trap, because it looks the most configured while it lends your brand name to an unauthenticated message.