IP Reputation in Cold Email: What It Is and How to Manage It

IP reputation is the trustworthiness score assigned to the IP address your emails are sent from. Inbox providers like Google and Microsoft use IP reputation alongside domain reputation to decide whether your email reaches the inbox or the spam folder. For cold email senders using Google Workspace or Microsoft 365, IP reputation works differently than you might expect because you are on shared infrastructure, not dedicated IPs.

At Alchemail, we manage deliverability across 200+ sending accounts and understand how IP reputation interacts with domain reputation in a shared environment. This guide breaks down what you can and cannot control about IP reputation and where to focus your efforts.

How IP Reputation Works

The Basics

Every email is sent from a server with an IP address. Inbox providers maintain reputation scores for these IP addresses based on:

• Spam complaint rates from recipients
• Bounce rates (high bounces indicate poor list quality)
• Spam trap hits (sending to known trap addresses)
• Volume patterns (sudden spikes are suspicious)
• Engagement metrics (opens, replies, and interactions)
• Blacklist status (whether the IP appears on public blacklists)

IP Reputation vs. Domain Reputation

Both matter for deliverability, but they work at different levels:

Factor	IP Reputation	Domain Reputation
What it tracks	Server sending behavior	Domain sending behavior
Who controls it	Infrastructure provider (mostly)	You (directly)
Shared impact	Affects all senders on the IP	Affects only your domain
Recovery speed	Days to weeks	Weeks to months
Primary signals	Volume, bounces, spam traps	Complaints, engagement, content
Visibility	Limited (SNDS, Postmaster)	Better (Postmaster Tools)

Key insight for cold email senders: Domain reputation has become the dominant signal for most inbox providers. Google explicitly prioritizes domain reputation over IP reputation for Workspace senders. This means your focus should be on domain health first, with IP reputation as a secondary consideration.

IP Reputation on Shared Infrastructure

Google Workspace IP Pools

When you send email through Google Workspace, your emails go through Google's shared IP pools. These pools serve millions of senders. Your individual sending behavior contributes to the pool's reputation, but so does everyone else on that pool.

What this means for cold email:

• You cannot control or choose your sending IP
• Google rotates IPs within their pool
• Your domain reputation is the primary factor Google uses for filtering
• Bad actors on the same IP pool can temporarily affect your delivery

Microsoft 365 IP Pools

Microsoft operates similarly with shared IP pools, but with some differences:

• Microsoft uses "IP relay pools" that group senders by behavior
• High-risk senders get moved to lower-reputation pools
• Microsoft is less transparent about pool assignments
• Microsoft's SmartScreen filter weighs IP reputation more heavily than Google does

The Shared IP Challenge

The biggest challenge with shared IPs is that you inherit some risk from other senders:

Scenario	Impact on You	Mitigation
Another sender on your IP pool spams	Temporary delivery slowdown	Domain reputation acts as buffer
Your IP pool gets temporarily blacklisted	Emails may bounce or go to spam	Report to Google/Microsoft support
IP pool reputation degrades over time	Gradual deliverability decline	Cannot fix directly, focus on domain

How to Monitor IP Reputation

Google Postmaster Tools

Google Postmaster Tools provides the most accessible IP reputation data for Google Workspace users:

1. Set up Postmaster Tools for each sending domain
2. Navigate to "IP Reputation" tab
3. Review reputation scores: High, Medium, Low, Bad
4. Track changes over time

Score meanings:

Score	Meaning	Action
High	Excellent reputation	Continue current practices
Medium	Minor issues	Monitor closely, review practices
Low	Significant issues	Reduce volume, investigate
Bad	Severe problems	Pause sending, investigate urgently

Microsoft SNDS (Smart Network Data Services)

Microsoft's tool for monitoring IP reputation:

1. Register at sendersupport.olc.protection.outlook.com
2. Add your sending IP addresses (find them in email headers)
3. View spam trap hits and complaint data
4. Monitor trends over time

Note: For shared infrastructure (Microsoft 365), you monitor the IPs Microsoft assigns to your sending, which may change.

MXToolbox

MXToolbox checks your IP against 80+ blacklists:

1. Find your sending IP from email headers ("Received:" lines)
2. Enter the IP at mxtoolbox.com/blacklists.aspx
3. Review results for any listings
4. Set up monitoring for ongoing checks

Email Headers Analysis

To find your sending IP:

1. Send a test email to a Gmail account
2. Open the email, click "Show Original"
3. Look for "Received:" headers
4. The IP in the originating "Received:" line is your sending IP

For Google Workspace, this will be a Google-owned IP. For Microsoft 365, it will be a Microsoft-owned IP.

What You Can Control vs. What You Cannot

What You CAN Control

1. Domain reputation: SPF, DKIM, DMARC configuration, sending practices, list quality
2. Sending behavior: Volume, frequency, content quality, bounce management
3. List quality: Verification, cleaning, targeted prospecting
4. Engagement: Writing emails that get opened and replied to
5. Authentication: Proper technical setup on all sending domains

What You CANNOT Control

1. Shared IP pool composition: Who else sends from the same IP range
2. IP rotation by providers: When Google or Microsoft change your sending IP
3. IP pool reputation shifts: Changes caused by other senders
4. Provider-level blacklisting: When an entire IP range gets flagged

Where to Focus

Given the control dynamics, here is our priority order at Alchemail:

