Sender Reputation: What It Is and How to Protect It

Sender reputation is the collective trust score that mailbox providers assign to your sending domain and IP address. A strong reputation gets your messages into the inbox. A damaged one gets them filtered, deferred, or blocked before they arrive. Unlike a single authentication check, reputation accumulates over time based on complaint rates, bounce behavior, sending consistency, and recipient engagement. You cannot fix it overnight, but understanding what drives it gives you a clear path to building and protecting it.

Domain Reputation vs. IP Reputation: Two Different Signals

Every email you send carries two reputation signals: one tied to your sending IP address, one tied to your domain. They work differently, and mailbox providers weight them differently.

IP reputation is the trust score assigned to the specific IP address your emails originate from. It reflects that IP’s behavior across all senders who use it. If you send through a shared IP pool on a platform like SendGrid or Amazon SES, other senders on that pool affect your IP reputation too. Dedicated IPs isolate you from neighbors, but then the reputation is entirely your own to build.

Domain reputation is tied to the domain in your From: header and is portable. It follows you when you change email service providers or switch IP addresses. As Twilio’s deliverability team explains, domain reputation is what makes you “portable” across infrastructure changes. Gmail treats it with higher priority than IP reputation because domains are harder to discard than IP addresses, making them a more durable indicator of sender behavior.

Recovery timelines differ sharply. IP reputation can generally be rebuilt with two to four weeks of clean sending behavior. Domain reputation takes six to twelve weeks to recover from serious damage.

The practical implication: invest in keeping your domain clean. A fresh IP can be warmed up; a burned domain attached to your brand is much harder to rehabilitate.

What Mailbox Providers Actually Measure

Inbox providers do not publish their exact filtering formulas, but the inputs are well understood from published guidelines and observed behavior:

Complaint rate. This is the percentage of delivered messages that recipients mark as spam. Google’s email sender guidelines state: “Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher.” Crossing 0.30% makes you ineligible for Gmail’s mitigation support and triggers active message rejection, not just spam folder placement.

Unknown user rate (hard bounces). Sending to addresses that do not exist tells providers your list data is stale or was acquired carelessly. Bounce rates above 2% damage sender reputation; above 5% puts deliverability at serious risk.

Spam trap hits. Spam traps are addresses maintained by blocklist operators and ISPs to catch senders with poor list hygiene. Hitting them signals either bought lists, scraped data, or a list that has not been cleaned in years.

Authentication alignment. SPF, DKIM, and DMARC do not directly improve your reputation score, but failing them prevents you from building domain reputation at all. Google requires all bulk senders (5,000+ messages per day) to have SPF, DKIM, and DMARC configured. See our guide to email authentication for setup specifics.

Sending consistency. Sporadic volume spikes after long quiet periods look suspicious. Mailbox providers learn your normal sending pattern; large deviations from it trigger scrutiny.

Engagement. Opens, clicks, replies, and “not spam” markings are positive signals. Low engagement alongside high volume tells providers your recipients do not want the mail, even if they have not complained yet.

How to Monitor Your Sender Reputation

Two tools give you the most reliable visibility into your reputation health.

Google Postmaster Tools

Google Postmaster Tools shows your spam rate as reported by Gmail users, measured against mail delivered to inboxes. This is not the same as your overall complaint rate. The calculation excludes messages Gmail already filtered to spam automatically, which means a low spam rate in Postmaster Tools does not guarantee good deliverability. It means Gmail users who received your mail in their inbox chose not to mark it as spam.

Postmaster Tools v2 (rolled out fully in late 2025) focuses on the spam rate dashboard with threshold lines at 0.10% (recommended maximum) and 0.30% (policy violation). The older four-tier domain reputation dashboard (High/Medium/Low/Bad) was retired. The spam rate chart is now the primary signal.

For a full walkthrough of setup and interpretation, see our Google Postmaster Tools guide.

Validity Sender Score

