Dedicated IP for Cold Email: Why It Matters, When It Helps, When It Doesn't

The IP address your cold email leaves from is the foundation of everything that comes after it. Authentication, warmup, content tuning, sequence design — every other deliverability lever stacks on top of one question: is your sending IP carrying its own reputation, or is it sharing a reputation pool with strangers?

This is the pillar guide on dedicated IPs for cold email. By the end you will have:

• A precise definition of dedicated vs shared IPs, with the reputation mechanics behind both
• Three real failure modes where shared IPs collapse a cold email program, drawn from patterns we see weekly
• How major receiving providers (Gmail, Microsoft, Yahoo, Apple) actually score IP reputation in 2026
• The math of how many mailboxes per IP is healthy, and what happens past that point
• How ColdRelay assigns dedicated IPs per customer (the actual mechanics, not the marketing pitch)
• Honest cases where a shared IP is fine and dedicated IPs are overkill
• A practical Q&A for the decisions you will make in the next 60 minutes

If the only thing you take away is the formula, it is this: at any cold email volume that would make Gmail nervous about you (so, basically any volume worth running for revenue), you want a dedicated IP. The rest of this guide explains the why and the how.

TLDR — The 30-Second Answer

• A dedicated IP is an IP address that only you send from. No other tenant, no other customer, no other workload shares the IP's reputation pool.
• A shared IP is the opposite — your sending blends with hundreds or thousands of other senders' traffic, and the IP's reputation reflects the average of all of them.
• For cold email, shared IPs fail you in three ways: reputation isolation is impossible, blocklist accountability falls on someone else, and warmup signal is washed out by other senders' noise.
• Modern receiving providers (Gmail, Microsoft, Yahoo, Apple) score reputation per IP and per domain. Dedicated IPs let you control both signals; shared IPs only let you control the domain signal.
• The healthy ratio is 100 to 150 mailboxes per dedicated IP, with the IP earning reputation from 2 outbound + 2 warmup per mailbox per day.
• ColdRelay assigns a dedicated IP to every domain you provision, isolated inside its own Azure tenant. No shared IP, no cross-customer contamination, no surprise neighbors.
• Shared IPs are fine if you are sending fewer than 50 to 100 cold emails per day total, you have no plans to scale, and you are okay with intermittent deliverability fluctuations from other senders' behavior.

For everything beyond that — keep reading.

What Is a Dedicated IP, Exactly?

An IP address is a numeric identifier (e.g., 198.51.100.42) attached to every internet-connected machine. For email, the IP your outgoing mail server uses becomes one of the inputs receiving providers use to decide whether your message lands in primary inbox, promotions, or spam.

A dedicated IP is an IP that is bound to one and only one sender. You alone are sending email from it. Every metric the receiving providers track for that IP — volume, complaint rate, bounce rate, engagement rate, blocklist status — reflects exclusively your sending behavior.

A shared IP is an IP that multiple senders share. The IP's reputation is the weighted average of every sender's behavior on it. This is the default for Google Workspace, Microsoft 365, and the vast majority of cold email "infrastructure" providers who are actually just resellers of shared cloud-hosted SMTP.

Where the IP fits in the email path

When you send a cold email, the path looks like this:

Your sending tool (Instantly, Smartlead, etc.)
    └── Authenticates via SMTP/API to your infrastructure provider
        └── Infrastructure provider's mail server (with an IP address)
            └── DNS resolution for the recipient's domain
                └── Recipient's MX server (Gmail, Outlook, etc.)
                    └── Spam filter scores the message
                        └── Inbox, promotions, or spam

The IP at step 3 is the one receiving providers see. They check it against:

• Their own internal reputation databases. Built up over years of observed sending behavior.
• Public blocklists. Spamhaus, Spamcop, Barracuda, SURBL, and dozens of smaller lists.
• Authentication results. SPF passes only if the IP is authorized for the sending domain.
• Engagement signals. Have recipients on prior emails from this IP opened, replied, and not marked as spam?

A dedicated IP gives you a clean slate (or a recoverable history) on all four of those checks. A shared IP means your sending behavior gets blended with whatever the IP's other tenants are doing.

What it is NOT

Two clarifications, because the terminology is sloppy in the industry:

