What is sender reputation? How inbox providers judge your email

Every time you hit send, the receiving mail server asks a quiet question before it does anything else: do I trust this sender? The answer is your sender reputation, and it decides whether your message lands in the inbox, gets filed as spam or never arrives at all.

Think of it as a credit score for email, with one important difference. There is no single bureau. Gmail, Outlook, Yahoo and every corporate filter keep their own private score for you, updated continuously from what they see. You never get to read the number directly, but the inputs are well known and almost all of them are within your control.

This guide explains how reputation works, which signals matter most, how to check where you stand and what to do if things have gone wrong.

What sender reputation actually measures

Sender reputation is a running judgment of how trustworthy your mail is, based on three kinds of evidence:

• Identity. Can the receiver prove the message really came from you? That is the job of SPF, DKIM and DMARC.
• History. How has mail from this domain and IP behaved in the past? Consistent volume, few bounces and few complaints build credit.
• Recipient reaction. Do people open, reply, move you out of spam and add you to contacts, or do they delete unread and click “Report spam”?

Receivers combine these into a score for each sending identity they track. The most important identities are your sending domain (the domain in your From address and your DKIM signature) and the IP addresses your mail leaves from. Some filters also track the domains in your links and the reputation of your ESP as a whole.

The key idea: reputation is behavioral. A legitimate business with sloppy list practices will end up with a worse reputation than a small sender who mails only people who asked for it.

How reputation turns into inbox placement

When your message arrives, the receiving server makes a routing decision in milliseconds. It runs roughly like this:

1. Connection. The server looks at your sending IP. If the IP is on a blocklist or has a poor score, the connection may be refused or throttled right away, often with a temporary code such as 421.
2. Authentication. SPF, DKIM and DMARC are evaluated. Failing mail from a domain with a strict DMARC policy can be rejected outright.
3. Reputation lookup. The domain and IP scores are pulled up and weighed together.
4. Content and engagement. Filters scan the message itself and check how this recipient has treated your past mail.
5. Placement. Inbox, promotions tab, spam folder or rejection.

Reputation is the thread tying all of these together. A strong one earns the benefit of the doubt when content is borderline. A weak one can send even an expected password reset to spam.

How the major mailbox providers score you

Each large provider runs its own system and exposes part of it through a free dashboard. The formulas are private, but the priorities are clear enough to act on.

Gmail

Google tracks both domain and IP reputation and shows them in Google Postmaster Tools. Gmail relies heavily on user behavior: complaints, “not spam” clicks, deletes without reading and replies. Since the February 2024 bulk sender rules, anyone sending more than about 5,000 messages a day to Gmail users must have SPF, DKIM and DMARC in place, use aligned authentication, offer one-click unsubscribe and keep the spam complaint rate below 0.3%, with 0.1% as the healthy target.

Microsoft (Outlook, Hotmail, Live)

Microsoft still gives IP reputation a lot of weight and exposes it through Smart Network Data Services (SNDS) and the Junk Mail Reporting Program. It is quick to throttle unfamiliar IPs and rewards steady, predictable sending. Since May 2025, Outlook consumer domains expect high-volume senders to meet the same SPF, DKIM and DMARC baseline that Google and Yahoo require, and non-compliant mail can be rejected with a 550 5.7.515 error.

Yahoo and AOL

Yahoo pushed DKIM and DMARC early and applies the same 2024 bulk sender rules as Gmail. It looks closely at complaint rates, bounce rates and consistency, and runs a Complaint Feedback Loop that tells you which recipients reported your mail so you can suppress them.

The signals that move your reputation

A handful of measurable signals drive most of the score. They are listed here roughly in order of how quickly they can hurt you.

Complaints

A complaint rate of 0.3% means three people out of every thousand reported you. That sounds tiny, and it is exactly why it is so easy to exceed. One campaign to an old segment can push you over. Make unsubscribing easier than complaining: a visible link and the List-Unsubscribe header with one-click support.

Bounces

Hard bounces such as 5.1.1 user unknown tell providers you are mailing addresses that do not exist. Remove them after the first hard bounce. Our bounce rate guide covers the difference between hard and soft bounces in depth.

Engagement

Engagement is the slow, positive force. People who open, click and reply keep your score healthy. The flip side is that mailing large numbers of people who ignore you drags the average down, even if none of them complain.

IP reputation vs domain reputation

You have at least two reputations to look after, and they behave differently.

For most senders, the domain is the asset to protect. On a shared IP pool you do not control your neighbors, but your ESP does, which is why the platform you choose matters. A dedicated IP gives you full control and full responsibility, and it usually only makes sense once you send steady, high volume. Our shared vs dedicated IP decision guide walks through the trade-offs.

