Field notes · October 2026 · 6 min read
The cold email deliverability checklist I run before every launch
A campaign can have the right list and the right offer and still land in spam. These are the checks I run before the first email goes out, and every week after. Where I've seen a check catch a real problem, the note under it says so.
01Domains
- Send from secondary domains, never the main company domain. If a cold domain burns, the domain your customers and invoices use stays clean.
- Point each sending domain at the main site with a redirect, so anyone who checks the domain lands somewhere real.
- Keep only a few mailboxes per domain. Two or three is a common ceiling; spreading volume across more domains limits the damage if one slips.
- Keep warmed spare domains ready. Rotating in a backup is faster than repairing a domain mid-campaign.
Seen in practice: a weekly placement test caught live domains slipping into spam. Rotating in a warmed backup restored full volume of 60 emails a day.
02Authentication
- SPF: one record per domain, listing every service that sends for it, and under the 10 DNS-lookup limit.
- DKIM: signed by the sending platform, with a 2048-bit key where the provider allows it.
- DMARC: at least
p=nonewith a reporting address. Since February 2024 Gmail and Yahoo require SPF, DKIM and DMARC from anyone sending over 5,000 emails a day to their users; treat that as the floor at any volume. - Custom tracking domain if opens or clicks are tracked, so links don't share a reputation with every other sender on the platform.
- Verify after publishing, not just before. Look the records up live; a typo or a duplicate SPF record only shows up once DNS is live.
Seen in practice: setting up six new sending domains, the post-publish check found two live DNS faults that would have failed authentication.
03Warmup
- Warm new mailboxes for two to four weeks before the first cold send, and keep warmup running alongside live campaigns.
- Use one warmup standard across every mailbox, so a problem on one mailbox stands out instead of hiding in different settings.
- Ramp cold volume gradually. A common per-mailbox ceiling is 30 to 50 cold emails a day; start well below it.
Seen in practice: standardising warmup settings across 90 mailboxes made each client's mailboxes comparable week to week.
04Lists
- Verify every address before upload. Remove invalid and role addresses, and treat catch-all domains as a risk.
- Watch bounce rate per campaign, not just overall. One bad list can hide inside a healthy average.
- Pause and re-verify any campaign bouncing above about 2–3%. Hard bounces tell inbox providers the list wasn't permission-based.
Seen in practice: across six campaigns, one bounced at 9.6%, about three times the average. A per-campaign view made it obvious; the blended rate hid it.
05Pre-launch placement test
- Send a test from every domain to seed inboxes at Gmail, Outlook and any other provider the list uses heavily.
- Record where each lands: inbox, promotions, spam or missing.
- Don't launch a domain that lands in spam. Fix authentication, warmup or content first, then test again.
Seen in practice: before a 30-domain rollout, all 150 Gmail seed tests landed in the inbox, so the campaign launched on every domain.
06Content
- Plain text first touch: no images, no attachments, at most one link.
- One clear ask per email, and a first line written for that prospect, not a template opener.
- A simple way to opt out in every email. It protects the domain as much as the recipient.
07Weekly monitoring
- Re-run the placement test weekly on every live domain. Placement drifts even when nothing in the campaign changes.
- Google Postmaster Tools: keep the spam rate under 0.1% and never let it reach 0.3%, Gmail's enforcement line.
- Check blacklists and DMARC reports for each sending domain.
- Act the same day: pause the slipping domain, rotate in a backup, and re-warm before it sends again.
Seen in practice: automating the weekly placement test cut hands-on time from 40 to 9 minutes a run across 32 domains. A generic open-source version is on GitHub.
Questions or a campaign that's landing in spam? ankitkha26@gmail.com