1. A dedicated IP is not the same as a dedicated server. You can have a dedicated IP on a shared server (one machine, multiple IPs, each tenant gets one IP). The IP is what reputation tracks; the server is the underlying hardware.

2. A dedicated IP is not the same as a static IP for outbound. A "static IP" in the cloud-networking sense just means the IP doesn't change on reboots. Static IPs can still be shared if multiple workloads are sending from them. The dedicated-vs-shared distinction is about who is sending from the IP, not whether the IP rotates.

Why Cold Email Specifically Needs Dedicated IPs

Marketing email and transactional email tolerate shared IPs reasonably well. Cold email does not. The reason is structural: cold email's deliverability profile is the worst case for IP reputation isolation.

Reason 1: Cold email starts with zero engagement signal

A marketing email goes to people who opted in. They expect the message. Open rates start at 20%+ and reply rates at 5%+. The receiving provider sees positive engagement and updates the IP's reputation favorably.

A cold email goes to someone who has never heard of you. Open rates start at 30 to 50% if everything is dialed in. Reply rates start at 1 to 5%. Spam complaint rates can spike before you have learned the audience. On a shared IP, those weak early engagement signals get diluted in the pool of every other sender's traffic — but they still pull the IP's reputation down, and the other tenants on the IP feel the damage too. On a dedicated IP, the weak early signal is yours alone, you can identify it, you can fix it. The signal is isolated and actionable.

Reason 2: Cold email's volume profile is "small and steady," not "big and bursty"

Most receiving providers' reputation models give the most weight to per-IP daily volume and how that volume is trending. Cold email has a specific profile: a few hundred to a few thousand emails per day from each domain, sustained for weeks. That profile is well-served by a dedicated IP, where the cold email volume is the entire signal for the IP — receiving providers see a consistent identity and learn to trust it.

On a shared IP, the cold email volume is one stream within a larger pool. The IP's overall volume profile (say, 50,000 emails per day across all tenants) doesn't reflect any individual sender. Receiving providers cannot build the per-sender trust model they would with a dedicated IP. Worse, the IP's reputation now answers to other senders' bursty behavior (a transactional sender hitting a notification spike, for example), which can introduce volatility that has nothing to do with your campaigns.

Reason 3: Blocklist accountability falls on someone, and that someone is you (or not)

When an IP gets listed on Spamhaus or Spamcop, it stays listed until somebody requests delisting and demonstrates the underlying issue is fixed. On a dedicated IP, that somebody is you. You see the listing, you take the action, you control the timeline.

On a shared IP, that somebody is your infrastructure provider, and the timeline is whenever they get to it (if they monitor at all). Many cold email teams have spent days delivering into spam without knowing the upstream IP was listed, because nobody on their team was responsible for blocklist monitoring — the shared IP was supposed to be the provider's problem.

For more on this, see IP Blacklist Check: The Complete Guide and Domain Blacklist Check Guide.

Reason 4: Warmup is per-IP, not just per-mailbox

Warmup builds reputation by sending engaging email and receiving positive responses. The engagement signal accrues to both the sending domain AND the sending IP. On a dedicated IP, your warmup volume is the only signal building the IP's reputation — every peer-to-peer warmup send moves the needle.

On a shared IP, the warmup signal from your mailboxes is one drop in a larger pool. Receiving providers can't distinguish your specific warmup pattern from the other tenants' sending behavior. Your warmup is effectively building reputation for the pool, not for your identity.

For the warmup mechanics in detail, see Cold Email Warmup: The Complete Guide.

Three Real Failure Modes With Shared IPs

These are patterns we see repeatedly in customer conversations and in deliverability post-mortems across the industry. The names and specifics are generalized, but each pattern represents an entire class of failures.

Failure 1: The "Sudden Tank" — a neighbor's bad campaign nukes your IP overnight

You have been sending cold email for three months. Open rates are steady at 42%. Reply rates around 4%. Things are working.

Monday morning, your open rates drop to 11%. Bounce rate spikes. Spam complaints from a marketing campaign you don't recognize start appearing in your DMARC reports — except they don't, because the campaign was sent from a different domain entirely. But the IP your domain uses is now on three blocklists.

