By the Outsquid team · · How we write
Cold email deliverability: the complete guide
What decides whether cold email reaches the inbox — authentication, sending volume, list quality and how people react — and what to do about each, in order.
Deliverability is whether your email reaches the inbox. For cold email it's the whole game: a perfect message in the spam folder gets the same reply rate as no message at all, and you rarely find out it happened.
Mailbox providers decide where an email goes from four things, roughly in this order of how often they cause trouble: authentication (can they tell the email really came from your domain?), volume (is this mailbox sending like a person or like a script?), list quality (do you know the people you're writing to?) and reactions (do recipients reply, ignore, or report you?). This guide takes them one at a time, with what to check and what to do, and links to the detailed guides for each.
1. Authenticate your domain
Three DNS records prove an email came from your domain: SPF lists the servers allowed to send for it, DKIM signs each message, and DMARC tells receivers what to do when the other two fail. Google and Yahoo have required them since 2024 — SPF or DKIM from everyone, all three from bulk senders — and Microsoft has enforced similar rules for high-volume senders to Outlook.com since 2025.
What to do:
- Publish exactly one SPF record, ending in
~allor-all, with fewer than 10 DNS lookups. The SPF generator builds one. - Turn on DKIM signing in your mailbox provider and publish its key — see the setup guides for Google Workspace, Microsoft 365 and Zoho Mail.
- Add a DMARC record, starting with
p=noneand a report address, then tighten. The DMARC generator writes it. - Check the result with the free DNS checker; every problem it can find is explained on its own page.
The full explanation, including alignment and the common mistakes, is in SPF, DKIM and DMARC for cold email.
2. Send at a pace inboxes trust
Volume is judged per mailbox and over time. A mailbox that sends 10 emails a day for months and then 200 overnight looks compromised; a new mailbox that starts at 200 has no history to excuse it.
What to do:
- Ramp new mailboxes up. Start at 5–10 cold emails a day and grow over about a month. Details in ramping up a new mailbox.
- Cap each mailbox at roughly 30–50 cold emails a day once established, with an hourly cap and a gap between sends. The providers' published limits — 2,000 a day for Google Workspace — are ceilings, not targets.
- Count every campaign. Limits must cover all the campaigns a mailbox is in, follow-ups included.
- Add mailboxes to grow, rather than pushing one harder. Several mailboxes spread the risk: if one has a bad week, the others carry on.
Connect mailboxes with their provider's own sign-in where you can — Google or Microsoft — or with SMTP and IMAP for anything else; IMAP is what lets replies stop a sequence.
3. Keep bounces low
Bounces are the clearest sign that you don't know who you're emailing. Under 2% is healthy; above 5%, stop and clean the list. A single bad import can wreck a mailbox's reputation in an afternoon.
What to do:
- Check addresses before the first email: the domain must accept mail, and
typos like
gmial.comand throwaway inboxes should never be sent to. - Re-check data that's more than about a month old.
- Pause a campaign the moment its bounce rate jumps, find the source, and remove it.
- Never email an address that has hard-bounced again.
How to read bounce codes, and what to do when the rate climbs, is in what's a safe bounce rate for cold email.
4. Earn replies, not complaints
Providers watch how recipients react. Replies are a strong positive signal; "Report spam" is the strongest negative one. Google asks senders to keep their reported spam rate below 0.3%, and ideally below 0.1% — for cold email that's a handful of complaints per thousand sends.
What to do:
- Write to people whose role makes your email relevant, and say why you chose them.
- Keep emails short and plain. Every link, image and tracking pixel makes an email look more like bulk mail; start with open and click tracking off.
- Follow up a few times, in the same thread, then stop — see writing cold email follow-ups that get replies.
- Make leaving easy and honour it everywhere: a line inviting a reply, an unsubscribe link and the one-click unsubscribe header. More in unsubscribes in cold email.
5. Watch the signals
Deliverability problems are quiet. Nothing tells you your emails went to spam; replies just stop. Watch for:
- A failing DNS check after someone changes a record or adds a tool.
- Rising bounces on a particular list or campaign.
- Replies dropping to zero on a campaign that used to get them.
- Errors from the provider: rate limits, authentication failures, a mailbox signed out.
When one appears, slow down rather than stop: reduce the mailbox's daily limit, fix the cause, then build back up.
A one-page checklist
- SPF, DKIM and DMARC pass for every sending domain, and MX exists.
- New mailboxes start at 5–10 a day and ramp up over a month.
- Each mailbox stays at 30–50 a day across all its campaigns, with gaps between sends.
- Every address is checked before it's emailed; bounces stay under 2%.
- Emails are short, plain and relevant; tracking is off unless you need it.
- Follow-ups stay in the thread and stop on a reply or an opt-out.
- Unsubscribes and bounces are suppressed everywhere, for good.
How Outsquid helps
Outsquid was built around this list. It checks SPF, DKIM, DMARC and MX for every sending domain every hour and gives each mailbox a health score; paces every mailbox with daily and hourly limits and a gap between sends, counted across campaigns; ramps new mailboxes up on their own; checks addresses before sending; and pauses a campaign or a mailbox when bounces climb. See deliverability and safeguards.
Everything in this guide
Authenticate the domain
- BlogSPF, DKIM and DMARC for cold email: what you actually needThe three DNS records every sending domain needs, what each one proves, and the settings that are safe for cold outreach.
- HelpSet up SPF, DKIM and DMARCWhat each record does, example records, and how Outsquid rates your domain.
- DNS guideGoogle Workspace SPF, DKIM and DMARC setupSPF, DKIM, DMARC and MX records for a Google Workspace domain: the exact values, where DKIM lives in the Admin console, and the order to set them up.
- DNS guideMicrosoft 365 SPF, DKIM and DMARC setupSPF, DKIM, DMARC and MX for a Microsoft 365 (Exchange Online) domain: the SPF include, the two DKIM CNAMEs from the Defender portal, and DMARC.
- DNS guideZoho Mail SPF, DKIM and DMARC setupSPF, DKIM, DMARC and MX for a Zoho Mail domain: where to find the values for your data centre and how to add a DKIM selector.
- Free toolSPF, DKIM and DMARC checkerSee any domain's email authentication records and what to fix.
- Free toolSPF record generatorPick who sends as your domain and get one valid SPF record.
- Free toolDMARC record generatorChoose a policy and a report address, copy the record for _dmarc.
Send at a pace inboxes trust
- BlogHow fast can a new mailbox send? Ramping up without burning itWhy new mailboxes need to start slowly, a sensible ramp schedule, and the signals that tell you to back off.
- HelpConnect a Gmail or Google Workspace mailboxSign in with Google, what Outsquid can access, sending limits, and reconnecting.
- HelpConnect an Outlook or Microsoft 365 mailboxSign in with Microsoft, admin approval for work accounts, and reconnecting.
- HelpConnect any mailbox with SMTP and IMAPThe settings you need, common providers, app passwords and testing the connection.
Keep bounces and complaints low
- BlogWhat's a safe bounce rate for cold email?Hard vs soft bounces, the thresholds that matter, and what to do the moment your bounce rate starts to climb.
- BlogUnsubscribes in cold email: the rules and the right thing to doWhat the mailbox providers and the main laws expect when someone asks you to stop, and how to make sure they never hear from you again.
- HelpUnsubscribes, the blacklist and bounce protectionHow opt-outs stop every campaign, blocking emails and domains, and the bounce guard.
In Outsquid
- ProductDeliverabilityOutsquid spreads every mailbox's sends across the day, starts new mailboxes slowly and checks your domain's DNS — so your emails keep landing in the inbox.
- ProductSafeguardsOutsquid is built to stop the errors that burn domains and embarrass senders. Every safeguard is on by default, on every plan.
Questions
What is email deliverability?
The share of your emails that reach the recipient's inbox rather than the spam folder or nowhere at all. It depends on your domain's authentication, your sending reputation, your list and how recipients react to what you send.
Why are my cold emails going to spam?
The usual causes, in order of how often we see them: missing or broken SPF, DKIM or DMARC; too many emails from one mailbox, especially a new one; a list with too many bad addresses; and emails that look like bulk mail, with tracking, links and images. Check them in that order.
How many cold emails can I send per day?
Around 30 to 50 per mailbox once it's established, starting from 5 to 10 a day for a new one. To send more, add mailboxes rather than pushing one harder.
How do I test whether my emails land in the inbox?
Check your domain's records with a DNS checker, then send a test to a colleague or a personal address on a different provider. Over time, watch replies: a campaign whose replies drop to zero may be landing in spam.
Sources