Cold Email Sending Infrastructure at Scale: 1 to 50 Domains

Sending 30 cold emails a day from a single domain is straightforward. Sending 1,500 cold emails a day across a portfolio of 50 domains with proper warmup, rotation, and verification is an entirely different operation. The difference is not just scale. It is infrastructure design.

Most guides cover the basics: buy a domain, set up SPF/DKIM/DMARC, warm it up, start sending. That works for a solo founder doing light outreach. But if you are running outbound at scale, whether for your own company or as an agency managing multiple clients, you need a systems-level approach to cold email infrastructure.

Here is how to build it from the ground up.

Why Multiple Domains Are Necessary

The core constraint of cold email is sending volume per inbox. Industry best practice caps sending at 30-50 emails per day per inbox. Going higher than that increases the risk of spam placement and reputation damage, regardless of how good your list quality is.

Simple math: if you want to send 500 cold emails per day and each inbox handles 40 emails, you need about 13 inboxes. If you put 2-3 inboxes per domain, that is 5-7 domains. If you want to send 1,500 per day, you need 38-50 inboxes across 15-25 domains.

Using multiple domains also protects your primary business domain. You should never send cold email from your main company domain (the one your website runs on, the one your team uses for daily business communication). If a cold email domain gets flagged or its reputation crashes, you can abandon it without affecting your core business operations.

Domain diversification also provides redundancy. If one domain gets temporarily blocked at Outlook, your other domains continue delivering. The campaign keeps running while you address the issue with the affected domain.

Choosing and Purchasing Domains

Your cold email domains should be related to your brand but distinct from your primary domain. Common patterns include variations of your company name, abbreviated versions, or descriptive alternatives.

If your company is "acmesolutions.com," your cold email domains might be things like "acmesolutions.io," "getacme.com," "acme-outreach.com," or "tryacme.io." The names should be professional and recognizable if a prospect looks them up, but separate from your primary domain.

Purchase domains from mainstream registrars like Namecheap, Google Domains, or Cloudflare. Costs run $10-15 per year per domain. At 20 domains, that is $200-300 per year, a negligible cost relative to the sending capacity you gain.

Check the history of any domain before purchasing. Some expired domains carry bad reputation from previous owners. Use tools like MXToolbox to check if a domain is on any blocklists before you buy it.

Set up a simple landing page on each domain. It does not need to be elaborate, but it should exist. A prospect who receives your cold email and visits the sending domain should see a professional page that confirms your company is real. A domain with no website raises suspicion.

Email Hosting Setup

Each domain needs email hosting. The two main options are Google Workspace and Microsoft 365.

Google Workspace costs $6-7 per user per month. Microsoft 365 runs about the same. For cold email domains, you typically set up 2-3 email accounts per domain (e.g., sarah@, mike@, team@).

At 20 domains with 2 accounts each, you are looking at 40 email accounts. At $7 per month per account, that is $280 per month for email hosting. Factor this into your cost calculations.

Google Workspace is generally preferred for cold email because Gmail has more predictable deliverability behavior and better inbox placement rates overall. Microsoft 365 works too, and some senders use a mix of both to diversify their sending infrastructure across providers.

DNS and Authentication Configuration

Every domain needs proper email authentication configured before you send a single email. This means SPF, DKIM, and DMARC records for each domain.

SPF records authorize which servers can send email on behalf of your domain. For Google Workspace, you include Google's SPF entry. For Microsoft 365, you include Microsoft's. If you use a cold email platform that sends through its own servers, include their SPF entry too.

DKIM signing is usually configured through your email hosting provider. Google Workspace and Microsoft 365 both provide DKIM key generation and DNS record instructions. Follow their setup guides for each domain.

DMARC should start at p=none for new domains. This tells receiving servers to report on authentication results without taking action on failures. Once you have confirmed everything is passing correctly (usually after 2-4 weeks of monitoring), you can tighten the policy to p=quarantine and eventually p=reject.

At scale, managing DNS records across 20-50 domains becomes a task in itself. Use a single DNS provider (Cloudflare is popular for this) and maintain a checklist or template for the records each domain needs. Consistency across domains prevents configuration drift that leads to authentication failures.

The Warmup Phase

Every new domain needs warmup before it can send real campaigns. The standard timeline is 4-6 weeks of warmup activity before transitioning to live outreach.

