- Dedicated IP, defined
- A dedicated IP is a sending address used by one sender only, so its reputation reflects that sender's behavior alone, for better or worse.
A dedicated address earns its cost above roughly 50,000 messages a month sent consistently. Below that, receivers see too little traffic to form a stable picture and treat the address with permanent mild suspicion.
Warming is mandatory and takes four to eight weeks. Start small, raise volume gradually, and send to your most engaged people throughout so the signals being recorded are positive ones.
Consistency is the ongoing cost. A dedicated address that sends heavily in March and nothing in April looks like a dormant sender waking up, and receivers treat that pattern cautiously.
The upside is isolation and control. Nobody else's campaign can move your numbers, and a reputation problem is always yours to diagnose and fix.
How ZapBounce reports it
Whether you send from a dedicated address does not change what a verification result says, since we are probing the recipient's server rather than evaluating yours. Clean data matters more here than on shared infrastructure, because a bounce spike during warming has nowhere to hide.
Doing the volume math per provider
A monthly total hides how thin your traffic is once it's split up. Say you send 20,000 messages a month in four weekly campaigns of 5,000. If 45% of your list is on Gmail, that's 2,250 messages to Gmail once a week, and nothing at all on the other six days. Outlook might see 1,100 a week, Yahoo 400.
From each provider's side, your IP shows up briefly, goes silent for a week, and shows up again. There's never enough steady traffic for a reputation to form, so you're treated as a stranger every Tuesday.
Compare a sender doing 600,000 a month in daily sends. Gmail sees about 9,000 messages from that IP every day. That's a continuous signal, and a good one if the list is clean. The monthly cost of the dedicated address is the same in both cases. Only the second sender is getting anything for it.
The jobs that arrive with the address
On a shared pool your platform handles the plumbing. With your own IP, some of it becomes yours, or at least yours to confirm.
Reverse DNS comes first. The IP needs a PTR record pointing to a hostname, and that hostname needs an A record pointing back to the same IP. Receivers check that the two match, and Gmail's sender guidelines require it.
Monitoring is next. You can now register the address with Microsoft's SNDS and its complaint feedback program, which you couldn't do on shared infrastructure, and you should. Add a blocklist monitor, because a listing is now your problem to notice and your delisting request to file.
Think about asking for two addresses instead of one. Keeping receipts and password resets on a separate IP from marketing means a bad campaign can't slow down the mail your product depends on. That only makes sense if each stream has enough volume of its own to stay warm.
Dedicated IP: common questions
When is a dedicated IP worth it?
Above about 50,000 messages a month sent on a regular schedule. Below that, a shared pool usually delivers better.
How long does warming a new IP take?
Four to eight weeks of gradually rising volume to engaged recipients. Rushing it undoes the exercise.
Does a dedicated IP guarantee better delivery?
No. It gives you sole ownership of the outcome, which helps only if your sending practice is good.