Domain reputation explained: how mailbox providers score senders

Most people treat domain reputation as a state they check, like a credit score they look up once a quarter. It’s better understood as a ledger. Every message you send adds a small entry, positive or negative, depending on how the recipient responds. The balance moves slowly when the entries are normal, and it can fall fast when a single segment starts generating complaints. By the time the balance is visible in a dashboard, the entries that caused it are days or weeks old.

That framing explains most of the reputation problems we see. Teams run a campaign, see nothing wrong, and then find their placement has slipped a week later. Nothing changed in the last send. The bad entries were written the week before, and the balance has only now crossed a threshold. This guide explains what providers actually score, which signals move the score, how to read the dashboards that expose it, and how to recover when the balance has gone negative.

What domain reputation measures

A mailbox provider doesn’t score one thing. It looks at three identities, and each one carries its own reputation.

The domain is the one you control most directly, and it’s the one that matters most when you send through a mailbox provider such as Google Workspace or Microsoft 365. In that setup your sending IPs belong to the provider and are shared with millions of other senders. Your individual IP reputation is largely outside your hands. The domain, by contrast, is yours, and providers increasingly judge a sender by its domain identity. That’s why the domain is the unit we focus on in this article.

The DKIM signing domain matters because it’s the identity that proves the message is authentic. If your From address is on one domain and your DKIM signature is on another, providers see an identity mismatch, and the reputation of the signing domain may count for more or less than the From domain depending on the provider. Keep them aligned, which is one of the basic checks in SPF, DKIM and DMARC explained.

The signals that move the ledger

Positive entries come from recipients who behave like people who want the mail. They reply, they move the message from spam to the inbox, they mark it as important, and they open it when they have a reason to. A steady volume with low bounces and few complaints also adds up slowly. Providers treat consistency as evidence that the sender is running a deliberate operation rather than a burst.

Negative entries come from recipients who push back. Spam complaints are the most direct negative signal, because they’re a recipient’s explicit statement that the mail is unwanted. Hard bounces are a negative signal of a different kind. They show that the list wasn’t checked, and they can indicate that the sender is hitting addresses that were never real. Spam trap hits are the most damaging of all, because they say the list was assembled or maintained carelessly. Blocklist listings are less a signal than a verdict, applied by third parties who have already decided the sender is a problem.

Volume changes are a signal too, and an easily overlooked one. A domain that goes from twenty messages a day to two hundred overnight looks like a campaign being switched on, and filters treat that pattern with suspicion regardless of the content. The ramp logic from our warmup guide applies to established domains as well as new ones, because the signal is the change, not the age.

Content matters less to reputation than most people assume, but it isn’t irrelevant. Filters evaluate links, formatting and repeated text, and a message full of trackers from a poorly regarded domain will lose points even when the sender is clean. Treat content as a multiplier on reputation rather than the source of it.

Reading Google Postmaster Tools

Google Postmaster Tools is the most useful free instrument for seeing how Gmail rates a domain. You verify the domain in the tool, and it then reports several views of your mail to Gmail. The most important is domain reputation, which is shown as one of four levels: High, Medium, Low or Bad. The tool also reports spam rate, authentication pass rates for SPF, DKIM and DMARC, and delivery errors.

Two things about the tool are easy to misread. The first is that data only appears once a domain sends enough mail to Gmail to form a meaningful sample. A new domain or a low-volume sender will show no data, and that absence is not a problem. It means you don’t yet have enough volume to be measured. The second is that the levels are coarse. A move from High to Medium is significant, and it usually means a specific segment has started to generate complaints or bounces. A move from Medium to Low is a serious warning, and a move to Bad means placement is already suffering.

Read the spam rate graph alongside the reputation level. A spike in spam rate on a particular day is the clue that points to a cause. Match the date against your sends: a new list source, a new template, or a change in sending volume is usually the explanation. The tool tells you the balance, and your send log tells you which entries caused it.

Blocklists and Microsoft’s view

Outside the mailbox providers, blocklists are the other major input. Spamhaus maintains the Domain Block List, which lists domains, and the Zen list, which covers IP addresses. Other operators publish lists that filters consult. A listing can reduce placement across providers at once, so it’s worth checking the major lists every week, not only when something goes wrong.

Microsoft offers its own view of IP reputation through Smart Network Data Services, which shows how Outlook.com rates the IP addresses sending to it. It’s useful when you send from infrastructure that Microsoft sees directly. For a team that sends through Microsoft 365 mailboxes, the relevant reputation is the provider’s shared IP pool and the domain identity you’ve built on top of it.

