Why does Brevo's IP type matter for inbox placement?

You’re sending emails at scale through Brevo. Your campaign looks perfect. Your list is clean. But your inbox placement feels inconsistent. Why does the same email land in the inbox for some users, and in spam for others?

The answer starts with something invisible: the IP address behind your send. Brevo’s shared IP pool means your messages travel alongside others’—a mix of volume, intent, and reputation. If someone else in that pool sends poorly, your delivery can suffer. A dedicated IP gives you full control, but demands care.

This comparison isn’t just theory—it’s about where your emails actually land. For high-volume senders or new brands, choosing the right IP type is a deliverability decision, not just a technical one.

Key takeaways

  • Brevo’s shared IP pool means your sender reputation is linked to other senders’ behavior, which can impact inbox placement.
  • Dedicated IPs offer isolation and control over reputation, but require a warm-up period and ongoing monitoring to maintain deliverability.
  • High-volume senders or new brands see the biggest difference: shared IPs may work short-term, but dedicated IPs are often necessary for consistent inbox placement over time.

How does shared IP deliverability work in Brevo?

In Brevo’s shared IP model, every sender uses the same IP address. Your deliverability depends on how others in the pool behave—if one user sends spammy content or gets marked as spam, it can hurt everyone’s inbox placement. This setup lowers costs but spreads risk across all users, making it less stable for high-volume or inconsistent senders.

Collective Reputation Means Shared Risk

With shared IPs, reputation isn’t individual—it’s pooled. If one sender triggers spam filters or gets reported, the IP’s reputation suffers across the board. This means even well-behaved senders can experience delivery issues, sometimes without knowing why. It's like sharing a single credit score with hundreds of others: one bad actor can pull the whole group down.

Think of it this way: if someone in your apartment building repeatedly leaves trash on the sidewalk, you may eventually get a notice—even if you never did it. That’s how shared IP pools work. The reputation is not yours alone; it’s a collective outcome of all senders using that IP.

Why Shared IPs Work for Some, Not Others

Shared IPs are cost-effective and simple to use, which makes them attractive for new senders or low-volume campaigns. If you send only a few hundred emails per month and maintain consistent, clean practices, you may never see issues. But if you’re sending at scale—thousands of emails weekly—or your list quality fluctuates, the risk grows significantly.

You’re not in control of how others behave. A single aggressive campaign on the same IP can lead to filtering by Gmail, Outlook, or other providers. Major email providers use machine learning to assess sending patterns in real time. If an IP shows spikes in engagement, complaint rates, or bounces, it can trigger filters or temporary blocks. These actions impact every sender using that IP, even those sending responsibly.

For more reliable performance, especially with growing send volumes, dedicated IPs are the standard choice. They allow senders to build independent reputation and avoid downstream risks. You can find real-world examples of this in deliverability guidelines from providers like Spamhaus and RFC 5321, which outline how email infrastructure handles sender accountability and reputation scoring.

Before you send a large list, verify it thoroughly to avoid spikes in bounces and complaints. Our bulk verification tool checks for invalid, disposable, and risky addresses—giving you a clear view of your list’s health. You can also test inbox placement with our inbox tester to see how your emails perform across major providers.

What’s the real cost of Brevo’s shared IP model?

Using Brevo’s shared IP means low upfront cost but high inbox delivery risk: your messages can be throttled or filtered simply because another sender on the same IP sent spam, triggered complaints, or had poor list hygiene. Even with clean lists, your deliverability is only as strong as the weakest sender on the shared infrastructure.

Shared IPs don’t care about your list quality alone

Deliverability on a shared IP depends on collective sender behavior. If one user sends to bought lists or fails to manage bounces, their activity can trigger reputation damage that affects everyone. Recipient domains monitor aggregate engagement and complaint rates across IPs — not individual senders — so a single high-complaint campaign can hurt all users sharing that IP.

This isn't hypothetical. According to Return Path’s industry data, shared IP reputation is often tied to sender diversity and engagement patterns. The more inconsistent the behavior, the higher the chance of a domain-wide throttle or filtering.

How your deliverability gets pulled down by others

Spam complaints or high bounce rates from any sender on the shared IP can lead to temporary or permanent filtering by major providers like Gmail or Outlook. These systems use aggregate reputation signals — not just your personal sending history — to decide if your message is spam. You have no control over what others do, especially if they’re not maintaining list hygiene or managing feedback loops.

