Infrastructure

Sender Reputation: How Providers Judge Your Domains and IP

Updated November 2026 · 8 min read

In short

Sender reputation is the trust mailbox providers attach to your sending domains and your sending IP. Gmail, Yahoo and Microsoft check it before reading a word of content. They look at the From domain, the bounce domain, the DKIM signing domains, the Reply-To and List-Unsubscribe domains, and the IP that delivered the email. Are they listed on blacklists? Properly configured? Really under your control? One listing on a major blacklist can block delivery outright. Identities you do not control quietly dilute your reputation into a shared pool.

Why domain and IP reputation decide delivery before content does

Mailbox providers filter in layers. Authentication answers “is this really you?”. Reputation answers “and do we trust you?”. Every domain behind an email carries a history: the From domain, the bounce domain (Return-Path), the domains that sign the message (DKIM), the Reply-To and List-Unsubscribe domains. So does the IP address that handed the email over. That history is made of complaints, spam-trap hits, volume patterns and blacklist listings. Providers consult it first.

For Email Marketers, the stakes are asymmetric. A single listing on a major blacklist can stop a campaign at the door, whatever its content. A weaker set-up blocks nothing on its own: a generic reverse DNS, or a Return-Path or DKIM signature living on your platform’s shared domain. But it pools your reputation with every other sender on that domain, and it erodes inbox placement over weeks. Sender Reputation makes both visible before the send.

Domain reputation and IP reputation: what providers actually evaluate

Authentication proves the identities are yours. Reputation decides whether they are trusted.

Your sending domains

Five headers, five domains that providers evaluate separately: the From domain your recipients see, the bounce domain (Return-Path) that receives delivery failures, the domains that sign the message (DKIM), the Reply-To domain and the List-Unsubscribe domain.

Each hostname is checked against the blacklists together with its parent domains. A listing on a parent therefore weighs on every subdomain beneath it. Two tiers of lists matter: Spamhaus DBL is used for direct blocking, while SURBL and URIBL feed the spam score. Expected: every identity “not listed” on the lists checked that day.

Your sending IP

The sending IP is the address that delivered the message. It is checked against Spamhaus ZEN. A listing there is critical. A PBL entry is a warning: the address belongs to a range not meant to send email directly. Its reverse DNS is verified both ways: the PTR name, then its forward confirmation (FCrDNS). Gmail and Yahoo require both. Generic names built from the IP digits are flagged.

The sending platform is inferred from the reverse DNS and the network owner. The IP pool is estimated as likely dedicated, likely shared or undetermined. This estimate always comes with its evidence. It is never a verdict.

Who controls each identity — Inbox Maestro’s reading

Beyond the lists, Inbox Maestro labels each domain by who really operates it. Brand: your own domain. Brand · delegated: your domain, run by your sending platform through DNS delegation. This is the normal, recommended set-up. ESP · shared: a domain pooled across the platform’s customers. Third party: neither your brand nor your platform. A Return-Path or a sole DKIM signature on a shared ESP domain is not an error. It is reported for information. But your reputation then rises and falls with every other sender on that domain. Expected: From, Return-Path and at least one DKIM signature under your control, directly or by delegation. A second signature on the platform’s domain is normal practice.

How to read a Sender Reputation check

Pass“IP and sending domains not listed on major blacklists · Identities under brand control.” Nothing to fix. The line may still end with points to review, such as a DKIM key below 2048-bit or a Return-Path on the platform’s shared domain. They do not change the verdict.
Warn“IP and sending domains not listed on major blacklists · Configuration issue: reverse DNS does not match the sending IP.” Other causes: a domain flagged as suspicious (SURBL, URIBL); a Reply-To or List-Unsubscribe on a domain that is neither yours nor your platform’s; an IP on Spamhaus PBL. Fixable before the send.
Fail“Sending domain yourbrand.com listed on a major blacklist (Spamhaus DBL) · IP not listed on major blacklists.” Same verdict when the IP itself is listed on Spamhaus ZEN. Providers block on these lists. Corrective action on the campaign is not optional.

How the verdict is built. Every identity (From, Return-Path, Reply-To, each DKIM domain, List-Unsubscribe) and the sending IP get their own status in the detail. The verdict at the top is the most severe of them. It is the one that counts for your campaign. The summary line always follows the same order: blacklist status first, then the concrete issue, then what is in order. A Warn or a Fail therefore always names its cause. Lists come in two tiers. Spamhaus (ZEN, DBL) is used for blocking: Fail. SURBL and URIBL feed the spam score: “flagged as suspicious”, Warn. Low-signal lists such as URIBL grey are information only. “Not listed” means on the lists checked that day. It is a snapshot, not a guarantee of placement.

