Topic · Deliverability
Shared IP
A shared sending IP carries mail for multiple customers of a service provider.
How it works
The provider manages pooled sending volume and reputation controls. Tenant traffic may share a sender IP while maintaining separate domains.
What can go wrong
One tenant's behavior may influence the perceived reputation of shared infrastructure.
What to check or do
Select reputable providers and monitor domain-level reputation independently.
How to investigate Shared IP
- Signal to investigate
- One customer sees filtering variation on a multi-tenant email provider.
- Evidence to collect
- Check the actual outbound IP pool in received headers, provider incident status and domain-specific complaint metrics.
- Common wrong conclusion
- Poor results on a shared IP do not prove another tenant is the only cause.
How to interpret the evidence
Shared pools mix signals from different customers, while receivers also evaluate domains, messages and recipient behavior. A good provider actively manages abuse and IP reputation.
What to change and how to verify it
Monitor authenticated domain reputation independently and ask the ESP about pool policies and segregation options.
Put this into practice
Run a focused check, then explore protection if your domain needs it.