TL;DR
- →Authentication proves who you are. Reputation proves you’re trustworthy, and it’s graded every single send, forever.
- →ISPs watch four things: engagement, spam complaints, list quality, and how consistently you send.
- →83% of delivery failures trace back to reputation, not content, and yet 70% of senders never check it.
- →Domain reputation is portable. Switching ESPs or rotating IPs won’t outrun a bad one.
- →Recovery is slow: weeks for minor damage, months for severe. Go check your dashboards.
Alright, so your SPF, DKIM, and DMARC are all passing. You proved to Gmail: “Hey, it’s really me.” But here’s what Gmail’s thinking next: “Okay cool. But do we actually LIKE this guy?” That’s the gap between authentication and reputation. Authentication is showing your ID at a nightclub. Reputation is whether the bouncer actually wants to let you in, and that decision gets re-made every single time you send.
once per record
every send
Authentication gets you past the ID check. Reputation is the bouncer deciding whether you’re welcome, re-decided every send.
Most senders never see the background check ISPs run on them. A recent analysis of 53 million+ emails found 83% of all non-delivery problems trace back to poor sender reputation, not subject lines, not content. And 70% of senders never even check their reputation dashboards. They’re flying blind in a car that’s already swerving.
What ISPs actually watch
Four things, all the time: engagement, spam complaints, list quality, and how consistently you send.
Engagement
Opens and clicks that show real people want your mail.
Complaints
Bites fastestSpam reports throttle delivery almost immediately.
List quality
Bounced and dead addresses quietly erode trust.
Consistency
Steady volume reads as legitimate; sudden spikes read as spam.
Engagement
Opens and clicks signal whether people want your mail. But there’s a wrinkle: Apple Mail Privacy Protection auto-prefetches every email, registering a fake “open” whether a human reads it or not. So ISPs increasingly weight DKIM authenticated engagement more heavily. Get your DKIM alignment wrong, and your genuine engagement gets discounted too.
Spam complaints
The one that bites fastest. Gmail and Yahoo both throttle you above 0.3% (three people per thousand hitting “report spam”), and Gmail explicitly recommends staying under 0.1%. Complaints are rolling, daily calculations too: one bad campaign can shift your reputation band for weeks after the fact.
List quality and volume
Keep bounces under 2% (over 5% and ISPs assume you’re buying lists or ignoring hygiene entirely). And don’t spike your sending: a new domain blasting 100,000 emails on day one, or a longtime sender jumping 10x overnight, reads as textbook spammer behavior. Legitimate senders are boring and consistent. Spammers spike, burn out, and vanish.
Reputation compounds, in whichever direction you send it
Good sends earn engagement, which earns trust, which earns reach, which earns more engagement. Bad sends run the exact same loop in reverse, and the spiral is hard to climb out of.
And it follows you everywhere
Reputation is tied to your domain, not your ESP. Switch platforms, rotate IPs, migrate infrastructure: it comes with you, baggage and all. IP reputation rebuilds in a few weeks, but domain reputation takes months, and severe damage sometimes never fully clears.
IP reputation vs. domain reputation
Recovery time by damage severity
The hidden danger: spam traps
Spam traps are fake email addresses ISPs seed specifically to catch bad senders. Hitting one proves you’re scraping, buying lists, or ignoring your list for years.
Immediate, catastrophic hit
Gradual erosion over time
Small, localized dip
- Pristine traps: never real, seeded to catch scrapers. Hit one and you can be blocklisted immediately.
- Recycled traps: real addresses abandoned 12+ months ago, quietly converted into traps. A slow erosion, not an instant hit.
- Typo traps: gnail.com instead of gmail.com. Means you’re not validating addresses at signup: a small hit, but a signal of carelessness.
So go check your dashboards
You can see all of this. Four dashboards, all free. Check them weekly, or daily mid-campaign.
- Gmail Postmaster Tools (postmaster.google.com), the big one. Shows complaint rate, domain reputation (High/Medium/Low/Bad), delivery errors, and authentication status.
- Yahoo Sender Hub (senders.yahooinc.com), same core metrics, same 0.3% complaint threshold.
- Microsoft SNDS covers Outlook, Hotmail, and Live. Note: consumer accounts only, not Microsoft 365 or Exchange Online.
- Validity Sender Score (senderscore.org), a third-party 0-100 score. Above 80 is good, below 50 is real trouble.
The quick read on your numbers:
- Complaint rate: under 0.1% golden, 0.1-0.3% watch it, over 0.3% fix it today.
- Bounce rate: under 2% fine, 2-5% clean house, over 5% is a real list problem.
- Domain reputation: High is great, Medium is a warning, Low or Bad means you’re already filtered.
If your numbers came back rough, recovery follows real ranges: minor damage clears in 2-4 weeks of clean sending, moderate damage takes 4-8 weeks, and severe damage (multiple blocklists, a “Bad” Postmaster rating) runs 8-16+ weeks. Some domains never fully recover. The clock only starts once clean behavior replaces the bad pattern, and resuming full volume too early is the most common way senders reset their own clock back to zero.
Free dashboards
- Gmail Postmaster Toolspostmaster.google.com
- Yahoo Sender Hubsenders.yahooinc.com
- Microsoft SNDSsendersupport.olc.protection.outlook.com/snds/
- Validity Sender Scoresenderscore.org
The Cliff Notes
- ✓Authentication proves who you are. Reputation proves you’re trustworthy, and it’s judged continuously, not once.
- ✓83% of delivery failures trace back to reputation, not content, and most senders never check it.
- ✓Domain reputation is portable. You can’t escape a bad one by switching tools.
- ✓Spam traps are hidden mines. Pristine traps blocklist you instantly; recycled and typo traps erode you slowly.
- ✓Recovery is slow: 2-4 weeks for minor damage, 8-16+ for severe. Check your dashboards weekly.
Next up, Section 4: the technical setup, the practical steps to put all of this into action.
Build. Scale. Believe.