How long to warm up a cold email domain: the 2026 operator answer

How long does it really take to warm up a cold email domain? 30 days minimum in 2026 because Google now flags younger domains with a yellow banner that tanks reply rates. The schedule that respects the calendar and the signals (spam under 0.08 percent, bounce under 2 percent) is what graduates a domain. The calendar is the input. The pattern is the output.

By
Thibault Garcia
28/5/26
Key Findings
30 DAYS IS THE 2026 FLOOR, NOT 14

Google now flags any domain younger than 30 days with a yellow banner that drops reply rates before the email is even read. Two-week warm-up is legacy advice that no longer holds. Buying pre-warmed infrastructure is the accepted shortcut when the 30 days is not available.

TRUST SIGNALS BEAT THE CALENDAR

A domain warms up when mailbox providers see authenticated mail, controlled volume, real engagement, and clean negative signals. The calendar is the input. The pattern is the output. Two domains the same age can end up with completely different reputations depending on what they sent and to whom.

LIST QUALITY DECIDES THE TIMELINE AS MUCH AS DAYS

A strong list with real relevance supports a faster reputation build. A weak list stretches the timeline far beyond the calendar number. Warm-up cannot fix a bad database. List re-validation on anything older than 3 months is non-negotiable.

SPAM UNDER 0.08 PERCENT, BOUNCE UNDER 2 PERCENT ARE THE HARD THRESHOLDS

Cross either and reputation damage takes weeks to undo. Reachly's working benchmarks on client domains: bounce under 3 percent, deliverability score above 97 percent. Below either, the domain has not graduated regardless of the warm-up schedule.

WARM-UP IS ENTRY COST, NOT THE FINISH LINE

A warmed domain gives you permission to begin. List quality, copy, follow-up discipline, and reply handling decide whether the warm-up pays off. The chain is domain to list to copy to follow-up to sales process. Any break in the chain and inbox placement just helps more bad outreach get seen.

Two to four weeks is the answer the rest of the internet will give you. That answer is incomplete, and acting on it is one of the fastest ways to burn a fresh domain.

The job is not running out a clock. The job is building trust with Gmail, Outlook, and the other mailbox providers so your emails land in the inbox instead of spam. If someone tells you to wait 14 days and start blasting, they are giving you calendar advice for a reputation problem. We have rebuilt enough scorched domains for new Reachly clients to know the difference matters.

This guide is the operator version. The short answer first, then the real answer, then the schedule, the infrastructure choice, and the signals that decide whether the domain is actually ready or just old enough to send.

The short answer and the real answer

The conventional answer: a brand-new domain usually needs 2 to 4 weeks, some teams stretch to 6 to 8 weeks for a more conservative ramp, and Microsoft's own guidance says maximum deliverability can take 4 to 8 weeks depending on target volume and engagement.

That is the short answer. It is also the answer that gets people in trouble.

A domain does not warm up because you left it alone for a few weeks. It warms up because mailbox providers saw a pattern they trust: authenticated mail, controlled sending volume, real engagement, and no ugly signals like spam complaints or hard bounces.

Two companies can buy domains on the same day and end up with completely different outcomes. One sends low volume to clean, responsive contacts and ramps carefully. The other sends too much, too fast, to a weak list. Same age. Different reputation. The calendar did not decide which one earned inbox placement.

The popular "just warm it for 14 days" advice is lazy because it skips the only part that matters. You are not trying to hit a date. You are trying to prove to mailbox providers that your domain behaves like a legitimate sender. If you want a second opinion on the mechanics, this email domain warming guide reinforces the same idea: gradual ramping beats arbitrary timelines.

Here is the framing that actually helps. Stop asking "how many days?" Start asking "have I earned enough trust to increase volume without damaging the domain?" Once you think that way, the rest of the process gets simpler.

Two weeks of warmup is the legacy advice. Thirty days is the 2026 number. Google now flags any domain younger than 30 days with a yellow banner above your email, and that banner tanks reply rates before the prospect even reads the first line. We treat 30 days as the floor for every new client domain. Buying pre-warmed infrastructure is the accepted shortcut when 30 days is not on the table.

Thibault Garcia
Thibault Garcia Founder, Reachly

What domain warm-up actually is

People call it warm-up. What you are really doing is reputation building.

A new sending domain starts with no track record. Mailbox providers do not know if you are a real business sending relevant outreach or a spammer running a fresh domain. So they watch your behavior closely, especially in the first month. The closest analogy is a credit file. No history does not mean you are bad. It means nobody trusts you yet.

Technical deliverability checklist

