How Long Should You Warm Up a New Domain for Cold Email? The 30-Day Ramp

Why can't a new domain send at full volume on day one?

Because mailbox providers have no history on it. A new domain blasting hundreds of cold emails looks exactly like a spammer spinning up a throwaway domain, and filters treat it that way.

Think of it like a brand-new engine. Redline it on the drive home from the dealer and something breaks. Gmail says it plainly in its Email sender guidelines: start with a low sending volume to engaged users, increase slowly, and avoid sudden spikes if you don't have a history of sending large volumes.

What is sender reputation, and what builds it?

Sender reputation is the score mailbox providers keep on your domain and sending addresses. You never see the score. You see what it does: inbox, promotions or spam.

• Builds it: replies, emails moved out of spam, messages people read and keep.
• Burns it: bounces, spam complaints, mail deleted without being read, sudden volume spikes.

The hard line to know: Google and Yahoo require every sender to keep spam complaints below 0.3%, and Google asks for under 0.1%. On a new domain you have no cushion, so one sloppy send can put you in the spam folder before you book a single meeting.

The play: what does a 30-day warmup ramp look like?

Here's our starting ramp, per mailbox. It's a conservative practitioner guideline, not a benchmark: Google gives no numbers, only the rule to start low and increase gradually. We ramp toward a steady-state cap of about 30 emails per mailbox per day, the same safe-send number our Outbound Calculator uses (see also cold emails per day per inbox). Slow down if anything moves the wrong way.

Swipe to see more →

Step by step:

1. Authenticate first. SPF, DKIM and DMARC before a single send; see SPF, DKIM and DMARC explained. Warmup can't fix a domain that fails authentication.
2. Week 1: send to people who will reply. Short, human messages. No links, no images, no tracking in week one. Reply to their replies.
3. Week 2: add your best prospects. Only your top-verified, highest-fit segment. This isn't the week for the "maybe" list. Keep the emails short and relevant, as in cold emails that work.
4. Week 3: run real campaigns and test placement. Send to a few seed addresses you own on different providers and see where you land. Landing in spam? Hold volume and fix that first.
5. Week 4: reach your cap and stay there. About 30 a day per mailbox is where we stop. Keep watching complaints and replies, and judge replies against the reply rate benchmark. Need more volume after warmup? Add mailboxes and domains, don't push each mailbox harder.
6. Hold, don't push. If complaints rise, placement drops or replies dry up, stay at the current week's volume until the numbers recover.

Why does engagement matter more than volume?

Volume alone doesn't warm a domain. Engagement does. A reply tells the provider real people want your mail. So does someone dragging your email out of spam or promotions into the inbox.

That's why week one goes to people who will answer. Ten emails that get five replies do more for a new domain than a hundred that get ignored.

Do automated warmup tools work?

They help, but they don't replace the ramp. These tools connect your mailbox to a network of other mailboxes that send each other messages, reply, and mark them as "not spam," so your domain shows steady engagement without you doing it by hand.

Our honest read: they're useful for keeping a mailbox active between campaigns and for adding engagement during the ramp. But network traffic isn't real buyers replying, and it can't fix bad data or bad targeting. Use it as a supplement to real engagement, never as permission to skip the 30 days.

Worked example: what does warming up a new sending setup look like?

Illustrative example.

Priya runs outbound for a five-person team. She buys a secondary domain for cold email so the main company domain stays protected, and sets up three mailboxes on it. Authentication passes on day zero.

• Week 1: each mailbox sends 5 emails a day to teammates, friendly customers and her own test addresses. About 75 emails across the three mailboxes over the work week, mostly answered.
• Week 2: 10 a day per mailbox, mixing in her best-verified tier-1 accounts. About 150 emails over the week. Replies keep coming, no complaints.
• Week 3: she moves up to 20 a day, but her mid-week placement test shows one of three seed inboxes sending her to spam. She drops back to 10 a day for four days, cleans a batch of unverified addresses out of the next campaign, and retests. Clean. She moves up.
• Week 4: 30 a day per mailbox, 90 a day across the team setup. When the team wants more, she adds mailboxes instead of pushing these three past 30.

The team wanted 90 emails a day on day one. Priya got there in about a month and still had a domain worth sending from. Her four-day pause cost less than a burned domain and a restart.

What are the most common domain warmup mistakes?

• Sending your first campaign on day one. The classic. A domain with no history plus a big spike is a spam signal.
• Warming up with cold prospects. Week one is for people who reply. Strangers who ignore you teach providers the wrong lesson.
• Adding links, images and tracking too early. Keep week-one messages plain.
• Using unverified lists during the ramp. Bounces on a new domain hurt more than on an established one.
• Pushing through warning signs. A rising complaint rate is a stop sign, not a speed bump.
• Warming up your main company domain for cold outreach. Use a separate sending domain so a mistake can't hit the domain your customers and invoices depend on.
• Treating an automated warmup tool as the whole plan. It supports the ramp. It isn't the ramp.

Try it: Planning volume for after warmup? The Outbound Calculator shows how many emails you need for your meeting target, so you know how many warmed mailboxes to have ready. Pick the Stack covers what to look for in the sending layer: separate domains and warmed inboxes. Automating volume with an AI tool? Read what an AI SDR is first, and never point it at a cold domain.