Shared IP pool
A shared pool is a set of sending addresses used by many senders at once. Its reputation is collective, and keeping it in good standing is the operator's job. For most volumes that is the right default: the pool is already warm, while a small sender on an address of its own would never send enough for receiving servers to form a view.
At a glance
- Category
- Infrastructure
- Reputation
- Collective, and managed by the operator
- Warm-up
- None needed — the pool is already sending
- Suits
- Low, irregular or growing volume
- Depends on
- The operator policing who is allowed to send through it
How it works
Mail from many customers leaves over the same set of addresses, so receiving servers see a continuous stream of traffic from each one and keep a view of the pool rather than of any single sender. The operator is responsible for who gets in: verification before sending, limits on new accounts, monitoring of bounce and complaint rates, and removing senders whose behaviour would cost everybody else. Pools are usually segmented so that different classes of traffic do not mix.
Why it matters
For most senders a shared pool is strictly better than a dedicated address, because reputation needs volume and a small sender does not have any. The pool provides the volume, and what you contribute is your share of the bounces and complaints. The trade is that you depend on the operator's discipline: a pool that lets anybody send is a pool whose reputation is somebody else's problem to create and your problem to live with.
Example
A company sending forty thousand receipts a month sends over a shared pool. Their mail is authenticated on their own domain, so the reputation that matters most to receiving providers is their domain's rather than the pool's, and it is theirs alone. They never warm anything, never watch a ramp, and when their volume triples over a year nothing about the sending path has to change.
Common mistakes
- 01Choosing a dedicated address too early because it sounds more professional, and then sending too little to build any reputation on it.
- 02Assuming the pool's reputation is the only thing that matters, when your own domain's reputation is what receiving providers weigh most.
- 03Blaming the pool for placement problems that come from your own list, which the pool did not create and cannot fix.
- 04Moving between providers repeatedly in search of a better pool, which resets your domain's history at every provider each time.
In Rasket
Every plan sends from managed shared pools, and a dedicated IP is an add-on for senders large enough to need one. Pricing
Related terms
Frequently asked questions
Is a shared pool worse than a dedicated address?
Not for most senders. A warm pool with a careful operator usually outperforms a cold dedicated address, because reputation is built from volume and a small sender cannot supply enough of it.
Can another sender's behaviour hurt my mail?
In principle yes, which is why the operator's admission and monitoring policy matters. In practice your own domain's authentication and reputation carry most of the weight at large providers.
When should I move off a shared pool?
When your volume is high enough and steady enough that receiving servers would see traffic from your own address most days. Below that, moving isolates you without giving you anything to be judged on.
Last updated 16 September 2026.
Start sending this morning
Verify a domain and send your first email in minutes.