Blog
What is IP Rotation? A Complete Guide

What is IP Rotation? A Complete Guide

Last Updated on: Nov 16, 2026
•
5 min read
Summarize with

What happens when a large volume of cold emails goes through a single IP address? A blocklisting issue or sudden throttling can affect every mailbox connected to it.

IP rotation distributes email traffic across multiple IP addresses instead of relying on one. Dedicated IPs give senders more control over each IP's reputation and keep their sending activity separate from other senders.

However, adding more IPs doesn't guarantee better deliverability. Each IP needs proper configuration, a gradual increase in sending volume, and regular monitoring.

In this guide, I'll explain how IP rotation works, its common types, and how to manage IPs for cold email.

What is IP Rotation?

IP rotation means using multiple IP addresses to handle network traffic instead of relying on one static address. A routing rule determines which IP handles each connection or request.

The term is used in different areas of networking. Proxy services, for example, use rotating IPs to route web requests through different addresses. Email infrastructure can also use multiple sending IPs to handle different email streams.

When an email leaves an outbound mail server, the recipient's mail server can see the sending IP address. Mailbox providers consider its reputation when evaluating incoming messages.

What is IP Rotation?

For cold email, IP rotation generally involves assigning different groups of mailboxes or email streams to separate sending IPs. The infrastructure determines which IP handles each message.

That said, frequent IP switching isn't always a good idea. Google recommends sending from the same IP where possible. If multiple IPs are necessary, Google recommends using different IPs for different message types.

How Does IP Rotation Work?

An IP rotation setup uses multiple IP addresses and routing rules to distribute traffic.

How Does IP Rotation Work?

The process usually involves four steps:

  1. Create an IP pool: Set up multiple IP addresses for different sending requirements. These can be shared or dedicated IPs.
  2. Connect the sending infrastructure: Configure outbound mail servers to send through the assigned IP addresses.
  3. Set routing rules: Decide which IP handles each email stream, campaign, or group of mailboxes.
  4. Monitor each IP: Track sending activity, reputation, authentication, and delivery issues separately.

For cold email, keeping IP assignments stable is important. Groups of mailboxes should have a consistent sending path instead of switching between random IPs for every message. 

This guide to scaling email with API-driven IP pools explains how senders group IPs by campaign type.

Mailbox providers also consider domain reputation and authentication, along with list quality and spam complaints. A good IP reputation alone cannot guarantee inbox placement.

Google's official email sender guidelines cover these requirements in more detail.

What are the Different Types of IP Rotation?

IP rotation methods differ based on when and how the system switches between addresses.

What are the Different Types of IP Rotation?

Time-Based IP Rotation

Time-based rotation switches to another IP after a set period. For example, a system might change IPs every 10 minutes or every hour.

The switch happens according to a schedule, regardless of the traffic being handled.

For cold email, frequent switching can make it harder to maintain a consistent sending history. A stable IP assignment is usually a better approach.

Request-Based IP Rotation

Request-based rotation assigns a different IP to each request.

For example, a proxy service might use a new IP every time someone loads a webpage. In email, the equivalent would be sending each message through a different IP.

Frequent switching is not a recommended cold email practice. Each new IP needs to establish its own sending reputation.

Session-Based IP Rotation

Session-based rotation, also called sticky-session rotation, keeps the same IP throughout a session. The system switches to another IP when the session ends.

For email, a similar setup would keep a group of mailboxes assigned to the same IP over time. The assignment remains stable unless there's a reason to change it.

Strictly speaking, a stable mailbox-to-IP assignment is closer to a stable routing arrangement. That distinction matters when planning cold email infrastructure.

Random IP Rotation

Random rotation selects an available IP from the pool without following a set order.

The system can select a different IP for each request or session. Random IP selection is a poor fit for cold email because it creates inconsistent sending patterns.

Using many rapidly changing IPs and domains to distribute unwanted email can also resemble snowshoe spam.

Spamhaus explains how this practice spreads spam across multiple IPs and domains to evade reputation-based filters.

What are the Benefits of IP Rotation?

IP rotation can help manage email infrastructure when multiple sending IPs serve different purposes.

Its main benefits include:

  • Separate email streams: Different IPs can handle promotional, transactional, and other types of email.
  • Better control over IP reputation: Dedicated IPs let senders manage their own IP reputation.
  • Faster issue detection: Each IP can be monitored separately to identify sending issues.
  • Isolated campaigns and clients: Different sending groups can use separate IPs to keep their activity apart.
  • Room to scale: Additional IPs can support separate sending streams as infrastructure grows.
IP rotation does not improve poor list quality, high complaint rates, or weak domain reputation. It should be part of a wider email infrastructure plan.

What are the Common Use Cases of IP Rotation?