Greylisting and throttling can also kick in when sending volumes spike from multiple users simultaneously. Even if you're sending small batches, you’re subject to patterns set by the broader IP pool, which can delay or block delivery during peak times.

Let’s be clear: even with 98% valid emails, your campaign might still land in spam or get delayed if the overall IP is under scrutiny. That’s the trade-off of low cost for high risk.

For a concrete check of what’s really happening with your list, you can test how your messages land in real inboxes — not just spam filters — using our inbox placement test. Or, verify your entire list before sending with our bulk email verification, ensuring every address is active, valid, and safe to send to.

How does Brevo’s dedicated IP deliverability work?

With Brevo’s dedicated IP, you get a single, static IP address assigned exclusively to your domain and sending volume. This means your sender reputation develops independently—no negative impact from other users’ practices. Deliverability depends solely on your sending behavior, list hygiene, and content quality. To succeed, you must warm up the IP gradually, maintain consistent sending patterns, and monitor reputation signals over time.

Separate Reputation, Full Control

Your dedicated IP isn’t shared with anyone else—no shared history, no shared risks. If another user on a shared IP sends spam or gets reported, it doesn’t affect you. This isolation lets your sender reputation grow based only on your actions: engagement rates, bounce rates, and spam complaints.

According to research by Return Path, sender reputation is a primary factor in inbox placement. With a dedicated IP, you build that reputation from the ground up, without external noise. It’s a long-term play, but one that scales predictably with proper discipline.

Active Management Is Required

You can’t just start sending at scale on a dedicated IP. A cold IP will be flagged by mailbox providers. Instead, you need to warm it up—start with small volumes, increase gradually, and ensure high engagement. This process typically takes 2–4 weeks, depending on volume and content type.

Consistency matters: sudden spikes in volume or sudden changes in message content can trigger scrutiny. Tools like MailTester’s inbox placement test help you validate delivery before sending to your full list.

Monitor reputation signals using tools that track blacklist status (like Spamhaus or MXToolbox), bounce rates, and engagement trends. You can’t rely on defaults—you must stay proactive.

Many senders treat dedicated IPs as a “set and forget” solution, but they’re not. Brevo gives you the tools, but you’re responsible for the execution. A well-maintained dedicated IP can deliver consistently, but only if you respect the fundamentals of email governance and sender hygiene.

What determines inbox placement with Brevo’s shared vs dedicated IP?

With Brevo’s shared IP, your inbox placement depends on how the broader sender group behaves—their spam complaints, engagement rates, and overall reputation. With a dedicated IP, your success hinges entirely on your own volume, list quality, subscriber engagement, and strict adherence to email standards. Both require proper authentication (SPF, DKIM, DMARC) and consistent sending practices to maintain good standing with inbox providers.

Shared IP: Reputation Is a Group Effort

On Brevo’s shared IP, you’re one sender among many. That means your deliverability can be impacted by how others in the pool send—especially if they trigger spam filters or generate complaints. A single poorly managed list can pull the entire IP’s reputation down, affecting everyone using it. This is why consistent list hygiene and low complaint rates are critical, even if you're sending only a few campaigns.

Dedicated IP: You Own the Reputation

With a dedicated IP, you're responsible for building and maintaining your own sender reputation. Deliverability depends on your sending volume over time, whether your emails are opened, clicked, and marked as spam. ISPs (like Gmail and Outlook) assess each IP independently, so a slow ramp-up in volume or sudden spikes can hurt placement. The same applies to list quality—if your content isn’t relevant, engagement drops, and inbox placement suffers.

Both models rely on strong technical foundations. Without SPF, DKIM, and DMARC properly configured, even the best content won’t reach inboxes. These protocols authenticate your domain and signal to ISPs that you’re a legitimate sender. Brevo handles some of this by default, but you should verify your setup regularly—use tools like MailTester’s real-time API to catch issues early.

For a deeper check of how your emails land in real inboxes, try MailTester’s inbox placement test. It simulates delivery across Gmail, Outlook, Apple Mail, and more, highlighting potential blocks or spam flags before you send to live audiences. It’s especially helpful when transitioning from shared to dedicated IP, or after re-engagement campaigns.

