Missing SPF or DMARC records for store email
What each record does
SPF is a DNS TXT record that lists permitted mail senders for a domain. DMARC publishes a policy for messages claiming to be from that domain and depends on authenticated alignment. MX records tell other servers where mail for a domain is received. They serve different purposes.
A website loading successfully over HTTPS doesn't establish that support or order-confirmation email is configured. The domain appearing in the store's URL may also differ from the domain used to send receipts.
What the scan verifies
SnafuFinder looks up publicly available SPF, DMARC and MX records for the submitted store hostname and bounded parent candidates. It can report missing records, certain invalid configurations or weak policies, and distinguish inherited records on shared platform domains.
It cannot inspect a private SMTP account, know all legitimate third-party senders or verify actual receipt delivery. A shared myshopify.com, wixsite.com or squarespace.com DNS policy shouldn't be presented as proof of a merchant-owned sender setup.
How to correct a finding
Identify the domain used in the visible From address of your order and support messages. List every legitimate sending provider before editing SPF. Publish one SPF TXT record with the authorized senders and a policy suited to your setup. Publish a DMARC record and review its reports before moving to enforcement.
After making DNS edits, repeat the audit and send an independent end-to-end email test. Don't guess an SPF include value or replace existing records without checking the provider's current instructions.
Check your store
Start with a free preview: one per day, no signup. The full audit is CAD $29, one-time, no subscription. The report identifies verified findings and unverified checks separately.
Check my storeSee the homepage, the illustrative sample report, or the pre-launch checklist.