What Is Sender Reputation?

Sender reputation is the answer to a question email providers have to ask several billion times per day: should we trust this sender? The answer has economic consequences for both senders (whose mail reaches inboxes or does not) and recipients (whose inboxes do or do not fill with attempted abuse).

This post is the long answer to “what is sender reputation?”, how it is calculated, why it matters, and where it intersects with email paywalls.

The Working Definition

Sender reputation is the trustworthiness score that email providers assign to a sending domain or IP address. Higher reputation means the provider trusts the sender more and is more likely to deliver mail directly to the inbox. Lower reputation means the provider trusts the sender less and is more likely to route mail to spam, delay it, or reject it outright.

The score is dynamic. Reputation changes over time based on how the sender behaves, how recipients react to the sender’s mail, and how the technical infrastructure of the sender holds up. A reputation that is high today can degrade in days if recipients start marking the sender’s mail as spam.

Each major provider (Google’s Gmail, Microsoft’s Outlook and Office 365, Yahoo, Apple’s iCloud Mail) maintains its own reputation system. The scoring formulas are proprietary and not publicly documented. The categories of signal that go into the scores are widely known.

The Inputs

Reputation calculation typically incorporates several categories of signal.

Authentication results. Did the sender’s mail pass SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting and Conformance) checks? Senders who fail authentication are flagged immediately. Senders who pass all three start with a higher baseline. Most providers in 2026 require at least one of SPF or DKIM to pass, and DMARC alignment is increasingly important for higher reputation tiers.

Complaint rate. How often do recipients of this sender’s mail click “mark as spam” or equivalent? Complaints are the strongest single negative signal. A sender with a complaint rate above approximately 0.3% is in trouble. Above 0.5%, the sender’s reputation degrades rapidly. The percentage looks small, but at scale (a sender sending 100,000 emails per week generates 300 to 500 complaints per week at that rate) it is the dominant input to reputation scoring.

Bounce rate. How often does mail to this sender’s recipient list bounce? High bounce rates indicate poor list hygiene (sending to invalid addresses), which providers interpret as a signal of either negligence or list-buying behavior. Both reduce reputation.

Engagement rate. Do recipients open, reply to, click, or otherwise interact with the sender’s mail? High engagement is a strong positive signal. Low engagement (especially combined with high volume) is a negative signal that the recipients did not actually want the mail.

Sending pattern consistency. Does the sender send a consistent volume over time, or does the volume spike and crash? Sudden volume increases (often associated with list buying or compromised accounts) are flagged. Steady, predictable senders score better.

Domain age. How long has the sender domain been in use? New domains start with neutral or slightly-cautious reputation that improves over weeks of clean sending. Domains less than 30 days old often have their mail routed to spam by default until they establish a track record.

IP reputation. The IP address the mail is sent from has its own reputation, separate from the domain. Shared sending infrastructure (like ESP-pooled IPs) inherits the reputation of the other senders using the same pool. Dedicated IPs accumulate reputation specific to one sender.

Historical patterns. Has the sender domain been associated with abuse in the past? Has the IP range been associated with botnets or bulletproof hosting? Historical signals attach to the sender even after corrective action.

The inputs combine into a score, and the score determines what happens to incoming mail at the receiving provider.

What Reputation Affects

The downstream effects of reputation are practical and consequential for senders.

Inbox vs spam routing. The most direct effect. Higher reputation = inbox; lower reputation = spam folder. The threshold is provider-specific and dynamic.

Throttling. Providers may delay accepting mail from lower-reputation senders. The delay is invisible to the sender at the SMTP level (the connection is just slower) but adds hours to delivery time.

Hard rejection. Senders below a certain reputation threshold may be outright rejected by the receiving server. The mail bounces and the sender is informed.

Greymail handling. Promotional mail from established senders is treated differently from cold outreach from new senders. Reputation determines which category the sender falls into for greymail purposes.

Categorization. Gmail’s tabbed inbox (Primary, Promotions, Updates, Forums, Social) uses reputation as one input to category routing. A sender with mid-tier reputation lands in Promotions; a sender with high reputation lands in Primary.

