Skip to main content
LearnGuides

Google Postmaster Bad Reputation Fix Guide (2026)

Saksham Jain
By Saksham JainPublished on: Apr 11, 2026 · 11 min read · Last reviewed: Apr 2026
InboxKit InfraGuard reputation monitoring dashboard
InfraGuard checks domain reputation every 6 hours and alerts before Postmaster Tools shows Bad, catching the drop while you can still act.

TL;DR

Postmaster Tools shows Bad or Low reputation when Gmail's internal classifier has flagged your domain. Fixing it takes a specific pause-diagnose-rebuild protocol, not just waiting it out.

What "Bad Reputation" Actually Means in Postmaster Tools

Google Postmaster Tools reports domain reputation on a four-level scale: Bad, Low, Medium, High. This rating is Gmail's own internal classification of your sender and it directly drives filter decisions. A Bad rating routes most of your mail to spam within 24-48 hours of the rating dropping.

The four levels translate roughly to:

LevelInbox Placement (rough)Gmail's Opinion
High85-95%This sender is trusted; route to Primary.
Medium65-80%Neutral; mix of signals, inbox is still default.
Low25-45%Enough negative signals to be skeptical; promotion/spam routing increases.
Bad5-20%Strong negative signals; default routing is spam.

Bad reputation is Gmail telling you explicitly that something in your sending pattern, volume, list quality, or authentication is broken. The rating is smoothed over ~7 days, so it lags actual behavior. By the time Postmaster shows Bad, the underlying issue has been active for at least a few days.

This guide walks through the exact pause-diagnose-rebuild protocol that reliably moves domains from Bad → Medium → High over 14-28 days. For the general overview of the Postmaster dashboards, see google-postmaster-tools-guide.

Step 1: Read All Five Dashboards, Not Just One

"Bad reputation" is not a single diagnostic. It is a symptom that shows up in one place but is caused by signals across five dashboards. Read all of them before deciding on a fix:

