How to Improve IP Reputation: A Step-by-Step Plan

IP reputation recovery is one of the slower deliverability remediation projects. Unlike authentication fixes (immediate) or blocklist delisting (24-72 hours), reputation rebuilding requires weeks of disciplined sending while you watch indicators trend in the right direction. Most senders give up partway through, send too much too fast, and reset the recovery clock.

This guide is the step-by-step plan I run for clients recovering from damaged IP reputation.

Step 1: Diagnose the cause

Don't start recovery until you know why reputation got damaged. Common causes:

Cause	Detection signal
Compromised account on the IP	Authenticated SMTP logs show unusual sender, sudden volume
Spam trap hits	SNDS shows trap count
Complaint spike	Postmaster Tools spam rate > 0.3%, SNDS complaint rate elevated
Sending to bad list	Bounce rate spike, complaints, traps
Volume spike or anomaly	ESP delivery logs show pattern change
Shared IP bad neighbor	Confirm IP is shared, check neighbor activity if possible
Authentication regression	DKIM key rotation forgotten, SPF record broken
New IP without warmup	IP is new and was scaled to full volume immediately

Pull data from Google Postmaster Tools, Microsoft SNDS, ESP delivery logs, and bounce reports. The cause must be identified before recovery starts.

Practitioner note: The most common cause I see for "IP reputation suddenly dropped" is a single bad list import or campaign that spiked complaints over a 1-2 day window. The damage shows in Postmaster Tools 5-7 days later. By the time the sender notices, the offending send is forgotten. I always pull the complaint timing from Postmaster Tools and correlate with send history to identify the source. The fix isn't always obvious without that correlation.

Step 2: Fix the underlying issue

Recovery without fixing the cause just delays the next damage event. Specific fixes:

Cause	Fix
Compromised account	Reset password, enable 2FA, audit auth logs, revoke sessions
Spam trap hits	Verify list, sunset inactive segments most likely to contain traps
Complaint spike	Audit opt-in for affected segment, fix consent issues, reduce frequency
Bad list source	Stop using the source, suppress affected segment
Volume anomaly	Investigate technical cause (loop bug, queued overflow), fix
Bad neighbor on shared IP	Move to dedicated IP if possible, or escalate to ESP
Authentication regression	Fix SPF/DKIM/DMARC records, verify with Mail-Tester
New IP without warmup	Implement warmup schedule going forward

Verify the fix is in place and working before starting recovery sends.

Step 3: Warm up with engaged-subscriber sends

Recovery sending follows similar rules to new-IP warmup:

Week 1 (very low volume, highest-engaged only):
- Send to subscribers who opened in the last 7 days
- Target: 10-20% of pre-damage daily volume
- Daily volume should be consistent, not spiky
- Spread across the day, not bursts

Week 2 (low volume, recently engaged):
- Expand to subscribers who opened in the last 30 days
- Target: 30-40% of pre-damage volume
- Continue daily consistency

Week 3-4 (medium volume, broader segment):
- Expand to subscribers who opened in the last 90 days
- Target: 50-70% of pre-damage volume
- Watch reputation indicators

Week 5+ (full volume, monitored):
- Resume normal volume if reputation has improved to Medium or High
- Continue suppressing 180+ day inactive subscribers
- Maintain hygiene discipline

Skip-ahead is the most common recovery mistake. If you rush from Week 1 volume to Week 4 volume, you reset whatever progress reputation has made.

Step 4: Monitor reputation indicators daily

During recovery, watch these every day:

Indicator	Source	Target
Domain reputation	Postmaster Tools	Trending up from current state
IP reputation	Postmaster Tools	Trending up
Spam rate	Postmaster Tools	< 0.3%, ideally < 0.1%
SNDS color	SNDS dashboard	Green, or yellow trending green
SNDS complaint rate	SNDS dashboard	Trending down
Bounce rate	ESP delivery report	< 2% per send
Open rate trend	ESP report	Stable or improving
Blocklist status	HetrixTools	No new listings

If any indicator deteriorates during recovery, reduce volume immediately and investigate.

Step 5: Rebuild gradually

Once reputation indicators show recovery (typically 4-6 weeks of disciplined sending), increase volume in 20-30% weekly increments. Watch indicators after each increase. If anything degrades, pull back to the previous volume level.

Total recovery time:

Damage level	Recovery time
Light (single complaint spike, fast intervention)	2-3 weeks
Moderate (multi-week pattern, no blocklist)	4-6 weeks
Severe (blocklist listing, sustained issues)	8-12 weeks
Critical (multiple compounding issues)	12-16 weeks

What not to do during recovery

Don't mail dormant subscribers. They are most likely to complain or ignore, which depresses recovery. Sunset them or pause indefinitely.

Don't switch IPs hoping for fresh start. New IP starts with no reputation and requires its own warmup. Same root cause will damage the new IP too if not fixed.

Don't change ESP mid-recovery. Adds infrastructure variability while ISPs are watching closely.

Don't try to "make up volume" later. Lost sends are lost. Trying to compress missed sends into a single high-volume blast wrecks the recovery.

Don't run promotional content during recovery. Use the recovery window for transactional and high-engagement subscribers only.

Practitioner note: I had a client who completed three weeks of clean recovery, saw Postmaster Tools improve from Bad to Medium, then sent a promotional campaign to their full list including 180-day inactive subscribers because they wanted to "test if recovery worked." Complaints spiked, reputation dropped back to Low, and we restarted the clock. Discipline through the full recovery window matters more than impatience to confirm progress.

When to consider IP migration

If reputation recovery fails after 8+ weeks of disciplined sending, consider:

1. Has the root cause actually been fixed? (Re-audit)
2. Is the IP shared with bad neighbors you can't influence?
3. Is the IP on a netblock that has historical bad reputation?

If yes to any, IP migration may be faster than continued recovery. New IP plus warmup takes 4-6 weeks, often faster than continuing to fight a permanently-damaged IP.

See sender reputation: domain vs IP.

For broader context

See deliverability recovery guide, stopping junk email classification, and Google Postmaster Tools guide.

If you need help running an IP reputation recovery, diagnosing what damaged it, or deciding whether to recover vs migrate, book a consultation. I run reputation recovery for senders weekly and can shorten the recovery timeline with disciplined execution.

Sources

• Google Postmaster Tools Help
• Microsoft SNDS Documentation
• Google Email Sender Guidelines
• M3AAWG Sender Best Common Practices
• Validity Sender Score
• RFC 7489 — DMARC

---

v1.0 · May 2026