Store Email Deliverability Checker
Check your store's SPF, DKIM, DMARC and MX records against Gmail and Yahoo's sender rules, and get corrected records to copy.
Open an email you sent, view the original, and copy the s= value from the DKIM-Signature line.
Gmail's bulk-sender rules start at 5,000 messages a day to Gmail accounts.
What Gmail and Yahoo check before the inbox
Both providers publish their sender rules. The DNS parts are what this tool checks:
| Requirement | All senders | 5,000+ a day to Gmail |
|---|---|---|
| SPF | SPF or DKIM | Required |
| DKIM | SPF or DKIM | Required |
| DMARC | Recommended | Required (p=none is enough) |
| From alignment | From domain must align with SPF or DKIM | |
| Spam rate | Under 0.3% | Under 0.3% |
| One-click unsubscribe | Required for marketing email |
Pick your volume in the tool: under 5,000 a day, a missing DMARC record is a gap. Over it, it's a failure. Spam rate, unsubscribe headers and alignment happen in your email platform, not DNS, so check those there.
How the checks work
- SPF. The tool finds every
v=spf1record (there must be only one), then follows each include and counts the terms that trigger DNS lookups:include,a,mx,ptr,existsandredirect. RFC 7208 caps that at 10. Over 10, SPF fails for every email. - DKIM. A DKIM key lives at
selector._domainkey.yourdomain, and the selector can't be listed from DNS. The tool tries 30 common ones (googlefor Google Workspace,selector1andselector2for Microsoft 365,k2andk3for Mailchimp,s1ands2for SendGrid, Klaviyo'skm1and others). If none match, DKIM isn't confirmed either way: enter your selector. - DMARC. It reads
_dmarc.yourdomainand checks for one valid record, the policy, a report address (rua) and strict alignment. - MX. It checks that replies can reach you, and spots Google Workspace or Microsoft 365 so it can tell whether SPF includes them.
Example: two SPF records
- Record 1
- v=spf1 include:_spf.google.com ~all
- Record 2
- v=spf1 include:sendgrid.net -all
Two records make SPF fail with a permanent error. The tool merges them into v=spf1 include:_spf.google.com include:sendgrid.net -all and shows its lookup count.
Fixing the records
- 01
Find your DKIM selector
Open an email you sent in Gmail, choose Show original, and find
s=in theDKIM-Signatureline. Enter it in the tool to confirm the key. - 02
Replace SPF with the corrected record
Delete every existing
v=spf1TXT record on the root domain and add the one record the tool gives you. - 03
Add or fix DMARC
Add a TXT record named
_dmarcwith the starter record. Leave it atp=nonewhile reports come in, then step up to quarantine and reject. - 04
Set up your platform's records
Shopify, Klaviyo and most email platforms authenticate with CNAME records they generate for you. Add those exactly as shown in the platform. For Shopify, use the Shopify email authentication checker.
On WooCommerce, order emails go out through your host's mail server unless you use an SMTP or email-sending plugin. Point it at a provider you've authenticated, or order emails may fail SPF and DKIM even with correct records.
Questions people ask
Why are my store's emails going to spam?
Missing or broken authentication is the most common fixable cause: no DMARC, two SPF records, SPF over 10 lookups, or no DKIM. After that, content, list quality and your spam rate matter.
Why can't the tool find my DKIM record?
DKIM keys sit under a selector name that DNS can't list. If your provider uses an account-specific selector, find s= in a sent email's DKIM-Signature header and enter it.
Should my SPF end in ~all or -all?
Either works with DMARC. Google's example uses ~all, and Microsoft recommends -all once DKIM and DMARC are set up. Avoid ?all and never use +all.
What counts as a bulk sender?
Gmail applies its bulk rules to anyone sending 5,000 or more messages a day to Gmail accounts. A store sending one campaign to a large list can cross that.
Does it work for WooCommerce, Klaviyo and Shopify?
Yes. It checks your domain's DNS, whichever platform sends the email.
Related tools
Last reviewed 30 September 2026.
Sources: Google: Email sender guidelines · Yahoo Sender Hub: Sender best practices · RFC 7208: SPF (DNS lookup limits) · RFC 9989: DMARC · Google Workspace: Set up SPF · Google Workspace: Set up DKIM · Google Workspace: Set up DMARC · Microsoft: Set up SPF for Microsoft 365 · Microsoft: DKIM for custom domains · Mailchimp: Email domain authentication · Mailchimp Transactional: Authentication and delivery · SendGrid: Domain authentication · Klaviyo: Troubleshooting branded sending domains
