# Reputation Monitoring and Remediation

> How senders monitor IP and domain reputation in practice — blocklist monitoring, seed/inbox-placement testing, provider dashboards, feedback loops, warning signs, and the delisting/recovery workflow.

Source: emailmarketing.net — https://emailmarketing.net/learn/operations/reputation-monitoring

Your sender reputation can slip at any time, and when it does, the consequences escalate from placement in the spam folder to blocklisting to outright rejection. Below is how to watch reputation continuously, and what to do when it drops.

Sender reputation works like a credit score. With no sending history, you have neither a bad reputation nor a good one: a history of performance must exist before mailbox providers extend "credit", in the form of tolerance for your volume and placement in the inbox. Reputation is not fixed. For what reputation is built from, see [Foundations of Email Deliverability](https://emailmarketing.net/learn/foundations/foundations-of-email-deliverability). For building it on new IP addresses, see [IP Warm-Up](https://emailmarketing.net/learn/ip-management/ip-warm-up).

## Delivery vs. deliverability: why you need to monitor

- **Delivery**: the receiving server accepted the message (visible in your logs as a 250 OK).
- **Deliverability**: where the message landed after it was accepted. That may be the inbox, a tab such as Promotions or Updates, the spam folder, or nowhere, because it was silently dropped ("missing").

Confirming delivery from SMTP responses is straightforward. Knowing placement is much harder, because each mailbox provider applies its own private routing and filtering algorithms after it accepts a message. A message that reaches the inbox at Yahoo may go to the spam folder at Gmail or Microsoft. Without placement data, deliverability problems are hard to detect and diagnose: engagement metrics quietly decline while the delivery rate stays high.

How much mail actually goes missing: Litmus's 2026 benchmark found that **87.25%** of legitimate marketing email reached the inbox (so about **1 in 7 never does**), with wide differences between providers:

| Provider | Market share | Inbox rate | Spam rate | Missing |
|---|---|---|---|---|
| Gmail | 42.9% | 89.8% | 6.4% | 3.8% |
| Yahoo | 15.7% | 87.3% | 6.4% | 6.3% |
| Microsoft | 14.4% | 77.4% | 15.1% | 7.5% |
| Apple | 3.6% | 82.0% | 10.8% | 7.2% |

For a wider set of dated benchmarks, attributed to their vendors, to judge your own numbers against, see [Deliverability Benchmarks](https://emailmarketing.net/learn/reference/deliverability-benchmarks). It covers Validity's seed-measured placement by provider, country, region and industry, and engagement rates for each industry.

## The monitoring stack

A working program for monitoring reputation combines five independent sources of data. No single one is enough.

### 1. Your own engagement and delivery metrics

The earliest warning signs are in data you already have. Track these metrics for each mailbox provider, not only in aggregate:

- Open rate, click rate and conversion rate. A significant drop at one provider while the others hold steady is the classic sign of placement in that provider's spam folder.
- Bounce rate, broken down by category (invalid address, policy block, reputation block, temporary).
- Unsubscribe rate and spam complaint rate.
- Messages deleted without being read, replies and forwards, where available.

Look at **trends from week to week**, not at daily noise. Mailbox providers base their decisions on patterns over time, and daily metrics are too volatile to act on. Spam filters increasingly use machine learning that adjusts in real time, so the goal is to spot a trend before it becomes a problem.

### 2. Blocklist (DNSBL and RBL) monitoring

A blocklist, either a DNSBL (DNS-based Block List) or an RBL (Realtime Block List), is a list you can query of IP addresses (and sometimes domains, URLs or usernames) suspected of sending spam. Two facts shape how you should use them:

- **Blocklists do not block anything themselves.** Mailbox providers use blocklist data **together with their own internal metrics** to decide what to block. A listing is an input, not a verdict.
- **Not all lists carry the same weight.** There are hundreds of DNSBLs, and most have negligible impact. Different providers give weight to different lists, and Gmail largely ignores third-party blocklists in favor of its own systems.

These are the lists worth monitoring, roughly in order of impact:

| Blocklist | Notes |
|---|---|
| Spamhaus | The most impactful; used by the majority of ISPs and email service providers |
| SpamCop | Based on reports from SpamCop users; moderate impact |
| Barracuda Reputation Block List | Widely consulted |
| Invaluement | Subscription-based IP and domain anti-spam list |
| SORBS | Lower impact; still monitored by some receivers |

In practice, reputation blocks show up as **failed or bounced events in your delivery logs**. Read the full SMTP rejection text, which typically names the blocklist. Automated, regular DNSBL lookups on all your sending IP addresses and domains catch listings before recipients' servers do.

### 3. Mailbox-provider dashboards (postmaster tools)

The major providers show you directly how the receiving side sees your reputation:

- **Google Postmaster Tools**: ratings of domain and IP reputation, spam complaint rate, pass rates for SPF, DKIM and DMARC, and delivery errors for mail to Gmail.
- **Microsoft SNDS (Smart Network Data Services)**: data for each IP address on mail to Microsoft's consumer domains, including volume, the filter verdict (green, yellow or red), complaint rate and spam-trap hits.

These tools are free. Set them up before problems occur, because they provide history you cannot reconstruct later.

### 4. Seed / inbox-placement testing

Seed testing sends a campaign to a panel of test mailboxes at different providers, and reports where each copy landed: the inbox, spam, a specific Gmail tab (Primary, Promotions, Updates, Social or Forums), or missing. Commercial tools (for example, Litmus Spam Testing, Mailgun Inbox Placement, and Validity's Everest) report:

- **Inbox Placement Rate (IPR)**: the percentage of successfully delivered emails that reach the inbox rather than spam, broken down by provider.
- Scans before sending against major commercial spam filters, plus blocklist and authentication checks (validation of SPF, DKIM and DMARC).
- A prediction of the Gmail tab for a given message.

Seed tests have limits. Seed panels cannot measure the engagement of real recipients, and seed mailboxes have no engagement history with you, so results lean conservative. Use them to isolate problems with content, templates or infrastructure. Test one variable at a time, since content testing is most useful when it is limited to specific messages. Combine the results with your live engagement data for the full picture.

### 5. Feedback loops (FBLs)

Most major mailbox providers offer feedback loops that report which recipients marked your mail as spam. Signing up matters for your overall deliverability. FBL data lets you suppress people who complain immediately (see [suppression handling](#suppression-lists-as-a-reputation-defense)), and it measures negative feedback for each provider. Check whether your sending platform enrolls you automatically or whether you must register yourself. **If you ignore FBL feedback, your reputation drops sharply and your sending is throttled or blocked entirely.**

## Warning signs and thresholds

The table below gives the operating thresholds that Klaviyo publishes, which apply whatever platform you use. These are **Klaviyo's house numbers**, deliberately stricter than the consensus across sources. For the range of values with attribution, and the enforcement lines that other providers publish, see the [canonical threshold table](https://emailmarketing.net/learn/operations/metrics-and-benchmarks#canonical-threshold-table):

| Metric | Klaviyo target | Signal when breached |
|---|---|---|
| Open rate | ≥ 33% (raw, including machine opens) | Unengaged list, or placement in the spam folder |
| Click rate | ≥ 1% | Weak content or call to action, or a placement problem if opens also fell |
| Bounce rate | < 1.0% | List not cleaned; providers read this as poor practice |
| Unsubscribe rate | < 0.3% | Expectations not met, or frequency too high |
| Spam complaint rate | < 0.01% | The single most damaging signal |

On complaints specifically, Klaviyo's **< 0.01%** is a conservative house number. The broader industry consensus target is **< 0.1%** (AWS SES, Postmark, SendGrid), and the **0.3%** ceiling set by Gmail and Yahoo is a hard limit you must never reach. The [canonical threshold table](https://emailmarketing.net/learn/operations/metrics-and-benchmarks#canonical-threshold-table) reconciles all of these. Klaviyo's open-rate target is a **raw** number, which includes machine opens and is inflated by Apple Mail Privacy Protection (MPP). Do not compare it with a rate that filters out bots.

Other red flags come before a loss of reputation:

- **Volume spikes.** Tripling your usual sending volume can trigger providers' detection of compromised accounts, and sudden increases invite filtering whatever the quality of the content. Keep sending consistent, and ramp up gradually for planned large increases (see [IP Warm-Up](https://emailmarketing.net/learn/ip-management/ip-warm-up)).
- **Rising rates of soft bounces or deferrals at one provider.** This is often throttling, the step before blocking.
- **Spam-trap hits** (visible in SNDS). They are evidence of poor list acquisition or hygiene, and ISPs flag senders whose traffic hits a higher than normal percentage of traps.
- **A decline in the baseline quality of your list.** Marketing databases degrade by about **22% per year** (addresses change, people change jobs, mailboxes are abandoned), so a list that is not actively maintained is always drifting toward trouble.

## Suppression lists as a reputation defense

Automatic suppression turns negative signals into protection. These are the standard mechanics, as major sending platforms implement them; replicate them on any infrastructure:

- **Hard bounces** (permanent, such as an invalid address): suppress immediately and permanently.
- **Soft bounces** (temporary, such as a full mailbox or a server that is down): suppress after repeated consecutive failures (for example, 7 consecutive soft bounces).
- **Spam complaints** (from FBLs): suppress immediately, and never mail that person again. A rejection such as "not delivering to a user who marked your messages as spam" is the suppression system working as intended, so do not bypass it.
- **Unsubscribes**: suppress from marketing mail immediately. Transactional mail (confirmations of orders, shipping or account changes) is not tied to subscription status and may still be sent to suppressed recipients. Welcome series, abandoned-cart messages and back-in-stock messages, however, are marketing, not transactional.

These mechanics fit the removal rule in the Messaging, Malware and Mobile Anti-Abuse Working Group (M3AAWG) *Sender Best Common Practices* (Version 4.0, August 2026, section 2.2). M3AAWG considers it a best practice to remove an address that bounces at least twice in a row, across a span of two weeks or more, whatever the failure code or text, and leaves the exact count and time span to each sender. The soft-bounce example above is Klaviyo's platform setting. It is a higher count than M3AAWG's minimum of two, so it follows the rule while waiting longer before removing an address. Count one bounce per campaign rather than one per retry, since M3AAWG's rule is about consecutive campaigns.

Two cautions keep the rule from removing good subscribers:

- **"Hard bounce" above means a failure about the address**, such as an unknown user. M3AAWG also asks senders to read the bounce text, because the code alone does not say whether to remove the address, and the text can reveal a blocklisting of the sender. A permanent refusal for policy or reputation reasons (a `5.7.x` code) is usually about your sending, not about the recipient. Investigate it instead of suppressing the address.
- **Do not count bounces from a period when you were blocked** toward any address's removal count. They say nothing about the addresses.

[SMTP Enhanced Status Codes](https://emailmarketing.net/learn/bounce-handling/smtp-enhanced-status-codes#status-codes-and-the-m3aawg-removal-rule) sets out how to apply the M3AAWG rule to each class of code.

## Remediation when reputation drops

### Systematic diagnosis (in order)

1. **Verify infrastructure and authentication.** SPF, DKIM and DMARC should pass and be aligned (see [DMARC](https://emailmarketing.net/learn/authentication/dmarc)). A mismatch between the From domain and the actual sending domain (even `mail.example.com` against `example.com`) is enough for some receivers to send mail to spam or reject it.
2. **Check blocklists** for every sending IP address and domain, and read the rejection texts in your logs.
3. **Check provider dashboards.** Did domain or IP reputation degrade, and when? Match the date against changes to campaigns or lists.
4. **Review changes to segmentation and lists.** A new acquisition source, an imported list, or a campaign to contacts who have lapsed is the most common trigger.
5. **Evaluate content and timing.** Run the failing message through a seed or spam test to separate content problems from reputation problems.
6. **Track complaint trends from week to week** to confirm whether your changes are working.

### Blocklist delisting workflow

1. **Identify the list and the listed asset** (an IP address or a domain) from rejection messages or DNSBL lookups.
2. **Find and fix the root cause first.** Requesting delisting is delicate. If you ask for removal without changing the behavior that caused the listing, your future requests lose credibility, and repeated requests handled badly can lead to a **permanent** listing. Typical causes are a bad acquisition source, spam-trap hits, a compromised account or form, and a spike in complaints.
3. **Follow that list's own removal process.** Each DNSBL handles removal differently, with different timelines. Some let listings expire automatically; others require a request with evidence of remediation.
4. **If you send through a shared provider**, its abuse or compliance team has often already started delisting. Coordinate with it rather than filing duplicate requests. Established relationships with blocklist operators speed up resolution considerably.
5. **After delisting, keep monitoring.** A listing that comes back soon after a delisting is treated more harshly.

### Recovering inbox placement

Recovery is slow, and providers do not explain it. They require a **sustained pattern of better signals** before they change placement, and when the damage runs deep, whole subdomains and IP addresses can become effectively unusable. The proven approach is to shrink your sending to your most engaged recipients and rebuild:

- Stop sending to anyone outside recently engaged segments. This is a new warm-up, following the same logic as a [warm-up](https://emailmarketing.net/learn/ip-management/ip-warm-up).
- Suspend high-risk flows during recovery: sends for third parties or affiliates, and win-back, sunset and re-engagement flows.
- Fix the root cause you diagnosed (the list source, the content or the authentication).
- Expect **8–12 weeks** to fully return to the inbox. This is the recovery timeline Litmus documented for itself after it focused on engaged subscribers.
- As a stopgap for critical mail, ask recipients to add your **sending domain** to their safe senders. Asking them to safelist an IP address makes sense only for dedicated IP addresses, because assignments of shared IP addresses are effectively dynamic.

## Related articles

- [Foundations of Email Deliverability](https://emailmarketing.net/learn/foundations/foundations-of-email-deliverability), on the signals reputation is computed from
- [Two Worlds of Email Deliverability](https://emailmarketing.net/learn/strategy/two-worlds-of-email-deliverability), on why recovery based on engagement works and gaming the system does not
- [Content and Design for Deliverability](https://emailmarketing.net/learn/operations/content-and-design-for-deliverability), on the content factors that seed tests reveal
- [Advanced IP Segmentation](https://emailmarketing.net/learn/ip-management/advanced-ip-segmentation), on containing damage to reputation by isolating mail streams