What happened: another sender sharing your IP ran a promotional campaign to a stale list, generated a spam complaint spike, and the IP's reputation crashed. The blocklists picked it up within hours. Your sending domain is fine, your SPF/DKIM/DMARC are fine, your content is fine. The IP is now toxic and there is nothing you can do — the listing isn't tied to your domain, so you can't request delisting yourself, and your infrastructure provider has dozens of other customers on the same IP whose behavior is just as plausibly the cause.

What dedicated IPs change: if the offending campaign were sent from your dedicated IP, you would know within hours (your DMARC reports would correlate, your sending volume metrics would correlate). If the campaign were sent from someone else's dedicated IP, your IP would be unaffected. The shared-IP failure mode disappears entirely.

Failure 2: The "Slow Bleed" — months of mediocre deliverability nobody can explain

The setup looks right. Authentication passes, content is tight, list is clean. But open rates are stuck at 28%. Reply rates at 1.5%. You know the team writing the campaigns is good; the inbox-placement-test results say you're landing in promotions or spam at meaningful rates.

You audit everything. Authentication, warmup, content, list hygiene, sending patterns. Each passes. The deliverability remains mediocre for months.

What's actually happening: the shared IP your messages leave from has a chronically average reputation. Not toxic, not high-quality — just average. Average for cold email means promotions tab. There is no single problem to fix because the IP's reputation is the aggregate of every tenant on it, and the average of every cold email sender on a shared IP is bottom-of-the-promotions-tab.

What dedicated IPs change: on a dedicated IP, your reputation is purely a function of how you send. If your warmup is good and your content is dialed in, your IP's reputation rises until you're consistently inboxing. There is no aggregate floor pulling you down to "promotions tab average."

Failure 3: The "Provider Won't Help" — the support ticket that goes nowhere

Your campaigns aren't landing. You open a support ticket with your infrastructure provider. You ask for the IP your domain is sending from. They send you back a /24 block ("your traffic uses IPs in the 198.51.100.0/24 range").

You ask which specific IP your sending uses. They can't tell you — it rotates across the pool. You ask what other tenants are on the IP. They can't tell you — other customers' identities are confidential. You ask for the IP's blocklist status and reputation history. They give you a generic dashboard showing the pool's average health.

You are debugging in the dark. No specific IP, no peer accountability, no recourse beyond "we'll look into it."

What dedicated IPs change: you own a specific IP. You can check its reputation on Talos, Sender Score, mxtoolbox.com, mail-tester.com, and any other reputation service. You can monitor its blocklist status continuously. You can correlate sending behavior with deliverability changes. Debugging stops being a black box.

How Receiving Providers Actually Score IP Reputation in 2026

Each major receiving provider has its own model. Knowing how they work shapes how you should think about dedicated IPs.

Gmail (and Google Workspace recipients)

Gmail tracks per-IP and per-domain reputation through Google Postmaster Tools. For high-volume senders (over 5,000 messages per day to Gmail), the per-IP reputation score appears in Postmaster Tools as Bad / Low / Medium / High. For lower volume senders, the score is hidden but still operative behind the scenes.

The signals that move the score:

• Spam complaint rate (most heavily weighted): must stay below 0.3% to maintain reputation, ideally below 0.1%
• Authentication results: SPF, DKIM, DMARC alignment
• Encryption rate: TLS on outbound
• Engagement signal: opens, replies, time spent reading
• Domain reputation (which interacts with IP reputation in Gmail's blended score)

For more on monitoring this, see Google Postmaster Tools for Cold Email.

On a dedicated IP, all of these signals reflect your sending. You see your own data in Postmaster Tools, you can correlate sending changes with reputation changes, and you can take action.

On a shared IP, Postmaster Tools shows the pool's blended data. Your individual sending pattern is invisible. Any action you take affects the pool's reputation only marginally.

Microsoft (Outlook.com, Hotmail, Microsoft 365 recipients)

Microsoft's SNDS (Smart Network Data Services) provides per-IP reputation data: filter result, complaint rate, traps hit. You can only see data for IPs you own — meaning if you're on a shared IP, you can't get this data at all (the IP's owner can, but you cannot).

Microsoft's reputation also leans heavily on:

• Complaint rate (their threshold is tight; over 0.1% triggers throttling)
• Spam trap hits: any hit damages reputation significantly
• Volume consistency: bursty senders look more suspicious than steady ones