Strong technical foundation
Essential for email trustworthiness
Enables Verifies Enforces
SPF
Sender Policy Framework
Record typeTXT
PurposePrevent spoofing by specifying which mail servers can send email for your domain.
ActionList approved IP addresses or hostnames authorized to send email.
DKIM
DomainKeys Identified Mail
Record typeTXT
PurposeVerify that the email content was not altered in transit and is from an authorized sender.
ActionPublish a public key and sign outgoing emails with the corresponding private key.
DMARC
Domain-based Message Authentication, Reporting and Conformance
Record typeTXT
PurposeProvide policy instructions to receiving servers and receive reports on email authentication.
ActionPublish a policy (none, quarantine, or reject) and specify reporting addresses.

Providers are not judging your domain on one thing. They are watching a pattern.

Authentication is in place. If SPF, DKIM, and DMARC are not set up properly, you look suspicious before content even gets evaluated. Volume changes are controlled. Sudden spikes look risky. Steady behavior looks normal. Recipients react like humans. Opens, replies, and natural engagement tell providers that your mail is wanted. Negative signals stay low. Spam complaints and hard bounces tell providers the opposite.

This is why warm-up success depends on recipient engagement rather than calendar time, and why recent deliverability guidance increasingly recommends throttling volume across 30 to 60 days and continuing warm-up activity for as long as the domain is used for sales and marketing.

Founders usually rush warm-up for one reason. Pipeline feels urgent. That urgency creates the exact behavior mailbox providers hate. A new domain appears, starts sending hard, and gets mixed engagement because the list or the copy was not ready. From the provider side, that is not a growth team moving fast. That is a sender who has not earned trust. The rushed launch does not save time. It burns the domain and forces you to spend longer recovering.

List quality changes the answer too. A strong list with real relevance can support a faster reputation build. A weak list can stretch the timeline far beyond what the calendar says, even on a domain that is technically old enough. Reachly's piece on domain reputation for cold email connects the technical setup with the actual sending behavior. That is the part many teams separate when they should be looking at it as one system.

Your technical foundation for deliverability

Before you send anything, fix the plumbing.

A lot of "warm-up problems" are not warm-up problems. They are setup problems. The domain was never authenticated properly, tracking was messy, or the sending environment looked inconsistent from day one. No volume schedule fixes that. You have to fix it once, then build on it.

You need the three records above in place before warm-up starts. If any of them are missing or broken, warm-up gets harder because mailbox providers cannot confidently verify who sent the message. You are asking for trust while failing the basic identity checks.

What good setup looks like in practice is simple. One sending setup per mailbox group, no random mix of tools and routes unless you know exactly how each one authenticates. Branding consistent between domain, sending identity, and reply handling. A custom tracking domain when your tool supports it, which keeps the sending environment cleaner than the generic shared tracking domains that get associated with spam patterns.

💡
Operator insight. Technical setup is boring right up until it ruins a good campaign. We have audited new client domains where SPF was published with a typo, DKIM was pointing at a decommissioned key, and DMARC was missing entirely. Volume looked fine. Inbox placement was sitting at 40 percent. None of that is a warm-up problem. It is a setup problem that warm-up made visible.

A few common mistakes that waste good domains. Skipping authentication checks before launch because the records "should have propagated." Using your main company domain for early cold outbound, which ties any reputation risk directly to the primary brand. Sending links too aggressively in the first 7 days, which makes natural human mail look like a campaign. Layering multiple automation tools on top of each other before any of them have settled, which makes troubleshooting impossible when something breaks.

For a broader reference point, these email deliverability best practices cover the non-obvious setup details that tend to get missed. Reachly's own write-up on cold email deliverability is a closer fit if you want a view tied specifically to outbound execution rather than newsletter sending. Our pillar piece on email deliverability covers the full infrastructure stack from authentication through ESP-to-ESP matching.

A practical warm-up schedule and volume plan

The right answer is rarely "14 days." Warm-up ends when the domain handles the volume you need without bad signals. That usually takes several weeks, but the calendar matters less than the pattern. Clean setup, tight lists, healthy engagement: you move faster. Thin replies, creeping bounces, slipping placement: the schedule stretches.

Microsoft's guidance puts the upper bound at 4 to 8 weeks for maximum deliverability and recommends increasing volume in controlled stages, with each step capped at about 1.5x the previous one. That is a useful benchmark. The Reachly floor is 30 days minimum because of the under-30-day yellow banner Google now adds.

4-week email warm-up schedule

