- what email verifier is the best service

However, I wanna run this test myself sometime. I feel that especially for big companies the verification is not really working. - as I said it's super improable that junior people have an email like [email] etc. which feels like it oftentimes comes up

If you want cost effectiveness you can use a cheap smtp tool like millionverifier then for any unknown or catch all statuses can run through a tool like enrichley (natively in clay). Had some agencies test against all catch all verification tools in clay and seeing minimum 5-10% more coverage and sub 2% bounce rates.

[user] Findymail founder here. Where do you source your emails? Findymail has great verification but it's even better in enrichment. If you're looking to get an external sub with the goal of saving Clay credits, grabbing a Findymail sub will let you find emails (verification included) AND verify emails you get from other sources.

[user] is obviously pitching his own solution here but let's just say that the claim that it "beats all verification tools" is at least debatable, at worst flat out wrong ... :slightly_smiling_face:

[user] basically explains our process, verify first thru million verifier (most cost efficient) then run all riskies to findymail. On average we see 40-50% of those riskies are actually valid, thats huge!

But also, controversial take: all email verifiers essentially are the same thing. Now, I understand some are a little bit better than others, but they all do the same thing. It's more important to just pick one and just go. But yeah, usually Millionverifier is reliable and it's the cheapest. And Findymail is more expensive, but we only use it for riskies.

[user] You're totally right with this. Current verification tools (Findymail included) only verify the deliverability (ie. the inbox exists) but not necessarily that the person is the one you wanted to reach initially. That's because currently email verification tools don't get the input data/request (ie. the person you wanted), just the email. This leads to exactly the issue you mentioned, I've talked about it here: linkedin.com