Sender Score: What the Number Can and Cannot Tell You

Sender Score can tell you how one public sending IP looks inside Validity's data network. It cannot grade your domain, prove where a message landed, or explain performance at every mailbox provider. Before changing a campaign, identify the IP that was scored and whether anyone on your team can control it.

Begin with the object being measured

The current Sender Score lookup defines the result as a zero-to-one-hundred measure of an IP address's reputation and email-program health. A sending domain can use several IPs, while one shared IP can carry mail for many unrelated domains.

Capture the exact public IP from the message headers or sending provider. Do not type a domain into a separate lookup, see a number, and assume it describes the same infrastructure. Add the date and time because telemetry without a timestamp cannot be compared later.

Validity says its data network includes observations from more than eighty mailbox and message-security providers. It lists signals such as complaints, unknown users, blocklists, infrastructure, gateway rejection, filtering, spam traps, and volume changes. The page gives a seven-day window for spam-trap hits, but it does not publish one universal freshness window for every component. Record what the interface displays instead of inventing a common period.

Separate shared IPs from dedicated IPs

On a dedicated IP, your sending program has direct influence over that IP's history, although a provider may still control configuration and remediation. On a shared IP, other customers affect the same reputation object.

Validity's sender reputation explanation makes the distinction explicit: shared-IP behavior can affect other senders, while a dedicated IP gives the operator more direct control and requires its own sending history. It also separates IP reputation, which describes where mail originated, from domain reputation, which identifies who sent it.

That produces the first decision branch. If the scored IP is shared, ask the provider what portion of the signals can be attributed to your traffic. If it is dedicated but provider-managed, ask who can change reverse DNS, rate limits, and pool assignment. If you own the IP and configuration, continue to the component evidence.

Read components, not just the headline number

A movement in the headline score is a prompt to inspect the contributing evidence. It is not a diagnosis by itself.

Match each displayed signal to a controllable layer. Unknown users point toward list validation and suppression. Complaint evidence points toward audience, expectation, and opt-out handling. Infrastructure findings belong with the sending provider or the person managing the IP. Volume movement belongs with campaign operations. A blocklist entry needs the named list, listing time, and remediation route.

Our view: a score without an owner map creates more noise than control. Teams often change message copy because it is visible, even when the measured object is infrastructure they do not operate.

Do not convert it into inbox placement

Mailbox providers combine different signals in different ways. Validity itself says mail can perform differently at Gmail and Outlook because providers use different algorithms and signal combinations. Sender Score therefore cannot prove inbox placement at a named provider.

It also cannot isolate domain reputation, content decisions, recipient engagement, authentication alignment, or the state of one campaign unless the underlying evidence makes that connection. Use provider-specific tools and message-level tests for those questions.

Our sender reputation guide covers the wider recovery decision. Keep this check narrower: confirm whether the IP-level telemetry is relevant and controllable before opening that playbook.

Build a one-page evidence card

For each lookup, save the public IP, lookup timestamp, shared or dedicated status, sending provider, domains using the IP, score, visible component signals, recent infrastructure changes, and named owner. Add links or screenshots that can be compared at the next review.

Then choose one action. Continue monitoring when the object is verified and no material component changed. Escalate to the provider when the IP is shared or provider-controlled. Pause the affected sending stream when evidence points to a controllable and active fault. Investigate another layer when campaign symptoms do not map to the scored IP.

The card prevents a team from changing campaign inputs when the measured fault belongs to infrastructure controlled by somebody else.

Identify the measured infrastructure before changing the campaign

We can trace the scored IP back to your domains, providers, and campaign owners during an ICP and campaign-fit discovery call. Book your free discovery call →