Playbook · Cold email
Cold Email Deliverability: The Technical Checklist
By Marián Cabadaj · Published 8 September 2026 · 7 min read
Cold email deliverability is whether your messages actually reach the primary inbox, rather than being filtered to spam, throttled, or rejected outright. It is decided by domain and sender reputation, not by how good the writing is.
This guide covers the authentication Google now requires of bulk senders, the exact spam rate ceiling that decides whether your mail keeps landing, why deliverability quietly drops before anyone notices, and a free calculator for your own current spam rate.

What Cold Email Deliverability Actually Means
Deliverability is not "did the email send." It is whether the receiving provider decided your message belonged in the primary inbox. That decision runs on domain and sender reputation, accumulated across every message you have ever sent from that domain, not on the quality of any single email. A perfectly written email from a domain with a poor reputation still lands in spam, and a plain, ordinary email from a well-authenticated, low-complaint domain still reaches the inbox.
The Authentication Requirements, From Google Directly
Google's own email sender guidelines set out exactly what is required, and the requirement gets stricter once you cross 5,000 messages a day to Gmail accounts.
| Requirement | Threshold | Applies to |
|---|---|---|
| SPF | Required for every sender | All senders |
| DKIM | Required for every sender | All senders |
| DMARC | Required on the sending domain (enforcement policy may be set to none) | 5,000+ messages/day to Gmail |
| One-click unsubscribe | Required, with a visible unsubscribe link in the body | 5,000+ messages/day to Gmail |
| Spam rate | Recommended below 0.10%, never at or above 0.30% | All senders, Postmaster Tools |
SPF and DKIM cost a morning of DNS work and are worth setting up long before you approach the 5,000-a-day threshold, since most teams cross it sooner than they expect once several reps share a domain. Our guide to outbound email automation covers the full sender rule set for Gmail and Outlook side by side, and our guide to automated sales prospecting covers where deliverability sits in the order things break once volume rises.
The Spam Rate Ceiling You Cannot Cross
Google publishes two numbers, and they are a target and a hard ceiling, not a range. Keep the spam rate reported in Postmaster Tools below 0.10% as the working target, and never let it reach 0.30%, the point at which mail starts getting filtered outright. Recovering from a breach of that ceiling requires seven consecutive days back under it, which means one bad week costs you the following one as well.
Why Deliverability Drops Before Anyone Notices
The common failure pattern is quiet. Reply rates fall, the team rewrites the copy, nothing improves, because a filtered message never had a copy problem in the first place. Check reputation signals before touching a single word: authentication status first, because it is binary and free to verify, then the spam complaint rate, then the bounce rate, and only after all three are clean does rewriting the email actually help. See our guide to cold email templates for what to fix once deliverability is confirmed healthy.
A new or poorly warmed domain is the most common root cause. Sending at full volume from day one on a domain with no sending history reads as suspicious to every major provider, regardless of how carefully the list was built or how well the follow-up sequence is spaced. Ramp volume gradually over two to four weeks, and keep a secondary domain for cold outreach so a reputation problem never touches the domain the rest of the company depends on.
How Leadalf Fits Around Deliverability
None of the requirements above change based on who receives the email, but the complaint rate that decides whether you stay under the spam rate ceiling absolutely does. A recipient with no real reason to hear from you is a recipient more likely to mark the message as spam, and every complaint pushes the whole domain closer to the 0.30% line. Leadalf watches LinkedIn, Reddit, X, the Meta Ads Library and job postings for buying signals, scores each one against your ICP, and delivers only the contacts that pass into Instantly or HeyReach, which keeps the complaint rate lower for the same reason a well-targeted list always beats a bigger one.
Frequently Asked Questions
What is cold email deliverability?
Deliverability is whether a sent email actually reaches the recipient's primary inbox, rather than being filtered to spam, delayed, or rejected outright. It is decided almost entirely by domain and sender reputation, not by the quality of the writing, which is why a well-written email can still land in spam.
Do I need SPF, DKIM and DMARC for cold email?
Yes. Google's official sender guidelines require SPF or DKIM for every sender, and require DMARC specifically once you send more than 5,000 messages a day to Gmail accounts. Below that threshold the rules are more forgiving, but setting up all three from the start avoids having to fix it later under pressure.
What spam rate is safe for cold email?
Google recommends keeping the spam rate reported in Postmaster Tools below 0.10%, and states it should never reach 0.30% or higher. Read the first number as the target and the second as a hard ceiling you should never approach, not as a range you can safely operate inside.
Does sending from a secondary domain actually help deliverability?
It isolates risk rather than improving deliverability on its own. A secondary domain that only sends cold outreach keeps a reputation problem from touching the primary domain your company depends on for every other kind of email, but it still has to go through the same warmup and authentication as any new domain.
How long does it take to warm up a new sending domain?
Typically two to four weeks of gradually increasing volume, starting low and raising it only as replies and opens stay healthy and complaints stay near zero. Skipping warmup and sending at full volume from day one is one of the fastest ways to get a brand-new domain flagged.