Cold Email Infrastructure: How to Set Up for Scale Without Burning Your Domains

Cold email infrastructure is a distinct engineering problem from marketing email or transactional messaging. When you're sending unsolicited email to prospects who haven't opted in, the technical stakes are higher: reputation is harder to build, providers are more suspicious of your traffic, and a single deliverability mistake can blacklist a domain you've spent months warming. Done correctly, cold email infrastructure allows you to run outreach at meaningful volume with acceptable inbox placement rates. Done sloppily, you burn domains faster than you can register them.

Never Send Cold Email From Your Primary Domain

The first rule of cold email infrastructure is protecting your primary business domain by never using it for cold outreach. If your company operates from yourbusiness.com, cold email goes out from a secondary domain — something like yourbusiness-hq.com, tryourbusiness.com, or a variation that still represents your brand without being the primary domain you depend on for everything else.

This isolation matters because cold email, even done well, carries more deliverability risk than permission-based email. Higher complaint rates, stricter filtering, and occasional blocklisting are all more likely when sending to cold contacts. If your primary domain takes those hits, your regular business email — customer support replies, invoices, onboarding messages — goes into spam folders too. The secondary domain contains the damage and preserves the domain your business actually depends on.

Plan to operate multiple cold email domains simultaneously and rotate them. When one domain's reputation degrades from volume or complaints, you rotate to a fresh one while the damaged domain rests and recovers. Most serious cold outreach operations maintain five to ten sending domains at any given time in various stages of warmup, active use, and recovery.

Domain and Mailbox Setup

Each cold email domain needs proper configuration before you send a single message:

• MX records pointing to an actual mail server — even if you're primarily sending rather than receiving, you need MX records so replies land somewhere. Domains with no MX records look abandoned and trigger immediate suspicion from filtering systems.
• SPF record listing your sending IP or relay service as an authorized sender for that domain
• DKIM with a valid signing key published in DNS for the domain
• DMARC at minimum p=none to start, so you can review aggregate reports and understand what authentication looks like before enforcing quarantine or reject
• A catch-all or dedicated reply mailbox so replies, out-of-office messages, and automatic responses are captured rather than bouncing back as undeliverable

Create one to three mailboxes per domain. Each mailbox that actually sends email should have a real name and a complete sender profile — generic mailboxes like noreply@ or team@ signal automation and suppress reply rates. Use names that match real people on your team wherever possible.

IP Warming for Cold Email

Warming IPs for cold email is more demanding than warming for permission-based sending because your recipients are less likely to engage positively. The fundamentals are the same — start slow, scale gradually, prioritize quality over speed — but the engagement signals you're generating are harder to achieve from a cold audience.

Start each new domain by sending to contacts where you have the highest confidence of some engagement: warm leads, people who've interacted with your brand in some way, conference attendees. Save the truly cold contacts for after the domain has some positive history. Even a small number of replies and positive engagement signals during warmup gives the domain a better baseline reputation than a large volume of ignored messages.

Typical warmup for a cold email domain: 10–20 sends per mailbox per day in week one, growing to 50–75 per day by week three or four. Sending more than 100 emails per mailbox per day consistently pushes into territory where mailbox providers start flagging the volume as automated, regardless of content quality. Respect that ceiling.

Content and Personalization for Deliverability

Deliverability for cold email depends partly on content signals. Spam filters evaluate message content alongside sender reputation, and mass-identical messages sent to different recipients are a strong signal of automation. Personalization at the individual level — not just a merge field with a first name, but genuinely variable content based on who you're writing to — improves both deliverability and reply rates simultaneously.

Avoid common spam filter triggers in cold email content:

• Excessive links — keep it to one or two per message at most
• Link shorteners and redirectors that obscure the final destination URL
• Images as the primary content — spam filters consistently score text-heavy messages better for cold outreach
• HTML-heavy formatting with multiple colors, fonts, and call-to-action buttons — plain text or minimal HTML outperforms heavy templates in cold email delivery
• Overuse of words that historically trigger spam filters: "free," "guarantee," "no obligation," "act now," "limited time"

Monitoring and Domain Rotation

Track the health of every cold email domain separately. Watch for increases in bounce rates, complaint rates, and deferral patterns from major ISPs. Set a bounce rate threshold — 3% is a reasonable ceiling — and pause a domain's sending immediately if it crosses that mark. Investigate before resuming, not after.

Subscribe to blocklist monitoring for each sending domain and IP. When a blocklist hit happens, stop sending from that asset immediately, identify the cause, and address it before attempting delisting through the blocklist operator's process.

Have a documented rotation plan ready before you need it. When a domain needs to rest, the next warmed domain should already be ready to take over. Operations that react to domain burnout after the fact — scrambling to register and warm a replacement while outreach is halted — lose momentum at the worst possible time. Treat domain rotation as a planned, ongoing operational process, not an emergency response.

If you're building cold email infrastructure that needs reliable SMTP relay with proper authentication and monitoring built in, MailDog's SMTP service provides the foundation. Review the MailDog blog for related reading on volume ramp-up strategy and dedicated vs shared IP decisions. For questions about infrastructure setup tailored to cold outreach, contact the MailDog team.