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.

Describe the result you need. AI will set up the tool and ask for any missing details.

Configure with AI

Enter to submit · Shift + Enter for a new line

Sent to AI. Leave out passwords and private customer data.

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:

RequirementAll senders5,000+ a day to Gmail
SPFSPF or DKIMRequired
DKIMSPF or DKIMRequired
DMARCRecommendedRequired (p=none is enough)
From alignmentFrom domain must align with SPF or DKIM
Spam rateUnder 0.3%Under 0.3%
One-click unsubscribeRequired 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=spf1 record (there must be only one), then follows each include and counts the terms that trigger DNS lookups: include, a, mx, ptr, exists and redirect. 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 (google for Google Workspace, selector1 and selector2 for Microsoft 365, k2 and k3 for Mailchimp, s1 and s2 for SendGrid, Klaviyo's km1 and others). If none match, DKIM isn't confirmed either way: enter your selector.
  • DMARC. It reads _dmarc.yourdomain and 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

  1. 01

    Find your DKIM selector

    Open an email you sent in Gmail, choose Show original, and find s= in the DKIM-Signature line. Enter it in the tool to confirm the key.

  2. 02

    Replace SPF with the corrected record

    Delete every existing v=spf1 TXT record on the root domain and add the one record the tool gives you.

  3. 03

    Add or fix DMARC

    Add a TXT record named _dmarc with the starter record. Leave it at p=none while reports come in, then step up to quarantine and reject.

  4. 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.

Want this builtinto your store?

I'm Emmanuel, a Shopify and WooCommerce developer. If this tool pointed at something you'd rather have fixed for you (a faster store, cleaner product data, a migration, a custom feature), send me a note.

Emmanuel Asika

Emmanuel Asika

Shopify & WooCommerce developer, Dublin

I build and fix online stores: new builds, migrations, speed, SEO and the custom bits apps can't do.

hello@emmanuelasika.com