Use a warmup tool (Warmy, Instantly's built-in warmup, MailReach, or similar) to generate engagement signals on each inbox. The tool sends emails from your inbox to its network of real accounts, and those accounts reply, open, and interact with the messages. This builds initial positive engagement history with mailbox providers.

If you are warming up 20 domains with 40 inboxes simultaneously, warmup tool costs add up. Budget $200-500 per month for warmup during the initial setup phase. Some cold email platforms include warmup in their pricing, which simplifies this.

Stagger your domain purchases and warmup. Do not buy 20 domains and start warming all of them on the same day. Buy 5-10, start warmup, then add more domains over the following weeks. This prevents you from having all your domains at the same maturity stage, which is both a risk management and a practical advantage (you can start sending from the first batch while later batches are still warming up).

Email Verification Before First Send

Before any domain sends its first real campaign, the prospect list must be thoroughly verified. This is non-negotiable.

A new domain sending its first real campaign is at its most vulnerable. Its reputation is fragile, built only on warmup signals. A batch of bounces from unverified addresses can damage that nascent reputation quickly.

Run your prospect list through standard email verification to remove invalid and disposable addresses. Then run the catch-all segment through a specialized tool like CatchallVerifier to determine which catch-all addresses are actually deliverable. Given that 15-40% of B2B email addresses sit on catch-all domains, skipping this step means sending your fragile new domains into a minefield.

The cost of verification is trivial compared to the cost of burning a domain. Replacing a burned domain means purchasing a new one, setting up hosting, configuring DNS, and spending another 4-6 weeks on warmup. That is weeks of lost sending capacity, all because you skipped a verification step that costs fractions of a penny per email.

Domain Rotation Strategy

Once your domains are warmed up and sending, you need a rotation strategy that distributes volume evenly and manages risk.

Round-robin rotation is the simplest approach: assign prospects to domains sequentially. Prospect 1 gets domain A, prospect 2 gets domain B, prospect 3 gets domain C, and so on. This ensures even distribution of volume across all domains.

Provider-weighted rotation is more sophisticated. Since Outlook has worse deliverability than Gmail, you might assign more domains to handle your Outlook-heavy prospects, reducing per-domain volume to Microsoft addresses. This compensates for Outlook's tighter filtering by keeping individual domain volume low.

Rest days improve domain health. Rather than sending from every domain every day, consider rotating domains on a schedule where each domain gets 1-2 rest days per week. This makes sending patterns look more natural and gives the domain's reputation time to stabilize between sending batches.

Monitoring at Scale

With 20+ domains, you cannot manually check Google Postmaster Tools for each domain every day. You need systems for monitoring.

Set up Google Postmaster Tools for every sending domain. Use the API or a dashboard tool that aggregates reputation data across all your domains into a single view.

Track per-domain metrics: bounce rate, reply rate, complaint rate (where available), and domain reputation. Set alert thresholds: any domain exceeding 2% bounce rate, 0.3% complaint rate, or dropping below Medium reputation should trigger immediate investigation.

Keep a domain health spreadsheet or dashboard that tracks each domain's age, warmup status, current daily volume, reputation score, and any incidents. This operational view helps you make quick decisions about which domains to scale up, scale back, or retire.

Cost Analysis

Let us map out the full cost of a 20-domain cold email infrastructure sending 800 emails per day (40 per inbox, 40 inboxes).

Domains: 20 domains at $12/year = $240/year ($20/month)

Email hosting: 40 accounts at $7/month = $280/month

Cold email platform: $100-300/month depending on tool and tier

Warmup: $0-200/month (often included in cold email platform)

Email verification: Variable based on list size. At 20,000 emails/month, roughly $50-100/month

Landing pages: Minimal, can use Carrd or similar at $19/year for multiple domains

Total monthly operating cost: approximately $450-900 per month for 800 emails/day capacity, or roughly 16,000 cold emails per month.

Cost per cold email sent: approximately $0.03-0.06. Cost per reply (at 5% reply rate): approximately $0.56-1.12. Cost per meeting (at 20% reply-to-meeting rate): approximately $2.80-5.60.

Those unit economics make cold email one of the most cost-effective outbound channels available, provided the infrastructure is built and maintained properly. The key word is "maintained." Cutting corners on verification, warmup, or monitoring to save a few hundred dollars per month can destroy domains that took weeks to build, costing far more in lost capacity than the savings were worth.

Build the infrastructure right from the start. It is one of those investments where doing it properly the first time is significantly cheaper than fixing it later.