Skip to content
  • There are no suggestions because the search field is empty.

IP and domain reputation

Inbox placement depends on how receivers rate the IPs and domains your mail comes from, not only on whether it authenticates. Each big provider says so. Yahoo lists "IP address reputation, URL reputation, Domain reputation, Sender reputation, ASN (Autonomous System Number) reputation," plus DKIM and DMARC results, as inputs. Microsoft's SNDS page opens with "Deliverability to Outlook.com is based on your reputation". Google warns that "over time, user spam reports can lower your domain's reputation".

Nobody publishes the formula or a score you can look up. What providers do publish is what moves it: complaints, list quality, sending patterns, and infrastructure. Authentication's job is narrower. It gives the receiver a verified domain to hang that history on. This article covers how the IP and domain halves work and what the provider tools can still show you.

IP reputation

Email IP reputation attaches to the addresses that connect to the receiver's servers.

On a shared IP, such as an ESP's pooled sending address, you share it with everyone else on that address. Google: "The activity of any senders using a shared IP address affects the reputation of all senders for that shared IP address. A negative reputation can impact your delivery rate." It also says messages from blocklisted IPs "are more likely to be marked as spam," which is a weighting, not an automatic block.

Yahoo adds infrastructure signals. It's "more likely to downgrade an IP's sending reputation if there isn't a reverse DNS entry," because the IP then looks dynamically assigned rather than like a mail server.

Gmail also applies quotas per IP: "The IP address quota is shared for all senders that use that IP address." When it's hit, every domain on that IP gets rate limited.

Domain reputation

Email domain reputation attaches to the domains a receiver can verify on your mail: the DKIM signing domain (d=), the SPF (Return-Path) domain, and the From domain. Each IP and DKIM domain has a reputation. Google's Postmaster Tools registers you by either the DKIM (d=) domain or the SPF (Return-Path) domain.

The useful property: domain reputation can follow you across IPs. Following its authentication recommendations should provide senders with a consistent reputation for their domain, regardless of which IP mail is sent from. Our reading of that, which no provider states in these words: if your ESP signs with its domain, the history it builds belongs to the ESP. If it signs with yours, aligned with your From address, the history is yours and comes with you when you change ESPs. That's one more reason to ask every vendor for aligned DKIM on your own domain (Identifier alignment for SPF and DKIM, How to add a third-party sender without breaking DMARC, SPF include vs DKIM from the vendor).

Google also lists ways to damage your own domain's reputation from the inside: internal users marking company mail as spam, and sending test phishing campaigns from your real domain, which "could be added to internet blocklists."

How authentication connects to reputation

Authentication doesn't create a good reputation. Behavior does. What authentication does is let a receiver tell your mail apart from forgeries of it. Without aligned SPF or DKIM, a receiver can't reliably attribute a message to you, so your good history doesn't protect your real mail, and a spoofer's mail can be confused with yours.

DMARC enforcement goes one step further: it asks receivers to treat unauthenticated use of your From domain as suspect (When you are ready for p=quarantine, When you are ready for p=reject). No provider says enforcement raises your reputation. Treat it as separating your mail from the forgeries, not as a score boost.

What you can actually see

Gmail Postmaster Tools. Dashboards for spam rate, authentication, delivery errors, and compliance status. The reputation view is going away: in the new version (v2), the Domain and IP Reputation dashboards are the exception and will be retired. Reputation data is not easily actionable, changes are slow to reflect, and the old dashboard can be misleading because reputation is only one of many factors affecting deliverability. As of 15 Nov 2026, Google has postponed retiring the old interface (v1), so some accounts may still see the old charts. Data also needs volume: if too few messages are sent on a day, dashboards stay empty to protect users' privacy.

Microsoft SNDS. Per-IP data for IPs you register and control, plus the Junk Email Reporting Program, which sends you reports when Outlook.com users junk your mail. It's IP-level. It doesn't rate your domain. Microsoft's line: "Reputation is always the responsibility of the sender."

Yahoo. The Complaint Feedback Loop sends you a copy of each spam complaint for enrolled DKIM domains. Yahoo also takes Sender Support Requests and says it may "modify your reputation in our systems if needed," adding "that still doesn't guarantee inbox delivery."

Your DMARC aggregate reports. These show which sources send as your domain, at what volume, and with what authentication results. They don't show reputation or placement (A field-by-field walk-through of a DMARC aggregate report). BIMI Certifications' DMARC reporting and visual analysis shows that per source. It isn't a reputation score.

Ramping up volume (ip warming)

"IP warming" is the industry's name for building volume gradually on a new IP or domain. Google doesn't use the term, but its sender guidelines describe the practice:

  • "Start with a low sending volume to engaged users, and slowly increase the volume over time."
  • "Send email at a consistent rate. Avoid sending email in bursts."
  • "Immediately doubling previously sent volumes suddenly could result in rate limiting or reputation drops."
  • If you change the format of your bulk mail, or make significant infrastructure or header changes, ramp the changed traffic separately.
  • If bounces or deferrals start, reduce volume until the error rate drops, then increase slowly again.

Yahoo puts the same idea in fewer words: a sudden spike can get you flagged as a compromised sender. Neither provider publishes a day-by-day schedule, so treat any fixed warm-up calendar as a vendor's practice, not a provider rule.

Practices that protect both halves

Straight from Google's and Yahoo's guidance:

  • Send only to people who asked for the mail. Yahoo recommends confirmed opt-in.
  • Don't buy lists, and don't pre-tick opt-in boxes.
  • Remove invalid and unengaged recipients, and opt out people who've complained.
  • Keep message types apart: separate IPs or streams for marketing and transactional mail, and the same From address for each category.
  • Publish valid, non-generic reverse DNS for every sending IP.
  • Keep the spam rate under Google's 0.1% target (Google and Yahoo sender requirements).

Common mistakes

  • Changing ESPs without aligned DKIM on your own domain. The domain history you built may have belonged to the old vendor's signing domain.
  • Mixing transactional and marketing mail on one stream. Complaints about promotions follow your receipts.
  • Waiting for a reputation number. Google is retiring its reputation dashboards and calls the old one potentially "misleading." Watch spam rate, bounces, and deferrals instead.
  • Letting staff report internal mail as spam. It can hurt your domain's reputation.
  • Reading blocklist status as the whole story. It raises the odds of spam placement at Gmail; it isn't the only factor.

If authentication passes and placement is still poor, the troubleshooting path starts at Why are my emails going to spam and Authentication vs inbox placement.

Free DMARC account

Not sure which sender is failing?

Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.

  • Every sending source in one dashboard
  • SPF, DKIM and alignment results per sender
  • No XML files to read

Create a free DMARC accountTalk to an expert

FAQ

Where did the reputation chart in Postmaster Tools go?

The Domain and IP Reputation dashboards aren't in Postmaster Tools v2 and will be retired. Gmail is pointing senders to compliance status, spam rate, and delivery-error data instead.

Does a shared IP hurt us?

It can. Every sender on a shared IP affects its reputation. Your domain reputation still follows your authenticated domain, which is why aligned DKIM on your own domain matters.

Is a dedicated IP email setup better than DMARC?

They solve different problems. A dedicated IP means only your sending shapes that IP's reputation, good or bad. DMARC tells receivers how to treat mail that fails authentication for your domain. Neither replaces the other.