Sender reputation is four reputations: which one is broken

"Sender reputation" is shorthand for at least four separately scored things: the sending IP, the sending domain and its subdomains, the individual mailbox or From address, and the URL domains inside your message. A receiver can trust three and distrust one, which is why a campaign from a reputable company on a reputable ESP can still land in Junk.

The four layers

Two consequences follow immediately. On a shared ESP pool you cannot fix the IP layer, only choose a different pool or platform. And the mailbox layer is invisible in every ESP dashboard, because ESPs report per account and per campaign, not per sending identity.

Which layer is broken: a short diagnostic

1. All mail from every domain you own is failing at one provider. Suspect the IP layer or a blocklisting. Check the IP against the live lists, and remember SORBS shut down in June 2024 while Validity's Heatwave blocklist launched on 3 September 2026, so your lookup set should have changed this year.
2. One sending domain is failing, others on the same ESP are fine. Domain layer. Check authentication alignment first, then Postmaster Tools spam rate, then recent list imports on that domain.
3. One mailbox out of ten is failing while nine are fine on the same domain. Mailbox layer — almost always volume or content behaviour specific to that sender: a sudden jump in daily sends, a signature image, or a sequence that collected complaints.
4. Placement collapses only when links are present. URL layer. Test the same message with the tracking redirect removed. A shared link-shortener or a brand-new tracking subdomain with no reputation is a common cause.
5. Everything fails at once, immediately after a change. Authentication. Someone edited DNS, rotated a DKIM key, or added an SPF include that pushed the record past the 10-DNS-lookup limit.

What each layer actually responds to

• IP: consistent volume, low complaint rate, and reverse DNS matching the HELO name. Nothing you can do quickly, and gaps in sending cost you.
• Domain: authentication that aligns, age and consistency, complaint rate, and whether recipients engage. Gmail's published bulk-sender threshold is a user-reported spam rate under 0.3%; treat 0.1% as your ceiling.
• Mailbox: per-sender volume that looks human, genuine replies, and not being the one mailbox in the fleet that sends five times as much as the others.
• URL domains: age, whether the domain is only ever used in bulk mail, and whether it is shared with other senders. A dedicated tracking subdomain on your own domain is better than a shared shortener, and no tracking at all is best for one-to-one outreach.

The order to fix things in

1. Authentication, because nothing else can be measured while it is broken. SPF resolving within 10 lookups, DKIM signing with a published selector, DMARC aligned to the visible From domain, verified by reading a received message rather than a configuration screen.
2. Complaints, because they are the fastest-acting negative signal. Remove unengaged recipients before you try anything else.
3. Volume shape, because spikes and gaps both read as suspicious. Steady beats large.
4. Engagement, which is the only positive signal you can actively build. Warm-up produces it before a campaign exists; real replies sustain it afterwards.
5. Then the IP, if you own one, and only with enough consistent volume to keep it warm.

What not to do

• Do not chase a single "reputation score" from a vendor. Ask which of SNDS, Postmaster Tools, your ESP's events, a seed test or a blocklist lookup it is derived from; if nobody can say, it is an opinion.
• Do not expect Postmaster Tools to show a domain reputation grade. Google retired that chart; spam rate and authentication rates are what remain.
• Do not move a damaged domain to a new ESP and expect a reset. The domain layer travels with you.
• Do not spin up fresh domains every few weeks instead of repairing one. Age and consistency are part of the score, and churn is itself a pattern.
• Do not average providers. Microsoft and Gmail disagree constantly, and the average hides the half that is failing.

MailPilot works the two layers you actually control day to day: it verifies SPF, DKIM and DMARC per sending domain, warms each mailbox individually over OAuth or SMTP, measures inbox placement per provider through a seed network, and records a reputation score per mailbox every day — so when one of four layers moves, you can see which one it was.