1. Domain reputation (highest impact, most control)
2. Email authentication (SPF, DKIM, DMARC)
3. List quality and verification (bounce and spam prevention)
4. Content quality (engagement signals)
5. IP reputation monitoring (awareness, limited direct action)

Dedicated IPs vs. Shared IPs

When to Consider Dedicated IPs

Dedicated IPs give you full control over reputation but come with significant requirements:

Factor	Shared IP	Dedicated IP
Cost	Included with provider	$20-100/month per IP
Setup complexity	None	Warm-up required
Volume requirement	Any	50,000+ emails/month minimum
Reputation control	Partial	Full
Risk from others	Yes	No
Risk from yourself	Shared	Fully concentrated

Dedicated IPs make sense when:

• You send 100,000+ emails per month consistently
• You have a dedicated deliverability team
• You need maximum control over reputation
• You can commit to consistent sending volume

Dedicated IPs are risky when:

• Volume is low or inconsistent (IP needs constant activity)
• You do not have monitoring expertise
• Your list quality is not consistently high
• You cannot maintain the IP through warm-up

The Cold Email Reality

Most cold email senders, including agencies like Alchemail, use shared infrastructure (Google Workspace and Microsoft 365) rather than dedicated IPs. Here is why:

1. Google and Microsoft maintain their IP pools at a level most individual senders cannot match
2. Domain reputation dominates filtering decisions for these providers
3. The cost and complexity of dedicated IPs is not justified for most operations
4. Shared IPs work fine when you control the domain-level factors

Managing IP Reputation Issues

Scenario 1: IP Pool Reputation Drops

Symptoms: Delivery rates drop across all domains simultaneously Diagnosis: Check Google Postmaster Tools IP reputation for all domains

Actions:

1. Reduce sending volume across all accounts
2. Check if multiple domains are affected (IP issue) vs. one domain (domain issue)
3. Increase warm-up activity to generate positive engagement
4. Wait for the IP pool to recover (usually 1-7 days)
5. Consider temporarily switching some accounts to the other provider (Google to Microsoft or vice versa)

Scenario 2: Microsoft IP Relay Pool Assignment

Symptoms: Outlook delivery degrades specifically Diagnosis: Microsoft may have moved your accounts to a lower-reputation relay pool

Actions:

1. Review Microsoft SNDS data
2. Contact Microsoft support for relay pool review
3. Reduce sending volume to Outlook recipients
4. Improve engagement metrics to get reclassified

Scenario 3: IP Blacklisted

Symptoms: Bounces mentioning blacklist or specific RBL name Diagnosis: Check MXToolbox for IP blacklist status

Actions:

1. Identify which blacklist and the reason
2. For shared IPs, report to your provider (Google or Microsoft)
3. They will handle delisting for their IP ranges
4. Monitor for resolution

IP Reputation Best Practices for Cold Email

1. Maintain Clean Lists

Every bounce and spam complaint from your sending affects the shared IP pool. Keep bounce rates under 2% and spam rates under 0.3%. Verify all emails with tools like LeadMagic before sending.

2. Warm Up Properly

Proper warm-up generates positive engagement signals that benefit both your domain and IP reputation. See our cold email deliverability guide for warm-up best practices.

3. Use Both Providers

Split your domains between Google Workspace and Microsoft 365. If one provider's IP pool has issues, the other continues operating. This is standard practice at Alchemail.

4. Monitor Regularly

Check Google Postmaster Tools and Microsoft SNDS weekly. Set up automated monitoring where possible. Early detection of IP reputation issues prevents escalation.

5. Focus on Domain Reputation

Since domain reputation is your primary lever, invest most of your energy there. Proper SPF, DKIM, and DMARC configuration and good sending practices protect both domain and IP reputation.

Frequently Asked Questions

Does Google Workspace use dedicated or shared IPs?

Google Workspace uses shared IP pools. Your emails are sent through the same IPs as millions of other Workspace users. Google manages the reputation of these pools actively. You can find your current sending IP by checking email headers, but it may change between sends.

Can I request a specific IP from Google or Microsoft?

No. Standard Google Workspace and Microsoft 365 plans do not allow IP selection. Enterprise plans may offer some IP options, but for cold email purposes, shared infrastructure works well when you manage domain-level factors properly.

How does IP reputation affect my cold email deliverability?

IP reputation is one factor among many. For Google Workspace and Microsoft 365 senders, domain reputation, authentication (SPF, DKIM, DMARC), content quality, and engagement metrics all play larger roles. IP reputation matters most when it is very bad (blacklisted) or when domain reputation data is sparse (very new domains).

Should I worry about IP reputation if I use Google Workspace?

Monitor it, but do not obsess over it. Google's shared IP pools are well-maintained. Your domain reputation has more impact on your deliverability than the IP pool. Focus on list quality, warm-up, authentication, and sending practices. Only escalate IP concerns if you see sudden, unexplained drops across all your domains simultaneously.

What happens if the IP pool I am on gets blacklisted?

Your provider (Google or Microsoft) handles delisting for their IP ranges. This typically resolves within 24-72 hours. In the meantime, emails may bounce or go to spam. Having accounts on both providers gives you a fallback when one provider's IPs have issues.

Get Expert Deliverability Management

IP reputation is just one piece of the deliverability puzzle. At Alchemail, we monitor all reputation signals across 100+ domains and 200+ accounts per client, maintaining spam rates under 0.3% and open rates of 40-60%. We have generated $55M+ in pipeline for clients in 2025 by keeping emails where they belong: in the inbox.

Book a call with us to discuss your deliverability needs.