1
Week 1
Focus
Low volume, high engagement
Volume per mailbox
5 to 10 emails per day
Audience
Highly engaged contacts only
2
Week 2
Focus
Gradual increase
Volume per mailbox
10 to 15 emails per day
Audience
Expand the audience slightly
3
Week 3
Focus
Moderate ramp-up
Volume per mailbox
Hold at the Google or Outlook daily cap
Audience
Introduce more segments
Week 4
Focus
Approaching cold outbound volume
Volume per mailbox
Google 15 per day, Outlook 10 to 12
Audience
Consolidate winning practices

Volume is not the actual target. Stable trust is. The practical rule is to increase only when the current level is holding up. Microsoft also ties warm-up speed to recipient quality. Weeks 1 to 2 should go to people who opened or clicked in the last 30 days. Weeks 3 to 4 can expand to recipients active in the last 60 days. During the first 6 weeks, avoid people with no engagement in the last 90 days. Better recipients create better signals, and better signals buy you the right to scale.

Here is the four-stage schedule we run for new client domains.

Stage Days Daily volume per mailbox Audience focus
OpeningDays 1 to 35 to 10 emailsHighest-confidence contacts only. Past customers, friendly partners, warm relationships
Early buildDays 4 to 1010 to 20 emailsReplies, opens, placement holding. Plain-text style. Minimal links
Controlled expansionWeeks 2 to 4Step up by ~1.5x at each stable plateauMore mailboxes or higher volume. Hold each stage 2 days before increasing
Cold outbound rampWeeks 4 to 8Cap at Google 15 / Outlook 10 to 12 per mailbox per dayReal prospecting only after the domain has shown stable behavior at lower volumes

How Reachly coordinates this at the campaign level: one ops lead owns infrastructure, one strategist owns audience selection per stage, and Smartlead handles ESP-to-ESP matching automatically. Google sends to Google, Outlook sends to Outlook. Mixing the two is one of the silent reasons placement drops mid-warm-up.

Three signals decide whether you move up, hold, or step back at any stage. Replies and natural engagement, where real responses matter more than vanity open rates. Bounces and technical errors, where a spike usually means the list or the setup is weaker than you thought. Inbox placement trends, where mail drifting toward spam or promotions is the early warning that more volume will make things worse, not test them.

If those signals stay clean, keep going. If they soften, pause at the current level. If they get worse, reduce volume and fix the cause before sending more. There is no scenario where sending more on a slipping domain produces better data. It produces a worse domain.

Manual warm-up gives you more control over who gets emailed and why. That matters because recipient quality decides the timeline more than the schedule does. Automated warm-up tools help with consistency, especially across several inboxes, but they do not fix bad targeting, weak copy, or a list pulled from the wrong source. A domain can look fine inside a warm-up tool and still struggle the minute real campaigns hit low-intent prospects. The best teams use both, then judge readiness by real campaign behavior, not by whether a tool says the domain is "warmed."

Choosing your sending infrastructure

The infrastructure question matters more than people think. Not because it is complicated, but because the wrong choice creates risk you did not need to take.

The usual decision is whether to send from a brand-new domain or from a subdomain of your main brand. Either can work. The trade-off is isolation versus continuity.

Domain choice: new vs subdomain

N

New domain

  • +Isolates reputation from the main brand domain
  • +Fresh start with no inherited risk
  • +Branding flexibility for outbound-specific identities
  • !No inherited trust history
  • !Full 30-day warm-up floor applies before any volume
  • !No brand recognition advantage in the inbox
S

Subdomain

  • +Inherits some trust from the parent domain
  • +Faster activation when the parent domain is established
  • +Brand consistency for prospects who recognize the parent
  • !Reputation risk spills back to the main brand
  • !Less isolation when something goes wrong
  • !Adds DNS and routing complexity
?

Decision framework

Match the choice to your risk tolerance, sending volume, and how much brand sensitivity the primary domain carries.

Warm-up duration is influenced by domain history. Established domains can compress to 1 to 2 weeks of activation. New domains hold to the 30-day floor minimum, and cautious teams wait closer to 3 months before pushing full-scale outbound from a fresh asset.

Choose a new domain when you want isolation (the safer move for founders protecting the main site), when you are testing outbound hard (more experimentation means more need for separation), or when you have multiple reps or product lines running campaigns simultaneously. Choose a subdomain when brand consistency matters more, the outbound motion is tightly controlled, and you understand the spillover risk. This second option is not for teams that treat deliverability as an afterthought.

The Reachly default is dedicated secondary domains separate from the main brand, with mailboxes warmed before any real outbound runs. That is not magic. It is the safer operational model when the goal is to not tie early experimentation to the core domain.