Dedicated IP: you can register the IP with SNDS, see your own data, identify spam trap hits early, fix list hygiene before things spiral.

Shared IP: zero visibility into Microsoft's signal. You're flying blind on what is increasingly important since Microsoft consolidated consumer email into Outlook.com.

Yahoo / Apple iCloud

Both providers have less public tooling than Gmail and Microsoft, but their underlying reputation models are similar: per-IP and per-domain scoring, heavy weighting on complaint rates, engagement signals as the secondary trust input.

The same dedicated-IP-vs-shared-IP dynamic applies. On dedicated, your reputation is yours. On shared, you're pooled.

Public reputation services

External services that score IPs include:

• Talos Intelligence (Cisco): trust scores for IPs based on observed sending patterns
• Sender Score (Validity): 0 to 100 score based on historical performance
• mail-tester.com: per-email score that includes IP reputation as one component (see Mail-tester for Cold Email)
• MXToolbox blacklist check: queries dozens of blocklists at once (see MXToolbox Blacklist Check Guide)

On a dedicated IP, these scores are yours. You can monitor them, correlate them with sending changes, and act. On a shared IP, the scores reflect the pool — useful for the pool's owner, less useful for you.

The Math: How Many Mailboxes per Dedicated IP?

A dedicated IP needs enough sending volume to maintain reputation, but not so much that any single behavior spike destabilizes it. The sweet spot for cold email is 100 to 150 mailboxes per dedicated IP, with each mailbox sending 2 outbound + 2 warmup messages per day.

Why 100 to 150 specifically

The lower bound (100): below this volume, the IP doesn't accumulate enough engagement signal to build a strong reputation. Receiving providers can't gauge whether the IP is trustworthy because there isn't much data. The IP gets categorized as "low volume, neutral" — which means promotions tab, not primary inbox. A 50-mailbox dedicated IP sees 100 outbound emails per day, which is below the threshold where Gmail starts assigning a meaningful reputation score.

The upper bound (150): above this volume, the IP's total daily output (300+ outbound) starts to look bursty if any single mailbox has a bad day. Spam complaint spikes from one campaign can drag the whole IP's reputation. Volume diversity (mailboxes from many domains) also becomes a problem; receiving providers prefer IPs with clear sender identity.

At 150 mailboxes × 4 emails per day total, the IP runs at 600 total outbound (300 prospect + 300 warmup) per day. That is the sweet spot where:

• Volume is high enough for receiving providers to build a clear reputation signal
• Per-mailbox volume per day stays at the safe 2-prospect-emails cap (see How Many Mailboxes Do You Need for Cold Email for the math)
• Spam complaint thresholds (0.1% of 600 = 0.6 messages per day) leave meaningful headroom
• Warmup signal is meaningful but not dominant

What happens past 150

We have seen customers ask "can I push to 200 mailboxes on one IP?" The honest answer is: technically yes, behaviorally no. Past 150, every incremental mailbox dilutes the IP's reputation slightly. By 200 mailboxes, receiving providers see an IP that is sending 800 emails per day across many domains and mailbox identities — a pattern that increasingly looks like a marketing platform, not a B2B outbound sender. Promotions-tab placement risk goes up.

The ColdRelay infrastructure enforces this. Every dedicated IP is capped at 150 mailboxes (the MAILBOXES_PER_DOMAIN_MAX constant in our pricing module). If you provision a 16th domain on the same account, you also get the 16th dedicated IP — the system never overcommits an IP.

What happens below 100

A dedicated IP serving fewer than 100 mailboxes is technically possible but economically wasteful. Each ColdRelay dedicated mailserver costs around $12/month to run; spreading that across 50 mailboxes means $0.24/mailbox just for the server, before any of the per-mailbox cost. Below 100 mailboxes per IP, the per-mailbox cost stops being competitive with shared infrastructure.

This is why ColdRelay's domain pricing rounds: every domain gets its own dedicated IP, and the pricing tiers assume domains are running at meaningful mailbox density.

How ColdRelay Assigns Dedicated IPs Per Customer

Now the actual mechanics. When you provision a domain on ColdRelay:

1. A new isolated Azure tenant spins up. This is a separate tenant from every other ColdRelay customer's tenant. There is no shared infrastructure at the tenant level.