DashboardWhat to CheckHealthyProblem
Domain ReputationOverall scoreHigh / MediumLow / Bad
IP ReputationSending IP scoreHigh / MediumLow / Bad (usually only affects dedicated IPs)
Spam Rate% of recipients marking as spam< 0.10%> 0.30% (Google's official threshold for bulk senders)
Authenticated Traffic% of your mail passing SPF/DKIM/DMARC alignment100%< 99%
Delivery ErrorsRate and cause of rejectionsZero listed"Unauthenticated email" / "High unknown user rate" / "Spam detected"

The diagnostic pattern you're looking for: which combination of dashboards is unhealthy tells you the root cause.

PatternRoot Cause
Bad Domain Rep + > 0.30% Spam RateContent triggering spam complaints. Fix the email body, not the infrastructure.
Bad Domain Rep + < 99% Authenticated TrafficAuthentication misalignment (usually DMARC). Fix SPF/DKIM/DMARC alignment first.
Bad Domain Rep + Delivery Errors "High unknown user rate"Bounce surge, list quality issue. Clean the list.
Bad Domain Rep + clean elsewhereVolume ramp too aggressive. Throttle immediately.
Bad Domain Rep + Bad IP RepShared-IP contamination. Migrate to real Google Workspace accounts.

Do not skip this step. Fixing the wrong root cause (e.g., rewriting content when the actual issue is DMARC misalignment) wastes 1-2 weeks and Gmail's rating moves slowly.

Step 2: Map the Symptom to the Root Cause

Once you've identified which combination of dashboards is problematic, map it to the specific fix. This table is the single most useful reference in this guide. Screenshot it.

SymptomRoot CauseFixRecovery Time
Spam Rate > 0.30%, Domain Rep Low/BadRecipients clicking "Mark as spam"Rewrite template to cut promotional signals; kill tracking pixel; shorten body to <120 words; send to better-targeted lists2-3 weeks
Delivery Errors: "Unauthenticated email"DMARC alignment failingFix DKIM alignment on sequencer; add custom DKIM selector; verify with Show Original. See dmarc-failed-gmail-fix3-7 days after fix
Delivery Errors: "High unknown user rate"Bounce rate > 3% on sendsClean list with NeverBounce / ZeroBounce; remove all catch-all and role accounts; target bounce rate <2%1-2 weeks
Volume graph shows recent 5x spike + Bad reputationVolume ramp triggered bulk-sender filterDrop volume to 30% of pre-spike level; ramp at 20% per week2-4 weeks
Bad IP Rep on shared-IP providerNeighbor contaminationMigrate to real Google Workspace or Microsoft 365 accounts. Shared-IP rehab is rarely worth it.Immediate on migration + warmup
Low Domain Rep on a brand new domainInsufficient warmupPause cold sends; run isolated warmup for 14-21 days before resuming2-3 weeks
Delivery Errors: "Spam detected" with clean contentGmail ML classifier edge caseSwitch templates; change subject lines; vary sending pattern2-4 weeks, variable

If multiple rows apply, fix them in the table's order. Authentication first, list quality second, content third, volume fourth. Address them in the wrong order and recovery stalls because you're not addressing the strongest signal.

Step 3: The 7-14 Day Pause Protocol

Fixing the root cause alone is not enough. You have to stop sending long enough for Gmail's smoothing window to pick up the corrected behavior. Recovery follows a specific pattern:

  1. 1Day 0: Pause all cold campaigns on the affected domain. Keep warmup running. Fix the identified root cause.
  2. 2Day 1-3: Monitor Postmaster Tools daily. Ratings usually don't move yet because the rolling window still includes the bad days. This is normal.
  3. 3Day 4-7: First signs of improvement if the root cause is fixed. Spam Rate should drop first (within 2-3 days), Domain Reputation starts moving 2-4 days after that.
  4. 4Day 7-10: If reputation is improving (Bad → Low, or Low → Medium), resume cold sending at 30% of pre-pause volume. If reputation is still Bad or dropping, the root cause is not fully fixed, so go back to Step 1.
  5. 5Day 10-14: Ramp to 60% of pre-pause volume if Postmaster Reputation continues climbing.
  6. 6Day 14-21: Back to 100% if Reputation is Medium or better.

Hard rules during the pause protocol:

  • Do not touch SPF/DKIM/DMARC during recovery unless that's the identified root cause. Authentication changes during recovery introduce variance and muddy the signal.
  • Do not run A/B tests during recovery. Keep template, volume, and sending time constant so you can see what's causing the movement.
  • Do not add new mailboxes to the domain during recovery. New mailboxes introduce new warmup load that Gmail has to evaluate.
  • Do keep warmup running. Warmup is the positive-signal generator during recovery. Pausing warmup removes the counter-signal and slows recovery.

Step 4: Rebuild with Isolated Warmup

Warmup is what generates the positive engagement signals Gmail uses to upgrade reputation. But not all warmup is equal:

Pooled warmup (shared across customers): Mailreef, Warmforge, most standalone warmup tools use a pool where your mailbox exchanges mail with every other customer's mailbox. During a reputation recovery, this is risky because if one customer in the pool has Bad reputation, your sends to them get marked as spam, which compounds your problem.

Isolated warmup: each customer's warmup pool is segregated, so your mailbox only exchanges mail with trusted, known-good seed accounts. During recovery, isolated warmup reliably generates positive engagement without cross-customer contamination.

Warmup cadence for reputation recovery:

DayWarmup VolumeCold VolumeTarget Signal
0-720-30/day0Positive engagement only: opens, replies, "Not Spam" moves
7-1425-35/day5-10/day (clean, high-intent)Maintain warmup while small cold volume tests the new baseline
14-2125-35/day10-20/dayRamp cold if Postmaster Reputation climbs
21-2820-25/day20-30/dayReturn to steady state

InboxKit isolated warmup runs at $3/mailbox/mo, specifically engineered for reputation recovery scenarios. Deeper warmup reference in domain-warmup-best-practices.

Step 5: Monitor Recovery Metrics

During the recovery window, three Postmaster metrics matter more than the headline Domain Reputation number because they move faster and predict where Reputation will go next:

MetricLeading / LaggingWhat Healthy Looks Like During Recovery
Spam RateLeadingDrops within 2-3 days of the root cause fix. Target < 0.15% during recovery, < 0.10% steady state.
Authenticated Traffic %LeadingShould be at 100% by day 1. If not, authentication is still broken.
Delivery ErrorsLeadingErrors stop within 1-2 days of the root cause fix. Persistent errors mean the root cause is wrong.
IP ReputationLaggingOnly relevant on dedicated IPs. Slowest to move.
Domain ReputationLagging5-10 days behind the other metrics. Don't use as primary signal during active recovery.

The pattern that means "recovery is working":

  1. 1Spam Rate drops first (days 2-4).
  2. 2Delivery Errors clear (days 2-5).
  3. 3Domain Reputation begins climbing (days 5-10).
  4. 4Reply rate on live sends recovers (days 7-14).
  5. 5Bounce rate normalizes (days 7-14).

The pattern that means "recovery is failing":

  1. 1Spam Rate stays above 0.20% despite content changes.
  2. 2Authenticated Traffic stays below 99%.
  3. 3Domain Reputation stays at Bad or Low after 14 days.

If you see the failing pattern at day 14, the root cause is either misdiagnosed or the domain is structurally damaged. Move to the retire-vs-rehab decision below.

When to Retire vs Rehab

Not every damaged domain is worth saving. Use this decision framework:

ScenarioDecisionRationale
First time Bad rating, clear root causeRehabOne-time incident, fixable in 2-4 weeks
Second Bad rating within 90 days on same domainRetirePattern indicates structural list/content/process issue
Bad rating + Spamhaus DBL hitRetireCombined signal means the domain is flagged by multiple systems; rehab cost is very high
Bad rating on a burner/secondary domainRetireSecondaries are meant to be replaced; replacement is faster than rehab
Bad rating on main brand domainRehab, aggressivelyStrategic value justifies the 4-6 week effort
Bad rating + domain age < 60 daysRetireYoung domains have no reputation reserve; fresh domain + warmup is faster
Bad rating + Authentication misalignedRehabFixable with DNS changes; reputation recovers once authentication passes

The economics: a burner cold email domain costs $10-15 + ~$3/mailbox/mo warmup. Full rehab of a Bad-rated domain takes 21-28 days of reduced sending. Fresh domain + 14-day warmup is typically 2-3x faster than rehab for most cold email setups. This is why professional cold emailers operate with rotating burner domains, and when one gets damaged, they retire it and spin up a replacement without disrupting campaigns. Architecture in how-many-domains-cold-email.

Prevention with Continuous Monitoring

Postmaster Tools has a 5-10 day lag because the ratings are smoothed. That means by the time you see Bad, the damaging behavior has been happening for 5-10 days already. Prevention beats rehab every time.

The three layers of continuous monitoring that prevent Bad reputation:

LayerWhat It CatchesLead Time Advantage
Bounce rate watchdogList quality issues before they trigger bulk rejections3-5 days before Postmaster reacts
SMTP error pattern watcherThrottling and soft bounces spiking above 3%2-3 days before reputation drops
Blacklist sweeper every 6hDomain appearing on Spamhaus DBL or similar24-48 hours before Gmail picks it up

InboxKit InfraGuard implements all three and auto-pauses sending on a mailbox or domain when any alert fires. The 6-hour check interval means you typically get 24-72 hours of lead time before Postmaster Tools would have shown a problem, enough time to fix the root cause without the reputation drop.

InfraGuard is free for the first month on all plans and then billed per-domain. The Agency plan at $99/mo for 30 slots is a common sweet spot for teams running ~20 cold email domains.

Beyond InfraGuard, two habits prevent Bad reputation entirely:

  1. 1Verify every list before sending. 10-minute manual check with NeverBounce or similar prevents the bounce-surge failure mode.
  2. 2Keep per-mailbox daily volume under 40/day. The single biggest predictor of a ramp-induced reputation drop is per-mailbox volume above 40/day.

For the full monitoring stack reference, see email-deliverability-monitoring-setup.

Frequently Asked Questions

5-10 days. The ratings are smoothed over a rolling window, so both the initial drop and the recovery are delayed. This is why leading indicators (Spam Rate, Delivery Errors) matter more during active recovery than the headline Reputation number.

Rarely. Bad means Gmail's classifier has already decided your pattern is abusive. Continuing to send the same pattern just confirms the classifier's decision. A 7-14 day pause while you fix the root cause is almost always faster than trying to push through.

No. Postmaster Tools is Google-only. For Microsoft 365, use SNDS (Smart Network Data Services). For Yahoo, there is no public postmaster dashboard, so you rely on DMARC aggregate reports and bounce patterns.

Usually list quality decay or gradual content fatigue. Recipients who once engaged stop replying; bounce rate on old addresses increases; the same template starts getting marked as spam more often. Reputation is a moving target. You have to rotate content and clean lists continuously to hold a High rating.

No. Blacklist is a public DNSBL like Spamhaus. Postmaster reputation is Gmail's private internal score. The two are correlated (blacklist hits often cause Postmaster drops) but they're separate systems with separate fixes. For blacklist diagnosis see [domain-blacklisted-diagnosis-guide](/learn/domain-blacklisted-diagnosis-guide).

Ready to set up your infrastructure?

Plans from $39/mo with 10 mailboxes included. Automated DNS, warmup, and InfraGuard monitoring included.