Definition of Dedicated IP
A dedicated IP is a unique Internet Protocol address used exclusively by one sender for email distribution.
Unlike shared IPs where multiple senders use the same address ranges, a dedicated IP gives you complete control over your sending reputation.
Why you should care
A dedicated IP helps newsletter creators who send high volumes take ownership of their deliverability. By maintaining consistent sending patterns and content quality on your own IP, you build a reputation that major inbox providers recognize and trust over time.
The big challenge is that dedicated IPs require more volume to maintain a healthy sending reputation. Most ESPs use shared IP ranges by default because they're more forgiving for smaller senders or inconsistent schedules.
If you send fewer than 50,000-100,000 emails monthly, you're probably fine with the shared ranges of the big ESPs.
Some resources we rely on
Ask Claude for help with Dedicated IP
Copy and paste this prompt into Claude or the AI of your choice. Be sure to tweak the context for your situation.
<goal>
Help me evaluate, request, and properly implement a dedicated IP address for my newsletter to maximize deliverability.
</goal>
<context>
* I run a [FREQUENCY] newsletter with approximately [# of SUBS] subscribers
* Currently using [PLATFORM] as my ESP on shared IPs
* Sending volume is [# of EMAILS] per month
* Considering upgrading to a dedicated IP
* Need to understand cost/benefit and proper implementation
</context>
<output>
Please provide:
* A decision framework to determine if a dedicated IP is right for my sending volume
* Step-by-step request template for obtaining a dedicated IP from my ESP
* Proper IP warming protocol specific to my sending volume
* Monitoring framework to track reputation improvements
* Risk analysis and contingency planning for dedicated IP management
</output>
<example>
Dedicated IP request template:
"Hello [ESP] Support Team,
I'd like to upgrade my account to include a dedicated IP address for my newsletter sending. Here's relevant information about my sending practices:
1. Current subscriber count: [NUMBER]
2. Monthly email volume: [NUMBER]
3. Sending pattern: [CONSISTENT/VARIABLE] sends on [DAYS]
4. Content type: [NEWSLETTER TYPE]
5. Current deliverability metrics: [BRIEF SUMMARY]
I understand proper IP warming is critical. I plan to implement a [X]-week warming schedule starting with [Y%] of volume and increasing by [Z%] weekly.
Please advise on:
- Setup timeline
- Additional costs
- Technical requirements
- Best practices specific to your platform
Thank you,
[YOUR NAME]"
</example>
<guardrails>
* Focus on senders with appropriate volume (50K+ emails monthly)
* Include warnings about the risks of dedicated IPs for low-volume senders
* Provide realistic expectations for deliverability improvements
* Emphasize the importance of proper IP warming
* Include contingency plans for delivery issues during transition
</guardrails>