2. A dedicated mail server starts up inside that tenant. This server hosts mailboxes for this domain only. It is not shared across customers.

3. A dedicated IP is allocated to the server. This IP is bound to the mail server for the lifetime of the domain on ColdRelay. It is not rotated, it is not shared with other customers, it is not part of a pool.

4. DNS records are configured automatically. SPF authorizes the dedicated IP. DKIM signs mail with a domain-specific key. DMARC reports flow to a customer-controlled address. (See How ColdRelay Auto-Configures SPF, DKIM, and DMARC for the mechanics.)

5. Warmup begins on day one. Each mailbox on the domain joins the peer-to-peer warmup network and starts building IP and domain reputation simultaneously. The 2-outbound + 2-warmup-per-mailbox-per-day cadence keeps the IP's reputation building without overcommitting.

6. Reputation monitoring runs continuously. Blocklist checks across major lists, Postmaster Tools data ingestion where available, internal placement scoring. Customers see the data; ColdRelay operates on the data.

What this means in practice

You can:

• Look up your dedicated IP for any domain in the ColdRelay dashboard
• Check that IP's blocklist status on any external service
• Register the IP with Google Postmaster Tools and Microsoft SNDS for direct reputation visibility
• Correlate any deliverability change with your own sending behavior, with confidence that no other customer's actions can move the metric
• Take action on the IP's reputation (warmup adjustments, sending pace, content) and see the result reflected in your IP's reputation alone

You will not:

• Wonder which other customers are on your IP (none are)
• Watch your reputation tank because of someone else's bad campaign
• Get stuck behind a support ticket about a shared pool
• Find your IP on a blocklist for traffic you never sent

For comparison vs the alternatives, see Best Cold Email Infrastructure Providers in 2026.

When Shared IPs Are Actually Fine

The honest version: dedicated IPs are not the right answer for every team. Three scenarios where shared infrastructure makes sense:

Scenario 1: You are sending fewer than 50 cold emails per day

If your outbound program is 50 emails per day total (so, 25 mailboxes or fewer at the canonical 2-per-day cap), a dedicated IP is overkill. The IP volume is too low to build a meaningful reputation signal anyway. You're in the "neutral, low-volume" reputation bucket where dedicated and shared perform roughly the same.

At this volume, you might as well use Google Workspace directly, accept the shared-IP fluctuations, and focus your energy on copy and targeting. The shared IP isn't ideal, but at 50 emails per day, you have so little signal that "ideal vs not" isn't moving the needle.

Scenario 2: You are experimenting and have no plans to scale

If you are running a 30-day cold email test to validate whether outbound is a channel for you, the dedicated-IP overhead (per-domain pricing, warmup time, setup) might exceed the test budget. Use a shared-IP provider, accept the deliverability noise, run the test, decide based on the result.

This is a "try before you commit" path. The shared-IP results will be noisier than dedicated, so weight your conclusions accordingly. If the shared-IP test shows promise, the dedicated-IP setup will likely outperform the test results once the IP reputation has built.

Scenario 3: You have a separate sending function with different requirements

Some teams send transactional email (password resets, receipts, account notifications) where the volume is low and recipients explicitly expect the message. A shared IP designed for transactional sending is typically fine for this — receiving providers treat transactional mail with more deliverability latitude.

Keep transactional and cold email infrastructure separate. They do not belong on the same IPs or domains.

The Practical Q&A

Questions we get from customers in the first 60 minutes of setup.

"How do I check my current sending IP?"

If you're using a sending platform connected to infrastructure: check the platform's SMTP settings. The hostname there will resolve to an IP. That is your sending IP.

Or send yourself a test email and check the headers. In Gmail: open the email, click the three-dot menu, "Show original." The Received: headers show the IP path. The last hop before your inbox is the IP of the sender.

For ColdRelay customers: the dashboard surfaces the dedicated IP for each domain on the domains page.

"Can I keep using my old shared IP while warming a new dedicated one?"

Yes, and you should. Build the dedicated IP's reputation through warmup (4 to 6 weeks) before migrating cold sends to it. Run the shared and dedicated IPs in parallel during the transition. Migrate domain-by-domain rather than all at once.