IP management becomes useful when different types of email traffic need separate sending paths.

  • Cold email agencies can assign separate sending infrastructure to different clients.
  • Sales teams running cold outreach can keep it on separate IPs from their company's regular business email.
  • New or untested lead lists can run on their own IPs, so any problems stay away from proven campaigns.
  • Different campaigns can use separate IP groups to make reputation monitoring easier.
  • High-volume senders can separate promotional emails from transactional messages.
The right setup depends on sending volume and email type. It also depends on the recipient provider and your ability to maintain each IP's reputation.

Static IP vs. Rotating IP: What's the Difference?

A static IP stays the same for each connection or sending session. A rotating IP setup switches between multiple addresses based on predefined rules.

Factor Static IP Rotating IP
What it is One static IP handles the traffic. Multiple IPs handle traffic based on routing rules.
IP assignment The IP address stays the same. The IP changes based on the selected method.
Reputation A sending history builds on one IP. Each IP builds its own reputation.
Management There is one IP to configure and monitor. There are multiple IPs to configure and monitor.
Best for It is best for consistent sending from one source. It is best for separate sending streams or specific routing needs.
Cold email fit It is a good fit when one sending IP meets the requirements. It is useful when multiple sending streams need separate IPs.
A static IP is easier to manage because there's only one sending address to monitor. Multiple IPs make sense when different email streams need separate sending paths.

Rotating IP vs. Dedicated IP: What's the Difference?

These terms describe two different things. Rotation describes how traffic moves between IP addresses. Dedicated describes who uses an IP address.

A dedicated IP can also be part of a multi-IP setup.

The more useful comparison is between shared and dedicated IPs.

Factor Shared IP Dedicated IP
Who uses it Multiple senders use the same IP. One sender uses the IP.
Reputation Other senders can affect its reputation. Reputation depends on your own sending activity.
Control The provider manages the shared IP. The sender has more control over its use.
Warmup The provider manages the shared pool. The sender needs to build its own sending history.
Cost The cost is usually included in the service plan. A dedicated IP often costs extra.
Best for It is best for senders who want a managed setup. It is best for senders who need greater control over their sending reputation.

Google confirms that activity from any sender using a shared IP can affect the reputation of other senders on that IP.

Dedicated IPs avoid that shared-sender issue, but they also make the sender responsible for maintaining the IP's reputation. They do not guarantee inbox placement or protect domain reputation from poor sending practices.

If you're moving to dedicated IPs, this guide on how to set up dedicated IPs for email outreach walks through the setup.

IP Rotation vs. Inbox Rotation: What's the Difference?

IP rotation and inbox rotation happen at different levels of the email sending setup.

IP rotation changes the outbound IP address. Inbox rotation changes the mailbox used to send an email.
Factor IP Rotation Inbox Rotation
What rotates Outbound IP addresses rotate. Sending mailboxes rotate.
Where it happens It happens in the email infrastructure or mail server. It happens in the sending software.
Main purpose It manages sending traffic across IPs. It distributes emails across multiple mailboxes.
What changes The sending server's IP address changes. The sender email address changes.
Main risk Frequent IP changes can create inconsistent sending patterns. Too much volume can overload individual mailboxes.

Inbox rotation does not automatically mean IP rotation.

For example, 20 mailboxes can send emails through the same outbound server and IP. In that setup, the mailboxes rotate, but the sending IP remains the same.

If those mailboxes use different outbound IPs, both types of rotation may happen together.

What are the Challenges of IP Rotation?

Managing multiple IPs also adds work.

Here are some important points to consider:

  • IP warmup: New IPs have little or no sending history. Microsoft says new IPs are more likely to face delivery issues until they build a positive reputation. A new IP can take a couple of weeks or less to ramp up, depending on sending volume, list accuracy, and complaint rates.
  • Email authentication: Every sending setup needs correct authentication. Google requires SPF or DKIM for all senders to Gmail accounts. Senders sending more than 5,000 messages per day to Gmail accounts must configure SPF, DKIM, and DMARC.
  • SPF lookup limits: RFC 7208 sets a limit of 10 DNS-querying terms during SPF evaluation. Adding more sending services can make this limit harder to manage.
  • DNS configuration: Google requires valid forward and reverse DNS records for sending IPs. The sending IP must match the IP address returned by the hostname's PTR record.
  • TLS requirements: Google requires a TLS connection when transmitting email to Gmail accounts.
  • Reputation monitoring: Each IP needs monitoring for its reputation, spam complaints, and delivery issues.
  • Frequent switching: Constantly replacing or switching IPs can make sending patterns harder to manage. Using many IPs and domains to distribute unwanted email can resemble snowshoe spam.
  • Infrastructure costs: Dedicated IPs add to infrastructure costs, and each one needs ongoing management.
Useful official resources include Google's sender requirements, Microsoft's guidance on new IPs, RFC 7208, and Spamhaus sender guidelines.

How to Choose the Right IP Strategy

The right setup depends on sending volume, email types, and how much control you need over each IP.

