IP warm-up vs domain warm-up: which one you actually need

IP warm-up builds history for a connecting machine. Domain warm-up builds history for the identity in your From: address and DKIM signature. They are not alternatives — they answer different questions a receiving provider asks — but only one of them is usually yours to do. If you send through Google Workspace, Microsoft 365, or a shared pool at any ESP, you do not own the IP and cannot warm it. You warm the domain, and the mailboxes on it.

Which applies to you

The common mistake is spending weeks on an IP ramp while sending from a domain nobody has ever seen, or the reverse: warming a domain beautifully and then pushing it through a brand-new dedicated IP on day one.

What each one is teaching the provider

A new IP raises an infrastructure question: is this machine a legitimate sender or a freshly rented host about to blast? Providers answer it by throttling and watching — deferrals, slow acceptance, caution — and they relax as a steady volume curve accumulates. That history is short-memoried and it decays. Go quiet for a few weeks and the IP looks new again.

A new domain raises an identity question: do the people who receive mail from this name want it? Providers answer that from recipient behaviour — complaints, replies, moves out of Junk, deletions without reading — and from whether the mail is authenticated and aligned. Domain history accrues slowly and persists. It is also what follows you when you change ESP, which is why it is the more valuable of the two assets and the one you should not casually abandon.

Mailbox warm-up is the third, smaller layer and it is the one most outbound teams actually need: a specific sending address on an established domain still has to establish a normal sending pattern and real two-way conversation before it carries volume.

Timelines

• IP: four to six weeks for a dedicated IP at real volume, pace set by deferrals rather than by your schedule. Only worth it if you can send steadily every day, forever — an idle dedicated IP is worse than a shared pool.
• Domain: two to six weeks before meaningful volume, longer if the domain is brand-new, longer still if it has a history you did not create. Authentication must be correct from the first message.
• Mailbox: two to four weeks per mailbox, and adding mailboxes is almost always safer than pushing one mailbox to its ceiling.

Do both correctly, in this order

1. Publish SPF (one record, under ten DNS lookups), DKIM, and DMARC with a reporting address before the first send. Read the aggregate reports for a week before enforcing.
2. Warm the domain and mailboxes with real mail to recipients who will open and reply. Low volume, every day, no gaps.
3. If you have a dedicated IP, ramp it on the same mail, splitting each day's volume across providers in the proportion your list has, and holding flat whenever a provider defers persistently.
4. Measure per-provider placement from seed mailboxes weekly. Hold volume on any provider that slips rather than pressing on.

What not to do

Do not warm an IP with mail from a cold domain, or a domain through a cold IP, and then wonder which half failed. Do not take a dedicated IP for a few thousand sends a month; the volume will not keep it warm and you will get worse results than a shared pool. Do not pause mid-ramp. Do not rotate domains to spread risk — many unwarmed domains is strictly worse than one warm one, and the pattern is legible. And do not expect to verify either ramp with a reputation grade: Google Postmaster Tools retired its domain and IP reputation charts, so the available evidence is Gmail spam rate under 0.3% — ideally under 0.1% — plus per-provider seed placement, and for IPs you own, Microsoft SNDS.

The part worth being careful about

Both kinds of warm-up work through two mechanisms: a volume curve that looks normal, and engagement that says people want the mail. The first is purely mechanical and entirely defensible. The second is defensible only when the engagement is real, and that distinction now carries direct risk. On 3 September 2026, Validity launched Heatwave, a blocklist aimed at synthetic reputation warming — pools of controlled mailboxes manufacturing opens, clicks and replies. It lists domains rather than IPs, launched with over a million domains listed, and feeds live filtering; lookup is at lookup.validity.tools and review requests go through its /delist path. Because its thresholds are not published, no tool — ours included — can honestly promise you exemption. Ramp on real mail, to real recipients, and keep the engagement genuine.

MailPilot works on the domain and mailbox layers rather than the MTA layer: it warms mailboxes over OAuth for Gmail and Outlook or over SMTP/IMAP for Amazon SES, SendGrid, Mailgun, Postmark and custom relays, checks SPF, DKIM and DMARC on each domain, and measures real per-provider inbox placement and per-mailbox reputation daily.