IP reputation is the variable cold email guides mention but never actually explain. Most tell you to "warm up your inbox" and move on. But warming up an inbox on a shared IP pool is like painting over rust — it looks better for a week before the problem resurfaces. The IP underneath the inbox is what determines whether your email lands or disappears, and most senders never check it.
💡 TL;DR
Cold email inbox IP reputation is built through consistent, low-complaint sending on a dedicated IP with full authentication — not through warm-up tools alone. A dedicated IP on a clean sending history reaches "High" Postmaster reputation within 14 to 21 days. Shared IPs carry the history of every sender on that pool and cannot be reliably built. Litemail's dedicated US and EU IPs with Postmaster-verified reputation within 48 hours bypass the ramp entirely. Keep spam complaints under 0.08% and bounce rate under 2% to maintain reputation once built.
What IP Reputation Actually Controls — and What It Doesn't
IP reputation is a trust score assigned to the sending IP address by receiving mail servers and spam filter systems. A high-reputation IP means the server trusts that emails from this address are legitimate. A low-reputation IP means they are pre-sorted toward spam before content is even evaluated.
Here is what IP reputation does and does not control:
Factor | Controlled by IP Reputation? | Controlled by What Instead? |
|---|---|---|
Whether email reaches inbox vs spam | Yes — primary factor | — |
Whether email is opened | No | Subject line and sender name |
Whether email passes authentication | No | SPF, DKIM, DMARC configuration |
Whether domain is blacklisted | Partial | Domain reputation (separate signal) |
Reply rate | Indirectly (via inbox placement) | Copy, offer, targeting |
IP reputation affects inbox placement. Domain reputation affects filtering decisions. Both matter. But IP reputation is the one most senders have least control over — and the one pre-warmed inboxes on dedicated IPs solve directly.
Shared IP vs Dedicated IP — Why This Is the Decision That Matters Most
Most sending inboxes — even Google Workspace accounts — send from shared IP pools. That means your sending reputation is influenced by the behaviour of thousands of other senders on the same IP range. You cannot control what they send, how their lists are maintained, or how many spam complaints they generate.
A 4-person demand generation team we know spent 8 weeks building a Google Workspace cold email setup. Good copy. Clean list. SPF, DKIM, DMARC all passing. Reply rates were still under 1%. They checked their sending IP through MXToolbox — it was on three spam blocklists. None of which they had triggered. A neighbour on the shared pool had. Recovery took 6 weeks after migrating to dedicated IPs.
Dedicated IPs solve this cleanly. Your IP's history is your history. No contamination. No unknown neighbours. Litemail provides US and EU dedicated IPs on every inbox — with sending history that is pre-verified clean before the inbox is assigned to you.
How IP Reputation Builds — The Real Timeline
On a dedicated IP with no prior history, here is what an honest reputation build timeline looks like.
📅
Days 1–7: Establishing baseline signals
Send 20 to 30 emails per day to verified, engaged contacts. These can be existing connections, opt-in contacts, or a tightly curated warm prospect list. Receiving servers log the IP as a new sender and watch for complaint signals. No complaints, no bounces — reputation registers as "Neutral" or "Low" on Postmaster.
📅
Days 8–14: Consistency builds trust
Increase volume by 20 to 30% every 3 to 4 days. Keep complaint rate at zero. Open rates above 30% are a positive signal — they tell the filter that recipients are engaging with, not ignoring or reporting, your mail. Domain reputation on Postmaster should move from Low to Medium during this period.
📅
Days 15–21: High reputation threshold
With consistent sends, zero complaints, and bounce rate under 2%, most sending IPs reach "High" domain reputation on Postmaster by day 21. At this point, you can send at full volume — 150 to 200 per inbox per day — with 90%+ inbox placement rate. This is the manual warm-up timeline. Pre-warmed inboxes start here.
How to Check Your IP Reputation Before Sending a Single Email
Most cold email guides tell you to monitor reputation after problems appear. Check it before you start. These are the tools and what each one tells you.
🔍
MXToolbox Blacklist Check
Enter your sending IP at mxtoolbox.com/blacklists.aspx. It checks against 100+ spam blocklists in one pass. Any listing — even one — can reduce inbox placement by 20 to 40 percentage points for recipients using that blocklist. Run this check before your first send and weekly thereafter.
🔍
Google Postmaster Tools
Postmaster shows domain reputation (not IP reputation directly) for Gmail-destined email. But domain reputation is heavily influenced by IP behavior — so it is a useful proxy. "High" domain reputation correlates with 90%+ Gmail inbox placement. "Low" or "Bad" means less than 50% placement regardless of copy or targeting.
🔍
Microsoft SNDS (Smart Network Data Services)
SNDS shows complaint rate and spam trap hit rate for Microsoft-hosted inboxes by IP address. Green status means clean. Yellow means monitor. Red means your IP is actively filtered by Microsoft's systems — affecting all Outlook, Hotmail, and Microsoft 365 recipients. Check this for any campaign targeting enterprise audiences.
🔍
Talos Intelligence (Cisco)
Talos assigns IP sender scores used by Cisco's email security products — deployed at millions of enterprises. A "Poor" Talos score blocks your email before it reaches the spam folder at companies using Cisco Email Security. Check your IP at talosintelligence.com. Most pre-warmed inbox providers with dedicated IPs maintain Good or Neutral Talos scores.
What to Do When IP Reputation Is Already Damaged
If you are already in this situation — inbox placement at 30 to 50%, Postmaster showing Low or Bad reputation — here is the honest answer: you cannot repair a damaged shared IP. You can only leave it.
Migration is the fix. Provision new inboxes on fresh dedicated IPs. Move your sending volume there gradually. Do not forward or redirect from the old inboxes — that transfers reputation signals. Start clean.
Repair of a damaged dedicated IP is possible but slow. It takes 4 to 8 weeks of clean sending — low volume, zero complaints, verified list only — to move Postmaster reputation from Bad to Medium. From Medium to High takes another 3 to 4 weeks on top of that. This is why avoiding the damage is worth more than any recovery tactic.
[INTERNAL LINK: email deliverability repair guide → /blog/email-deliverability-recovery]
Maintaining IP Reputation at Scale — The Signals That Matter
Building reputation is one task. Keeping it at scale — across multiple inboxes, multiple clients, or high daily send volumes — is a different challenge. These are the signals that directly move IP reputation up or down.
Signal | Positive Impact | Negative Impact | Safe Threshold |
|---|---|---|---|
Spam complaint rate | Below 0.04% | Above 0.08% — immediate filter tightening | Under 0.08% |
Bounce rate | Under 0.5% | Above 2% — domain reputation damage | Under 2% |
Open rate | Above 25% — engagement signal | Under 5% — non-engagement signal | Target 25–40% |
Spam trap hits | Zero | Any — immediate reputation damage | Zero |
Unsubscribe rate | Under 0.2% | Over 0.5% — list quality signal | Under 0.5% |
Spam traps are worth calling out specifically. A spam trap is an email address set up by blocklist operators or ISPs to catch senders using purchased or scraped lists. Hitting even one trap can trigger a blocklisting. Use a verified list, remove role addresses (info@, support@, admin@), and run through NeverBounce or ZeroBounce before every new campaign.
The Bottom Line
IP reputation is the foundational deliverability variable — it determines inbox vs spam placement before content is evaluated.
Shared IPs cannot be reliably built. Your reputation on a shared pool is influenced by every other sender on it. Dedicated IPs are the only way to fully control your sending reputation.
Manual warm-up on a dedicated IP takes 14 to 21 days to reach "High" Postmaster status. Pre-warmed dedicated IP inboxes from Litemail skip this entirely — Postmaster-verified within 48 hours.
Check MXToolbox blacklists, Google Postmaster, Microsoft SNDS, and Talos Intelligence before launching any campaign. A clean check takes 15 minutes and prevents weeks of recovery work.
Keep spam complaints under 0.08% and bounces under 2%. Those are the two numbers that directly trigger filter tightening when crossed.
Damaged shared IP reputation cannot be repaired — it can only be left. Migrate to new dedicated IPs and start clean. Recovery on a damaged dedicated IP takes 8 to 12 weeks minimum.
Frequently Asked Questions
How long does it take to build IP reputation for cold email?
On a dedicated IP starting from zero, a clean sending history reaches "High" Postmaster domain reputation in 14 to 21 days with consistent low-complaint sends. Pre-warmed inboxes on dedicated IPs with clean sending history bypass this ramp — Litemail delivers Postmaster-verified reputation within 48 hours of inbox provisioning.
What is the difference between IP reputation and domain reputation for cold email?
IP reputation is the trust score assigned to the sending server's IP address by receiving mail systems. Domain reputation is the trust score assigned to your sending domain. Both affect inbox placement — IP reputation is the first filter, domain reputation is a secondary one. For cold email, a clean dedicated IP is the foundation; strong domain reputation is built on top of it through consistent clean sending.
How do I check if my sending IP is on a spam blocklist?
Run your IP through MXToolbox's blacklist checker at mxtoolbox.com/blacklists.aspx. It checks over 100 blocklists in one query. Also check Microsoft SNDS for Microsoft-hosted inbox deliverability data, and Talos Intelligence for Cisco email security reputation. Run all three before any new campaign launch and weekly during active sends.
Can I fix a damaged cold email IP reputation?
On a shared IP — no. You cannot fix shared IP reputation because you do not control the other senders on it. Migration to a clean dedicated IP is the only solution. On a damaged dedicated IP, repair is possible through 8 to 12 weeks of clean, low-volume sending with zero complaints — but prevention is far cheaper than recovery.
What spam rate is safe for maintaining IP reputation?
Keep spam complaint rate under 0.08% to stay inside Google's safe threshold and avoid immediate filter tightening. Below 0.04% is the target for stable high-reputation sending. Above 0.08% triggers immediate filter adjustment. Above 0.3% risks domain-level blocking. Monitor daily via Postmaster during active campaigns.
Do warm-up tools actually build IP reputation?
Warm-up tools build sending volume history on your inbox — but only on the IP it is assigned to. If that IP is shared, warm-up tools cannot build the IP's reputation because it is shared across thousands of accounts. Warm-up tools are useful for volume history on dedicated IPs. They do not solve shared IP contamination.
