Sender reputation is the trust score mailbox providers keep for the domains and IP addresses that send you mail. It’s built from your history: how often recipients report your messages as spam, how many of your messages bounce, whether you hit spam traps, and whether your mail is properly authenticated. A good reputation gets you into the inbox; a bad one gets you filtered to spam, throttled, or rejected outright.

Providers don’t publish a formula, but their sender guidelines tell you clearly what they reward and punish. This guide covers what goes into sender reputation, how to check it, and the habits that keep it healthy.

What is sender reputation, exactly?

Every major mailbox provider (Gmail, Yahoo, Microsoft, Apple, and corporate filters) keeps its own internal view of each sender. There’s no single universal score. What you have is many private reputations, one per provider, attached to a few identifiers:

Your sending domain. Mostly the domain in your DKIM signature and visible From: address, plus subdomains you send from.
Your sending IP address. The server that connects to the recipient’s mail server.
Other domains in your mail. Link and tracking domains, image hosts, and the Return-Path domain can all carry reputation.

The M3AAWG Sender Best Common Practices (version 4.0, updated August 2026) notes that any domain appearing in a message or the SMTP transaction, including the Return-Path, From:, DKIM signature, HELO name, reverse DNS name, Reply-To, and links, may be used to judge reputation. That’s why consistent domains across those fields matter.

For a closer look at how the two main identifiers differ, see domain reputation vs IP reputation.

The signals that build or damage sender reputation

Spam complaints

When a recipient clicks “Report spam,” that’s the clearest negative signal you can get. Google tells senders to keep the user-reported spam rate below 0.1% and never reach 0.3% or higher, per its sender guidelines FAQ. Yahoo’s sender requirements use 0.3% as the ceiling. Those numbers are small: at 0.3%, three complaints per thousand delivered messages is already too many.

Details on calculating and lowering it are in our spam complaint rate guide.

Bounces

Lots of hard bounces suggest you’re mailing an old, bought, or badly collected list. The M3AAWG BCP says the volume of permanent failures is one of the indicators receivers use to build a reputation about a sender, and that large volumes of hard bounces are often a sign of a poorly managed registration process or an old list.

Sending platforms enforce their own limits because their shared IPs depend on it. Amazon SES recommends a bounce rate below 2%, places accounts under review at 5%, and may pause sending at 10%.

Spam traps

Spam traps are addresses that never signed up for anything, or abandoned addresses repurposed to catch senders who don’t clean their lists. Hitting them tells providers and blocklist operators that your list collection or hygiene is poor. AWS notes that even a small number of spam trap hits can have a very negative effect on reputation. See spam traps: types and how to avoid them and our post on the two kinds of spam traps.

Authentication results

Mail that fails SPF, DKIM, or DMARC is easier to spoof, so providers trust it less. Authentication also lets providers attach reputation to your domain rather than only to an IP you might share with others. Since February 1, 2024, Google and Yahoo require authentication from everyone who sends to their users, with stricter rules for bulk senders.

Engagement

Opens, replies, moving mail out of spam, adding you to contacts, and deleting without reading all feed into filtering. Providers don’t publish how much each counts. The practical rule: mail people want builds reputation, mail people ignore slowly erodes it.

Volume patterns

A sudden spike from a sender with no history looks like a compromised account or a spammer. Google’s sender guidelines ask senders to increase volume slowly, send at a consistent rate instead of in bursts, and cut back when bounces or deferrals rise.

Blocklist listings

Public blocklists such as Spamhaus are used by many receiving servers. A listing can cause outright rejections at those servers even if Gmail still accepts your mail.

How to check your sender reputation

No tool shows you the internal score, but several give you useful proxies.

Source	What it shows	Who it helps
Google Postmaster Tools	Spam rate, authentication, compliance status for Gmail	Anyone sending meaningful volume to Gmail
Microsoft SNDS	Data on IPs you control sending to Outlook.com	Senders with their own IPs
Yahoo Complaint Feedback Loop	Individual complaint reports for DKIM-signed mail	Any sender who signs with DKIM
Blocklist lookups (e.g., Spamhaus)	Whether your IP or domain is listed	Everyone
Your own logs	Bounces, deferrals, and SMTP error text per provider	Everyone

A few notes on these:

Google Postmaster Tools reports the spam rate for DKIM-authenticated mail to Gmail. Its compliance status dashboard shows whether you meet Gmail’s sender requirements, per the Postmaster Tools help page. Google has also changed how it presents reputation in the newer version of the tool; our post on Postmaster Tools v2 and the retired reputation scores covers what that means for monitoring.
Microsoft’s Outlook.com postmaster policies list SNDS and the Junk Email Reporting Program (JMRP) as its free reputation tools.
Your bounce logs are the most underused source. A sudden cluster of 421 4.7.0 deferrals or 550 5.7.1 policy rejections from one provider tells you that provider has lowered its view of you, often before anything else shows it.

How to protect your sender reputation

Collect addresses the right way

Reputation problems usually start at signup. The M3AAWG BCP calls confirmed opt-in the best level of permission. At minimum:

Never buy, rent, or scrape lists.
Use a confirmation email for new signups where you can.
Say clearly what you’ll send and how often.
Don’t pre-check consent boxes.

Verify addresses before they reach your list

Catching bad addresses at the form and before imports keeps bounces down. Our free email verifier checks syntax, domain and MX records, disposable domains, role-based addresses like sales@, free-provider detection, and common domain typos. It doesn’t open an SMTP connection to the mailbox, so it can’t prove an inbox exists, but it removes a lot of the obvious junk. Running the same checks on signup forms stops bad addresses before they’re ever stored.

Suppress bounces and complaints immediately

Remove hard bounces on the first occurrence.
For repeated soft bounces, M3AAWG suggests removing an address if it bounces consecutively at least two times over two weeks or more.
Remove anyone who complains, right away. The Amazon SES FAQ says not to even send a message acknowledging the removal.

Stop mailing people who don’t engage

Long-inactive subscribers don’t just drag down engagement; old addresses can turn into spam traps. Run a re-engagement campaign, then remove people who don’t respond.

Make unsubscribing easy

Bulk senders to Gmail and Yahoo must support one-click unsubscribe and show a visible unsubscribe link. Google says to honor unsubscribe requests within 48 hours; Yahoo says within 2 days. An unsubscribe that works is one less spam report.

Separate your mail streams

Send marketing from one subdomain (e.g., news.example.com) and transactional mail from another (e.g., mail.example.com). If a promotion goes badly, your password resets keep arriving. Our post on why you shouldn’t send from your root domain covers the setup.

Keep volume steady

Avoid big swings. If you normally send 20,000 messages a week, don’t suddenly send 200,000 to a list you haven’t mailed in a year. New domains and IPs need a deliberate, gradual ramp.

How to recover a damaged sender reputation

If your reputation has already taken a hit, follow this order:

Stop the bleeding. Pause campaigns to cold or old segments. Keep sending only to your most engaged recipients and to essential transactional mail.
Find the cause. Look at complaint data, bounce logs, and any blocklist listings. Was it a new list import? A new signup source? A content change?
Fix the cause. Remove the bad segment, fix the form, or fix the broken authentication record.
Clean the list. Remove hard bounces, complainers, and long-term inactives. Verify any imported data.
Rebuild slowly. Increase volume gradually, starting with engaged recipients, watching deferrals and complaint rates as you go.

Recovery takes consistent good behavior over time. Gmail, for example, restores mitigation eligibility only after a sender’s spam rate has stayed below 0.3% for seven consecutive days.

FAQ

Can I check my sender reputation score?

Not directly. Mailbox providers keep their scores private. You can monitor proxies: Google Postmaster Tools for spam rate and compliance, Microsoft SNDS for IP data, feedback loops for complaints, blocklist lookups, and your own bounce and deferral logs.

Does sender reputation follow me if I switch email providers?

Domain reputation does, because it’s tied to the domain you authenticate with DKIM and use in your From: address. IP reputation doesn’t if you move to new IPs, but new IPs have no history and need warming. Switching providers doesn’t fix a list or permission problem.

How long does it take to build a good sender reputation?

It takes weeks of consistent, low-complaint sending. AWS says warming a new dedicated IP takes around two weeks at some providers and up to six weeks at others, and M3AAWG suggests planning for about six weeks for a new domain. Reputation keeps building after that as long as your sending stays clean.

Can a single bad campaign ruin my sender reputation?

It can hurt it badly, especially if it goes to an old or purchased list and triggers complaints, bounces, and spam trap hits all at once. Most providers react to trends, so one bad send followed by clean behavior usually recovers. Repeated bad sends are what lead to lasting filtering and blocklisting.

Sender Reputation: What It Is and How to Protect It