Domain reputation vs IP reputation
Mailbox providers evaluate both the domain you send from and the IP address you send from — independently. Understanding which layer is causing a deliverability problem is the first step to fixing it correctly.
Domain reputation vs IP reputation: the short version
Domain reputation is tied to the sending domain — the domain in the From header and in the DKIM signature. It is built from the history of all mail sent under that identity: complaint rates, engagement, authentication consistency, and sending patterns.
IP reputation is tied to the specific IP address used to deliver mail. It reflects the behaviour of every sender that has used that IP — not just the current one.
The two can diverge. A domain with a strong sending history can be delivered from an IP with a poor reputation and still face filtering. Conversely, a clean IP cannot compensate for a domain that has accumulated complaints or is on a blocklist.
What domain reputation measures
Domain reputation is a long-term trust score assigned by mailbox providers to the sending domain.
Providers track spam complaint rates, engagement levels (opens, clicks, deletes without reading), bounce patterns, DMARC compliance, and the consistency of authentication across all mail sent from the domain.
Domain reputation accumulates over months and years. It is harder to damage overnight than IP reputation, but it is also harder to rebuild once it has been seriously degraded.
Google Postmaster Tools exposes domain reputation data specifically for Gmail, making it a useful monitoring tool for senders concerned about domain-level deliverability.
What IP reputation measures
IP reputation tracks the sending behaviour associated with a specific IP address — complaint rates, spam trap hits, volume patterns, bounce patterns, and blacklist listings.
Unlike domain reputation, IP reputation is not tied to a brand or identity. It reflects the physical infrastructure used to send mail. A new IP starts with no reputation. A shared IP carries the combined history of every sender who has used it.
IP reputation can shift more quickly than domain reputation in both directions — a clean IP can pick up a blacklist listing within days of a spam campaign, and can also recover faster once the root cause is fixed.
Why changing IPs does not reset domain reputation
Domain reputation follows the domain, not the infrastructure. When a sender moves to a new IP or a new ESP, their domain's historical complaint rate, engagement signals, and authentication record move with them.
A common mistake is to assume that moving to a new sending IP or a higher-reputation shared IP pool will solve inbox placement problems caused by the sending domain's history.
If the domain has accumulated spam complaints or has a pattern of authentication failures, those signals persist at major providers regardless of which IP delivers the mail.
Why changing domains does not fix a bad IP
IP reputation is independent of the domain identity. A clean sending domain delivered from a blocklisted or poorly configured IP still faces the IP-level filtering applied to that address.
Moving to a new domain while continuing to send from the same IP leaves the IP-level problem unsolved. Receiving servers see the incoming connection from the same IP before they evaluate the domain in the message.
Fixing an IP reputation problem requires addressing the root cause — removing the IP from blocklists, correcting DNS configuration, and building positive sending history — not simply switching domains.
Shared IP vs dedicated IP considerations
On a shared IP, the reputation of the IP reflects the behaviour of all senders using it. Poor practices by one sender — high complaint rates, spam trap hits, sudden volume spikes — can affect inbox placement for every domain on that IP, even those with clean sending history.
A dedicated IP gives a sender full control over IP reputation, but also full responsibility. A new dedicated IP starts with no sending history. Without a gradual warm-up period — starting with low daily volumes to the most engaged recipients and increasing slowly — providers will treat it as an unknown and apply cautious filtering.
For low-volume senders, a reputable shared IP pool managed by a trusted ESP is often more reliable than a cold dedicated IP.
How authentication connects domain and IP reputation
Authentication records — SPF, DKIM, and DMARC — are the mechanism that allows mailbox providers to reliably link incoming mail to a specific domain identity.
Without authentication, providers cannot confidently assign sending history to the correct domain. SPF authorises the sending IP for the domain, DKIM binds the message to the signing domain, and DMARC ensures alignment between the visible domain and the authentication identities.
When authentication is consistent and correct, positive signals from an IP can contribute to domain trust, and a well-established domain can help offset temporary uncertainty about a new or changed IP.
A domain that frequently fails authentication cannot build stable domain reputation, and providers may be less confident in attributing sending history to it at all.
How to diagnose which reputation layer is the problem
Start with blacklist checks. If your sending IP appears on a major DNSBL, the problem is at the IP layer. Use the MXFend Blacklist Checker to test your sending IP against Spamhaus ZEN, Barracuda, and others.
Check SMTP TLS and reverse DNS. Missing PTR records, HELO/EHLO mismatches, and TLS certificate problems are all IP-level signals. Use the MXFend SMTP TLS Checker to verify transport security.
Check authentication records. If SPF, DKIM, or DMARC are missing or misconfigured, the domain layer cannot build consistent trust. Use the MXFend SPF, DKIM, and DMARC Checkers to audit each record.
Monitor domain reputation directly. Google Postmaster Tools shows Gmail's view of your domain reputation and complaint rates. If domain reputation is low despite clean authentication, the problem is likely in sending practices or engagement rather than technical configuration.
Run a full Email Security Score. The MXFend Email Security Score audits all of the above in a single report, covering both IP-level and domain-level signals.
How MXFend can help
MXFend provides dedicated tools for diagnosing both IP-level and domain-level reputation signals:
Blacklist Checker — tests your sending IP against major DNSBLs. A blacklist listing is a clear IP-level problem.
SMTP TLS Checker — verifies STARTTLS support, TLS certificate validity, and transport security configuration at the IP level.
SPF Checker — validates SPF record syntax and confirms which IPs are authorised to send for your domain.
DKIM Checker — verifies DKIM selector records and key configuration.
DMARC Checker — checks DMARC policy, alignment mode, and reporting.
Email Security Score — combines all checks into a single weighted report covering both IP and domain reputation signals.
Frequently asked questions
Is domain reputation the same as IP reputation?
No. Domain reputation is assigned to the sending domain based on its history of complaint rates, engagement, and authentication. IP reputation is assigned to the sending IP address based on the behaviour of every sender that has used it. Both are evaluated independently by mailbox providers.
Which matters more, domain reputation or IP reputation?
Both matter, and they affect deliverability independently. Modern mailbox providers — especially Gmail — weight domain reputation heavily for established senders. IP reputation tends to matter more for new senders or those on shared infrastructure. A deliverability problem can originate at either layer or both.
Does changing my sending IP fix deliverability problems?
Only if the problem is at the IP layer — for example, a blacklist listing or a misconfigured server. If the problem is domain reputation, moving to a new IP does not help because domain reputation follows the domain, not the infrastructure.
Can a shared IP hurt my domain reputation?
A shared IP does not directly affect your domain reputation, but IP-level filtering problems on a shared IP can prevent your mail from reaching the inbox regardless of how strong your domain reputation is. If the shared IP is on a blocklist or has high complaint rates, your mail may be filtered before domain signals are even evaluated.
How do I know if my problem is domain reputation or IP reputation?
Check your sending IP against major DNS blacklists using the MXFend Blacklist Checker. If the IP is listed, that is an IP-level problem. If the IP is clean, check authentication records with the SPF, DKIM, and DMARC Checkers, and monitor domain reputation in Google Postmaster Tools. Running the MXFend Email Security Score audits both layers in a single report.