No2Bounce fails miserably in email validation; here’s the cold hard truth.

No2Bounce fails miserably in email validation; here’s the cold hard truth.

This blog post will be all about numbers, performing validation on no2bounce and ReadyToSend, and gonna show you why spending even a single dollar on no2bounce indirectly harms your ROI.

We will be using this list of 500 emails - email list

So, I uploaded the list on No2Bounce, which is considered effective for catch-all validation, but the statistics say something else.

No2bounce Stats

Validation Results
Validation Results
Status Count Percentage
Valid 214 42.8%
Invalid 113 22.6%
Unknown 173 34.6%

now let's upload the same file to ReadyToSend

ReadyToSend Stats

Validation Results
Validation Results
Status Count Percentage
Valid 328 65.6%
Invalid 145 29%
Unknown 27 5.4%
💡
ReadyToSend "Actually" validates risky/catch-all emails in real time with 98% accuracy.

So now that the numbers clearly show that ReadyToSend validation performs better, I personally dove deep to see which emails no2bounce marked as valid and whether they are "actually" valid. By valid, I mean in terms of catch-all / risky emails, which raises the question of whether the mailbox exists or if it's a catch-all trap that forwards mail to a catch-all inbox. There is a significant difference when you send to them. If you send to a catch-all address where the mailbox doesn't exist, your mail will be delivered, but in a catch-all inbox, the person you send the mail to may never check it because all company catch-all mails go there. Now, if you use ReadyToSend, the emails we mark as valid are real inboxes that exist. That's why our valid emails perform much better than no2bounce valid emails; you can try this for yourself.

I'd love it if you read the entire blog. No hate to no2bounce: a lot of improvement is needed. Reach out if you want us to be your backend 😉