What cold email IP warming actually means
Cold email IP warming is the deliberate, low-volume ramp that teaches mailbox providers your new sending domain belongs in the inbox. The motion runs 30 days, layers DNS authentication on top of engagement signals, and ends with a domain that can carry 500 sends per day without triggering Gmail or Microsoft 365 spam filters. The phrase IP warming is shorthand. The work in 2026 covers the IP, the From domain, and the message body.
Direct answer. Cold email IP warming is a 30-day ramp that earns inbox placement for a new sending domain through three layers of work: DNS authentication via SPF, DKIM, DMARC, and MTA-STS; a daily volume curve that doubles every five days; and an engagement loop that produces a reply rate above 15% during the first two weeks. Skip any layer and the domain stalls.
IP warming. IP warming is the controlled increase of email send volume from a new sending IP or domain to build a reputation with mailbox providers like Google and Microsoft. Reps warm a domain before any outbound campaign because cold launching from zero reputation triggers spam filters within hours.
The cold email playbook changed in 2024 when Google and Yahoo updated their bulk sender requirements, then tightened again in early 2026. Reps who launch a domain today face stricter authentication, lower complaint ceilings, and faster throttling than reps did even 12 months ago. The 30-day ramp is now the minimum, not the maximum.
This guide ships the full technical setup: DNS records, the day-by-day volume curve, the engagement loop, the monitoring stack, and the seven mistakes that pull a domain off the rails. For broader context, start with the cold email deliverability playbook or the email warmup glossary entry.
95%
Inbox placement for properly authenticated domains
Validity State of Email Report, 2026
17%
Inbox lift when DMARC reaches p=quarantine vs none
Google Postmaster, 2026
500/day
Sane ceiling for a freshly warmed domain at day 30
Gangly customer benchmark, 2026
0.3%
Spam-complaint hard cap before Gmail throttles a domain
Google Bulk Sender Requirements, 2024
Why mailbox providers throttle new sending domains
Mailbox providers throttle new sending domains because reputation is the only fast defence against bulk spam. A brand-new domain has no history, so Gmail and Microsoft 365 assume the worst and route the first few hundred messages through aggressive filters. Reputation builds with every clean send and collapses with every complaint.
Domain reputation. Domain reputation is the score Gmail, Microsoft 365, and Yahoo assign to your sending domain based on authentication health, engagement signals, and complaint rates. Reps with high domain reputation reach the primary inbox; reps with low reputation land in Promotions or Spam. See the full domain reputation glossary entry.
Validity reported that properly authenticated domains hit a 95% inbox placement ceiling in 2026, while unauthenticated domains landed in spam more than half the time (Validity State of Email Report, 2026). The gap closes only after the receiver has scored your sending pattern across at least 1,000 messages.
The provider rules diverge slightly. Gmail prioritises engagement: open rates, replies, and Important markers. Microsoft 365 weighs authentication and complaint rate more heavily. Yahoo treats list hygiene as the gating factor. A warming ramp that ignores any of the three will fail at exactly one provider, which usually means losing 30% of your TAM.
The DNS foundation: SPF, DKIM, DMARC, and MTA-STS
The DNS foundation has four required records and one optional record. Publish all four before sending a single message. The receiver checks them in milliseconds and uses the results to decide whether the message even enters the spam classifier. Authentication is not a tuning knob — it is the gate.
DMARC. DMARC (Domain-based Message Authentication, Reporting, and Conformance) is the policy that tells Gmail and Microsoft 365 what to do when an inbound message fails SPF or DKIM. A reps domain without DMARC at p=quarantine or stronger now lands in spam by default at most major providers.
| Record | Purpose | Where published | Sample value |
|---|---|---|---|
| SPF | Authorises the sending IPs for the domain | TXT record on root domain | v=spf1 include:_spf.google.com include:sendgrid.net ~all |
| DKIM | Signs every message with a public-key signature mailbox providers verify | TXT record at selector._domainkey | v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQ... |
| DMARC | Tells receivers what to do when SPF or DKIM fail and asks for aggregate reports | TXT record at _dmarc.domain | v=DMARC1; p=quarantine; rua=mailto:dmarc@domain.com; pct=100 |
| MTA-STS | Forces TLS on inbound mail and prevents downgrade attacks | TXT record at _mta-sts plus HTTPS policy file | v=STSv1; id=20260601T000000Z |
| BIMI | Displays your verified logo in supporting inboxes once DMARC is at enforcement | TXT record at default._bimi | v=BIMI1; l=https://domain.com/logo.svg; a=https://domain.com/vmc.pem |
Fast tip. Generate a 2048-bit DKIM key, not 1024. Microsoft 365 began downweighting 1024-bit keys in 2025 and reps with shorter keys see inbox drops at random.
Five publish steps, in order. Step one: register the secondary domain and point its nameservers at a DNS provider that supports TXT records over 255 characters. Step two: publish SPF with every authorised sender included once and ~all as the qualifier. Step three: generate the DKIM selector at your sending ESP and publish the public-key TXT record. Step four: publish DMARC at p=none with rua reporting on, then read reports for two weeks. Step five: publish MTA-STS in enforce mode with a policy file at https://mta-sts.domain.com/.well-known/mta-sts.txt.
For a plain-language refresher on authentication mechanics, the SPF DKIM DMARC explainer walks through every record without the jargon. For the deeper deliverability stack, see the email authentication guide.
The 30-day IP warming ramp: volume and reply targets
The 30-day ramp doubles volume every five days and holds reply rates above 15% for the first two weeks. The shape matters more than the absolute numbers. Mailbox providers fingerprint the curve: a steady doubling looks human, a sudden 10x looks compromised, a flat line looks dead.
Watch the bounce. If bounce rate crosses 2% on any day, freeze volume and audit the list. Continuing to send with bounces above 2% trains Gmail to spam-foldering the domain.
- Day 01–05
Target: 10 → 25 / day · Min reply: ≥ 25%
Seed inbox only. Hand-typed, threaded replies. No links.
- Day 06–10
Target: 25 → 50 / day · Min reply: ≥ 20%
Add five real prospects per day. Plain text. One link maximum.
- Day 11–15
Target: 50 → 120 / day · Min reply: ≥ 15%
Mix prospects and seed. Begin daytime sends in recipient time zone.
- Day 16–20
Target: 120 → 220 / day · Min reply: ≥ 12%
Drop training wheels: full sequence step one only.
- Day 21–25
Target: 220 → 350 / day · Min reply: ≥ 10%
Enable step two follow-up. Watch bounce rate hourly.
- Day 26–30
Target: 350 → 500 / day · Min reply: ≥ 8%
Full sequence. Hold at 500 / day for one week before scaling.
Two rules govern the ramp. Rule one: never increase volume on a day with a bounce above 1% or a complaint above 0.1%. Hold flat or step back. Rule two: never go more than 48 hours without sending. Even at low volume, daily activity teaches the receiver the domain is alive. The pattern is the signal.
Reps running multiple secondary domains in parallel can compress the calendar but not the engagement floor. Three secondary domains warmed in parallel still need 30 days each. Splitting volume across domains is for scale, not for speed.
Seed inboxes, engagement loops, and human reply patterns
Engagement is the second pillar. Authentication gets the message past the gate; engagement keeps it in the inbox. The Gangly Warm-Loop Protocol below is the engagement layer most outbound teams skip and most fail because of.
Seed inbox. A seed inbox is a real, monitored mailbox you control across Gmail, Outlook.com, Microsoft 365, and Yahoo. Reps send to seed inboxes during warming to confirm placement and to manufacture early positive engagement signals without burning real prospects.
The Gangly Warm-Loop Protocol. A defined four-step engagement loop that runs every weekday for the first 20 days of the ramp. The loop produces above-15% reply rates that warm the domain on the engagement axis, not just the volume axis. The protocol replaces the third-party warmup pool services that mailbox providers have begun detecting and downgrading in 2026.
- 1
Send to 10 seed inboxes per provider
Gmail, Outlook.com, Microsoft 365, Yahoo, and one self-hosted domain. Subjects vary. Bodies vary. Treat each as a real outreach.
- 2
Reply from the seed within 18 hours
A human reply, threaded, with the original message quoted. Threaded replies are the strongest engagement signal Gmail uses.
- 3
Mark the message Important and move it out of Promotions
Gmail weighs both signals. A move from Promotions to Primary lifts the domain reputation faster than any single other action.
- 4
Log placement in a daily seed sheet
Inbox vs Promotions vs Spam, per provider, per day. The sheet is the single source of truth for whether to step volume up or hold.
Three patterns separate human replies from warmup-tool replies. Humans quote the previous message inline. Humans ask a question that requires the original sender to answer. Humans send replies between 8am and 6pm in the recipient time zone. Build the loop to mimic all three.
Warmup pool risk. Mailgun and SparkPost published independent 2026 analyses showing mailbox providers now detect the engagement patterns of automated warmup pools. Domains warmed exclusively by pool tools see inbox lift collapse within 60 days.
Monitoring the warm: postmaster signals that decide placement
Monitoring the warm means watching three dashboards every weekday and acting on the worst signal of the three. Reps who only check open rates miss the placement collapse until it is too late to reverse.
Google Postmaster Tools. Google Postmaster Tools is the free Google dashboard that shows your domain reputation, spam rate, authentication pass rate, and delivery errors for Gmail. Reps verify the sending domain on day one of warming so reputation data is available from the first send.
The three dashboards to bookmark on day one. Google Postmaster Tools shows domain reputation, spam rate, and authentication pass rates for Gmail (Google Postmaster, 2026). Microsoft SNDS shows IP reputation, complaint rate, and trap hits for Microsoft 365 and Outlook.com (Microsoft SNDS, 2026). Your ESP dashboard shows bounce rate, deferral rate, and complaint rate aggregated across receivers.
Green-band signals
- ✓ Postmaster domain reputation Medium or High
- ✓ SPF + DKIM pass rate above 99%
- ✓ Spam rate below 0.1% (Gmail throttles at 0.3%)
- ✓ Bounce rate below 1%
- ✓ Seed placement above 90% across providers
Red-band signals
- ✗ Postmaster reputation Low or Bad
- ✗ Spam rate above 0.3% on any day
- ✗ DMARC aggregate report shows alignment failures
- ✗ SNDS yellow or red band on any sending IP
- ✗ Seed placement drops to Promotions for two days running
A single red-band signal means pause sending the same day. Two means cut volume by 50% and audit the list. Three means stop the ramp, investigate root cause, and restart at day 1 once the issue is resolved. The cost of a one-week pause is cheaper than the cost of a burned domain.
For the broader monitoring tool stack, see email deliverability monitoring. For the related metric, see the sender score glossary entry.
The seven IP warming mistakes that kill a new domain
The seven mistakes below pull more domains off the rails than every other failure mode combined. Six come from compressing the timeline, one from reusing burned infrastructure. Treat the list as a pre-flight checklist before day one of any new warming run.
- 1
Skipping the seed inbox loop
Warming with only prospects gives mailbox providers zero positive engagement signal. Reply rates collapse and the domain stalls.
- 2
Doubling daily volume before day 10
Mailbox providers fingerprint sudden volume jumps as a compromised account. The domain enters a soft-throttle that takes weeks to clear.
- 3
Running the ramp from a cold IP pool
Shared cold pools inherit the worst sender in the pool. Move to dedicated IPs or vetted shared pools before day one.
- 4
Publishing DMARC at p=none and never moving
Mailbox providers treat p=none as advisory. Step to p=quarantine by day 21 and p=reject within 60 days of launch.
- 5
Sending HTML email during week one
Rich HTML and tracking pixels shift the spam-classifier baseline. Use plain text for the first 10 days, then add one link.
- 6
Letting bounce rate creep above 2%
Catch-all and role inboxes pollute the list and signal poor list hygiene. Verify every address before send.
- 7
Reusing a burned domain
Domain reputation is sticky. A domain that was previously listed on Spamhaus or Microsoft SNDS will not warm. Buy a fresh one.
Two patterns connect every mistake on the list. Compressed timeline: leadership pushes for volume before the engagement data is in. Inherited reputation: the domain was bought used, the IP pool was shared with a high-complaint sender, or the seed inboxes leaked between brands. Both patterns are visible on day one. Both are preventable.
Verdict. The 30-day ramp is the cheapest insurance an outbound team buys. Compressing it to 14 days saves two weeks and costs three months of inbox placement. Run the full ramp once and the same domain stays warm for years.
For more on the cleanup side of deliverability, see email bounce management and email list hygiene.
How Gangly fits
Gangly handles the engagement layer of the IP warming workflow that most teams cannot scale by hand. The Outreach Writer drafts seed-loop variants that pass detection. The Workflow Sequencer runs the daily ramp curve and freezes volume the moment a red-band signal lands. CRM Hygiene removes catch-all and role addresses before they ever enter the warming pool.
- Outreach Writer : Generates seed-loop and prospect-step variants that vary subject, body, and call-to-action so receivers see human-shaped patterns.
- Workflow Sequencer : Runs the 30-day volume curve and auto-pauses on bounce, complaint, or postmaster red-band signals.
- CRM Hygiene : Verifies every address before it enters the warming pool and suppresses catch-all and role inboxes that drag bounce rate.
- Signal Detection : Surfaces the warm-ready prospects that should land in the ramp first, so the early sends draw real replies.
Teams running the Gangly stack ship a freshly warmed domain in 30 days with average inbox placement above 92% by day 30 (Gangly customer benchmark, 2026). The same teams cut domain burn-rate to under 5% per year, compared with the 18% industry baseline reported by Validity. For a full walkthrough of how the stack ties to outbound, see the Gangly sales workflow page or book a 20-minute live demo.
By Siddharth Gangal