IP Reputation Explained: How to Check and Improve It

What IP Reputation Means

Every email server has an IP address. Mailbox providers track behavior from each IP: complaint rates, bounce rates, spam trap hits, volume patterns, authentication results. This history becomes the IP's reputation.

High reputation IPs get inbox placement. Low reputation IPs get spam filtered or blocked. It's that simple.

Dedicated vs Shared IPs

Aspect	Dedicated IP	Shared IP
Reputation	Yours alone	Collective
Volume required	50K+/month	Any
Warmup needed	Yes (4-8 weeks)	No
Control	Full	Limited
Cost	Higher	Included
Risk from others	None	Yes

Choose dedicated if:

• You send 50,000+ emails/month consistently
• You want complete control over reputation
• You can commit to consistent sending volume
• You have resources for proper warmup

Choose shared if:

• You send less than 50,000/month
• Your volume is inconsistent
• You don't want warmup complexity
• Your ESP has strict sender vetting

Practitioner note: Shared IPs get a bad reputation, but quality ESPs like Postmark maintain excellent shared IP reputation through strict sender policies. A shared IP at Postmark often outperforms a poorly managed dedicated IP. The question isn't "dedicated vs shared"—it's "who else is on this IP and do I trust them?"

Checking IP Reputation

Microsoft SNDS

Register at sendersupport.olc.protection.outlook.com

Shows your IP's status across Outlook/Hotmail:

• Green — Good standing
• Yellow — Some issues
• Red — Poor reputation

Requires IP ownership verification. The most important tool for Microsoft deliverability.

Sender Score

Check at senderscore.org

Scores 0-100 based on 30-day sending history:

• 90-100 — Excellent
• 80-89 — Good
• 70-79 — Fair
• Below 70 — Poor

Factors in complaint rates, spam traps, bounces, and volume patterns.

Talos Intelligence (Cisco)

Check at talosintelligence.com/reputation_center

Shows:

• Good — Trusted
• Neutral — Limited data
• Poor — Reputation problems

Talos data powers Cisco email security used by many enterprises.

Spamhaus Lookup

Check at check.spamhaus.org

Shows whether your IP is on Spamhaus blocklists:

• SBL — Known spam sources
• XBL — Exploited/compromised systems
• PBL — Dynamic/residential IPs

Spamhaus listings cause widespread blocking.

MXToolbox

Check at mxtoolbox.com/blacklists.aspx

Scans 100+ blocklists at once. Quick health check for any IP.

Building IP Reputation (Warmup)

New IPs have no reputation—neither good nor bad. Mailbox providers are skeptical of unknown senders and filter defensively.

IP warmup establishes positive reputation through gradual volume increase:

Week 1: 200-500/day Week 2: 500-1,000/day Week 3: 1,000-2,500/day Week 4: 2,500-5,000/day Week 5+: Increase 30-50% weekly

Critical requirements:

• Send only to highly engaged recipients
• Perfect authentication (SPF, DKIM, DMARC)
• Monitor for bounces and complaints
• Stop immediately if reputation dips

Practitioner note: Failed warmups happen when senders get impatient. "We have 500,000 subscribers and need to email them now!" That's exactly how you burn a new IP. Warmup is an investment—rushing it wastes the IP and forces you to start over.

Factors That Hurt IP Reputation

Factor	Severity	Recovery Time
Spam trap hit	High	Weeks
Blocklist listing	High	Varies
Complaint spike	High	2-4 weeks
High bounce rate	Medium	1-2 weeks
Sudden volume spike	Medium	Days to weeks
Authentication failure	Medium	Days

Spam Traps

Addresses that exist only to catch spammers. Three types:

• Pristine — Never belonged to real users (worst)
• Recycled — Abandoned addresses repurposed as traps
• Typo — Common typo variations monitored

Hitting spam traps indicates list quality problems.

Blocklists

Major blocklists that damage IP reputation:

• Spamhaus SBL/XBL — Most impactful, causes widespread blocking
• Barracuda — Corporate mail systems
• SORBS — Older list, still checked
• SpamCop — User-submitted complaints

Check blocklist status regularly and address listings immediately.

Recovering IP Reputation

If your IP reputation crashed:

Immediate actions:

1. Check all blocklists and request removal
2. Stop sending to any questionable lists
3. Verify authentication is working
4. Identify what caused the drop

Recovery process:

1. Reduce volume to engaged recipients only
2. Send to your absolute best segment
3. Monitor reputation metrics daily
4. Gradually increase volume as metrics improve

Timeline:

• Blocklist removal: Hours to weeks (varies by list)
• Reputation improvement: 2-4 weeks
• Full recovery: 4-8 weeks

Practitioner note: Sometimes an IP is unsalvageable. If you're on multiple major blocklists, getting removed takes weeks, and reputation damage is severe, it may be faster to get a new IP and warm it properly. This isn't always an option—new IPs cost money and require warmup—but it's sometimes the pragmatic choice.

IP Pools and Rotation

High-volume senders often use IP pools:

Benefits:

• Distribute volume across IPs
• Isolate different mail streams
• Redundancy if one IP has problems

Risks:

• More complexity to manage
• One bad IP can affect pool reputation
• Warmup required for each new IP

Typical setup:

• Pool A: Transactional email (protect reputation)
• Pool B: Marketing to engaged users
• Pool C: Re-engagement/higher-risk sends

Shared IP Considerations

If you're on shared IPs:

Choose your ESP carefully:

• Do they vet senders strictly?
• What's their removal policy for bad actors?
• How many senders share each IP?

Monitor your metrics:

• Sudden deliverability drops may be another sender's fault
• Ask ESP about IP health if metrics decline
• Consider upgrade to dedicated if problems persist

You still matter:

• Even shared IPs weight sender behavior
• Poor practices still hurt your reputation
• Authentication still required

Microsoft's IP Focus

Microsoft weights IP reputation more heavily than Gmail:

Provider	Primary Weight
Gmail	Domain reputation
Microsoft	IP reputation
Yahoo	Both equally

This means:

• New IPs need careful warmup for Microsoft
• Microsoft SNDS is essential monitoring
• Shared IP problems hurt Microsoft delivery more

If you're having Microsoft-specific delivery issues while Gmail is fine, IP reputation is likely the culprit.

Long-Term IP Management

Daily:

• Check blocklist status
• Monitor authentication pass rates

Weekly:

• Review SNDS data
• Check Sender Score trends
• Monitor bounce rates by domain

Monthly:

• Audit IP allocation strategy
• Review warmup status for new IPs
• Consider consolidation if some IPs are underused

If you're managing multiple IPs and struggling with reputation across different mail streams, schedule a consultation. IP architecture for high-volume sending requires careful planning.

Sources

• Microsoft: SNDS Documentation
• Validity: Sender Score
• Spamhaus: IP Lookup
• Cisco: Talos Intelligence

---

v1.0 · March 2026