Finally, keep in mind that even with a dedicated IP, no IP is immune to issues. A high volume of bounces, spam complaints, or poor engagement can still trigger filters. The key is consistency—steady sending, clean lists, and responsive content. For large volumes, consider bulk verification to prune invalid addresses before sending. That’s not just good hygiene—it’s a non-negotiable part of sustainable deliverability.

Can you improve shared IP deliverability with list hygiene?

Yes—cleaning your list directly improves shared IP deliverability on platforms like Brevo. Invalid addresses, spam traps, and role accounts hurt the sender reputation shared across all users on the same IP. By removing these, you reduce bounces, lower spam complaints, and help maintain a healthier reputation for the entire IP pool.

The role of list hygiene in shared environments

In a shared IP setup, your deliverability isn't just about your individual practices—it's tied to how everyone else on that IP behaves. If many senders use outdated or low-quality lists, spam traps get triggered, bounce rates spike, and providers like Brevo may throttle or block the whole IP range. That’s why proactive list hygiene is not optional; it’s essential.

When you scrub your list before sending, you remove addresses that would otherwise cause failures. This includes non-existent domains, catch-all addresses, and known spam traps. The fewer errors your sends generate, the less likely your shared IP gets flagged.

How MailTester helps enforce hygiene at scale

Let’s be clear: you can't trust every email address. Some look valid but are dead ends. That’s where MailTester comes in. Our bulk verification checks real-time DNS, SMTP, and syntax rules to identify invalid, risky, or catch-all addresses before they ever hit your send queue.

Using MailTester’s bulk verification tool, you can validate thousands of emails in minutes. You get clear verdicts—valid, invalid, catch-all, or risky—so you know exactly what to keep or remove. This process cuts down on bounce rates and keeps your sender reputation intact.

Lower bounce rates directly benefit shared IP performance. According to industry data from SMTP.com’s email deliverability report, senders with bounce rates above 5% are significantly more likely to be throttled or blocked by ISPs. By maintaining a clean list, you help keep the entire shared IP pool in good standing.

Still, shared IPs come with limits. Even with perfect hygiene, Brevo’s shared IP may not offer the same consistency as a dedicated IP for high-volume senders. But for most campaigns, disciplined list management is the best step you can take to improve inbox placement and deliverability without upgrading.

How does inbox placement testing help with IP decisions?

You can’t trust spam filters alone when deciding between Brevo’s shared IP and a dedicated IP. Inbox placement testing shows how your messages land in real inboxes—Gmail, Yahoo, Outlook—under actual sending conditions. Only real data reveals whether shared or dedicated IP delivers better results for your content and audience.

Testing real inboxes beats guesswork

Spam score tools tell you if your email looks suspicious. They don’t tell you if it ends up in the primary inbox or the cluttered "Promotions" tab. For IP decisions, what matters is whether your message lands where it should: in the user’s main inbox. That’s why testing with real recipients is essential.

MailTester’s inbox-placement test sends actual messages through your chosen IP type—including Brevo’s shared IP and a dedicated one—to see how the same content performs across Gmail, Yahoo, and Outlook. No simulated environments. No assumptions. Just the real outcome across major providers.

Data reveals what’s truly working

Shared IPs may work fine for low-volume, low-sensitivity emails. But when you’re sending to high-value lists or time-sensitive offers, even small drops in inbox placement can hurt engagement. By testing both IP types side-by-side, you see which one delivers higher primary inbox rates with your specific content.

For example, a B2B SaaS company might find their newsletters get better inbox placement on a dedicated IP, even when using the same list and copy. No guesswork. Just real data showing that the dedicated path delivers more visibility—and more opens.

This approach aligns with industry standards. The Messaging, Malware, and Mobile Anti-Abuse Working Group (M3AAWG) emphasizes that genuine inbox placement testing is critical to understanding sender reputation and deliverability performance [M3AAWG].

Use MailTester’s inbox placement test to compare how your messages land across providers. You can test this directly from your email platform (like Brevo) and see performance differences clearly.

Whether you're on a shared IP or considering a dedicated one, inbox placement testing gives you evidence—not speculation. That’s how you make a decision that actually moves the needle.

What steps should you take before switching to dedicated IP on Brevo?

You should validate your full list with MailTester before switching to a dedicated IP on Brevo, confirm SPF, DKIM, and DMARC are properly set up, warm up the IP gradually with small, consistent sends, and monitor engagement, complaints, and feedback loops daily. Rushing this process increases the risk of spam filtering and inbox placement drops.