How to know when your domain is ready

The calendar does not decide this. Your data does.

A domain is ready when the signals stay clean as volume rises. Staged increases without complaints, bounce issues, or obvious placement problems means you are moving in the right direction. If those signals worsen, you are not done, even if the schedule says you should be.

There are two numbers you should treat as hard thresholds during warm-up. Spam rate must stay below 0.08 percent. Bounce rate must stay below 2 percent. These are the limits Customer.io domain warming guidance calls out and the ones every deliverability team we work with treats as red lines. Cross either and the reputation hit takes weeks to recover, sometimes longer.

That tells you two important things fast. First, poor list quality can ruin warm-up even with perfect technical setup. Second, "sending more to test it" is the wrong response when those metrics move the wrong way.

Beyond those two hard thresholds, watch reply quality (real people replying in a normal way, not responses drying up as volume grows), bounce patterns (a few isolated issues are normal, repeated hard bounces point to list or verification problems), inbox placement checks via tools like GlockApps or Mail-Tester, and domain hygiene more broadly. A resource on protecting your domain's online identity is useful for spotting reputation issues that show up outside the mailbox itself.

Before scaling real campaigns, ask three questions. Are negative signals stable (spam and bounce under control)? Can the domain handle staged increases (every increase is met with steady metrics)? Is the list clean enough for cold outbound (warm-up cannot fix a bad database)? If you want a practical checklist for placement and recovery once you are sending real campaigns, this Reachly guide on how to avoid the spam folder in cold email pairs well with the thresholds above.

Do not graduate a domain because the schedule ended. Graduate it because the data stayed clean. Reachly's bounce rate target on client domains is under 3 percent. Deliverability score above 97 percent. Below either of those, the domain is not ready for full-volume campaigns regardless of what day on the calendar it is.

Your warmed domain is just the start

A warmed domain gives you permission to begin. It does not create pipeline on its own.

What happens next decides whether the setup work paid off. Clean lists, tight segmentation, credible copy, and fast human reply handling matter more than the fact that the domain completed a warm-up schedule. If those pieces are weak, inbox placement just helps more bad outreach get seen.

That is the part a lot of founders miss. They ask how many days warm-up takes, hit the number, then assume they are safe to scale. Readiness was never just a calendar milestone. It was a trust milestone. Mailbox providers form that trust from your setup, your sending behavior, and the way recipients react when real campaigns start.

We have seen a well-configured domain hold up at modest volume because the list was verified, the targeting was narrow, and the copy matched the prospect. We have also seen a fully warmed domain struggle inside a week because the team loaded a broad scraped list and pushed generic messaging. Same warm-up age. Very different outcome.

That is why warm-up should be treated as entry cost, not the finish line. A strong outbound system works as a chain. Domain health gets you placement. List quality gets relevance. Copy gets attention. Follow-up gets replies. Sales process gets meetings. If any of those break, the chain breaks. The modern outbound sales strategy post covers how the chain holds together across cold email, LinkedIn, and cold calling. The cold email best practices piece covers the reply-rate side of the chain in detail.

Protect the domain like an asset once it is ready. Start with your best segment. Keep daily volume controlled. Watch reply quality closely. If positive replies stay healthy and negative signals stay low, increase carefully. If complaints, hard bounces, or silence show up after a volume jump, fix the list or the offer before you send more.

Choosing your sending infrastructure

More control and flexibility versus more complexity and responsibility. The right choice depends on your resources, priorities, and risk tolerance.

Pros
Volume capacity
Match sending capacity to your growth without hitting platform-imposed ceilings.
Full control
You own your IPs, domains, and reputation. Complete control over decisions and changes.
Customization
Tailor the setup to your exact routing, segmentation, and integration needs.
Advanced analytics
Deeper visibility into performance and the ability to build custom dashboards and reports.
Compliance and data ownership
Easier to meet specific compliance requirements and keep your data inside your environment.
Cons
Complex setup
Requires upfront planning, configuration, and testing to get authentication and routing right.
Ongoing maintenance
You are responsible for infrastructure, monitoring, updates, and troubleshooting.
Deliverability risk
You own your reputation. Missteps can lead to blocking, spam foldering, or IP and domain issues.
Higher costs
Infrastructure, tools, monitoring, and talent add up over time.
Technical overhead
Requires specialized expertise and ongoing attention from your team.

How Reachly handles domain warm-up for clients

