Skip to main content

Email protection for your Shopify store.

Your customer has your brand in the From line, your logo and your order-number format. Nothing in the message tells them which one to trust.

Illustrative Recon Email interface with fictional Northfell data

Two order confirmations, two minutes apart

Both landed in the same inbox. The only difference is in headers the customer will never open.

Inbox · 09:14 Authenticated

Your order #1042 is confirmed

Yourbrand <orders@yourbrand.com>

SPF
Pass
DKIM
Pass
DMARC
Aligned
Inbox · 09:16 Spoofed · delivered anyway

Your order #1043 needs payment

Yourbrand <orders@yourbrand.com>

SPF
Fail
DKIM
None
DMARC
No policy to enforce

Both were delivered. The second one only fails checks nobody is enforcing.

Publishing DMARC is what turns those failures into a rejection.

Illustrative example · synthetic data · demonstration domains are fictional

The five records that decide it

SPF
Which services may send as you. Shopify, Klaviyo, support tools and workspace mail all have to be listed, and the record has to stay inside its lookup limit.
Pass
DKIM
A signature on each message proving it was not altered in transit, checked per sending service.
Pass
DMARC
The policy telling a mailbox what to do when the first two fail. Without it both results are advisory, and a spoof is delivered like the real thing.
Not published
MX
Where your mail actually routes, so replies and support requests reach the service you expect.
Pass
MTA-STS
Requires receiving mail servers to use an encrypted connection. Optional, and worth having.
Advisory

Why email settings matter to your brand

Customers recognize emails from your store about orders, deliveries and support. Someone using your exact domain in the From field can borrow that trust. Email authentication gives receiving providers a way to check which systems are allowed to send and what to do when a message fails those checks.

These settings also matter for the messages you really send. Shopify notifications, marketing campaigns and support replies may come from different services. A working setup needs to account for those senders. Authentication helps providers evaluate your email, but it does not guarantee that every message lands in the inbox.

SPF, DKIM and DMARC work together

SPF lists authorized sending systems for an email’s envelope domain. DKIM adds a signature that receiving providers can verify using a public DNS key. DMARC checks whether a passing SPF or DKIM result aligns with the domain a customer sees in the From field, then publishes your requested policy for failures.

A record can exist without providing the protection you expect. For example, a DMARC policy of p=none collects reports without asking providers to quarantine or reject failed messages. Conversely, enforcing a strict policy before all legitimate services are aligned can disrupt customer mail. Recon shows the public settings so you can identify what needs review.

What Recon checks in the background

Recon reads public email records for the domain you monitor. It checks SPF, discoverable DKIM records, the published DMARC policy, mail-routing records and related transport settings. Findings appear in your Shopify admin with the record or setting that needs attention.

These are public DNS checks. Recon does not read your customer emails, open your private provider dashboard or know every service your business intends to use. Finding a DKIM key is not the same as proving every message is signed. Use delivered-message headers and your provider’s verification screen to confirm a change actually works.

Fix the record at your DNS provider

When a public record is missing or needs review, Recon explains the issue and can prepare a record to add at your domain host. Review it against the sender’s own instructions before publishing. Record values, hostnames and types can differ by account. Keep a copy of the earlier configuration so your team can investigate unexpected results.

First inventory your senders. Then publish the appropriate records, wait for DNS caches to update, and send test messages from each service. Check the authentication results in the delivered emails. Start DMARC in monitoring mode while you identify legitimate traffic, and tighten policy only when those senders are aligned.

Keep checking as your tools change

Your email setup changes when you add a marketing platform, switch support tools or connect a new fulfillment service. A healthy result today does not tell you whether a service added next month is authenticated. Recon keeps checking the public records on your plan’s schedule so you can see what needs attention.

Free runs weekly scans and puts new findings in the weekly summary. Paid runs daily sweeps with broader monitoring. The app keeps the findings beside your other brand protection checks, so your team can review email settings, copied stores and domain health from the same Shopify admin.

Questions before you install

Does Recon change my DNS records for me?

No. Recon explains public findings and prepares relevant records. You or the person who manages your domain reviews and publishes them at the DNS provider.

Will DMARC stop every fake email?

No. DMARC addresses messages impersonating your exact domain when receiving providers apply the policy. It does not stop a lookalike domain, a compromised mailbox or every kind of phishing.

Can I use these checks with a myshopify.com address?

Shopify owns the myshopify.com domain and its DNS records. Connect a domain you control to review and change your own email authentication settings.

Recon keeps watch. You run your store.