Ensure your list is clean and reliable

Before any IP change, your email list must be free of invalid or inactive addresses. Use MailTester’s bulk verification feature to check every address on your list. This helps avoid bounces, spikes in spam complaints, and damage to sender reputation.

  • Verify your entire list using MailTester’s real-time email validation—detects syntax errors, role accounts, disposable domains, and catch-all addresses before you send.
  • Clean lists significantly reduce hard bounces and increase deliverability by ensuring only valid, engaged recipients receive your messages.
  • Lists with high invalid address rates are flagged by receivers (e.g., Gmail, Yahoo) and often blocked early.

Lock down your authentication and alignment

Without proper authentication, even a dedicated IP won’t reach inboxes. Brevo’s dedicated IP relies on your domain’s reputation, so make sure all SPF, DKIM, and DMARC policies are implemented correctly. Misconfigurations create openings for spoofing and lead to inbox filtering.

  • Use RFC 7208 and RFC 7672 as guides for proper DMARC deployment. Start with a policy like DMARC: rua=mailto:[email protected]; pct=100; rua=mailto:[email protected] to monitor reports.
  • Ensure your SPF record doesn’t exceed 10 include clauses (known as the SPF limit) to avoid failures.
  • DKIM signing should be active on all outgoing messages. Brevo’s system handles DKIM if you use their sending platform—but it's still your responsibility to ensure it's enabled.
  1. Confirm your list quality—run 100% of your addresses through MailTester’s bulk verification before switching. This prevents unnecessary bounces and protects your sender reputation from low-quality traffic.
  2. Set up authentication—verify SPF, DKIM, and DMARC are fully configured and passing checks. Use tools like MxToolbox or MailTester’s inbox placement tester to validate real-world deliverability.
  3. Warm up the IP gradually—start with 1–2% of your list every week. Send to engaged users first. Monitor engagement and rejection rates closely.
  4. Monitor daily—track spam complaints, bounces, open rates, and feedback loop data. If engagement drops or blocks rise, scale back and diagnose immediately.

What are the trade-offs in choosing shared vs dedicated IP?

You get faster setup and lower cost with Brevo’s shared IP, but your deliverability depends on how other senders use it—meaning poor practices by others can hurt your inbox placement. A dedicated IP gives you full control over your sender reputation and higher long-term reliability, but requires ongoing monitoring and warming-up to avoid spam filters. The choice boils down to balancing cost, control, and the need for stable inbox delivery over time.

Shared IP: cost-effective, but reputation-dependent

With Brevo’s shared IP, you don’t need to manage reputation or warm up an IP—just start sending. That’s efficient for low-volume campaigns or testing. However, since multiple senders use the same IP, one bad actor can trigger spam filters or blacklisting, which affects everyone sharing it. If a single sender’s list is outdated or sends misleading content, your messages might get throttled or rejected—even if your own sending practices are clean.

For example, a shared IP that’s flagged by major providers like Gmail or Outlook due to high complaint rates can lead to a temporary delivery halt for all users. This unpredictability makes shared IP less ideal for consistent, long-term campaigns. You trade low friction for limited control over sender health. To verify your list’s quality before risking that, you can use bulk verification to filter out invalid or risky addresses.

Dedicated IP: control, but requires upkeep

A dedicated IP gives you full ownership of your reputation. You can track performance, ramp up sending volume gradually, and avoid the impact of other senders’ misbehavior. This often results in better inbox placement over time—especially for transactional or high-volume campaigns.

But with that control comes responsibility. You must warm up the IP by starting with low volumes and gradually increasing, monitor engagement, track bounces, and react to feedback loops. If you neglect this, even small spikes in spam complaints can lead to blocking. The longer you send consistently, the higher your chances of building lasting trust with inbox providers. You can test how likely your content is to land in the inbox using inbox placement tests.

Ultimately, the trade-off isn’t just technical—it’s strategic. If you’re scaling, managing sender health matters. You’re not just sending emails; you’re building a deliverability track record. For teams using Brevo, understanding this balance helps you choose the right IP model based on volume, audience quality, and long-term goals. The key is not to pick one style and stay there—some campaigns benefit from shared IPs, others need dedicated control. Use the tools you have, like the verification API, to build sender confidence and reduce risk. For a full picture of what’s possible, see pricing details and explore integrations that keep your workflow smooth.