The work we hand to clients is operational. Setting up SPF, DKIM, DMARC, and custom tracking. Buying or registering the secondary domain. Warming the mailboxes for 30 days before any cold outbound runs. Running the staged volume increases. Watching the spam and bounce thresholds. Pausing and fixing when the signals soften.

Most internal teams do not have the bandwidth to run all of that every week, on every new domain, alongside the actual selling motion. That is the gap we close.

Smartlead is the sending platform we use at the campaign level because of the ESP-to-ESP matching (Google to Google, Outlook to Outlook), live deliverability monitoring, and the auto-tapering warm-up that runs in parallel with live sends. We pair it with dedicated secondary domains, 30-day mailbox warm-up before any prospect receives a campaign, and reply management that catches problems before they show up in the metrics.

Across 400+ campaigns and 50+ clients, the pattern is consistent. Domains that respect the 30-day floor and the staged ramp hold reputation. Domains that try to compress the timeline pay for it in the next two months of placement issues. The math always favors patience.

Skip the warm-up debate. We run the domain for you.

Reachly handles domain setup, 30-day mailbox warm-up, sequencing, targeting, and reply management for multichannel campaigns across cold email, LinkedIn, and cold calling. Triple-certified across Clay, Smartlead, and HeyReach. Bounce rate stays under 3 percent. Deliverability above 97 percent. The Great Room signed a $250K contract on this exact infrastructure.

See how Reachly works

FAQ

How long does it take to warm up a new cold email domain?

30 days is the 2026 floor for a brand-new domain. Some teams stretch to 6 to 8 weeks for a more conservative ramp. Microsoft's guidance puts the upper bound at 4 to 8 weeks for maximum deliverability. The conventional 2-week answer is legacy advice. Google now flags any domain younger than 30 days with a yellow banner that tanks reply rates before the prospect reads the first line.

Can I warm up a cold email domain faster than 30 days?

The accepted shortcut is buying pre-warmed sending infrastructure that already has reputation history. Outside of that, no. Compressing the timeline on a fresh domain almost always burns the asset. Reachly treats 30 days as a hard minimum and runs the warm-up on dedicated secondary domains before any client prospect receives a campaign.

What spam rate and bounce rate are acceptable during warm-up?

Spam rate must stay below 0.08 percent. Bounce rate must stay below 2 percent. Customer.io and most deliverability teams treat these as the hard thresholds. Cross either and the reputation damage takes weeks to recover. Reachly's working benchmarks are tighter: bounce under 3 percent across client campaigns and deliverability score above 97 percent before a domain graduates from warm-up.

Should I use a new domain or a subdomain for cold email?

Use a new domain when you want isolation, are testing outbound hard, or have multiple reps and products running campaigns simultaneously. Use a subdomain when brand continuity matters more and your outbound motion is tightly controlled. The Reachly default is a dedicated secondary domain separated from the main brand, which keeps any reputation risk away from the core site.

What daily sending volume should I start warm-up at?

Start at 5 to 10 emails per mailbox per day for the first 3 days. Increase by roughly 1.5x at each stable plateau. Cap at 15 emails per mailbox per day for Google and 10 to 12 for Outlook. Higher volumes work but burn infrastructure faster and create the spikes mailbox providers treat as risk signals.

Are automated warm-up tools enough or should I warm up manually?

Use both. Automated warm-up handles consistency across multiple inboxes and creates the engagement signals mailbox providers look for. Manual control matters because recipient quality decides the timeline more than the schedule does. Smartlead handles the automated piece for Reachly client campaigns. The team still selects the audience for each stage manually because list relevance decides whether the warm-up sticks.

How do I know when my cold email domain is fully warmed up?

When the domain handles staged volume increases without spam rate going above 0.08 percent, bounce rate above 2 percent, or inbox placement drifting toward spam. Reachly graduates client domains only when bounce sits under 3 percent and deliverability score is above 97 percent on real campaigns, not warm-up tool checks. The calendar does not decide. The data does.

Thibault Garcia
Founder
I’ve spent the past 11 years working across sales and growth marketing, helping businesses build predictable pipeline. My focus is on lead automation, lead generation, LinkedIn optimisation, sales funnels, and practical growth systems. I’ve worked with 500+ businesses on improving their revenue operations, and I enjoy breaking down what consistently works in outbound, positioning, and building repeatable growth.
 
class SampleComponent extends React.Component { 
  // using the experimental public class field syntax below. We can also attach  
  // the contextType to the current class 
  static contextType = ColorContext; 
  render() { 
    return <Button color={this.color} /> 
  } 
} 

Get more meetings with the people who matter, 100% done for you.
Book a Call