Sender Reputation

We verify billions of email addresses, and the single biggest reason a client’s campaign underperforms has nothing to do with subject lines or send times. It is sender reputation — the invisible score every mailbox provider keeps on a sending domain and IP — and it decides your mail’s fate long before a human ever sees the subject line.

What feeds the score

Mailbox providers like Gmail, Outlook, and Yahoo do not publish their exact scoring formulas, but the inputs are well understood because they show up consistently across postmaster tools and deliverability research. Four signals dominate.

Hard bounces. Every message sent to an address that does not exist comes back as a hard bounce, and a high hard bounce rate is one of the clearest signs a sender is not maintaining their list. Providers read it as carelessness at best and list-buying or scraping at worst.

Spam trap hits. A spam trap is an address with no real owner, planted specifically to catch senders with poor list hygiene. Mailing even a handful of traps is a much stronger negative signal than an ordinary bounce, because there is no innocent explanation for it.

Complaint rates. Every time a recipient clicks “report spam,” that event is fed back to the mailbox provider and counted against the sending domain and IP. Complaint rate is measured as a percentage of delivered mail, and providers set their thresholds low, often around one in a thousand messages.

Engagement. Opens, clicks, replies, and manual moves to a primary folder all read as positive signals. Deletes without opening, moves to spam, and long stretches of silence from a segment all read as negative ones. Providers use engagement as a proxy for whether recipients actually want the mail they are receiving.

Authentication. Passing SPF, DKIM, and DMARC, with proper alignment between the signing domain and the visible “from” address, is now table stakes. Mail that fails authentication is treated as unverifiable and scored accordingly, regardless of how clean the rest of the sending practice is.

Domain reputation vs IP reputation

Reputation is tracked at two levels that interact but do not move in lockstep. IP reputation belongs to the specific sending server’s address. On shared sending infrastructure, that reputation is pooled across every customer using the same IP range, which is why a dedicated IP is often recommended once volume justifies it: it isolates your history from everyone else’s.

Domain reputation belongs to the “from” domain itself and persists across IP changes, migrations between email service providers, and new sending infrastructure. Mailbox providers increasingly weight domain reputation more heavily than IP reputation, because a domain is a much more durable identity than an IP address that can be rotated or reassigned. In practice this means a spotless domain history can carry a freshly warmed IP, while a domain with a poor history will drag down the reputation of any IP that sends on its behalf.

Thresholds that trigger throttling or blocks

Reputation damage rarely arrives as a single dramatic event. It shows up as a graduated response once a sender crosses certain thresholds. A complaint rate that creeps above roughly 0.1 percent, or a hard bounce rate of a few percent, is often enough to trigger throttling: the receiving server accepts mail more slowly, defers a growing share of it, or begins routing a portion straight to the spam folder while it evaluates whether the sender is trustworthy.

Cross those thresholds by a wider margin, especially with repeated spam trap hits or a sudden, unexplained spike in volume from a previously quiet domain, and the response escalates to an outright block: the receiving server refuses the connection or the message outright, and the sending domain or IP can land on a public blocklist. You can check whether that has already happened with the email blacklist check, which scans a domain or IP against the major blocklists in seconds.

How list verification protects it

Because hard bounces and spam complaints are the two heaviest, most controllable inputs into sender reputation, verifying a list before you send is one of the few levers a sender has direct control over. A verification pass catches the addresses most likely to hurt the score: mailboxes that no longer exist and would hard bounce, known spam traps hiding in an old or purchased list, and disposable or role addresses that tend to drag engagement down and complaint risk up.

• Verification is part of the same engine behind the free email checker and the verification API, so bad addresses are caught before a send, not after a bounce report.
• To check whether reputation damage has already happened, scan a domain or IP with the email blacklist check.
• To inspect the raw delivery responses behind a bounce and confirm what actually happened, use the bounce checker.

Reputation is slow to build and fast to lose, so the highest leverage move is preventing the damage in the first place rather than repairing it after the fact. The full verification pipeline that protects sending reputation at scale is documented on the email verification page, with volume tiers on the pricing page.