Which IP type is right for your Brevo sending volume?

You should use a shared IP with Brevo if you send under 10k emails/month and maintain strong list hygiene. For 10k–100k/month, a dedicated IP can improve deliverability—but only if you warm it up properly and avoid reputation damage. If you send 100k+ monthly, a dedicated IP is necessary, but success hinges on consistent data quality, clean list practices, and ongoing sender reputation management. The right choice isn’t about the IP type alone; it’s about your operational discipline.

Low volume: shared IP works—if you keep your lists clean

  • Under 10,000 emails per month? A shared IP is usually sufficient. Brevo’s infrastructure handles the bulk of reputation management.
  • But if your list includes invalid, role, or frequently bouncing addresses, even shared IPs can get flagged. Regular list pruning is non-negotiable.
  • Use tools like MailTester’s bulk verification to catch bad addresses before sending. This prevents bounces and protects your sender reputation.

Moderate to high volume: dedicated IP requires careful execution

  • Between 10k–100k emails/month, a dedicated IP can offer more control—but it requires a warm-up period of 2–4 weeks to build trust with inbox providers.
  • Without consistent sending volume, clean data, and low bounce rates, your dedicated IP can quickly get blacklisted. Reputation is earned, not guaranteed.
  • For 100k+ mailings monthly, you need a dedicated IP to avoid being penalized by shared IP congestion. But even then, high volume with poor data quality leads to blocklists and low inbox placement.
  • Test placement regularly using real inbox checks. MailTester’s inbox placement test shows how your emails land across major providers.
  • Poorly managed send volumes—sudden spikes or inconsistent patterns—hurt deliverability more than volume alone. Stability matters.
  • Keep your SPF, DKIM, and DMARC records properly configured. These are fundamental, not optional. See RFC 7208 for DMARC standards.

Deliverability isn’t about technology alone. It’s about data quality, sending consistency, and operational discipline. A shared IP can work at scale if you manage it well. A dedicated IP will fail if you don’t.

How MailTester helps you make better IP decisions for Brevo

Before committing to a dedicated IP with Brevo, verify your list at scale. Use the bulk verification API to filter out invalid, catch-all, and disposable addresses—reducing bounce rates and protecting sender reputation.

Test your list quality early. Run inbox-placement tests to see how your email content performs with both shared and dedicated IPs. This data shows real-world deliverability performance, not theoretical outcomes.

With 98.9% accuracy, MailTester provides reliable results you can trust. No guesswork. No wasted sends. Just clear insights to guide your IP strategy.

Sources

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

Does Brevo’s shared IP hurt deliverability for new senders?

Yes. Shared IP means your reputation depends on other senders. New senders with low engagement or poor lists are more likely to be filtered.

Can you use a dedicated IP with Brevo’s free tier?

No. Dedicated IPs are available only in paid Brevo plans, typically starting at higher volume tiers.

How long does a dedicated IP warm-up take on Brevo?

Typically 2–4 weeks, with gradual volume increases and strict monitoring of engagement and complaints.

Do role email addresses hurt deliverability on shared IPs?

Yes. Role accounts (e.g. sales@, info@) often generate no engagement and appear as spam traps in aggregate.

How does MailTester verify email addresses?

It checks syntax, domain validity, MX records, SMTP response codes, and catch-all detection through real-time checks.

Is there a way to test deliverability before sending to all subscribers?

Yes. Use MailTester’s inbox-placement testing to evaluate how your messages land in Gmail, Yahoo, Outlook, and other inboxes.

What happens if my Brevo list has 15% invalid emails?

High bounce rates degrade sender reputation, especially on shared IPs. This increases filtering risk across all shared senders.

Should I switch to dedicated IP if I’ve been getting blocked?

Only after cleaning your list and confirming consistent sending habits. A blocked IP is often caused by poor list hygiene, not IP type.

Can disposable email domains harm shared IP reputation?

Yes. Disposable domains often lead to high bounce rates and spam complaints, which can trigger filters on shared IPs.

How many free verifications does MailTester offer?

You get 100 free verifications to start with, and purchased credits never expire.

Can MailTester integrate with Brevo?

Yes. Use the MailTester verification API to clean your list before importing it into Brevo for send.

Do SPF and DKIM affect shared IP deliverability in Brevo?

Yes. Proper authentication is required to prevent filtering, regardless of IP type.