Domain reputation and IP reputation are separate deliverability signals. Domain reputation tracks sending identity over time (From domain, alignment, complaints, engagement). IP reputation tracks connecting infrastructure (sending patterns, blocklists, PTR hygiene, shared-pool neighbors). Changing ESPs or IPs does not erase domain history; a new IP starts cold while domain behavior continues to matter. In 2026, monitor observable signals—Compliance status, spam rate, authentication, feedback loops—rather than retired reputation badges.
Domain reputation vs IP reputation at a glance
| Aspect | Domain reputation | IP reputation |
|---|---|---|
| Primary identity | From / organizational domain (and intentional subdomains) | Sending IP address or pool |
| Common inputs | Aligned authentication, complaint history, engagement patterns, consistency of sending identity | Volume patterns, abuse/complaint history on the IP, blocklist status, PTR/reverse-DNS hygiene, neighbor behavior on shared pools |
| What follows when you change ESP | Domain-level history can travel with the same From/DKIM domain | New IP or pool starts with little or no history |
| What starts cold on a new dedicated IP | Domain signals remain | IP history is rebuilt from controlled traffic |
| Where to observe signals today | Postmaster Tools spam rate & Compliance, Yahoo domain-based CFL/insights, DMARC reports, engagement metrics | Microsoft SNDS, blocklist checks, PTR validation, provider IP reviews (where available) |
Authentication is necessary but not a positive reputation grade. Messages can pass SPF, DKIM, and DMARC and still be filtered on content, complaint, or engagement signals.
What still matters after the old Postmaster badges
Google Postmaster Tools v2 no longer includes the standalone Domain Reputation and IP Reputation dashboards that once showed High/Medium/Low labels. Current operator-facing data centers on Compliance status (including any Deliverability analysis wording on that page), spam rate, authentication results, encryption, feedback-loop data, and delivery errors.
Gmail’s public sender guidelines may still mention domain and IP reputation. Treat that as residual wording, not an instruction to hunt for retired v2 panels. The actionable thresholds remain: keep user-reported spam below 0.10%; rates at or above 0.30% remove access to support and mitigation.
Yahoo’s Complaint Feedback Loop is domain-based and requires DKIM signing. Yahoo Sender Hub Insights typically surface delivered volume and spam complaint rate for verified DKIM domains; separate Placement and Campaign Performance feeds exist for eligible senders under documented access requirements. Microsoft SNDS continues to provide useful IP-centric telemetry.
What follows you — and what starts over
- Change ESP, keep the same aligned From/DKIM domain: Domain-level complaint history, engagement patterns, and identity consistency can follow. The new infrastructure starts relatively clean at the IP layer.
- Move to a new dedicated IP: The IP begins with little history and needs controlled, consistent traffic to build a record. Domain behavior continues to influence filtering.
- Separate marketing and transactional on subdomains: You can isolate volume and complaint patterns. Parent-domain effects are not automatically eliminated; intentional subdomain authentication and monitoring remain important. See why marketing and transactional email should use separate subdomains.
A clean dedicated IP cannot repair a domain that already generates high user-reported spam. For the purchase decision itself, see Don’t Buy a Dedicated IP Until the Domain Is Clean.
Observable signals by provider (2026)
- Google Postmaster Tools: Compliance status, spam rate, authentication, encryption, feedback loop, delivery errors. Prioritize these over any residual “reputation” language in guidelines.
- Yahoo: Domain-based Complaint Feedback Loop (DKIM required); Sender Hub volume and complaint insights; controlled-access Placement/Campaign feeds where eligible.
- Microsoft: SNDS for IP-centric views; continue to watch complaint and blocklist data.
- Cross-provider: Blocklist status, DMARC aggregate reports, bounce and complaint rates from your own ESP events, and engagement metrics you control.
How we analyzed this
The conceptual split between domain and IP layers follows long-standing filtering practice and is confirmed by how history travels (or does not) when operators change providers or infrastructure. Monitoring recommendations are grounded in the current Postmaster Tools v2 surface, public Gmail/Yahoo sender requirements, Yahoo’s domain-centric CFL model, and the continued availability of IP-oriented tools such as SNDS. No complete scoring formulas are published by mailbox providers; claims stay limited to observable first-party and provider-exposed signals. ArawaMail documentation describes platform-managed outbound sending via Cloudflare (outbound identity, DKIM, custom MAIL FROM) and does not expose domain or IP reputation scores, Postmaster integration, or placement dashboards in the Retrieve Email API.
Practical monitoring checklist
- Confirm SPF, DKIM, and DMARC pass and align; review DMARC reports regularly (how to read a DMARC report).
- Track spam rate and Compliance status in Postmaster Tools; keep user-reported spam well below 0.10%.
- Monitor domain-based complaint feedback where available (Yahoo CFL) and IP-centric views (SNDS, blocklists).
- Separate high-risk or high-volume streams onto intentional subdomains when patterns diverge.
- Treat third-party “reputation scores” as secondary; prioritize the first-party and provider signals above.
Related reading: Your domain is the product, Reverse DNS and PTR records, Two vendors, one From address, Don’t let an AI agent burn your domain, Gmail and Yahoo bulk-sender requirements, and Email list hygiene in 2026.
FAQ
If I change ESP but keep the same From domain, what history follows me?
Domain-level complaint history, engagement patterns, and identity consistency associated with that From/organizational domain can follow. The new ESP’s IP pool starts with its own history (or lack of it).
If I move to a new dedicated IP, what starts cold?
The IP itself starts with little history and needs controlled traffic to build a record. Domain reputation signals continue to apply.
What should I monitor now that Google’s old reputation dashboards are gone?
Compliance status, spam rate, authentication, delivery errors, feedback-loop data, blocklists, and any provider-specific placement or complaint insights you can access.
Does ArawaMail expose a reputation score?
No. Current documentation and the Retrieve Email API surface message fields and last_event (for example “sent”); they do not expose domain-reputation scores, IP-reputation scores, or integrated Postmaster/SNDS dashboards.