Warming Up a Sending Domain or IP: The Step-by-Step Method

A domain or IP address that has never sent email has no track record with Gmail, Outlook or Yahoo. Sending tens of thousands of messages right away from that brand-new identity almost always lands in spam, regardless of how good the content is. Warm-up means gradually increasing send volume, day by day, to build the reputation that mailbox providers rely on before trusting a sender. It’s one of the pillars of email deliverability, alongside technical authentication.

#Reputation is built, not declared

Mailbox providers lean on a domain and IP’s history to decide a message’s fate before even reading its content: complaint rate, bounce rate, open rate, volume consistency. A sudden, large send from an identity with no history looks, to these systems, like spammer behavior, even when the sender is entirely legitimate. Technical authentication set up beforehand, through SPF, DKIM and DMARC, is a necessary condition but not a sufficient one: it proves the sender’s identity, not its long-term reliability.

#The signals watched during ramp-up

Three metrics matter more than any other during warm-up: complaint rate (ideally under 0.3%), hard bounce rate (under 2%), and engagement rate (opens and clicks) on the targeted segment. A spike in complaints or bounces during ramp-up should stop the progression, not just slow it: drop back to the previous step rather than stalling on a volume that’s already causing problems.

These steps are indicative: the real progression depends on the final target volume and the engagement observed at each stage. A simple rule works in most cases: never raise daily volume by more than 20-30% from one day to the next, and only move to the next step after two or three days of stable metrics.

#Segment, don’t blast the whole list

The temptation with a new domain is to spread the usual send across several days without changing the target audience. That’s a mistake: warm-up works because it starts with the recipients most likely to open and click, which generates strong positive signals from the very first sends. Prioritize contacts who engaged with a recent communication, deliberately delay sends to addresses inactive for more than six months, and flat-out exclude addresses that were never verified (entered without double opt-in, imported from a third-party source), which artificially inflate the bounce rate.

A brand-new domain that sends tens of thousands of messages a day right out of the gate will almost always land in spam, regardless of how good the content is.

#Check the setup before starting the ramp-up

Before the first send, confirming that DNS records are fully propagated and consistent avoids warming up a broken configuration:

dig +short TXT example.com | grep spf
dig +short TXT default._domainkey.example.com
dig +short TXT _dmarc.example.com

# Check that the sending IP's PTR record matches the domain
dig +short -x 203.0.113.10

A common mistake is starting warm-up before DNS propagation is complete across all resolvers: a DKIM record still missing at some providers causes authentication to fail on part of the traffic, which pollutes the metrics during the very first days, exactly when they matter most.

#Shared or dedicated IP: a choice that comes before warm-up

For volume under roughly 50,000 messages a month, a shared IP at a reputable provider inherits reputation already built by other senders in the pool, which shortens the warm-up period. Beyond that, a dedicated IP becomes worthwhile, but it starts with zero history and requires a full warm-up, typically spread over four to eight weeks depending on the target volume. Keeping the shared pool as a fallback during the dedicated IP’s ramp-up, at the moment of transition, limits the risk if the new IP runs into an unexpected problem.

#Tracking tools

Google Postmaster Tools remains the reference for tracking domain and IP reputation with Gmail specifically, with a few days of reporting lag to factor into how the charts are read. A daily tracking sheet (volume sent, bounce rate, complaint rate, open rate by segment) makes it possible to spot a drop before it worsens, well before it becomes visible in overall open-rate statistics.

#Common mistakes that break a warm-up in progress

Changing message content or subject lines mid-ramp-up muddies the metrics: a drop in open rate could come from the new volume step or from the new content, with no easy way to tell the two apart. It’s better to keep content stable throughout the warm-up period and only vary volume and the targeted segment.

Pausing a warm-up for several weeks and then resuming doesn’t pick up where it left off: the reputation built erodes with inactivity, and it’s usually necessary to drop back one or two steps to restart on solid footing. A regular sending schedule, even at low volume, beats alternating bursts and silence.

Mixing transactional and marketing sends on the same IP during warm-up exposes transactional traffic (order confirmations, password resets) to the fallout from a poorly received marketing campaign. Separating the flows onto distinct subdomains or IPs from the start of the infrastructure design avoids this cross-dependency, well before volume alone would justify a dedicated IP.

#What to remember

Warm-up isn’t a minor technical formality but the condition for a new domain or sending IP’s deliverability over the medium term. A gradual ramp-up, built on the most engaged contacts and monitored daily on complaint and bounce rates, builds in four to eight weeks a reputation that impatience can destroy in a few days.

Further reading: Google Postmaster Tools official documentation.