Guide

Cold email infrastructure that keeps your domains alive

Cold email is a reputation game. You are sending to people who do not expect your email, so every provider weighs your sending domain and IP against a baseline of "does this look like a real, established sender?" The moment that baseline breaks, your open and reply rates drop and you start landing in spam or getting hard bounces. The people who scale cold email without burning their domains are not sending harder, they are running infrastructure that is authenticated, warmed up, rotated, and watched every day. Here is that infrastructure.

1. What cold email infrastructure actually is

It is four things working together. Sending domains (your main domain plus dedicated sending subdomains or secondary domains), the IP or ESP that actually delivers from them, a warm-up process that builds reputation before you hit volume, and rotation that spreads sending across domains and mailboxes so no single one takes the whole load. Most "cold email stacks" sell you the tooling. What they do not sell you is the monitoring that tells you a domain quietly broke at 3am, before the next campaign burns it.

2. How many sending domains do you need

Start with your main domain for low volume, then add dedicated sending subdomains (like mail.yourdomain.com or go.yourdomain.com) for your campaigns. Each subdomain carries its own reputation, so a bad campaign on one does not drag down your main domain. As you scale, add secondary domains and spread sending across them. A common rule of thumb: keep sending volume per domain low enough that you stay well under the volume that triggers spam complaints, and add a new domain before you need to push the current one past that line. The exact number depends on your list size and how fast you warm up, but the principle is always the same: never let one domain carry more than it can safely handle.

3. Authenticate every sending domain

Every sending domain and subdomain needs SPF, DKIM, and DMARC set up correctly, and they need to stay correct. This is where cold email stacks quietly fail. An SPF record breaks when you switch ESPs and forget to update the include. A DKIM key rotates and the old selector stops signing. A DMARC record that was p=none gets tightened by a provider and now rejects your own mail. Each of these is a silent, compounding failure that shows up as a sudden drop in deliverability with no obvious cause. The fix is not to set these up once and forget them, it is to check them on a schedule and alert the moment one fails. That is the whole job of a deliverability monitor.

4. Warm up before you send

A fresh domain has no reputation. If you send 500 cold emails from a brand new subdomain on day one, you will land in spam and possibly get blocked. Warm-up means sending a small, growing number of emails to engaged recipients over two to four weeks, so providers see a normal, human-like sending pattern before you scale. Most cold email tools include a warm-up module. The thing they do not tell you is that warm-up only works if the domain is authenticated. Warming up a domain with a broken SPF record teaches providers the wrong thing. Authenticate first, then warm up.

5. Rotation and IP reputation

Rotation is spreading your sending across domains, subdomains, and mailboxes so no single one is the obvious bottleneck. It also protects you when one domain does get flagged: you pause it, let it cool, and keep sending from the others. IP reputation matters too, especially if you send from your own IP instead of an ESP. A shared IP that other senders have abused will drag your deliverability down no matter how clean your domain is. If you are on a shared IP and your deliverability is inconsistent, that is usually why, and moving to a dedicated IP (or a cleaner ESP pool) is the fix.

6. The monitoring that keeps domains alive

This is the part most stacks skip. You have multiple sending domains, each with its own SPF, DKIM, DMARC, MX, TLS, and IP reputation. Any one of them can break between campaigns, and the break is invisible until your replies drop. A deliverability monitor re-checks every domain on a schedule and pings you the moment a record fails, expires, or a provider changes your sending IP. For an agency running many client domains, that is the difference between catching a broken SPF record in minutes and finding out from an angry client that their campaign went to spam. It is also the difference between a domain you recover and one you have to abandon.

Start with a free check on one domain

Run a free audit on one of your sending domains now and see the seven-check score plus the exact records to fix: cold email deliverability checker. When you are ready to watch every sending domain and client domain on a schedule, that is what the Agency tier is for, up to 25 domains with daily re-checks and alerts.

Related guides
Cold email domains: how many you need
Cold email warm-up: the right way
Cold email deliverability: how to stay out of spam
Why email goes to spam