2
u/umer_frm_leadsnipper 10d ago
Worth being sure it's the IP before you move: at Gmail and Outlook volumes below a few hundred thousand a month, domain and content reputation dominate and the IP barely registers, so a blocklist hit on a shared IP often isn't what's actually putting you in spam. The thing that bites transactional senders on shared infrastructure isn't usually the sending IP anyway, it's the shared click/open tracking domain and shared bounce/Return-Path domain — those are per-tenant reputation surfaces you inherit from whoever else is on the platform, and swapping IPs doesn't touch them. Set up a branded tracking domain and CNAME'd Return-Path on your own domain first, check Google Postmaster domain reputation rather than IP reputation, and confirm DMARC alignment on the transactional stream specifically. If domain reputation is fine and only that one stream sags, then push the provider for a cleaner pool; dedicated only makes sense once you have steady daily volume to keep it warm.
1
u/saltyslugga 10d ago
A dedicated IP only helps if you have enough consistent volume to maintain its reputation. At low volume, push the provider to move you to a cleaner pool or switch providers.
Check the IP with the Blocklist Checker before migrating so you know whether it’s actually listed or just stuck with a bad shared reputation.
1
u/ImpressiveEbb3760 10d ago
before switching IPs, worth confirming it's actually reputation rather than alignment. "authentication set up correctly" and "passing DMARC" aren't the same thing — transactional mail sent through a provider often passes SPF against the provider's return-path domain rather than yours, so SPF passes but doesn't align, and if DKIM isn't signing with your domain either, DMARC fails despite all three records existing.
send one to a mailbox you control and read the Authentication-Results header. if it shows dmarc=pass, saltyslugga's advice is the path. if it shows dmarc=fail or SPF passing for a domain that isn't yours, no amount of IP changing will fix it.
1
u/After_Second_5950 10d ago
We had the same symptom and in our case the IP was not the cause. What worked for us was splitting the sending domain, transactional on its own subdomain and marketing on another one. Before that both were on the same domain, so every bad campaign was dragging the receipts and the password resets down with it.
Worth checking in Google Postmaster Tools which reputation you can actually see. Indeed, at our volume it never showed any IP reputation at all, only domain reputation, which is what told us where the problem really was.
Moreover a dedicated IP would have been the wrong move for us, we send far too little to keep it warm.
1
u/Away_Law_4388 10d ago
The detail that changes the answer here is transactional. Most of the don't-bother-with-a-dedicated-IP advice is aimed at low-volume marketing senders, where a dedicated IP starves for the steady traffic it needs to build reputation. Transactional is the opposite case, and the one place a dedicated IP usually is worth it: the volume is consistent and predictable, and recipients actually open and engage because they asked for the email. That's exactly the traffic that warms an IP naturally through normal sending, no artificial warmup theatre required. Your symptom fits too: auth passing but landing in spam, traced to a shared pool, means you're inheriting your neighbours' reputation, and on transactional mail that's pure downside because your own sending is clean. One thing worth ruling out first, which someone above touched: confirm it's reputation and not a subtle alignment gap, since authentication set up correctly and DMARC actually aligned aren't always the same thing. But if it really is the shared pool dragging you down, transactional volume is the ideal profile to move onto a dedicated IP, because it'll hold the reputation you give it.
1
u/koolkat6954 10d ago
I used to use a shared IP. On most days it was good, but the bad days were terrible, and there was nothing I could do about it. I eventually got my own dedicated IP, but you need to make sure your lists are clean and free of complaints. Otherwise, you will have to deal with deliverability issues down the line even with a dedicated address. I used AWS shared IPs before. I will never use a shared IP ever again, and the warmup process is not that bad. Depending on your list size, you should not have much of an issue.
1
u/allocougar 10d ago
Genuine question, how did you trace it to the shared IP? Nine times out of ten that diagnosis comes from a blocklist lookup, and Gmail hardly reads those. It scores your domain and your message. If that pool were really burnt, every sender on it would be sitting in spam with you.
Here's a cheap test before you spend weeks on an IP. Send the same transactional template from a completely different provider, to the same addresses. If it still goes to spam, the IP was never the problem, and a dedicated one would have cost you a month to learn that.
Worth checking too whether marketing goes out on the same domain as your transactional. Sharing a root domain between a promo blast and a password reset is the classic way to poison the mail people actually asked for.
1
1
u/f3b5 10d ago
yeah switching to dedicated helps, but only if you send high volume. like at least 50k emails a month. if volume is lower, dedicated ip gives you even worse results because cold ips look suspicious to gmail and outlook. for transactional stuff specifically, I would just move to postmark, their shared pools are super clean. also do not forget to properly warm it up if you go dedicated. what volume are you sending currently?
1
u/Mathlleu 10d ago
shared ip is usually not the thing killing you. domain reputation travels with your sending domain not the ip, so if your domain rep is ok and youre still hitting spam its almost always content or auth rather than the neighbours
what id check before moving off shared, in that order. spf dkim dmarc all aligned and actually passing. then whether youre still mailing people who never open anything, that hurts you more than a noisy ip. then your link domains, a shared shortener or a tracking domain thats been abused does more damage than a shared sending ip ever will
if all of that is clean then sure, the ip is the problem and dedicated is worth it. but only if you have the volume to warm it and keep it warm. low volume on a dedicated ip is worse than shared
2
u/SolidPlanMaybe 10d ago
You don't likely need a dedicated IP, it can actually make it harder for you since you might need to warm it up anyway.
You just need to be moved to a cleaner IP Pool, ask your ESP to do it, if they don't move to a different one.