How to Check If Your Cold Email Sending IP Is Dedicated

The fastest way to check is to look at your mailbox or SMTP provider's admin settings or billing page for a line that says "dedicated IP," "static IP," or shows an IP address tied only to your account. If you can't find one, or your provider's plan page doesn't mention IPs at all, you're almost certainly sending on a shared IP pool. You can confirm this technically by running an SMTP header trace or an IP reputation lookup to see if the IP resolves to a known shared-hosting range used by many unrelated domains.

Most senders assume they have a dedicated IP because they're paying for a "business" email plan. In reality, Google Workspace, Microsoft 365, and most SMTP relay services route outbound mail through large shared IP pools by default. Here's how to verify it, not guess.

What does "dedicated sending IP" actually mean?

A dedicated IP is an IP address used exclusively by one sender (one company or one domain) to send outbound email. No other customer's mail touches that IP. This matters for cold email because:

• Your sending reputation is isolated. A reckless sender on a shared IP can't tank your deliverability.
• Inbox providers (Gmail, Outlook) build a reputation history tied to that specific IP over time, which is easier to manage.
• If something goes wrong, you can pinpoint the cause instead of troubleshooting blind alongside strangers.

A shared IP means your mail is mixed with mail from other customers of the same provider. If even a few of them send spammy campaigns, blocklist flags and spam-folder placement can affect your mail too, even though you did nothing wrong.

How do I check if my current sending IP is dedicated?

Run through these checks in order. They take about 10 minutes total.

1. Check your provider's dashboard or plan documentation

Log into your mailbox or ESP admin panel and look for:

• A setting literally called "Dedicated IP," "Static IP," or "IP Pool" under sending/deliverability settings.
• Your plan tier. Dedicated IPs are almost always a paid add-on or a higher-tier feature, never a silent default.
• Billing line items mentioning "IP address." If you're not being billed for one, you don't have one.

If you're on standard Google Workspace or Microsoft 365, stop here: neither offers dedicated outbound sending IPs for regular mailbox use. Mail routes through Google's or Microsoft's shared infrastructure. The same is true for most "unlimited mailbox" cold email providers unless they explicitly advertise dedicated IPs and show you the address.

2. Pull the actual IP from a message header

Send a test email to an address you control (a personal Gmail works), open the received message, and view the full header source (in Gmail: "Show original"). Look for the line:

• Received: from [IP address]. This is the IP your mail actually left from.

Note that address, then send a second test email a few minutes later. If the IP changes between sends, you are on a rotating shared pool, not dedicated. A dedicated IP is identical every time.

3. Run a reverse DNS (PTR) lookup on that IP

Use a free tool (MXToolbox, or the command dig -x [IP] in a terminal) to do a reverse lookup. Compare the result:

• Dedicated: the PTR record resolves to something tied to your domain or your provider's naming convention for your account specifically (a hostname that references your company or a unique identifier).
• Shared: the PTR resolves to a generic provider hostname shared across thousands of customers (a generic mail-relay naming pattern with no account-specific identifier), or to a cloud/hosting provider's default reverse DNS with no custom record at all.

4. Check the IP's reputation and "neighbors"

Look up the IP on a blocklist/reputation checker (MXToolbox Blacklist Check, Talos Intelligence, or Sender Score). If the tool shows reputation data referencing high overall sending volume inconsistent with your own activity, or the IP has a history of complaints that don't match your campaigns, that's a strong signal you're sharing it with other senders.

5. Ask your provider directly

If the above is inconclusive, ask support one direct question: "Is the IP address my mailbox sends from used exclusively by my account, or is it shared with other customers?" A provider offering genuine dedicated IPs will answer immediately and specifically, often giving you the IP and confirming it's assigned only to you. Vague answers ("our infrastructure is optimized for deliverability") usually mean shared.

Why does it matter whether my cold email IP is dedicated or shared?

For cold outbound specifically, where you're emailing people who haven't opted in, IP reputation is the single biggest lever on inbox placement. On a shared IP:

• You inherit the sending behavior of every other tenant on that IP, good or bad.
• If the IP gets blocklisted because of someone else's spam, your mail stops delivering too, often with no warning.
• You can't build a clean, predictable sending history, because the IP's reputation is a blend of everyone's mail.
• Diagnosing deliverability drops is nearly impossible. You can't tell if it's your content, your list, or another tenant's bad behavior.

On a dedicated IP, every reputation signal, spam complaints, bounce rate, engagement, is attributable entirely to your own sending. Warmup progress and domain reputation are yours to build and protect, instead of being diluted or dragged down by strangers.

How do I get a dedicated IP for cold email sending?

Standard Google Workspace and Microsoft 365 subscriptions don't offer this as a consumer feature. You need infrastructure built specifically for cold outbound. Look for a provider that:

• Explicitly states dedicated IPs (not just "premium" or "enhanced" delivery) and will tell you the IP address on request.
• Lets you choose or confirm IP geography (US vs. EU), which matters for domain and content relevance.
• Gives you full admin access to the mailboxes sitting on that IP, so you're not locked into their tooling.
• Sets up SPF, DKIM, and DMARC correctly for the sending domain tied to that IP. A dedicated IP without proper authentication still won't deliver well.

This is the core of what Inboxlogy provides: authorized Google Workspace and Microsoft 365 mailboxes running on dedicated US or EU IPs, with automated SPF/DKIM/DMARC setup, full API access, and 100% ownership and admin access over the mailboxes, starting at $2.80/mailbox per month with no setup fee. One thing worth being clear about: Inboxlogy provisions the dedicated infrastructure and authentication, but warmup itself runs inside whichever sending tool you connect it to (Instantly, Smartlead, ReachInbox, etc.), not inside Inboxlogy. The dedicated IP gives that warmup process a clean, isolated reputation to build on, rather than warming up alongside unrelated senders.

FAQ

Can two different domains share the same dedicated IP?

Technically yes, if they're both controlled by you and intentionally grouped. That's still "dedicated" in the sense that no outside sender touches it. It stops being dedicated the moment a provider puts an unrelated customer's domain on the same IP.

Does a dedicated IP guarantee better deliverability?

No. A dedicated IP removes the risk of inheriting someone else's bad reputation, but you still have to warm it up properly, authenticate the domain (SPF/DKIM/DMARC), and send relevant, low-complaint mail. A dedicated IP with no warmup and sloppy content performs worse than a well-managed shared IP.

Is it possible to have a dedicated IP but still fail SPF/DKIM checks?

Yes, and it's a common gap. The IP and the authentication records are separate things. You can have a perfectly clean dedicated IP that still lands in spam because SPF, DKIM, or DMARC aren't correctly configured for the sending domain. Always check both.

How long does it take to see the reputation benefit of switching to a dedicated IP?

There's no fixed timeline. It depends on sending volume and warmup pace in your sending tool, but a brand-new dedicated IP starts with no history at all, so it needs to be warmed up gradually just like a new domain. The benefit isn't instant. It's that the reputation you build afterward belongs entirely to you.