You've probably come across a line like this on some email tool's homepage: "Zero bounce guarantee" or "100% verified, guaranteed." It reads well. It sounds like the one problem every marketer worries about has been solved by someone, finally.
But if you have ever sent out a campaign to a list of several thousand people,you know a few always slip through. No matter how much you carefully prepared the list, a certain amount of mail will always bounce back. So how much bounce back is too much bounce back? Is zero percent bounce rate achievable or is it just another nice sentence written by your marketing department?Let's actually work through the numbers instead of guessing.
What does a bounce actually mean?
A bounce is what happens when an email you send doesn't reach an inbox and instead comes back undelivered. There are two kinds, and the difference matters more than most people realise.
A hard bounce is when the email address doesn't exist, or the domain is defunct. Think of it as a courier going to a house that's been torn down, there's no place for it to go. This is permanent. No amount of retrying will fix it.
A soft bounce is temporary. Perhaps the recipient’s mailbox is full, or their mail server is down for maintenance at the time of sending. Resend the email the following day, and it may be successfully delivered. This is more like the courier finding the gate locked for a few hours — the house is very much there.
When companies claim a "zero bounce guarantee", they always mean hard bounces, since soft bounces are out of their control. That is the first noteworthy observation to make.
Why the promise feels believable
Email verification tools do real, useful work. Before the message is sent out, a verification service checks the address in several steps. Firstly, it makes sure that the address is spelled correctly; no verification service can save you from a typo, like [email protected] . Secondly, it checks if the domain (the part after @) is real by running a DNS/MX lookup (roughly equivalent to asking "does this street exist?"). Lastly, an SMTP check is made, which means that the verification service tries to briefly connect to the recipient's mail server and asks if a mailbox with that specific address exists.
This is a genuinely good process, and when done properly, it catches the vast majority of dead addresses before you ever send a single email. Pingovo also runs exactly this kind of check on every address — syntax, DNS/MX, and SMTP — before indicating it as safe, risky, or invalid. But "catches most" and "catches all" are two very different claims, and this is where the math starts working against any absolute guarantee.
Where the math actually breaks down
Catch-all domains don't give an honest answer
Some company mail servers are set up to accept mail for any address at their domainSome company mail servers are set up to accept mail for any address at their domain, even if that address doesn't actually exist. This is common with smaller businesses and agencies that route everything through one inbox internally. When you run the SMTP check on such a domain, the server will tell you that it will accept delivery for any address you ask. In particular, this includes addresses that you make up on the spot., even if that address doesn't actually exist. This is common with smaller businesses and agencies that route everything through one inbox internally. When you run the SMTP check on such a domain, the server will tell you that it will accept delivery for any address you ask. In particular, this includes addresses that you make up on the spot.
So the tool has no honest way to confirm whether the mailbox is genuinely active. It gets marked as "risky" rather than "valid," which is the correct and transparent thing to do - but it also means a slice of every list stays genuinely uncertain, through no fault of the checking process.
Addresses die after they're verified, not before
Verification tells you the state of an address on the day you check it. It cannot tell you what happens three weeks later. People change jobs, colleges throw away old student email IDs when students graduate, someone stops using an inbox they created for one sign up form, and so on. Industry patterns suggest that business email lists lose a small percentage of their addresses to natural decay every single month, simply from people moving on.
If you verify a list today and only send the campaign a month later, some addresses that were perfectly real when checked will have gone quiet by the time you press send. That's not a problem of verification, that's just the passage of time.
Servers are sometimes deliberately unclear
Some mail servers implement greylisting: a technique where the server refuses the initial connection from an unfamiliar sender (for example, to filter out spam bots, which would not resend the e-mail). A genuine verification attempt can get caught in this same filter and come back inconclusive rather than a clean yes or no.
Now put it together with real numbers
Say you have a list of 10,000 addresses collected over several months through website signups.A verification pass removes evidently broken syntax and dead domains (maybe 600 addresses). This leaves 9,400 that pass the checks. If 3% of these are on catch-all domains, that's about 280 addresses the tool can't be certain of. Add natural decay if there's any gap between verification and sending, and even an extremely well-run campaign is likely to land somewhere around a 0.3% to 1% bounce rate - not zero, but low enough to be considered excellent by most inbox providers.
That's the honest answer. The mathematics there don't allow for "zero", but rather for "very low".
What's actually a good bounce rate to aim for?
Most inbox providers consider anything under 2% healthy, and under 1% is genuinely strong performance. Once a list begins to go above 5%, mailbox providers begin to take notice and can take action on whether your emails are landing in the inbox or the spam folder. So the goal was never really "zero" — it's keeping the number small enough that it never damages how your emails are treated going forward.
A quick, real example
Take a small ed-tech company in Pune, that acquires leads through signups on webinars, over eight months. Some signups used college emails that get deactivated on graduation. Even if the company verifies the entire list, the week before they send an admissions reminder, there are going to be some addresses that have already died, and that's not a false positive from the verification tool - it's a true negative, from the fact that the address didn't exist anymore at the time of checking.
Or picture a small clothing brand in Jaipur sending out a Diwali sale campaign to a list built over a year of website visitors. A set of addresses is caught under one of the vendor's shared company domains that are set up as catch-all. The validation tool then rightly marks these as "risky" rather than claiming absolute confidence it has no basis for. Whatever the brand decides to do about that (skip them, send the mail to them anyway, send a smaller test group first) - that's a decision only the brand can take on a case-by-case basis.
Why an honest tool won't promise "zero"
A tool that tells you "risky" instead of forcing a false "valid" or "invalid" label is actually doing you a bigger favour than one that claims perfect accuracy. It's giving you information that can help you make a good decision with.
Verification is also only one part of staying out of the spam folder. Even a perfectly clean list sent from a brand-new email account can land in spam, simply because the receiving server has no history to judge that sender by. This is where warmup comes in — gradually increasing how much mail an account sends, so that mailbox providers build up trust in it over time rather than treating day-one bulk volume as suspicious. A list with a 0% bounce rate sent through a cold, untrusted account could very well still be doing poorly. Both issues are related, but not the same issue.
What to actually look for instead of a guarantee
Rather than chasing an illusory promise that the math doesn't support, it's much more useful to look for a few practical questions: does the tool tell you about every address whether it's valid, risky, or invalid, rather than forcing everything into a clean yes or no? Does it check syntax, domain, and mailbox existence separately, so you can see where an address failed? Does it flag catch-all and disposable addresses honestly, instead of just quietly counting them as safe? And does it give you tools for ongoing list health, like warmup and engagement tracking, rather than treating verification as a one-time event you do and forget?
Pingovo's verification does all three: syntax, DNS/MX and SMTP checks, and separates out disposable, role and catch-all addresses, rather than lumping them all together for your scoring. The same account also handles warmup and campaign sending, so the bounce and engagement data from a real campaign can inform how you clean the list next time, instead of verification living in a completely separate tool from the sending itself.
So, what should you actually expect?
Not zero. Close to zero, with honesty about the small percentage that no checking process can ever fully close. If a provider promises you 100% deliverability, you need to ask them one simple question: How do you handle catch-all domains and addresses that become inactive after the date of verification? Their answer will tell you a lot more than the number printed on their homepage.