Validity’s Sender Score assigns your sending IP a number from 0 to 100 based on a rolling 30-day average. The score is calculated from data contributed by more than 80 mailbox and security providers in the Validity Data Network, described by Validity as “the largest email data cooperative in the industry.” The inputs include complaint rates, unknown user rates, external blocklist appearances, and sending volume patterns.

A score of 85 means your IP outperforms 85% of all tracked IPs in Validity’s network. Scores above 80 indicate healthy sending behavior; below 70 suggests active deliverability risk.

One important limitation: Gmail, Microsoft, and Yahoo do not use Sender Score as a direct filtering input. They maintain their own internal reputation systems. Sender Score is best used as an independent diagnostic signal, not as a substitute for monitoring each provider’s own tools.

Other diagnostic tools worth running periodically: MXToolbox for blocklist checks, and Microsoft’s Smart Network Data Services (SNDS) for Outlook inbox visibility.

Building Reputation From Scratch: IP Warming

A new IP address has no reputation. Mailbox providers treat it with caution, and sending full volume immediately triggers filtering. The solution is IP warming: a gradual ramp-up of sending volume over two to six weeks, as Braze’s deliverability guide describes.

The core principle is straightforward. Start with a small daily volume to your most engaged subscribers, the people who reliably open and click. Their positive engagement signals to mailbox providers that this IP sends wanted mail. Increase volume steadily each day or week, monitoring bounce rates and complaint rates as you go. If either metric spikes, pause and clean before continuing.

Before sending a single message from a new IP, authentication must be complete. SPF, DKIM, and DMARC need to be configured and verified. Warming a domain with broken authentication is wasted effort.

For shared IP users on major ESPs: your IP reputation is partly managed by the platform, but domain reputation is always yours alone to maintain.

Protecting Reputation in Ongoing Sending

Warming gets you started. List hygiene and sending discipline keep you there.

Remove hard bounces immediately. A single hard bounce should trigger removal from your list. Continuing to send to addresses that reject your mail is a reputation tax you pay on every send. See our soft bounce vs. hard bounce explainer for how each type should be handled.

Suppress unengaged subscribers. Recipients who have not opened or clicked in 90 to 180 days are a liability. They lower your engagement signal and increase the chance of a spam complaint. Either run a re-engagement campaign with explicit opt-in confirmation, or suppress them. A smaller, engaged list outperforms a large, disengaged one on every deliverability metric that matters.

Honor unsubscribes within two days. Gmail’s bulk sender requirements explicitly require this. Continuing to send after an unsubscribe request is a direct path to complaints.

Use consistent sending domains and volumes. Changing your From: domain frequently resets your domain reputation. Sudden volume spikes from a domain with light sending history look like list bombing or account compromise.

Authenticate everything. If you send from subdomains (e.g., mail.yourapp.com for transactional, news.yourapp.com for marketing), each subdomain needs its own DKIM signing key and must be covered by your DMARC policy. See how to set up DMARC for the technical details.

Repairing a Damaged Reputation

If your spam rate has crossed 0.30%, Gmail is already rejecting or deferring your mail. Recovery requires stopping the bleeding before increasing volume.

First, identify the source of complaints. Check Postmaster Tools to see whether the spike is concentrated in a specific campaign, sending domain, or time window. Segment your list to isolate the problem cohort rather than pausing all sends.

Second, remove the damage sources. Hard-bounce addresses, people who never opted in, and anyone who has complained should be suppressed immediately. If you are using a third-party list or data enrichment service, stop sending to those contacts.

Third, resume sending at reduced volume, starting with your most engaged subscribers only. The goal is to rebuild positive engagement signals faster than complaint signals accumulate. Treat this as a second warmup.

Fourth, fix the root cause. Complaint spikes usually trace back to one of three issues: irrelevant content sent to the wrong segment, a list that was never properly opt-in verified, or a reactivation campaign that sent to lapsed subscribers without re-permission. Our email deliverability best practices guide covers the segmentation and opt-in workflows that prevent recurrence.

Expect domain reputation recovery to take six to twelve weeks of consistent clean sending. There is no shortcut.

Frequently Asked Questions