Sendersy
All posts
Deliverability

How to Warm Up a New Email Domain or IP

A week-by-week warm-up schedule for new sending domains and IPs so you build reputation instead of getting blocked.

Igor Petrov
Infrastructure, SMTP
May 26, 20267 min read

A brand-new sending domain or IP address has zero reputation, and in email, zero reputation is treated with deep suspicion. Mailbox providers have no history to judge you by, so a sudden burst of mail from an unknown source looks exactly like a spammer who just registered a throwaway domain. If you blast thousands of emails on day one, providers will throttle, defer, or outright block you — and the reputation hit from that first bad impression can take weeks to undo. Warming up is the deliberate process of ramping your volume slowly so that mailbox providers observe consistent, well-received sending and gradually learn to trust you.

Think of warm-up as building credit. You cannot walk into a bank and borrow a fortune with no history; you start small, demonstrate reliability, and your limit rises over time. Email reputation works the same way. Every day of clean, engaged sending raises the volume providers will accept from you without suspicion, until you reach the steady state your program actually needs. This guide lays out a practical schedule, explains what to watch, and covers the mistakes that force people to start the whole process over.

Why warm-up is non-negotiable in 2026

It is tempting to think warm-up is an old-fashioned ritual, but the opposite is true: as providers have grown more sophisticated, sudden-volume detection has become sharper, not softer. Gmail and Yahoo's bulk-sender requirements and the general tightening of filters mean that an un-warmed domain sending at volume is one of the fastest ways to land in spam. The cost of skipping warm-up is not theoretical — it is a damaged domain that then needs an even slower, more painful rehabilitation than a proper warm-up would have taken in the first place.

Warm-up matters whether you are standing up a brand-new domain, moving to a new sending provider, or bringing a dedicated IP online. In each case the receiving world has little or no recent positive history for that sending identity, and your job is to supply that history gradually and on your own terms rather than having providers form a bad opinion all at once.

A simple warm-up schedule

The exact numbers depend on your target volume, but the shape is always the same: start small, increase gradually, and let positive signals earn you the next increment. A workable starting schedule looks like this:

  • Days 1–3: 50–100 emails per day to your most engaged contacts.
  • Week 1: roughly double the daily volume if complaints stay near zero.
  • Weeks 2–4: keep doubling while watching bounces and spam rates closely.
  • Week 4+: reach full volume once your metrics are stable.

Treat that as a guide, not a contract. The real rule is "increase only while the signals stay healthy." If you are aiming for a small steady volume, your warm-up may take only a couple of weeks; if you are ramping a dedicated IP toward hundreds of thousands a day, expect four to eight weeks of patient increases. Rushing the schedule to hit a launch date is the single most common way warm-ups fail.

Send to your best contacts first

The order in which you add recipients matters enormously. Early opens, clicks and especially replies are the strongest positive signals a new sender can generate, so you want your first sends going to the people most certain to engage: recent customers, active users, anyone who knows your brand and will be glad to hear from you. These recipients produce the clean engagement that convinces providers you are legitimate.

Conversely, leave your coldest and riskiest segments for last. Re-activation lists, long-dormant subscribers, and anyone you are unsure about should wait until the domain is fully warm, because they generate the low engagement and occasional complaints that can poison a fragile new reputation. Warming up on your best audience and expanding outward is the whole art of it.

Sendersy

Send email that actually lands in the inbox

API and visual editor, SPF/DKIM/DMARC out of the box, analytics and warm IPs. Free tier — 200 emails/month, no card required.

Watch the signals and react

Warm-up is not a fire-and-forget schedule; it is a feedback loop. After every increase, watch your bounce rate, your spam-complaint rate, and your engagement. If complaints or bounces spike, do not push to the next volume tier — instead, pause the ramp and hold steady at the current level until the numbers settle, or even step back down a tier. Pushing through bad signals is how a warm-up turns into a reputation disaster.

Instrument the process so you can actually see those signals. Connect Google Postmaster Tools to watch your domain and IP reputation and spam rate from Google's own perspective, and use your platform's delivery log to track bounces and deferrals per provider. Different providers warm at different rates, so it is normal to see one provider accept your increasing volume happily while another is still cautious; let the slowest one set your pace.

Authentication comes before warm-up