5 best practices

  1. Check the blacklists before every important send, and weigh them by severity. A Spamhaus listing is critical, because providers block on it: ZEN for the IP, DBL for a domain. SURBL and URIBL raise the spam score. They call for investigation, not panic. Check every identity, not only the From domain.
  2. If a Spamhaus listing appears, make it the priority of the day. Identify the cause: a compromised account, a purchased or stale list, spam-trap hits. Correct it on the campaign concerned, then request delisting. Pausing the send is one option, and not always a possible one. The corrective action is never optional: a listing left in place weighs on every following campaign.
  3. Set up a custom bounce domain and a brand DKIM signature with your sending platform. Ask for 2048-bit keys, and rotate the ones still at 1024-bit. Almost every ESP offers this. It is what moves your reputation from the platform’s shared pool to your own domain.
  4. Keep Reply-To and List-Unsubscribe on domains you control. On a dedicated IP, make sure the reverse DNS exists, points back to the IP and carries a meaningful name. On a shared pool, that is your platform’s job. The check tells you whether it is done.
  5. Build reputation over weeks, not sends: consistent volumes, clean lists and brand-controlled identities. Google Postmaster Tools and Microsoft SNDS show how your domains and IPs are perceived day after day.

Common mistakes

  • Checking only the From domain against blacklists. The bounce domain, the DKIM domains, the Reply-To and the sending IP are judged too. Any one of them can carry the listing.
  • Putting a helpdesk, agency or ticketing domain in Reply-To or List-Unsubscribe: providers see an identity they cannot connect to the brand.
  • Moving to a dedicated IP without setting its reverse DNS. A dedicated IP with a missing or generic name looks worse than a well-run shared pool.
  • Treating every blacklist alike. A Spamhaus listing stops delivery. A URIBL grey entry is information. Reacting to both the same way wastes time on the wrong one.
Inside Inbox Maestro

How Inbox Maestro checks it

Inbox Maestro reads the identities of the real test email your platform sends: the From, Return-Path, Reply-To, DKIM and List-Unsubscribe domains, and the IP that delivered it. It checks them the way mailbox providers do. Are they listed on public blacklists (Spamhaus, SURBL, URIBL)? Is the sending IP properly configured? Who really controls each domain?

Each identity and the IP get their own status. The report then gives one final verdict, the most severe of them: Pass, Warn or Fail. Its summary line always states the blacklist status first, then the concrete issue if any. You find it in the Checkup section of your report, under Infrastructure, next to Authentication.

Checkup › Infrastructure › Sender Reputation
How mailbox providers see the sender’s domains and IP behind this email.
Sending identityFrom · Return-Path · Reply-To · DKIM d= · List-Unsubscribe — domain, who controls it, blacklist status, MX
Pass
Sending IPObserved on this test send — address, Spamhaus ZEN status, reverse DNS and FCrDNS, platform (inferred), IP pool estimate with evidence
Warn
Verdict: Warn — “IP and sending domains not listed on major blacklists · Configuration issue: reverse DNS does not match the sending IP”. The verdict at the top is the one that counts. Below it, the report shows the issue that caused it and highlights the matching row in the detail. A “Good to know” section follows: DKIM on the platform’s domain only, 1024-bit keys, DMARC still in monitoring mode. It informs without changing the verdict. Sources and check date close the block.

Frequently asked questions

What is the difference between Authentication and Sender Reputation?

Authentication (SPF, DKIM, DMARC) proves the message really comes from the domains it claims. Sender Reputation checks whether those domains and the sending IP are trusted: not listed on blacklists, under the brand’s control, and properly configured. An email can pass authentication and still be filtered on reputation.

Is a Return-Path on my ESP’s domain a problem?

It is not a failure. It is reported for information. Your bounces are handled, but the reputation they build goes to a domain shared with the platform’s other customers. A custom bounce domain moves that reputation to your brand. Most platforms offer one.

My From address is on my platform’s domain and only the display name shows my brand — is that a problem?

It is not a failure, but the report flags it. That domain is labelled “Sender domain”, with a note that it differs from the brand you display. Every send then builds reputation for a domain shared with the platform’s other customers. Neither recipients nor filters can tie the message to your brand. The fix: use a dedicated sending domain or subdomain of your brand, delegated to the platform. Reputation and authentication are then yours.

What should I do if a domain is listed on Spamhaus?

Treat it as the priority of the day. Identify the cause: a compromised account, a purchased or stale list, spam-trap hits. Correct it on the campaign concerned, then follow Spamhaus’s delisting procedure. Pausing can be an option, but it is not always possible. What matters is that the corrective action happens. A listing left in place weighs heavily on the performance of every following campaign. And delisting without fixing the cause leads to re-listing.

Check the reputation of your sending domains and IP — before sending.

Send a test email from your usual platform. Inbox Maestro checks the sending domains and IP as mailbox providers see them: blacklists, control and configuration.

Get Your Email Checkup →