Sender reputation is the trust score that mailbox providers like Gmail, Yahoo, and Microsoft assign to the domains and IP addresses you send email from. That score, rebuilt continuously from your recent sending behavior, is the biggest single factor in whether a message reaches the inbox, drops into the spam folder, or gets rejected at the connection. No provider shows you a public number, but they track it precisely, and you can measure every signal that feeds it.
Reads public DNS only. Nothing is stored unless you save the domain to an account.
Reputation is not a fixed grade. It is a rolling assessment of how recipients react to your mail, how clean your list is, whether your messages are authenticated, and whether your sending pattern looks like a legitimate business or a spammer. Fix the inputs and the score follows, usually within days to a few weeks.
Domain reputation vs IP reputation
Providers score two related but distinct things: the reputation of your sending domain and the reputation of the IP address that delivered the message. They are not interchangeable, and a problem in one can sink delivery even when the other is healthy.
- IP reputation is tied to the specific server address that opens the SMTP connection, and it reflects the sending history of that IP. On shared infrastructure you inherit the behavior of every other sender on the same address. On a dedicated IP the history is entirely yours.
- Domain reputation follows the domains in your message, primarily the
From:domain and the DKIM signing domain (thed=value). Because it travels with the domain rather than the IP, it is portable. If you switch email providers or rotate IPs, your domain reputation moves with you, which is why it has become the dominant signal at Gmail.
The two connect through authentication. DMARC alignment ties a passing DKIM or SPF result back to your From: domain, so the reputation you build accrues to your brand rather than to a shared IP pool you do not control. Microsoft, by contrast, still leans heavily on IP reputation at connection time, so a shared IP with one bad neighbor can trip filtering at Outlook even when your domain is spotless. For a fuller breakdown of when each one matters, see our guide on domain reputation vs IP reputation.
What mailbox providers actually score
No provider publishes an exact formula, but the inputs are well understood and consistent across Gmail, Yahoo, and Microsoft. These are the signals that move your reputation.
| Signal | What it measures | Target |
|---|---|---|
| Complaint rate | Share of delivered mail recipients mark as spam | Under 0.3%, ideally under 0.1% |
| Bounce rate | Invalid addresses that reject on delivery | As low as possible |
| Spam-trap hits | Mail sent to addresses that exist only to catch bad senders | Zero |
| Engagement | Opens, replies, and time in inbox versus deletes | High and consistent |
| Volume consistency | Whether daily volume is steady or spikes | Smooth, predictable ramp |
| Authentication | Valid SPF, DKIM, and DMARC with alignment | Pass on every message |
Complaint rate is the most punishing input. Google's bulk-sender rules ask senders to keep the spam complaint rate reported in Postmaster Tools below 0.1% and never let it reach 0.3%. Cross that ceiling and delivery to Gmail can degrade for weeks, even for mail your subscribers asked for.
Bounce rate signals list quality. A high share of hard bounces (permanent failures such as 550 5.1.1 for an unknown recipient) tells providers you are mailing addresses you never validated, which correlates strongly with purchased or scraped lists. Validate addresses at collection with a syntax and MX check, and suppress any address that returns a 5.x.x permanent failure so you never mail it twice.
Spam-trap hits are among the most damaging events. A trap is an address that generates no legitimate mail and exists only to identify senders with poor hygiene. Pristine traps (addresses never used by a real person) point to scraped or purchased data. Recycled traps (once-real addresses now repurposed) point to a stale list. Either way, hitting one is treated as strong evidence of abuse. Our guide on what a spam trap is covers how they work and how to avoid them.
Engagement is increasingly the deciding factor. Providers watch whether recipients open, reply, and keep your messages, or delete them unread. Positive engagement lifts reputation faster than almost any other lever, and a list full of dormant contacts drags it down even when nobody files a complaint.
Volume consistency matters because spammers send in bursts. A new domain or IP that suddenly pushes tens of thousands of messages looks exactly like an abuser, which is why a gradual ramp is essential when you start sending.
Authentication is now a hard requirement, not a bonus. Since February 2024, Google and Yahoo require bulk senders (5,000 or more messages per day to their users) to publish SPF and DKIM, publish a DMARC record set to at least p=none, pass DMARC alignment on the From: domain, offer one-click unsubscribe per RFC 8058, and send from an IP with valid forward-confirmed reverse DNS (a PTR record that resolves back to the sending IP). If these mechanisms are new to you, start with SPF, DKIM, and DMARC explained.
How to check your sender reputation
You cannot read the raw score, but two free tools expose the underlying data directly from the two largest mailbox providers.
Google Postmaster Tools
Postmaster Tools reports on mail sent to Gmail and Google Workspace users. For years it published a four-tier domain and IP reputation rating (High, Medium, Low, and Bad), but Google retired those reputation dashboards when it moved everyone to the v2 interface in late 2025. The current version surfaces the same underlying signals through two dashboards:
- Compliance Status shows whether you meet the bulk-sender requirements: SPF, DKIM, and DMARC results, alignment, TLS, and the one-click unsubscribe and PTR checks.
- Spam Rate shows the percentage of your delivered Gmail messages that users marked as spam, which is the single number Google tells you to keep under 0.1%.
You still verify ownership with a DNS TXT record, and Gmail continues to use reputation internally even though it no longer draws the old rating. Reputation feedback also shows up in SMTP responses when mail is throttled or rejected. Full setup steps are in our Google Postmaster Tools guide.
Microsoft SNDS
Smart Network Data Services covers Outlook, Hotmail, and Live addresses. Unlike Postmaster Tools, SNDS reports by IP address, so it is most useful when you control a dedicated IP or a fixed range. It shows message volume, complaint rate, and, critically, spam-trap hit counts for each IP. See our guide on what Microsoft SNDS is for how to request access and read the tables.
Between the two tools you cover most consumer mailboxes. Complement them by checking whether your IP or domain appears on major Spamhaus lists: the SBL and CSS for spam-source IPs, the XBL for compromised or exploited hosts, the PBL for end-user ranges that should not send directly, and the domain-focused DBL. A listing on any of them can block delivery outright, so treat blocklist monitoring as part of the same routine.
A practical plan to improve sender reputation
Reputation recovers in the order you fix the inputs. Work through these steps.
- Lock down authentication first. Publish an SPF record that stays within the 10 DNS-lookup limit to avoid a
PermError(which makes receivers ignore SPF entirely), sign with a 2048-bit DKIM key, and publish DMARC. Start atp=noneto observe, then move top=quarantineandp=rejectonce alignment is clean. - Clean your list. Remove hard bounces immediately, verify new addresses at signup, and suppress contacts who have not engaged in several months. This is the fastest way to cut complaint rates and eliminate trap hits.
- Send to people who asked for it. Use confirmed opt-in, honor unsubscribes the same day, and add a working
List-Unsubscribeheader with one-click support. Making it easy to leave lowers complaints far more than it costs you in subscribers. - Warm up gradually. New domains and IPs have no history, so ramp volume over weeks, starting with your most engaged recipients. Our email domain warmup guide lays out a schedule.
- Keep volume steady. Smooth your sends instead of blasting an entire list at once. Predictable patterns read as legitimate.
- Monitor continuously. Watch the Postmaster Tools and SNDS dashboards weekly, read your DMARC aggregate reports, and treat any spike in complaints as an incident to investigate before it compounds.
Reputation is earned slowly and lost quickly. The senders who stay in the inbox treat these signals as an ongoing operational metric, not a one-time setup task.
Frequently asked questions
How long does it take to fix a bad sender reputation?
Minor damage from a single bad campaign usually recovers in one to two weeks once you stop the behavior that caused it. Serious damage from spam-trap hits or a blocklisting can take a month or more of consistent, well-authenticated sending to engaged recipients.
Does a dedicated IP guarantee a good reputation?
No. A dedicated IP gives you full control over IP reputation, but it starts with no history and has to be warmed up, and your domain reputation still depends on complaints, engagement, and authentication. At low volume, a shared IP in a well-run pool often delivers better.
Is domain reputation or IP reputation more important?
Both matter, but domain reputation has become the dominant signal at Gmail because it follows your brand across providers and IP changes. IP reputation still gates delivery at connection time, especially at Microsoft, so you cannot ignore either.
Can I see my exact reputation score?
No provider publishes a numeric score. Google Postmaster Tools now gives you a Compliance Status view and a Spam Rate percentage, and Microsoft SNDS gives per-IP complaint and trap data. Together these are the closest you get to the raw inputs.
Sender reputation starts with authentication that passes on every message. Run a free SPF, DKIM, and DMARC scan of your domain to confirm your records are valid and aligned, then fix anything the report flags before your next campaign.