Customers Not Getting Your Invoices or Order Emails?

When receipts, invoices or password resets vanish, the cause is often a sending tool your domain hasn't authorised.

Check your domain first: it's free

Our checker reads your public SPF, DKIM, DMARC and MX records and explains each in plain English. Nothing is stored.

Quick test (5 minutes)

Run the free email check on your domain.
Trigger a real invoice, order confirmation or password reset to a personal Gmail address.
Open it in Gmail → three-dot menu → Show original, and look at SPF, DKIM and DMARC.

Why this happens

Your store, payment, accounting or app platform sends email "from" your domain, but your domain hasn't authorised it. Google notes that if third-party senders aren't included in your SPF record, their messages "are more likely to be marked as spam", and that DMARC needs the authenticating domain to match your From: domain.

Common senders and their official setup guides

Shopify: add Shopify's CNAME records to authenticate your sender email domain. Shopify Help: Setting up your email
Stripe (receipts and invoices from your domain): add the DNS records Stripe gives you, including DKIM CNAMEs. Stripe Docs: email domain
Supabase Auth (sign-up and reset emails): Supabase's default email server "is not meant for production use"; set up custom SMTP with a provider that authenticates your domain. Supabase Docs: Send emails with custom SMTP
Google Workspace / Microsoft 365 (your normal mailbox): turn on DKIM. Google · Microsoft

Other tools (accounting, helpdesk, CRM) usually have a "custom sending domain" or "domain authentication" page in their settings or help center.

Step by step

List every tool that sends email with your domain in the From: address.
In each one, turn on domain authentication and add its DKIM records at your DNS host.
Update your single SPF record if the tool asks for an include:, and keep it within the 10-lookup limit (RFC 7208).
Add a DMARC record at p=none with a report address, and read the reports for a few weeks.
Re-test with Show original and the checker.

What not to do

Don't add a second SPF record: merge into one.
Don't jump straight to -all or p=reject before every sender passes; you could block your own invoices.
Don't mix promotions into receipts: Google advises against mixing content types in one message.

Prefer someone to fix it for you?

We set up or correct SPF, DKIM and DMARC through a fixed-scope Fiverr gig. You add the records yourself with our guide or grant delegated, revocable access to your DNS host. We never ask for passwords, and we can't guarantee inbox placement: that also depends on content, reputation and the receiver.

See the email-fix gig on Fiverr

Frequently asked questions

Why do some customers get my emails and others don't?

Different receivers filter differently, and some apply stricter checks to unauthenticated mail. If one of your sending tools fails SPF, DKIM or DMARC, its emails may reach some inboxes and be filtered by others.

Do I need to change email providers?

Usually not. Most store, payment and app platforms let you authenticate your own domain by adding DNS records. Check each tool's official setup guide.

Will you need my DNS or email password?

No. You add the records yourself with our guide, or grant delegated, revocable access through your DNS host's team or delegate feature. We never ask for passwords.

How fast will it work?

DNS changes often show within minutes to a few hours. Receivers may take longer to reflect better results, so keep testing over several days.

Can you guarantee my invoices will reach the inbox?

No. We can make sure your domain's authentication is set up correctly and show you the before and after, but each receiver makes its own filtering decisions.

Sources

Official documents we read on 24 Oct 2026. Requirements change, so check the source before acting.