The practical point is that a blocklist listing on a shared IP affects everyone on that IP, including senders you have no relationship with. If you’re choosing dedicated infrastructure for cold outreach, check the IP’s history before you commit, because an address with a previous owner’s problems is your problem now.

How the score decays and recovers

Reputation accrues slowly and falls quickly. A domain that has spent months sending clean mail can lose several levels in about a week if a bad segment goes out at volume. Recovery, by contrast, takes weeks. The score is an average over recent activity, and it can’t improve until enough good entries have replaced the bad ones.

The usual recovery plan has four steps. First, stop sending to the segment that caused the damage, and do it immediately rather than at the end of the campaign. Second, cut volume on the domain to a fraction of its normal level, enough to keep the sender active but not enough to add new complaints. Third, remove every address that complained, bounced, or was flagged, and suppress them everywhere the list is used. Fourth, keep replies flowing from engaged recipients while the score recovers, because positive entries are what lift the balance back.

Expect weeks, not days. Teams often try to speed recovery by switching domains, which is a mistake. A new domain starts with no history, and the cold-start penalty can be worse than the damage you were trying to escape. Repair the domain you have unless its history is genuinely beyond saving, in which case retiring it cleanly is better than rotating.

A worked diagnosis

Here is a scenario we see often enough to be worth walking through. A team sends a campaign from a domain that has been at a Medium reputation for months. On day three of a new list source, they send to a few thousand addresses bought from a provider that promised “fresh” contacts. Within a week, Postmaster shows reputation falling to Low, and the spam rate on the chart spikes on the days the new list went out.

The first check is the segment. The team filters complaints by list source and finds that nearly all of them come from the purchased rows. The second check is bounces, which show a hard bounce rate above 4 percent concentrated in the same rows, which suggests the list was never verified. The third check is the send log, which shows volume jumped from a steady level to nearly triple in two days, on top of the new list. Three signals, one cause.

The fix follows the recovery plan. The purchased rows are suppressed and removed from every sequence. Volume on the domain drops by most of its level for three weeks. The team keeps replies flowing to its engaged contacts, and it adds a verification step and a sunset rule to the list process. After about a month, the reputation returns to Medium. The lesson is not that purchased lists are always bad. It’s that a list you haven’t verified, sent at a volume you haven’t ramped, is a list that can move the balance faster than you can see it.

The monitoring routine

A small set of checks, run on a fixed schedule, catches most reputation problems before they become expensive. The table below sets out the metrics we track and the points at which we act on them.

The thresholds are practical guides, not guarantees. Google’s own guidance on complaints sets the 0.1 percent target and warns against reaching 0.3 percent, and the bounce threshold is a common planning figure rather than a published standard. Use the numbers as the points where you stop, look, and find the cause, rather than as a score you can hit and forget.

Wrap-up

Domain reputation is a balance built from many small entries and reduced by a few large ones. Providers score the identity you control most directly, which for cold outreach is the sending domain. You move that balance with real engagement, clean lists, steady volume and consistent authentication, and you lose it with complaints, bounces, trap hits and sudden spikes. The only free window into how Gmail sees you is Postmaster Tools, and the only practical response to a falling balance is to cut the cause and wait.

If you’d rather not run this monitoring by hand, OutboundLeadPro handles the basics that keep the balance healthy, including a free Smart check on every email and DNS auto-fix for SPF, DKIM and DMARC. You can see how those fit into the workflow on the features page. For the sending side of the same question, our guide to secondary domains explains how to keep a reputation problem on one domain from spreading to the rest of the business.

Keep reading

Playbook

Cold Email A/B Testing: Why Most Tests Prove Nothing

Cold email A/B testing is often too small to mean anything. Here is the sample-size math at real reply rates, and how to read the results.

Daniel Khoury September 19, 20263 min read

Playbook

How to avoid spam folder placement: 12 causes and fixes

Want to avoid spam folder placement? These 12 causes, from authentication to list quality to complaints, each come with a concrete fix you can check.

Daniel Khoury September 24, 20263 min read

Playbook

How to build a lead list that stays clean after the first send

Build a lead list around a real ICP, with stage gates that reject bad rows before they cause bounces and complaints. Includes a worked example.

Daniel Khoury October 7, 20263 min read

Explainer

SPF, DKIM and DMARC explained for cold email

The three email authentication records decide whether you reach the inbox — and most cold outreach fails because one is missing or wrong. Here's each one in plain English.

The OutboundLeadPro Team October 11, 20262 min read