The migration cost: the new IP starts at neutral reputation and takes the warmup period to climb to "trusted." During that window, deliverability from the new IP will be lower than the established (shared or dedicated) IP. Plan for it.

"Does a dedicated IP guarantee inbox placement?"

No. The IP is one input to the receiving provider's reputation model. Authentication, content, list hygiene, engagement signal, domain reputation, sending pattern, and warmup all still matter. A dedicated IP is a multiplier on those — if you do everything else right, dedicated outperforms shared significantly. If you skip authentication and send spam content from a dedicated IP, you will tank the IP's reputation faster than you could on a shared IP (because the dedicated IP's reputation is yours alone — there's no pool to dilute your behavior into).

"What's the warmup timeline for a new dedicated IP?"

Realistic numbers:

• Week 1: warmup-only on all mailboxes. Zero prospect emails. Receiving providers see a low-volume, high-engagement profile and assign neutral reputation.
• Week 2: warmup continues. Begin prospect sends at 25% capacity (so, 0.5 prospect emails per mailbox per day on average — though daily-allocation logic typically makes this every-other-day rather than half-emails).
• Week 3 and 4: ramp prospect sends to 100% (the canonical 2 per mailbox per day). Warmup continues at 2 per mailbox per day. The IP reaches steady-state reputation.
• Week 5+: full operation. Deliverability should be inboxing for the majority of recipients on Gmail / Microsoft / Yahoo / iCloud, assuming list quality and content are reasonable.

"How do I monitor my dedicated IP's reputation?"

A few sources, weekly cadence:

1. Google Postmaster Tools: register the IP and the sending domain. Daily score updates for high-volume senders.
2. Microsoft SNDS: register the IP. Daily filter result and complaint data.
3. Sender Score (Validity): monthly score, 0 to 100. Useful for tracking trends.
4. Talos Intelligence: trust score for the IP.
5. MXToolbox: blocklist status (see the MXToolbox guide).

ColdRelay's dashboard pulls Postmaster Tools data and runs internal placement testing, so customers see consolidated reputation data without having to monitor each source manually.

"What's the cost difference between shared and dedicated IPs?"

Shared infrastructure (Google Workspace, Microsoft 365, resold cloud SMTP) typically runs $3 to $7 per mailbox per month. Dedicated infrastructure on ColdRelay runs $0.55 to $1.00 per mailbox per month depending on tier. The dedicated infrastructure is cheaper per mailbox, with the caveat that you need to commit to a meaningful mailbox count (100+) to hit the tier breaks and amortize the dedicated server cost.

For the full cost analysis, see Cold Email Infrastructure Cost Breakdown.

"What if my dedicated IP gets blocklisted?"

Three possible paths depending on the listing:

1. Spamhaus or major list: request delisting through the list's process. Demonstrate that the underlying issue (whatever caused the listing) is fixed. Typical resolution: 1 to 3 days.
2. Minor or transient list: many lists auto-expire after the listing trigger passes. Wait 7 days, recheck, often resolved.
3. Major reputation damage: rotate the IP if the listing is severe enough that the IP's reputation won't recover quickly. ColdRelay can issue a new IP for the domain (with a fresh warmup cycle required).

The key advantage of dedicated: you know exactly what happened, you can fix it, and the resolution timeline is yours to manage.

"Can I bring my own IP?"

For most customers, no. Bringing your own IP requires significant infrastructure setup, IP procurement, ASN management, abuse mailbox configuration, and authentication chain coordination. It is appropriate for very large senders (enterprise marketing teams, high-volume transactional platforms) but not for B2B outbound at typical cold email scale.

ColdRelay assigns dedicated IPs from our own allocation, with a clean history and proper PTR records. For 95%+ of cold email use cases, this is what you want — the operational complexity of BYO-IP is not worth it.

When NOT to Migrate to Dedicated IPs

Three honest cases.

You're sending fewer than 100 cold emails per day total

The IP volume is too low. Receiving providers don't have enough signal to score the IP meaningfully. You will get the same deliverability on a shared IP at this volume, and you skip the warmup period.

You're using a sending tool that doesn't support custom SMTP

A few cold email platforms only work with their own infrastructure. If you're tied to that platform and switching costs are real, the shared IP is effectively part of the package. You can still optimize within the constraint.

