Every check that matters before you hit send. Authentication, infrastructure, content, list hygiene, compliance — plus the high-risk industry extras SendGrid, Mailchimp and Brevo will not tell you about.
This is the checklist we run internally at SendHaven before every customer launches their first campaign on our infrastructure. It is not a 12-bullet blog listicle. It is the full audit — 47 checks across 8 categories — that separates senders who hit the inbox from senders who quietly rot in the spam folder wondering why their open rates collapsed.
Fair warning: this checklist is written for senders who take deliverability seriously. If you are a hobbyist sending 500 newsletters a month from a Gmail address, most of this will be overkill. If you are sending 10,000+ messages a month — transactional, marketing, cold outreach, or anything in between — every single item below will either save you or catch up to you eventually.
We built this list after years of running dedicated email infrastructure for operators in the industries most ESPs refuse to serve: iGaming, crypto, forex, CBD, adult, dating, cold outreach. High-risk senders have less margin for error than consumer-facing SaaS, so our standards are higher than the average deliverability guide you will find online. Print this, bookmark it, or turn it into a Notion database — just run it.
The 30-second version: Authentication + clean list + warm IP + good content + honest consent = inbox. Everything on this checklist serves one of those five pillars. If you are short on time, go straight to sections 1, 2 and 4 — they cover 80% of the wins.
Run the full 47 points when you are setting up a new sending domain, migrating from another ESP, or diagnosing a deliverability drop. For ongoing sends, pull out the "pre-send audit" subset (sections 1, 2, 3 and 4) and run it before any major campaign.
Every check has a pass criterion. If you cannot confidently tick a box, the item is a fail — not a "maybe." Deliverability does not grade on a curve. Filter systems see binary signals: you pass the check or you contribute to a reputation decay that eventually lands you in the spam folder.
If you want the deeper theory behind any of these checks, we wrote a full email deliverability guide that walks through SPF, DKIM, DMARC, IP reputation and engagement signals in detail. This page is the quick-reference audit; that page is the textbook.
Authentication is non-negotiable in 2026. Google, Yahoo and Microsoft all require DMARC for senders above 5,000 messages per day, and "required" means rejected or spam-foldered if missing. This section is the single highest-leverage part of the entire checklist.
mail.brand.com, send.brand.com) — never your apex root domain, never a free mailbox.v=spf1 records is an automatic fail — many filters will reject outright.-all (hard fail) or ~all (soft fail). +all is an open relay and an instant spam-folder sentence.include: directives breaks SPF silently and catastrophically.s2026a._domainkey), and you have a rotation plan so you can switch keys without downtime if one is compromised._dmarc.yourdomain.com. Start with p=none for monitoring, then move to p=quarantine once you have verified all legitimate sending sources are aligned. Target p=reject within 90 days.rua aggregate reporting address is set to an inbox you actually read (or better, a service like Postmark DMARC or dmarcian that parses the reports for you).The machine that sends your mail matters almost as much as the domain on it. This section is where cheap ESPs leak the most deliverability — they stuff thousands of senders onto shared IP pools and you inherit the reputation of whoever is sending next to you.
localhost or server1.Modern spam filters care less about "spam words" than they did a decade ago, but content still matters — especially structural signals like HTML validity, text-to-HTML ratio and link hygiene.
multipart/alternative). Missing text parts are a strong spam signal and hurt accessibility.List hygiene is where most otherwise-competent senders torch their reputation. A list that was clean 12 months ago is full of abandoned accounts, spam traps and corporate addresses that now bounce hard. Bad lists are the #1 cause of sudden inbox-rate collapses we see when diagnosing new customers.
info@, admin@, support@, sales@) are filtered out before send — they are complaint magnets and never convert.Heads up: If you inherited a list from a prior team member and cannot prove consent on every address, treat the entire list as suspect. Re-permission it with a fresh single-email consent request before you migrate to any new infrastructure. This is cheaper than burning a fresh IP on a dirty list.
Gmail and Yahoo both score senders primarily on engagement: opens, clicks, replies, forwards, "move to inbox" actions. This section is about making sure you are not accidentally killing engagement through segmentation mistakes or bad send-time logic.
You cannot manage what you do not measure. The free tools below give you the same visibility mailbox providers have into your sending reputation — and most senders do not even know they exist.
rua) reports are being parsed and reviewed at least weekly. Unknown IPs sending on your behalf is the strongest early signal of a compromised API key or forgotten third-party integration.Compliance is not just a legal chore — missing footer elements and broken unsubscribe flows are direct reputation penalties with Gmail and Yahoo, regardless of jurisdiction.
List-Unsubscribe and List-Unsubscribe-Post: List-Unsubscribe=One-Click headers are present on every message. These are mandatory since the 2024 Gmail/Yahoo bulk sender rules — missing them is a direct spam-folder trigger.If you send email for iGaming, crypto, forex, CBD, adult, dating or cold outreach, you are operating under stricter filter rules than consumer SaaS senders. These four extras are the difference between surviving and thriving in the high-risk lane.
We run this audit on every new SendHaven customer during onboarding. Across 50+ businesses we have migrated in the last year, these are the five failures that show up most often:
d= domain does not match the From header. DMARC fails silently, everything lands in spam, and the sender swears "authentication is set up correctly." It is not.Honest take: If you catch and fix the first four points on this checklist alone (authentication), you will solve more deliverability problems than the rest of this document combined. Everything else is polish on top of a foundation that either works or does not.
A healthy inbox placement rate is 95% or higher to Gmail, Yahoo and Microsoft combined. Anything under 90% means you have a fixable problem — usually authentication, list hygiene or IP reputation. Raw delivery rate (not bouncing) should sit above 98%; the gap between delivery rate and inbox rate is how much mail is landing in spam.
Run the full 47-point checklist quarterly. Run the pre-send subset (sections 1, 2, 3, 4) before every major campaign or new domain launch. Automated monitoring through Google Postmaster Tools and Microsoft SNDS should be checked weekly — both take five minutes and they will save you from a six-week inbox rate recovery.
Yes, unconditionally. Since February 2024 Google and Yahoo have required DMARC for any sender above 5,000 messages per day. Microsoft now enforces the same threshold. Missing DMARC does not mean "slightly worse deliverability" — it means outright rejection at the largest inbox providers on the planet.
Authentication alignment. SPF, DKIM and DMARC must all pass and align with the visible From domain. Everything else on the list matters, but if you fail authentication you lose before the filter even reads your content. A single misaligned DKIM selector can destroy an entire campaign's inbox rate.
Four to eight weeks for B2C senders, two to four weeks for B2B with a clean list. Day 1 starts at 50-200 messages to your most engaged subscribers, doubling volume every 2-3 days while keeping complaint rate under 0.1%. Rushing warmup is the fastest way to burn a new IP into uselessness.
Only if your volume justifies it. Below roughly 100,000 messages per month, a reputable shared pool outperforms a cold dedicated IP because mailbox providers cannot build a reliable reputation signal on low-volume IPs. Above 100k/month, dedicated becomes non-negotiable — you stop paying the reputation tax of whoever else is on your shared pool. For high-risk industries, we recommend dedicated from day one regardless of volume.
Below 0.1% — one complaint per 1,000 messages. Google Postmaster Tools shows this as your User Reported Spam Rate. Above 0.3% you will see throttling. Above 0.5% you are effectively blacklisted at Gmail until the rate recovers over several weeks of clean sending.
Free tools: MXToolbox blacklist check, Spamhaus lookup, and MultiRBL.valli.org. The blacklists that actually matter to your deliverability are Spamhaus SBL and CSS, Barracuda, Invaluement and SURBL. URIBL listings matter as much as IP listings now — filters inspect the domains inside your message body.
Email deliverability is not a mystery. It is a checklist. Forty-seven boxes, eight categories, a handful of free monitoring tools, and a discipline of running the audit on a schedule rather than in panic mode after a campaign tanks.
The teams who consistently hit the inbox are not smarter than the teams who do not — they are just the ones who ticked every box on a list like this one before hitting send, and then did it again the next quarter. If you are running a high-volume or high-risk sending program and you want a human to walk this audit with you, book a free 15-minute audit call with our engineers. We will tell you honestly whether your current ESP can fix the issues you have, or whether you need dedicated infrastructure to get out of the shared-pool reputation drag.
And if you are already past the point of "can this ESP handle me" and staring at a suspension email, our full SendGrid alternatives guide walks through the 10 best migration options — with an honest breakdown of which ones actually accept iGaming, crypto, forex, CBD, adult and dating senders instead of quietly banning you six months in.
Free 15-minute call with a SendHaven engineer. We will walk through the 47 checks against your current sending domain and tell you exactly what is leaking inbox rate.
Book a free audit