Why are my emails going to spam? A practical checklist
The most common technical and reputation reasons your emails land in spam — and what to check first.
Updated
When legitimate emails land in spam, the cause is usually one of three things: authentication, reputation or content and list quality. Work through them in this order — authentication problems are the easiest to find and fix.
1. Authentication (check this first)
- SPF: exactly one record, no more than 10 DNS lookups, and every sending service accounted for. See SPF: too many DNS lookups.
- DKIM: every service that sends as your domain signs with DKIM for your domain, using a 2048-bit key where possible.
- DMARC: a record exists and SPF or DKIM aligns with your From address. See How to set up DMARC.
- Your own mail server (if you run one) needs a matching reverse DNS (PTR) record.
Run the free SPF, DKIM & DMARC checker — it finds the most common setup errors in seconds.
2. Sender reputation
- Spam complaints: Gmail asks bulk senders to stay below 0.3% complaints (ideally under 0.1%). Monitor this in Google Postmaster Tools.
- Blocklists: check whether your sending IP or domain appears on major blocklists.
- New domains and sudden volume spikes: warm up gradually instead of sending thousands of emails from a brand-new domain.
- Shared IPs: on cheap email platforms, other customers' behavior can affect you.
3. Content and list quality
- Only email people who opted in; remove addresses that bounce.
- Bulk email needs a visible unsubscribe link — Gmail and Yahoo also require one-click unsubscribe headers for bulk senders.
- Avoid link shorteners and links to domains with a bad reputation.
- Balance images and text; don't send image-only emails.
- Make the From name and subject line match what people expect from you.
Quick test
Send an email to a Gmail address, open it and choose Show original. You'll see whether SPF, DKIM and DMARC say PASS — and which domain each one used.
Check your page in seconds
Free, no signup: see what's wrong and get the exact DNS records to fix it.
Check your domain with the free SPF, DKIM & DMARC checker →