Should I Validate Risky Catch Alls with Prospeo After Using Debounce?

I saw LinkedIn posts recently that said there is no need to validate Catch Alls since they are sent emails less often. I've been validating with debounce and prospeo, but when debounce comes back as Risky, should I waterfall validate it with Prospeo or is it "safe enough"?

2 comments

Clay Team
APP
·
·
Great question, Gabe! Haven't seen a post about it but some users have reported domain health issues when they don't validate and exclude many of those risky emails. Of course, not all catch-alls would be bad as you say, but still risky at scale.
Muhammad
·
·
Gabe D. I would suggest you to validate the catch-all emails using Scrubby (a bit expensive). This is the best way to verify them. because it sends them actual emails using burner accounts to check if the mailboxes on catch-all domains bounce or not. We verify catch-all emails as well for our clients using a similar approach at lower than Scrubby.