How to warm up email domains

How to warm up email domains starts with restraint, not a warmup tool. Send a small number of relevant emails, increase volume slowly, and stop increasing it when bounces, complaints, or authentication problems move in the wrong direction.

The mistake I see most often is predictable: a team buys four domains, creates three mailboxes on each, then sends 40 cold emails from every inbox on the first day. They think the mailboxes are separate. Gmail and Microsoft see a new domain suddenly sending 480 messages.

That domain gets a reputation before the campaign has had a chance to prove it deserves one.

How to warm up email domains without guessing

For a new domain and new mailboxes, start with roughly 5 to 10 emails per mailbox per day. Hold that level for a few days. If authentication is clean, hard bounces stay low, and nobody is complaining, move to 10 to 15 per day. Increase again in small steps, usually around 20 to 30 percent at a time.

A five-person SDR team might use this pattern:

• Days 1 to 3: 5 to 10 emails per mailbox each day
• Days 4 to 7: 10 to 15
• Week 2: 15 to 25
• Week 3 onward: increase only when the data supports it

Treat that as a ceiling for decision-making, not a schedule you have to obey. A brand-new domain sending to 20 carefully chosen prospects is in a different situation from one sending 80 generic emails to an old export.

The useful unit is emails per mailbox, per domain, to a list you have actually checked.

Domain warmup isn't mailbox warmup

These terms get mixed together, and that confusion leads teams to make bad volume decisions.

Domain warmup builds a history for acme-analytics.com. Mailbox warmup builds a history for jordan@acme-analytics.com. The mailbox matters, but three new mailboxes under the same domain still share the domain's sending history.

So if three mailboxes each send 30 messages on Monday, the domain has sent 90 messages. Adding mailboxes doesn't make the volume disappear.

Artificial warmup networks are a separate issue. They send messages and replies between inboxes to create activity. That may make a dashboard look healthy, but it doesn't make an irrelevant prospecting campaign useful. Real recipients can still ignore the message, report it, or unsubscribe as soon as the campaign starts.

My view is pretty simple: warmup tools are optional, but list quality and authentication aren't. Teams often spend money simulating engagement while leaving a stale contact database untouched. That's backwards. Use warmup to establish a sensible sending pattern, not to disguise a bad ideal customer profile.

Fix the sending setup before you send anything

Authentication isn't a final check you do after the sequence is live.

Set up SPF for every service authorized to send mail. Configure DKIM so receiving providers can verify the message. Publish DMARC, using a monitoring policy first if the setup is new. Check that the visible From domain aligns with the authenticated domain wherever possible.

For a 12-person SaaS sales team, this means auditing more than the sales engagement platform. Marketing automation, CRM sequences, calendar tools, customer support software, and transactional email may all send under the company domain. One forgotten vendor with a broken DKIM record can create a problem that looks like poor copy.

Check the domain's MX records and website too. Confirm TLS is working, make sure tracking domains are branded where practical, and keep SPF within its DNS lookup limit. Review DMARC reports instead of publishing the record and forgetting about it.

Give recipients a clear unsubscribe path. This isn't just a compliance task. Someone who doesn't want another email should be able to stop the messages without marking them as spam.

What to send during the first week

Send the sort of email you plan to send later, just to a smaller and better-known audience.

Existing customers, partners, colleagues, and prospects with a genuine reason to hear from you are reasonable starting points. A short product update to 10 active customers is more useful than 10 fake replies generated by an inbox network. Keep the email plain. Give the recipient a clear reason for the message and an easy way to respond.

For a 30-person cybersecurity vendor launching a new outbound domain, I would choose 100 verified contacts across a week over 500 unverified addresses on Monday. The smaller group lets the team catch bad addresses, wrong roles, and confusing positioning before those problems become reputation signals.

The SDR team also needs to avoid obvious bursts. If every mailbox sends 25 messages at exactly 9:00 a.m., using the same subject line and the same link, you've created a pattern that is easy to detect and easy to repeat at scale. More importantly, you may be sending the same weak message to 25 people before anyone notices it isn't working.

Stop treating the calendar as the authority

The most damaging habit is doubling volume because the team reached day 14. A warmup plan is not a countdown timer.

Check hard bounces daily during the ramp. Keep them below 2 percent and investigate any sudden increase. A company selling compliance software to US fintechs should verify that contacts still work at firms that haven't changed domains, been acquired, or removed the role. Old exports and generic addresses create avoidable bounces.

Complaints matter more than open rates. Open data is noisy because of privacy features, image blocking, and unreliable tracking. A spam complaint means someone took an active negative action. If complaints rise, stop increasing volume. Review the audience, the message, and the unsubscribe path.

Your cold outreach should also make the selection logic obvious. A finance systems leader at a 200-person payments company that changed processors last quarter is a plausible audience for reconciliation software. A random list of operations executives isn't.

Warmup cannot compensate for weak targeting. No setting in an email platform changes that.

The signals that should control your next increase

Before raising volume, look at authentication results, hard bounces, complaints, delivery failures, replies, and provider warnings. Treat open rate as a loose directional signal, not as permission to send more.

Here’s a practical example. A 10-mailbox team moves from 150 total sends per day to 300. Hard bounces rise from 1.2 percent to 4 percent. Reverse the increase immediately. Remove risky contacts, check the data source, and verify authentication. Don't wait for a sequencing tool to label the domain unhealthy.

Google Postmaster Tools can help when you have enough Gmail volume. Microsoft SNDS may provide useful information too. Neither gives you a complete picture, so compare those signals with bounce and complaint data from your own sending platform.

A separate outbound domain can make sense for a 500-person SaaS company that wants product notifications to remain isolated from prospecting. Keep the domain clearly related to the company, authenticate it properly, and don't treat it as permission to send poor campaigns. It limits the blast radius. It doesn't make spam safe.

How long does domain warmup take?

Plan on two to six weeks for a new domain with new mailboxes to reach a stable operating volume. A small, engaged audience may let you move faster. An entirely cold campaign, an older domain with questionable history, or a weak data source may require longer.

Set the target from the team's actual capacity. If four SDRs can each write and review 20 useful emails a day, there is no reason to warm toward 100 per mailbox. That creates 400 messages the team can't personalize, inspect, or follow up on.

When performance drops, pause the ramp. Reduce volume, remove risky contacts, verify the records, and read the emails as a recipient would. A domain is ready for more volume when real recipients keep receiving the messages without a rise in bounces, complaints, or negative replies.