
Most deliverability problems are discovered after a campaign goes out — when replies don't come and bounces pile up. By then, the damage to your domain is already done. This guide shows how to check email deliverability before launching: a pre-flight sequence covering authentication, reputation, lists, test sends, content, and capacity, a go/no-go table for the final decision, and what to watch in the first hours after launch.
Launch Day Is the Worst Time to Find a Broken DKIM Record
💡 TL;DR
Check email deliverability before launching in six steps: confirm SPF, DKIM, and DMARC pass on a real test message; check domains and IPs against blocklists; verify the list and keep expected bounces under 2%; send seed and personal test messages and read the headers; review links, tracking, and unsubscribe; and confirm volume caps and warm-up status. Launch only when every item passes, then watch bounces and complaints closely for the first 24 hours.
Fair warning: a single missing DNS record, a stale list, or a blocklisted domain can turn a carefully written campaign into a reputation problem within hours. Mailbox providers judge your first sends quickly, and fixing a damaged domain takes far longer than checking one beforehand.
The checks below take about an hour for a typical campaign. That hour is the cheapest insurance in email.
By the end of this, you'll have a repeatable way to check email deliverability before every launch. For the bigger picture, see the complete email deliverability guide.
Step 1: Confirm Authentication on a Real Message
Don't trust DNS records alone. Check what receivers actually see.
Look up the records: one SPF record, DKIM for each sending domain, and DMARC.
Send a real message from the campaign's sending account to a Gmail address you control.
Open "Show original" and confirm SPF, DKIM, and DMARC all show PASS.
Check alignment: DKIM's header.d= should be your own domain, not a platform default.
Repeat for each sending domain — a template applied to ten domains can fail on one.
If anything fails, stop here. Our DNS templates for Google Workspace and Microsoft 365 and the DKIM guide cover the fixes.
Step 2: Check Reputation and Blocklists
🧱Blocklists
Check every sending domain and, if you have dedicated IPs, every sending IP. A listing before launch means fix first.
📊Google Postmaster Tools
Confirm each domain is added, and look at recent spam rate and reputation if there's enough history to show data.
🔎Microsoft SNDS
For dedicated IPs sending to Outlook.com, check for problems.
🆕Domain age and history
New domains or mailboxes with no history need a gradual start, not a full campaign.
Here's the advice we'd push back on: "If the domain isn't blocklisted, it's fine." Blocklists catch serious problems, but a domain can be unlisted and still have poor reputation with a major provider. Postmaster data and recent results tell you more.
Step 3: Verify the List
Your list decides your bounce rate, and your bounce rate is one of the first signals providers see.
Run every address through a verification service shortly before sending.
Remove invalid and risky addresses; handle catch-all domains cautiously.
Apply suppression lists: past opt-outs, complainers, and (for cold outreach) existing customers.
Check the source: lists older than about 60 days should be re-verified.
Target an expected bounce rate under 2% — see our bounce rate guide.
In practice, list problems cause more failed launches than any other single issue — and they're the easiest to prevent.
Step 4: Send Test Messages and Read the Results
Use two kinds of tests together to check email deliverability from the recipient side.
Test | How | What it shows | Limits |
|---|---|---|---|
Personal test inboxes | Send to your own Gmail, Outlook.com, and Yahoo accounts | Where it lands, how it renders, headers | Your accounts have their own history |
Seed test | Send to a placement tool's seed list | Placement across many providers | Seeds don't behave like real recipients |
Header review | Read Authentication-Results on each test | SPF, DKIM, DMARC results per provider | Shows authentication, not reputation |
Treat seed results as a warning light, not a verdict. A clean seed test with failing authentication is still a failure; a few seeds in spam with everything else healthy may not predict real results. More on interpreting them in inbox placement tools.
Step 5: Review Content, Links and Unsubscribe
Links: every link works and points to a reputable domain; cold emails use one link at most.
Tracking: link tracking uses a custom tracking domain, or is turned off.
Merge fields: no unfilled {placeholders} in a sample of rendered messages.
Unsubscribe: marketing mail has working one-click unsubscribe; cold outreach has a clear opt-out line.
Sender identity: real name, company, and postal address.
Wording: honest subject lines with no fake "Re:" — see spam trigger words.
Content is the last of the deliverability factors in importance, but broken links and placeholders hurt both filtering and replies.
Step 6: Confirm Capacity, Pacing and Reply Handling
Daily caps set per mailbox — for cold outreach, 25–40 per inbox per day, lower for new inboxes.
Warm-up status confirmed — fresh mailboxes need 4–6 weeks; pre-warmed ones can start sooner.
Sends spread across a window rather than all at once.
Platform limits understood — see Gmail sending limits.
Replies monitored — someone owns every inbox's replies from the first hour.
Then make the call with the table below.
Check | Go | No-go |
|---|---|---|
SPF, DKIM, DMARC on test message | All pass and aligned | Any fail |
Blocklists | Not listed | Listed |
List verification | Expected bounces under 2% | Higher, or unverified |
Test placement | Mostly inbox across providers | Consistent spam at one provider |
Content | Links, merge fields, opt-out all working | Any broken |
Capacity | Caps and pacing set; replies owned | Missing |
How the Check Changes by Campaign Type
The same six steps apply to every campaign, but the weight of each changes. Here's how to adjust when you check email deliverability for different kinds of sends.
Campaign type | Pay extra attention to | Why |
|---|---|---|
First cold outreach campaign on new domains | Warm-up status, low caps, list verification | No sending history yet; first impressions count |
Large newsletter after a long gap | List hygiene and unengaged contacts | Old addresses bounce and dormant recipients complain |
Product launch announcement | Volume pacing and throttling | Sudden spikes trigger deferrals |
Migration to a new platform or domain | Authentication and alignment on every domain | DNS changes are easy to miss |
Agency launching for a new client | Client domain ownership, DNS, and suppression lists | Many moving parts across accounts |
Keep a written checklist and attach the results to each campaign. Over time, it shows which checks catch problems most often for your program — and it gives anyone on the team a reliable way to check email deliverability without relying on memory.
For repeat campaigns on stable infrastructure, a shorter version is fine: authentication on a test message, list verification, and a quick seed test. Save the full sequence for new domains, big changes, and anything that has gone wrong recently. When in doubt, check email deliverability the long way — it costs an hour, while a damaged domain costs weeks.
What to Watch on Launch Day
Checks before launch reduce risk; watching after launch limits damage if something slips through.
When | Watch | If it goes wrong |
|---|---|---|
First hour | Bounces and SMTP responses | Bounces climbing past 2%: pause and re-verify |
First hour | Temporary deferrals (4xx) | Slow down — see email throttling |
First day | Replies and opt-outs | Complaints or angry replies: pause and review targeting |
First week | Postmaster spam rate | Approaching 0.1%: pause the domain |
Thresholds follow Google's email sender guidelines. Litemail inboxes come with SPF, DKIM, and DMARC pre-configured and pre-warmed options with 4+ weeks of sending history, which removes two of the most common reasons to check email deliverability and find a problem.
Launch on infrastructure that passes the checks — Litemail Google Workspace and Microsoft 365 inboxes come with authentication configured, dedicated US and EU IPs, sending history on pre-warmed plans, and free domain replacement. See Pre-Warmed Inbox Plans → About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated DNS, dedicated US and EU IPs, and full admin access. Pre-warmed plans start at $39/month for 5 inboxes; add-on inboxes go as low as $4.99/inbox on the Scale plan. View pre-warmed inbox plans →
Related reading: Email Deliverability: Complete Guide · Inbox Placement Tools · Stop Cold Emails Going to Spam · Monitor Email Infrastructure Health
Key Takeaways
Check email deliverability before every launch, not after replies drop.
Confirm SPF, DKIM, and DMARC pass and align on a real test message for every sending domain.
Check blocklists and Postmaster data; unlisted doesn't always mean healthy.
Verify the list and keep expected bounces under 2%.
Use personal test inboxes, seed tests, and header reviews together.
Watch bounces, deferrals, and complaints closely for the first 24 hours.
Frequently Asked Questions
How do I check email deliverability before sending a campaign?
Confirm authentication on a real test message, check blocklists and reputation, verify the list, send seed and personal tests, review content and links, and confirm caps and pacing.
How long does a pre-launch deliverability check take?
About an hour for a typical campaign, longer if you find problems to fix.
Are seed tests enough to check deliverability?
No. They're one useful signal, but seed inboxes don't behave like real recipients. Combine them with authentication checks, reputation data, and real results.
What bounce rate is safe for a launch?
Aim for an expected bounce rate under 2%. Verify the list shortly before sending.
What should I do if a test lands in spam at one provider?
Check authentication and reputation for that provider, review links and content, and consider a smaller first send to that segment.
What should I watch right after launching?
Bounces and SMTP responses in the first hour, replies and opt-outs on the first day, and Postmaster spam rate during the first week.
Does Litemail help with pre-launch checks?
Litemail inboxes come with SPF, DKIM, and DMARC pre-configured and pre-warmed options, so authentication and warm-up checks usually pass from the start.
Start Every Campaign From a Clean Pre-Flight
Litemail inboxes come with SPF/DKIM/DMARC configured, sending history on pre-warmed plans, dedicated US and EU IPs, and free domain replacement if a domain is ever blacklisted.
Plans from $39/month · Google Workspace and Microsoft 365 · Setup in about 5 minutes
Buy Pre-Warmed Email Inboxes & Domains | Litemail — Pre-warmed Google Workspace and Microsoft 365 inboxes with automated DNS, US and EU IPs, and setup in about 5 minutes. Fresh inboxes from $2.50/inbox; pre-warmed from $4.99/inbox at scale. View plans and pricing →
Related reading: Pre-Warmed Inboxes · Pre-Warmed Domains · Cold Email Infrastructure Setup · Cold Email Deliverability Guide · Litemail Home · Plans and Pricing