Keep these points in mind:

  • Understand how much email each sending IP handles before adding more addresses.
  • Use different IPs when promotional, transactional, and other email types need separate sending reputations.
  • A managed shared pool is a good fit for senders who don't need dedicated infrastructure. 
  • Dedicated IPs make sense when control over IP-level reputation is important and the sender can maintain them.
  • Keep IP assignments stable and avoid switching addresses for every message.
  • Set up SPF, DKIM, and DMARC where required. Also configure valid PTR records and TLS.
  • Track bounces and spam complaints for each IP, along with blocklist status.

Google recommends keeping spam rates below 0.10% in Postmaster Tools and avoiding rates of 0.30% or higher. Postmaster Tools also shows authentication results and delivery errors. Google retired its domain and IP reputation dashboards in 2025.

One important distinction: adding more IPs does not bypass Gmail's sender requirements or make unwanted email acceptable. Google advises senders to email people who want to receive their messages.

How Infraforge Helps With IP Rotation

If you're planning to use IP rotation for your cold email campaigns, Infraforge offers private email infrastructure with dedicated IPs. It helps you manage multiple IPs, domains, and mailboxes without handling every technical task manually.

Here's how Infraforge supports IP rotation:

  • Dedicated IPs: Your mailboxes send from private IPs instead of a shared pool, so other senders' activity doesn't affect your reputation.
  • Multi-IP provisioning: Purchase additional IPs as your sending grows and rotate across multiple IPs to spread volume and protect your reputation. Each additional IP costs $99 per month, billed quarterly.
  • Separate IPs for each workspace: Each workspace can use its own IP, so one client's campaigns don't affect another client's inbox placement. Domains and mailboxes can also be moved between workspaces.
  • IP visibility for each domain: A domain's A record shows the IP it uses. If an IP gets blocklisted, you can find the domains on it and pause only those mailboxes instead of your whole setup.
  • Automated DNS setup: Infraforge sets up DMARC, SPF, and DKIM records and custom domain tracking for your domains. Bulk DNS updates let you change records across multiple domains at once.
  • Sender rotation and sending limits: Built-in sender rotation and smart sending limits spread emails across mailboxes and keep daily volume under control.
  • Pre-warmed domains and mailboxes: Start your campaigns with pre-warmed domains and mailboxes instead of waiting for new ones to warm up.
  • Deliverability monitoring: Track the health of your domains and mailboxes with real-time deliverability monitoring and alerts.
  • API access and Salesforge integration: Manage your infrastructure programmatically through the Infraforge API, or connect Infraforge directly to your Salesforge sequences.

As a rule of thumb, keep each IP below 40 mailboxes. At that ratio, 200 mailboxes need about 5 IPs.

If you want to simplify IP rotation and manage your cold email infrastructure from one platform, explore Infraforge and get started with dedicated IPs.

Conclusion

IP rotation can help you manage multiple sending IPs and keep your cold email campaigns organized. 

The key is to use the right IP setup, warm up new IPs properly, and monitor their reputation.

If you're planning to set up IP rotation for your cold email campaigns, get dedicated IPs from Infraforge. 

It gives you the infrastructure to manage your sending IPs and scale your cold email operations with greater control.

Frequently Asked Questions

1. Is IP rotation good for cold email?

IP rotation can help organize multiple sending streams, but it does not guarantee better deliverability. Google recommends using the same IP where possible and assigning separate IPs to different message types when multiple IPs are needed.

2. How many IPs do I need for cold email?

There is no single number that works for every sender. The requirement depends on sending volume and email types. Recipient providers and the sending limits on each IP matter too.

Use only as many IPs as the infrastructure needs. Using far more IPs than your volume requires can look like snowshoe behavior to filters.

3. How often should I rotate IPs for email?

There is no universal rotation schedule. Frequent switching can make it harder to build a consistent sending history.

Keep IP assignments stable and change them when there is a clear infrastructure or operational reason.

4. Does inbox rotation also rotate IPs?

Inbox rotation does not always rotate IPs. It changes the sending mailbox, and the IP changes only when those mailboxes use different outbound IP addresses.

5. Does a new IP need warmup?

Yes, a new IP needs warmup because it has little or no sending reputation. Microsoft recommends a gradual ramp-up because new IPs are more likely to experience delivery issues until they build a positive reputation.

The ramp-up period depends on volume, list accuracy, and complaint rates. Pre-warmed domains and mailboxes can shorten the wait for new senders.

6. Does Infraforge rotate IPs automatically?

Infraforge's multi-IP provisioning lets you rotate across multiple IPs to spread sending volume and protect your reputation. Each workspace can use its own IP, and built-in sender rotation spreads emails across your mailboxes.

Scale outreach on private email infrastructure

Set up dedicated IPs, domains, and mailboxes.
Start with
4.7 rating on G2
Add as a preferred
source on Google