For commercial senders, reputation is the difference between mail reaching the inbox and disappearing into spam. The deliverability industry exists primarily to manage sender reputation.

How Senders Build Reputation

Building reputation is slow and brittle. The general practice for senders looking to build clean reputation:

Configure authentication thoroughly. Publish SPF records authorizing the sending IPs. Sign mail with DKIM. Publish a DMARC record at minimum in monitoring mode (p=none), eventually progressing to quarantine and reject as the sender confirms authentication is clean. Without these, no other reputation work matters.

Send only to opted-in recipients. Buying lists is the fastest way to destroy reputation. Recipients who did not subscribe complain at high rates, and the complaint rate is the dominant negative signal. Confirmed-opt-in (where the recipient must click a link to verify subscription) produces the cleanest list.

Honor unsubscribes promptly. The List-Unsubscribe header should be implemented. Click-to-unsubscribe should work in one click. Senders who continue mailing after unsubscribe see complaint rates climb.

Keep volume consistent. Sudden spikes look bad. Slow, steady ramp from zero to target volume over weeks (the “domain warm-up” process) is the standard for new senders.

Monitor your reputation. Google Postmaster Tools, Microsoft SNDS, and Sender Score (free third-party score from Validity) all give visibility into reputation. Established senders monitor these continuously.

Protect your domain from abuse. A compromised email account on your domain that starts sending phishing tanks the entire domain’s reputation. Implementing strong account security and DMARC enforcement protects the domain reputation from individual account compromises.

The total time to build reputation from zero to a healthy state is typically 4 to 12 weeks of clean, consistent sending. Reputation can be lost in days through a single bad sending event, and recovery takes weeks again.

Where Email Paywalls Sit

Sender reputation is a property of the sender, evaluated at the receiving server’s anti-abuse layer. Email paywalls operate at a different layer: the recipient’s inbox routing, after the receiving server has already accepted the mail.

A high-reputation sender has earned the right to reach the inbox. The receiving server delivers the mail. Rythm then checks whether the sender is on the recipient’s guest list. If yes, the mail reaches the inbox normally. If no, the cover charge applies regardless of how strong the sender’s reputation is at the technical infrastructure level.

This is intentional. Sender reputation is a measure of “is this sender’s infrastructure trustworthy,” which is different from “does this recipient want to hear from this sender.” A salesperson with excellent technical reputation is still a salesperson; the recipient may not want their cold outreach. Reputation does not solve the recipient-preference problem.

The cover charge applies the recipient-preference filter on top of whatever reputation filtering the receiving provider has done. The two filters serve different purposes and stack cleanly.

What Recipients Should Know

Recipients generally do not need to think about sender reputation, because the receiving server handles it. Two situations where it does become visible:

Senders you want to receive from sometimes go to spam. This usually indicates that the sender has a reputation problem, not that your provider is broken. Add the sender to your contacts, mark their mail as “not spam,” and reply to them; these signals improve your provider’s specific routing for that sender.

Senders you do not want to receive from sometimes reach the inbox. This usually indicates that the sender has built reputation despite sending unwanted mail (legitimate cold outreach often falls into this category). Reporting the mail as spam is the right action; it both routes future mail correctly and contributes a complaint signal to the sender’s overall reputation.

For recipients overwhelmed by unwanted mail from technically-clean senders, sender reputation is not the lever. The lever is structural filtering that does not depend on the provider’s reputation scoring. We covered this in what is an email paywall and why am I getting so much spam.

The Bottom Line

Sender reputation is how email providers decide which mail reaches the inbox. The score is dynamic, based on authentication, complaints, bounces, engagement, sending patterns, domain age, IP history, and historical abuse. It is real and consequential for senders. It is also orthogonal to the question of whether the recipient wanted to receive any individual sender’s mail.

For senders, reputation is the work of running a clean operation. For recipients, reputation is mostly invisible because the receiving provider handles it. For overlapping categories like cold outreach from technically-clean senders, sender reputation cannot save the recipient from volume; that is the layer where structural filters like Rythm operate, after reputation has already been evaluated and the mail accepted.