Good, with 4 things to fix

myshopify.com scored 80/100 (grade B). The main issues are no DKIM key found for the common selectors and MX: mail relies on implicit A record, plus 4 more.

Checked 2026-10-04 02:08 UTC · fresh check

2 passed4 need attention0 failing2 for information

Diagnosis notes

Warning: DNS lookup budget exhausted
This diagnosis stopped sending DNS queries after 150 queries. Checks that needed more lookups report their remaining results as unknown; the domain's records may be unusually large or slow to answer.

All checks

MXCan servers find your inbox?Mail relies on implicit A recordNeeds attention

Warning: Mail relies on implicit A record
myshopify.com has no MX records, so senders fall back to its A/AAAA address (RFC 5321 implicit MX). Publish an explicit MX record, or a null MX ("0 .") if the domain should not receive mail.

SPFWho may send as you?No issues foundPass

Nothing to report.

DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention

Warning: No DKIM key found for the common selectors
None of the 47 selectors probed under myshopify.com publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for myshopify.com.
Warning: Some DKIM lookups failed
17 of 47 selector lookups under myshopify.com returned TIMEOUT, so whether those selectors hold a key is unknown. Try again later; if it persists, check the domain's nameservers.

DMARCWhat happens to fakes?No issues foundPass

Nothing to report.

AlignmentDoes it match your From?SPF alignment is unknownInfo

Info: SPF alignment is unknown
The SPF record of myshopify.com authorizes no sender (no +ip4, +ip6, +a, +mx, +exists or +ptr term, include of a record that has one, or +all before all), so SPF never passes and cannot align. That is correct for a domain that sends no mail; otherwise DMARC depends on DKIM alone.

BIMICan inboxes show your logo?Could not look up the BIMI recordNeeds attention

Warning: Could not look up the BIMI record
The TXT query for default._bimi.myshopify.com returned TIMEOUT, so BIMI status is unknown. Try again later.

MTA-STSIs mail to you encrypted?Could not look up the MTA-STS recordNeeds attention

Warning: Could not look up the MTA-STS record
The TXT query for _mta-sts.myshopify.com returned TIMEOUT, so MTA-STS status is unknown. Try again later.

TLS-RPTWill you hear about failures?No TLS-RPT recordInfo

Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.myshopify.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this

How to fix it

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to myshopify.com, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.

Applies to: _smtp._tls.myshopify.com

Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@myshopify.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.myshopify.com with the value v=TLSRPTv1; rua=mailto:<that address>.