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.
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.
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.
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.
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.
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.
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.
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.



.webp)