None of this works without SPF, DKIM and DMARC correctly published and aligned first. Warming up an unauthenticated domain is pointless, because providers cannot even confirm the mail is really from you, and much of it will fail regardless of how slowly you ramp. Set up authentication, verify it with a test message that shows three PASS results, and only then begin sending volume.

A subtle but important point: keep your sending pattern consistent during and after warm-up. Reputation is a moving average, so a domain that warms up and then goes silent for weeks will see its hard-won reputation decay, and the next big send will look like a cold start again. Steady, predictable volume maintains the trust that warm-up built.

Shared pools as an alternative

Warm-up is the price of controlling your own sending identity, but you do not always have to pay it yourself. Sending from a well-managed shared IP pool means your mail goes out on IPs that are already warm and maintained by the provider, which is ideal for low-to-medium or bursty volume where you could never keep a dedicated IP busy enough to stay warm. The domain reputation you still build yourself through good habits, but the IP warm-up is handled for you.

Frequently asked questions

How long does warm-up take? Anywhere from two to eight weeks depending on your target volume and how cleanly your early sends are received. Let the signals, not the calendar, decide.

Can I skip warm-up if I use a shared pool? Largely yes for the IP, since it is already warm; you still build domain reputation gradually, but the steepest part is handled for you.

What if I damaged a domain by skipping warm-up? Stop, prune to your most engaged contacts, and restart a slow ramp — recovery is essentially a warm-up done after the fact, and it takes longer than doing it right the first time.

Dedicated IP warm-up specifics

Warming a dedicated IP is stricter than warming a domain, because an IP's reputation depends heavily on a steady, sufficient volume. If you bring a dedicated IP online and then send only sporadically, it never accumulates enough positive history to be trusted, and its reputation actually drifts downward between sends. This is the core reason most senders should not use a dedicated IP at all: unless you can keep it consistently busy with tens of thousands of messages a day, a warm shared pool will outperform it. Only warm a dedicated IP if your sustained volume genuinely justifies one.

If you do warm a dedicated IP, be especially conservative in the first two weeks and especially attentive to per-provider acceptance, since each major provider forms its own opinion of a new IP independently. Expect Gmail, Outlook and Yahoo to warm at different speeds, and let the most cautious one govern your ramp rather than averaging across them.

Common warm-up mistakes

The mistakes that ruin warm-ups are predictable. The first is impatience — pushing to full volume to hit a launch date, which providers read as a sudden spike and penalize. The second is starting with a cold or purchased list, so the early sends generate bounces and complaints precisely when your reputation is most fragile. The third is going silent after warming up, letting the reputation decay so the next campaign looks like a fresh cold start.

A fourth, subtler mistake is changing too many variables at once during warm-up: new domain, new IP, new template, new from-name, new content style, all at the same time. If something goes wrong you cannot tell which change caused it. Warm up one new sending identity at a time, holding everything else stable, so the signals you are watching actually mean something.

Warm-up and the rest of your program

Warm-up does not exist in isolation; it sets up everything that follows. The engaged-first ordering you use to warm a domain is the same discipline that keeps it healthy long term — keep mailing engaged people, keep pruning the unengaged, keep your authentication aligned. In that sense a good warm-up is not a one-time event but the beginning of a permanent habit of sending in a way that earns trust.

It also pairs naturally with list growth: as you add new subscribers through double opt-in, you are feeding your warm domain a steady stream of fresh, engaged, confirmed contacts, which is exactly the diet that keeps reputation strong. Warm-up, list hygiene, authentication and engagement are four facets of the same underlying goal — being a sender that mailbox providers are glad to deliver.

A realistic timeline expectation

Set expectations with stakeholders before you begin: a proper warm-up takes weeks, not days, and trying to compress it to meet a marketing deadline is how reputations get damaged. If a big launch is coming, start warming the domain well in advance so it is at full volume by the time you need it, rather than discovering on launch day that you cannot send at scale. Treat warm-up as lead time on a critical dependency, the same way you would treat provisioning any other piece of infrastructure that has to be ready before go-live.

Ramp safely

None of this works without SPF, DKIM and DMARC in place first. Sendersy registers DKIM automatically and runs warm sending pools, so new domains ramp safely without you hand-managing a schedule. Add your domain free and start sending on infrastructure that is already trusted.

Share:
Written by
Igor Petrov
Infrastructure, SMTP

Owns SMTP relays, queues and monitoring. Knows why a message is stuck before you ask.