Verification isn't a feature. It's the whole point.
What an unverified email actually costs
If you send a cold email campaign to a list with a 20% bounce rate, the cost isn't just the wasted credits. It's:
- Your sender reputation. Every hard bounce tells Gmail, Outlook, and your own deliverability platform that you don't know who you're emailing. Reputation damage compounds — by the time you notice, your good emails are landing in spam too.
- Your SDR's time. Following up on a list where one in five contacts doesn't exist means 20% of every step is wasted: follow-ups that never deliver, CRM entries that need cleaning, manual checks to figure out why a "promising lead" went silent.
- Your reply data. When you can't tell whether someone didn't reply or never received the message, you can't iterate on your messaging. The signal gets drowned in noise.
A 20% bounce rate isn't unusual on tools that don't verify. It's typical. And the credit cost — what most people think they're saving — is the smallest part of the damage.
What verification actually involves
For every email we return, we run a real SMTP check against the receiving mail server. We connect, we ask if the address would accept a message, and we read the response.
- A confirmation means the mailbox exists.
- A rejection means it doesn't, and we never return that address to you.
- A catch-all response (the server accepts everything) means we can't actually tell, and we exclude those by default.
- A temporary failure (server too busy, throttled) means we retry, and if we still can't tell, we return no result and charge no credits.
This is slower than guessing. It costs us more per lookup. We do it anyway because the alternative — passing the cost of bad data on to you — is what makes the rest of the industry feel hostile.
What we never do
- We never return an email we couldn't verify and pretend we did.
- We never charge you for an address that fails verification.
- We never quietly relax our standards when our cost goes up.