How reputation works for different kinds of senders

The rules are the same for everyone, but where the risk sits depends on what you send.

Brand-new senders

A new domain or IP has no history, which is not the same as a good history. Providers treat unknown senders cautiously, so the first few weeks decide a lot. Start small, send to people who expect your mail and let positive engagement accumulate before you scale. Registering a domain and blasting 100,000 messages on day one is the classic spammer pattern, and filters are built to catch it.

Transactional senders

Receipts, password resets and shipping notices are wanted mail, so they usually earn strong engagement. The risk is sharing a domain or IP with marketing mail. If a promotional campaign triggers complaints, your order confirmations suffer too. Many teams send transactional mail from a separate subdomain or IP pool for exactly this reason; the transactional vs marketing deliverability guide explains how to split them.

Marketing and newsletter senders

This is where most reputation damage happens, because volume is high and engagement varies. The biggest risks are mailing inactive segments, importing old lists and sending more often than subscribers expect. A clear sunset policy and consistent cadence do most of the protective work.

B2B senders

Business recipients often sit behind corporate filters such as Microsoft 365, Proofpoint or Mimecast, which lean on IP reputation and blocklists more than consumer inboxes do. Business lists also decay faster as people change jobs, so bounce rates creep up unless you verify regularly.

How to check your sender reputation

There is no official public score, so you triangulate from several sources.

Run a public reputation check

The Sender Reputation Checker grades your domain from A to F across authentication, blocklists and DNS and tells you what to fix. It is the fastest way to catch configuration problems.

Look at Google Postmaster Tools

Verify your domain with a DNS TXT record and you will see domain reputation (High, Medium, Low or Bad), IP reputation, spam rate, authentication pass rates and delivery errors for Gmail traffic.

Look at Microsoft SNDS

Register your sending IPs to see complaint rates, trap hits and a simple green, yellow or red status for Outlook traffic. If you are on a shared IP, your ESP holds this data instead.

Scan the blocklists

Run your domain and IPs through the Blacklist Checker. A listing on Spamhaus in particular can explain sudden rejections across many receivers. If you find one, the blacklist removal guide explains how to get off it.

Read your own bounce logs

Rejection messages are reputation feedback in plain text. Codes like 5.7.1 or 4.7.0 often include a reason, and a sudden rise in them is an early warning.

How to build and protect a strong reputation

Good reputation is earned by doing a few boring things consistently.

Authenticate everything

Publish SPF, sign with DKIM using a 2048-bit key, and publish a DMARC record. Start DMARC at p=none to collect reports, then move to quarantine or reject. Check each record with the SPF Checker, DKIM Checker and DMARC Checker. The email authentication guide covers setup step by step.

Mail only people who asked

Collect addresses through your own forms, ideally with confirmed (double) opt-in. Never buy, rent or scrape lists. Purchased lists are the most common source of spam traps and complaints.

Keep your list clean

Suppress hard bounces immediately. Stop mailing people who have not engaged in six to twelve months, or run a short re-engagement series first and then remove non-responders.

Make leaving easy

A one-click unsubscribe costs you a subscriber. A spam complaint costs you reputation with every future recipient at that provider. Offer the easy exit.

Send consistently and warm up changes

Keep a predictable cadence. When you add a new domain, a new IP or a big new segment, ramp volume over two to four weeks, starting with your most engaged recipients. The warmup guide has sample schedules.

Recovering from a damaged reputation

If placement drops suddenly, resist the urge to change everything at once. Work through it in order.

1. Diagnose. Compare the timing of the drop with recent changes: a new list import, a new template, a DNS edit, a volume spike or a new blocklisting. Postmaster Tools and your bounce logs usually point to the cause.
2. Fix the root cause. Clean the list, repair authentication or resolve the listing. Nothing else helps until this is done.
3. Shrink to your best recipients. Mail only people who opened or clicked in the last 30 to 90 days. Their positive signals rebuild trust fastest.
4. Rebuild slowly. Expand volume in steps, watching complaints and bounces at each stage before the next increase.

A small dip typically clears in one to two weeks. Serious damage can take four to eight weeks or longer.

Three myths worth dropping

“A clean IP guarantees good delivery.” It helps, but domain reputation follows you and behavior matters more than infrastructure.

“We are not spammers, so reputation is not our problem.” Legitimate senders with poor hygiene or broken authentication get filtered all the time. Filters judge behavior, not intent.

“Our open rates are fine, so our reputation is fine.” Apple Mail Privacy Protection and similar features inflate opens, and opens only come from mail that was delivered. A falling inbox rate can hide behind stable open numbers, which is why the provider dashboards and your deliverability habits matter more than one metric.