June 2026·9 min read·Outreach

Cold Email Deliverability in 2026: SPF, DKIM, DMARC, and Domain Health

You can write the perfect cold email. If it lands in spam, nobody reads it. Here's the technical foundation every founder and sales team needs to understand before sending a single email.

Why deliverability comes first

Most cold email advice focuses on copy: subject lines, opening sentences, call-to-action placement. Copy matters — but only if your email reaches the inbox. In 2026, Google and Microsoft reject roughly 15-20% of cold email outright before the recipient ever sees it. That number is climbing.

You can A/B test subject lines forever. If your DNS records aren't configured correctly, none of those tests matter — your emails never made it to the inbox.

Deliverability isn't one thing. It's a stack: DNS configuration, domain reputation, sending behaviour, and infrastructure management. The good news: the DNS layer is completely within your control. The better news: once configured correctly, it works silently in the background for every email you send.


SPF: telling the world who can send as you

SPF (Sender Policy Framework) is a DNS record that lists which servers are allowed to send email from your domain. Think of it as a guest list: if a server not on the list tries to send email claiming to be from @yourcompany.com, receiving servers know to reject it.

SPF in Plain English

Without SPF, anyone can send email that looks like it came from your domain. With SPF, receiving servers check your DNS record and say: \"This IP address is on the approved list — let it through\" or \"This IP isn\'t listed — reject or flag.\"

A basic SPF record looks like: v=spf1 include:_spf.google.com ~all. This tells the world: Google's mail servers are authorized to send from my domain. The ~all at the end means: treat anything else as suspicious.


DKIM: proving the email hasn't been tampered with

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every email you send. When a receiving server gets your email, it checks the signature against a public key stored in your DNS. If the signatures match, the server knows two things: the email genuinely came from your domain, and nobody modified it in transit.

1

You send an email

Your email server attaches a DKIM signature — an encrypted hash of the email's content and headers.

2

It travels across the internet

The email passes through multiple servers. DKIM ensures nobody altered the content along the way.

3

The receiving server checks

Gmail or Outlook looks up your domain's DKIM public key in DNS. It decrypts the signature and compares it to the email content.

4

Match = trusted. No match = suspicious.

If the signature matches, the email gets a trust boost. If it doesn't, the email is flagged or rejected.


DMARC: the enforcement layer

DMARC (Domain-based Message Authentication, Reporting, and Conformance) ties SPF and DKIM together and tells receiving servers what to do when authentication fails. Without DMARC, you have SPF and DKIM configured but no policy for what happens when they fail. DMARC is the enforcer.

DMARC PolicyWhat It MeansWhen to Use
p=noneMonitor only — don't reject anythingWhen you're first setting up, to observe
p=quarantineSend failing emails to spamOnce you're confident SPF/DKIM are correct
p=rejectReject failing emails outrightFull protection — recommended for production

Beyond DNS: domain reputation

DNS records get you in the door. Domain reputation keeps you there. Email providers track sending behaviour per domain: volume, bounce rates, spam complaints, engagement. Build a bad reputation and even perfect SPF/DKIM/DMARC won't save you.

Send volume patterns

Sending 50 emails/day consistently is better than 500 on Monday and zero for the rest of the week. Providers watch for spikes.

Bounce rate

Keep it below 3%. Above 5% and providers start routing you to spam. Above 10% and you may be blocked entirely.

Spam complaint rate

Google's Postmaster Tools tracks this. Keep it below 0.1% (that's 1 complaint per 1,000 emails). Above 0.3% is dangerous.

Engagement signals

Replies, forwards, and "not spam" clicks all boost your reputation. Providers watch whether recipients interact with your emails.


The warmup connection

A new domain with perfect DNS records is still a new domain. Email providers treat new senders cautiously — they don't know if you're a legitimate business or a spammer who registered a domain yesterday and started blasting 1,000 emails.

Warmup isn't optional. It's the bridge between \"new domain, good DNS\" and \"trusted sender, inbox placement.\" Skip it and you start from a reputation deficit that takes weeks to fix.

A proper warmup schedule starts small (5-10 emails/day), increases gradually over 4-6 weeks, and uses seed accounts — real mailboxes that automatically open and reply to your emails, signalling to providers that people want your messages. It's slow, but there's no shortcut.


Common mistakes that tank deliverability

What hurts deliverability

  • ×Sending from a brand-new domain at high volume
  • ×Missing or misconfigured SPF/DKIM/DMARC
  • ×High bounce rates from stale contact lists
  • ×Spikey sending patterns (500 one day, zero the next)
  • ×Using the same domain for cold email and transactional email

What protects deliverability

  • Proper DNS: SPF, DKIM, DMARC all configured and tested
  • Staged warmup: 5 → 30 → 50+/day over 4-6 weeks
  • Clean, verified contact data (95%+ deliverability)
  • Consistent daily volume with gradual increases
  • Separate domains for cold outreach and product emails

The infrastructure advantage

Here's the part most cold email guides skip: configuring DNS is step one. Managing the ongoing infrastructure — domains, email accounts, provider diversity, fingerprint isolation, warmup coordination — is the actual work. It's tedious, error-prone, and critical.

Why This Matters for Small Teams

A founder doing their own outreach doesn't have time to manage DNS records across 3 domains, monitor bounce rates, and coordinate warmup schedules. This is why most small teams either avoid cold email entirely or send from their primary domain and wreck their deliverability within a month.

The alternative: infrastructure that's managed for you. Domains, DNS, email accounts, warmup — configured, monitored, and maintained. You focus on conversations, not configuration. This is the difference between cold email as a chore and cold email as a reliable pipeline channel.

Outreach infrastructure, managed for you.

Domains, DNS, warmup, and monitoring — all handled. You focus on conversations. No credit card required.

Start free