Cold email domains: how many you need, how to rotate them, and how to keep them out of spam

Cold email runs on a pool of domains, not one. Your main domain is for your brand, your site, and your real customers. Cold email is a separate workload with separate domains, because the sending behavior that works for cold email (high volume, low engagement, purchased lists) is exactly what gets a domain flagged if it is on your brand domain. This guide covers the domain math, how to set each one up, when to rotate, and how to keep the pool out of spam.

How many domains you need

The number comes from three constraints: the volume you want to send, the warm-up time each domain needs, and the rotation cycle. A domain that is not warmed up cannot take full volume, and a domain that is warmed up has a limited useful life before its reputation degrades.

• Warm-up time. A fresh domain needs roughly 2 to 4 weeks of warm-up before it can take meaningful volume. During warm-up you send small, rising amounts to real, engaged recipients.
• Volume per domain. A warmed-up domain can typically take on the order of 30 to 50 cold emails per day per mailbox, with a few mailboxes per domain. Go higher and the engagement rate drops and the spam risk climbs.
• Useful life. A cold email domain degrades over time. Most teams rotate a domain out every few months, before the reputation is too far gone to recover.

The math: divide your target daily volume by the per-domain daily cap, then add a buffer for warm-up and rotation. If you want to send 500 cold emails a day at 40 per domain, that is about 12 to 13 active domains, plus a few more warming up or in rotation. Teams that run less volume need proportionally fewer.

How to set up each domain

Every domain in the pool needs the same authentication and reputation setup, or it will not send. This is the part that is easy to get wrong and hard to debug later.

• SPF. The domain's SPF record must list the sending IP or the ESP that sends for it. Keep the record under the 10-DNS-lookup limit. Check the SPF, or generate the record.
• DKIM. The selector your provider uses must have a matching DNS record, and the key must be 2048-bit. Check the DKIM.
• DMARC. Start at p=none with reporting, then tighten it as the domain proves itself. Check the DMARC.
• PTR. The sending IP must have a reverse DNS record that matches the forward record. Most ESPs handle this, but if you send from your own IP, set it.
• IP reputation. The sending IP must not be on a blocklist, and it should not be shared with other senders who can drag it down. Check the IP.

The fastest way to verify all of this on a new domain is the free audit, which scores the whole stack and tells you the exact record to add before you start sending.

When and how to rotate

Rotation is not optional. A cold email domain that is not rotated will eventually get flagged, and recovering a flagged domain is slower than starting a new one. The goal is to retire a domain while it is still healthy, not after it is already in trouble.

• Watch the engagement rate. A steady drop in open and reply rate is the first sign the domain is degrading. If it falls below your baseline for a week or two, start the next rotation.
• Watch the spam complaints. Any spike in complaints is a hard signal to rotate out, not wait.
• Hand off the volume. Move the volume to a warmed-up domain before you retire the old one. Do not let the old domain carry the volume while the new one is still warming up.
• Keep a warm bench. Always have at least one domain in warm-up, ready to take over. If you run out of warm domains, you have to stop sending or risk the active ones.

How to keep the pool out of spam

The pool is only as strong as its weakest domain. One flagged domain can hurt the whole program if the domains share an IP or if the rotation is sloppy.

• Warm up every domain before it takes volume. No exceptions. A domain that skips warm-up starts with a low reputation and gets filtered. See the warm-up guide.
• Keep the list clean. Bounces and complaints poison the domain. Prune the list and honor unsubscribes the same day. What a bad bounce rate means.
• Isolate the sending IP. If you can, send from an IP that is not shared with other senders. A shared IP means other senders can drag your reputation down.
• Check the domains and IPs regularly. A blocklist hit or a broken record will not announce itself. Check the domain and check the IP on a schedule.

How to monitor the pool

A pool of domains is a pool of moving parts. A record breaks on one domain, an IP gets listed, a rotation goes wrong, and you do not notice until the engagement rate drops. The fix is to check every domain in the pool on a schedule, not just the ones you remember.

That is what the Agency plan is for: it monitors up to 25 domains, checks the full stack on each one daily, and alerts you the moment a record breaks or an IP gets listed. For a pool of cold email domains, that is the difference between catching a problem early and finding out from your engagement rate.

Run the free audit on your first domain now. It scores the whole stack and points at the exact record to fix first. Then see the Agency plan →