You're not committing to outbound for at least 6 months

Dedicated IP reputation takes 4 to 6 weeks to fully build. Running outbound for 3 months on a dedicated IP means most of your sending happened while the IP was still building reputation — the deliverability benefit barely had time to materialize. If you're not committing past 6 months, the timeline math is borderline.

FAQ

What is a dedicated IP in cold email?

A dedicated IP is an IP address used exclusively by one sender. For cold email, this means your sending reputation is yours alone — not pooled with other tenants. ColdRelay assigns a dedicated IP per domain, isolated inside its own Azure tenant.

Do I need a dedicated IP for cold email?

If you're sending more than 100 emails per day and plan to scale, yes. Below that volume the IP doesn't accumulate enough signal to justify the warmup overhead. Above that volume, dedicated IPs significantly outperform shared IPs on inbox placement, reputation control, and blocklist accountability.

How much does a dedicated IP cost for cold email?

On ColdRelay, dedicated IPs are bundled with domain pricing — every domain gets its own dedicated IP at no additional charge. Per-mailbox pricing tiers from $1.00 (under 200 mailboxes) down to $0.55 (5,000+) cover the full infrastructure including the dedicated IP.

How long does it take to warm up a new dedicated IP?

4 to 6 weeks to reach full reputation. Warmup-only for week 1, partial sending in week 2, full sending by week 4. Continued warmup at 2 messages per mailbox per day forever (it's not a one-time event).

Can a dedicated IP get blacklisted?

Yes. Any IP can be blacklisted if the receiving algorithms decide the sending behavior matches spam patterns. On a dedicated IP, the cause is always traceable to your sending. On a shared IP, the cause could be any tenant's behavior — including yours. Dedicated makes recovery faster because you know what happened.

Is a dedicated IP the same as a static IP?

No. A static IP is an IP that doesn't change on infrastructure restarts; it can still be shared. A dedicated IP is one used by a single sender; it is usually static, but the defining feature is exclusivity, not stability.

How many emails can I send from one dedicated IP?

Around 600 total daily messages is the sweet spot — that is 150 mailboxes × 4 messages per day (2 outbound + 2 warmup). Below that, the IP doesn't accumulate enough engagement signal. Above 150 mailboxes per IP, reputation starts to dilute. ColdRelay caps at 150 mailboxes per domain (= per dedicated IP) for exactly this reason.

Does ColdRelay provide dedicated IPs to every customer?

Yes. Every domain you provision on ColdRelay gets its own dedicated IP, isolated inside its own Azure tenant, with automated SPF/DKIM/DMARC configuration. There is no shared IP option — dedicated is the only mode ColdRelay operates in.

Can I check my dedicated IP's reputation?

Yes. The IP is yours, so all reputation services work for you: Google Postmaster Tools, Microsoft SNDS, Sender Score, Talos Intelligence, MXToolbox blocklist queries, mail-tester.com per-message scoring. ColdRelay's dashboard aggregates the major signals; you can also monitor independently.

Next Steps

The IP is the foundation. Everything else (authentication, warmup, content, sequence design, list hygiene) compounds on top of it. If you're scaling cold email and you have not made an explicit choice about dedicated vs shared, you have made the shared choice by default — and you're inheriting all of the failure modes above.

Three concrete next steps:

1. Check your current sending IP and its blocklist status. If you don't know your IP, find out today. If it's shared, you now know your deliverability ceiling.
2. Read the warmup guide. The warmup process is what turns a dedicated IP from neutral to trusted. The warmup cadence (2 messages per mailbox per day, peer-to-peer) is what builds the engagement signal.
3. Compare infrastructure providers. Decision-matrix for picking the right dedicated infrastructure for your scale and ICP.

When you are ready to provision dedicated infrastructure: start with ColdRelay. First dedicated IP active in 60 minutes, warmup begins immediately, deliverability monitoring runs continuously.

ColdRelay assigns dedicated IPs per domain on isolated Azure tenants. There is no shared IP option in our infrastructure — every customer's reputation is theirs alone. The numbers in this guide (100 to 150 mailboxes per IP, 2 outbound + 2 warmup per mailbox per day, tiered per-mailbox pricing) come directly from the canonical pricing module that powers our mailbox calculator and pricing page.