Sender reputation

How sender reputation works

Mailbox providers do not treat every sender the same. Amazon SES describes reputation as a measure of confidence that a sender is not sending spam 1. That score sits on the IP, the domain, or both, and it moves as mail goes out into the wild.

The inputs are concrete and measurable. Hard bounces show the list still holds dead addresses 1. Spam complaints show recipients marked the mail as unwanted 1. Low opens and quiet deletes look like indifference. Failed SPF, DKIM, or DMARC checks look like spoof risk to the filter. Providers combine those signals into a quiet score that operators rarely see as one neat number.

Google Postmaster Tools is one public window into that score for mail aimed at personal Gmail inboxes 2. Google asks bulk senders who send 5,000 or more messages a day to authenticate mail and to keep spam rates reported in Postmaster Tools below 0.3 percent 2. Crossing that line raises the odds that later waves land in spam or get rejected at the door 2.

Reputation is sticky both ways. A clean history makes a volume ramp safer on the next campaign. A spike of hard bounce events or complaints can take weeks of careful sending to repair 1. Shared IPs couple one sender's behavior to everyone else on the same pool 2. Dedicated IPs isolate the score, but they also mean the sender owns every mistake alone.

List quality is the lever most teams still control each day. Removing domains with no MX record, disposable addresses, and obvious role inboxes before the send cuts the bounce and complaint fuel that burns reputation 3. Content and cadence still matter after that filter. A perfect list cannot save a domain that ignores unsubscribe signals or suddenly doubles volume overnight without history 2.

Authentication belongs on the same checklist. Providers reward aligned SPF and DKIM, and they expect a DMARC policy on bulk streams 2. Missing those records does not always block mail on day one. It does make every later complaint look worse, because the domain never proved it authorized the message.

Why sender reputation matters for outbound teams

Outbound fails quietly when reputation slips under the ESP dashboard. The ESP still reports accepted. The CRM still shows sent. The prospect never sees the thread in the primary inbox. Teams then blame copy or targeting while the real gate is a damaged sending identity sitting in spam.

Reputation also sets how fast a new domain can grow without tripping filters. Google tells senders to raise volume gradually and to avoid sudden spikes that double prior volume without a sending history 2. That guidance is the practical core of email warm-up. Skipping it to hit a quarterly number is how new domains end up rate-limited on week two.

Agencies that inherit client domains should treat reputation as a first audit item, not a late deliverability ticket. Pull Postmaster Tools when Google mail is a large share of the audience 2. Review bounce and complaint webhooks for the recent month of sending. Pause domains that already sit near Google's 0.3 percent spam-rate line before anyone adds more cold volume 2.

Product builders who send transactional and marketing mail from one domain mix two risk pools on purpose. A password-reset stream with near-perfect engagement can still suffer when a marketing blast from the same domain draws complaints 1. Splitting domains by purpose keeps the high-trust stream insulated from cold outreach noise.

Verification is the cheapest preventive step before a cold wave leaves the queue. RichAPI Email verifier returns status, disposable, and mxFound for 2 credits per verdict 3. A waterfall miss with no verdict bills zero credits 3. New accounts start with 100 free credits and no card 3. Dropping mxFound false and disposable rows before send is how teams stop buying reputation damage one bounce at a time.

When reputation is already hurt, the move is to stop the cold send. Fix authentication first. Suppress hard bounces. Lower daily volume. Rebuild with engaged recipients before prospecting resumes. Sending harder into a damaged score makes the hole deeper, not shallower 1.

Example of protecting sender reputation before a cold send

A sales team wants to email thousands of new contacts from a domain that has only sent light transactional mail so far. The first move is not the sequence copy. It is a reputation check paired with a list clean.

They open Google Postmaster Tools for the domain and confirm spam rates sit well under 0.3 percent 2. They confirm SPF and DKIM pass on a seed test message 2. Then they run every contact through RichAPI Email verifier before any campaign step fires 3.

Rows with mxFound false leave the sendable list right away 3. Disposable domains leave next 3. Catch-all and unknown statuses move to a slower nurture track. Only cleaner statuses stay in the first cold wave. The wave itself stays small on day one, then grows across the week instead of landing the full contact list on Monday morning 2.

Billing stays predictable through the cleanup. Each verifier verdict costs 2 credits 3. Misses that return no verdict cost zero 3. The 100 free credits on a new RichAPI account cover an early sample of the same verification flow 3.

Two weeks later Postmaster Tools still shows a low spam rate on the domain 2. The team raises daily volume with evidence instead of hope. That is sender reputation managed as an operating habit, not a mystery score behind the ESP.

Sender reputation vs domain reputation

Sender reputation often tracks the full sending identity, including IP history. Domain reputation focuses on the domain name mailbox providers see in the From header and in authentication-aligned domains.