Deliverability is not one setting. It is the combined result of domain authentication, sending infrastructure, sending pattern, and list quality, evaluated continuously by every inbox provider a message passes through. A single misconfigured record or a single bad sending habit can undo months of built-up sender reputation.
This guide covers the four layers that determine inbox placement, in the order most cold-email programs should address them.
Layer 1: DNS Authentication
Three DNS records establish that a message claiming to come from your domain actually does.
SPF lists which mail servers are authorized to send on behalf of your domain. A missing or incomplete SPF record is the single most common reason cold email lands in spam before anything else about the message is even evaluated.
DKIM attaches a cryptographic signature to each outgoing message, proving it was not altered in transit and genuinely originated from an authorized sender. Every sending platform needs its own DKIM selector published on your domain.
DMARC tells receiving servers what to do when SPF or DKIM fails, and gives you visibility into who is sending mail as your domain. Start with a monitoring policy before moving to a stricter enforcement policy, so you can see failures before you start rejecting mail based on them.
Get all three published correctly before sending a single cold email. No amount of good copy or good targeting overcomes a broken authentication layer.
Layer 2: Domain and Inbox Warmup
A brand-new domain and a brand-new inbox have no sending history, which means inbox providers have no basis to trust them. Warmup is the process of building that history gradually: low, automated send volume that generates opens and replies before any real cold outreach begins.
Skipping warmup and sending cold volume from day one is the fastest way to burn a domain permanently. Inbox providers watch the ratio of sudden volume to prior history closely, and a spike from zero looks identical to a compromised account regardless of intent.
Warmup typically runs two to four weeks before a domain is ready for real cold volume, and readiness should be measured by actual engagement signals (opens, replies, low bounce and complaint rates), not just elapsed time.
Layer 3: Sending Pattern and Volume Discipline
Once a domain is warm, the sending pattern itself becomes a reputation signal. Sudden volume jumps, identical send times across an entire list, and near-zero variance in message content are all patterns inbox providers associate with bulk mail rather than real correspondence.
Distributing sends across multiple inboxes and domains, staggering send times, and keeping daily volume per inbox within provider-tolerant limits all reduce the chance any single inbox trips a spam threshold. This is why cold outreach at scale runs across a fleet of inboxes rather than one, and why a single burned domain should never take down the entire program: rotation and isolation contain the damage.
Layer 4: List Hygiene and Content
Even with perfect authentication and a perfectly warmed fleet, sending to a bad list undoes everything above it. High bounce rates and spam complaints are read by inbox providers as reputation signals against the sending domain, not just against the individual message.
Verify email addresses before sending, remove hard bounces immediately, and honor unsubscribe and complaint signals without exception. On content, avoid spam-trigger patterns: excessive links, all-caps subject lines, and templated copy sent identically to a large list all increase spam-folder risk independent of authentication status.
Putting the Four Layers Together
Deliverability problems almost always trace back to one of these four layers, and the fix is almost never "try a different subject line." A domain landing in spam despite good authentication is usually a warmup or volume-discipline problem. A domain with good history suddenly landing in spam is usually a list-hygiene problem: a recent import with bad data, or a spike in bounces.
Treat deliverability as infrastructure, not a switch you flip once. Authentication needs to be checked on every new domain, warmup needs to run on every new inbox, sending pattern needs monitoring as volume scales, and list hygiene needs enforcement on every import. Programs that treat all four as ongoing discipline keep inbox placement high. Programs that treat deliverability as a one-time setup step eventually burn through their sending capacity and have to start over on new domains.