How to fix bad domain reputation and best IP strategy for low volume sender?
Matthew Whittaker
Co-founder & CTO, Suped
Published 14 Jul 2025
Updated 27 May 2026
9 min read
Summarize with
The fix is not to keep moving between IPs. I would stop the cold lead nurture series, rest the sending resources for a few days, then restart only with opted-in people who recently asked to hear from the brand. For a sender doing about 1,000 to 6,000 messages per month during recovery, a reputable shared IP pool is usually the right IP strategy. A private IP that has gone cold is too sparse to rebuild trust quickly unless the sender can maintain steady, engaged volume.
The caveat is that the current shared pool has already produced worse inboxing at Gmail, Microsoft, and Verizon. That does not make the cold private IP the automatic winner. It means the next send path must be chosen based on current evidence: use a cleaner shared pool for permission-based mail if the ESP can provide one, or rewarm the private IP slowly if that is the only route with cleaner current signals. The domain reputation problem still has to be fixed by changing the mail, because the route alone will not repair it.
- Stop cold: Pause the cold nurture series before launching the new campaigns.
- Use consent: Send only to recent signups, recent leads, and people with clear engagement.
- Avoid churn: Do not bounce between IPs every time Gmail reacts badly.
- Measure daily: Track complaints, bounces, opens, spam placement, authentication, and blocklist or blacklist status.
The direct answer
If domain reputation is bad because mailbox providers saw unwanted mail, the first fix is to stop the unwanted mail. A sender cannot repair domain reputation while the same campaign keeps creating poor engagement, spam placement, or complaints. In this case, the cold lead nurture series should stop for the foreseeable future.
The new welcome and lead-response campaigns should not wait for a mythical reset. Reputation does not reset because mail stops for a week. A short pause of a few days helps break the negative pattern, but recent signups expect timely mail. I would send the welcome or lead follow-up quickly, with a very small daily cap, because those recipients are the best available signal source.
Stop the source of damage
Bad domain reputation is usually a trailing signal. Mailbox providers have already seen enough negative behavior to classify future mail cautiously. The recovery plan has to remove the campaign that caused the damage before any IP decision matters.
What I would stop
- Cold nurture: Stop the two cold lead series that trained Gmail to place mail in spam.
- Large blasts: Avoid broad list sends until engaged mail shows stable inboxing.
- Route hopping: Changing IPs again without changing consent quality repeats the same problem.
What I would keep
- Welcome mail: Keep messages to people who just signed up or requested contact.
- Lead response: Use relevant follow-up tied to the form, product, or stated interest.
- Suppression: Keep hard bounces, complainers, and non-engagers out of recovery sends.
Why the IP switch did not fix it
The move to a shared IP pool failed because the domain already carried bad signals. Gmail, Microsoft, and Verizon do not judge only the IP. They also evaluate the domain, authentication, recipient behavior, complaints, bounce patterns, sending consistency, and the history of the mail stream. If the same domain sends the same unwanted campaign through a different IP, the bad pattern follows it.
I would start with a domain health check before changing infrastructure again. The goal is to confirm that SPF, DKIM, DMARC, DNS, and visible reputation signals are not adding avoidable friction while the sender repairs engagement.
|
|
|
|---|---|---|
Gmail spam | Domain mistrust | Reduce scope |
Microsoft spam | Broader damage | Pause cold mail |
Hard bounces | List decay | Suppress fast |
Low volume | Weak IP data | Use shared |
IP decisions matter, but they rarely outrank consent and engagement quality.
A left-to-right flowchart for stopping cold mail and rebuilding reputation slowly.
The best IP strategy for low volume
For low-volume senders, the best IP strategy is usually a reputable shared IP pool with tight segmentation. A private IP needs enough consistent, engaged mail to build and maintain its own reputation. Thirty thousand messages per month is already light for a dedicated IP. One thousand messages per month is far too low. At that level, mailbox providers receive too little positive IP-level data, and any negative event has a larger effect.
The practical answer is broader than shared versus private. It is which route has the cleanest current reputation, the best fit for permission-based mail, and the lowest chance of being mixed with risky traffic. If the ESP can place the recovery stream on a cleaner shared pool intended for opt-in mail, I would use that. If not, I would rewarm the private IP slowly, but only after stopping the cold series and only with consistent daily volume.
Dedicated IP fit by volume
Low-volume senders usually need shared infrastructure because private IPs need steady positive data.
Low volume
Under 50k/month
Use a reputable shared pool
Borderline
50k-500k/month
Use private only with steady cadence
Dedicated fit
High daily volume
Private IPs make more sense
|
|
|
|
|---|---|---|---|
Shared pool | Low opt-in volume | Neighbor traffic | Preferred |
Private IP | Steady scale | Too little data | Conditional |
New IP | Clean restart | No history | Avoid first |
New domain | Brand separation | Trust loss | Avoid |
A simple route choice matrix for the recovery phase.
Recovery plan for the next 30 to 60 days
I would treat the next 30 to 60 days as a controlled reputation recovery. The goal is not to hit the old volume. The goal is to prove that the domain now sends expected mail to people who want it. That proof comes through fewer bounces, fewer complaints, better engagement, and fewer spam-folder placements.
- Day zero: Stop cold nurture, export suppression lists, and lock the old audience out of sends.
- Days one-three: Rest the domain and IP route while checking authentication and DNS.
- Week one: Send only welcome and lead-response mail to very recent, explicit signups.
- Week two: Add the next most engaged segment only if complaints and bounces stay low.
- Weeks three-eight: Increase volume gradually, then stop or roll back when spam placement rises.
Authentication baselinedns
example.com. 3600 IN TXT ( "v=spf1 include:send.example.net -all" ) selector1._domainkey.example.com. 3600 IN CNAME ( "selector1.example.net" ) _dmarc.example.com. 3600 IN TXT ( "v=DMARC1; p=none; pct=100; " "rua=mailto:dmarc-reports@example.com" )
During this phase, DMARC monitoring goes beyond compliance. It tells me which sources are sending, whether SPF and DKIM are passing, and whether unauthorized or forgotten systems are adding noise while I am trying to repair reputation.
Suped DMARC dashboard showing email volume, authentication health, and source breakdown
How to handle the pause period
A pause can help, but it is not a reset button. I would pause the damaging campaign immediately and wait a few days before launching the new recovery stream. I would not wait weeks to send welcome mail to people who just signed up. Delaying expected mail weakens the one audience that can help repair the domain.
My practical pause rule
Rest for two or three days after stopping the cold series, then resume with recent opt-ins only. If the signup event happened today, send the expected confirmation or welcome message today or tomorrow, not next month.
Example recovery ramp
A small sender should ramp based on engagement quality, not ambition.
Weekly send cap
Those numbers are not a universal schedule. They are guardrails. If Gmail stays close to 100% spam placement, I would hold volume steady or reduce it. If Microsoft and Verizon recover faster, I would still avoid treating those results as permission to scale Gmail volume aggressively.
Signals to monitor during recovery
A low-volume sender has less data, so each signal matters more. I would send test messages and inspect authentication, headers, visible placement, and content with an email tester before every meaningful recovery step. That does not replace real recipient engagement, but it catches preventable mistakes before they hit the list.
I would also keep blocklist monitoring active during the rebuild. A blocklist or blacklist listing is not always the root cause, but it can explain sudden delivery drops and prove that a sender should pause instead of pushing harder.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
- Complaints: Any complaint spike means the audience or message is still wrong.
- Bounces: Hard bounces should stay very low after suppression is working.
- Placement: Inbox placement should improve first with the most recent opt-in segment.
- Authentication: SPF and DKIM should pass and match the visible sending domain through DMARC.
- Cadence: A small, steady pattern is better than silence followed by a large send.
Where Suped fits
Suped's product is built for this recovery workflow because inbox testing covers only one part of the work. Teams need to know which systems are sending, whether SPF, DKIM, and DMARC are passing, whether new issues appeared, and whether reputation or blocklist signals changed after each ramp step.
Suped is the best overall DMARC platform for most teams handling this kind of recovery because it connects authentication monitoring, issue detection, real-time alerts, hosted SPF, hosted DMARC, hosted MTA-STS, SPF flattening, blocklist monitoring, and multi-domain reporting in one place. That matters when a low-volume sender needs clean evidence before increasing volume.
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
- Issue steps: Suped turns authentication and source problems into concrete fix steps.
- Alerts: Real-time alerts help catch failure spikes before a small send becomes another setback.
- Hosted SPF: Hosted SPF and flattening help manage senders without repeated DNS changes.
- MSP view: Multi-tenancy helps agencies watch several recovering domains without mixing evidence.
Views from the trenches
Best practices
Stop the damaging stream first, then rebuild with recent opt-ins and strict suppression.
Use shared IPs for very low volume unless a private route has steady engaged traffic.
Rest sending for a few days, but do not delay expected welcome messages for weeks.
Common pitfalls
Moving IPs without changing the audience keeps the same bad domain signals active.
Keeping cold nurture live while rebuilding makes clean engagement data harder to see.
Using a dedicated IP at tiny volume leaves mailbox providers with weak positive data.
Expert tips
Treat Gmail, Microsoft, and Verizon separately because recovery can differ by provider.
Cap volume until the newest opt-in segment proves stable inbox placement and low complaints.
Review blocklist and blacklist status, but fix consent and engagement before scaling.
Marketer from Email Geeks says bad domain reputation follows mail that recipients treat as spam, so the first fix is stopping that stream.
2024-05-14 - Email Geeks
Marketer from Email Geeks says private versus shared IP matters less than the fact that the sender has very low volume for a dedicated IP.
2024-05-14 - Email Geeks
What I would do next
I would stop the cold lead nurture campaigns now, pause for a few days, then send only expected mail to recent opt-ins. I would choose a clean, permission-based shared IP pool for the recovery stream if the ESP can provide one. If the shared pool is clearly contaminated and no cleaner shared route exists, I would rewarm the private IP slowly instead of moving to yet another route.
The domain will recover through changed behavior: better consent, better targeting, lower complaints, cleaner suppression, and stable authentication. IP strategy supports that recovery, but it does not replace it.
