GTM Stack
Email Verificationcatch-allverificationdeliverabilitybounce-rate

What's the best way to handle catch-all emails in my outbound lists?

After running verification, about 40% of my list comes back as 'catch-all' or 'accept-all'. These emails might be valid but might bounce. Should I send to them or exclude them? What's the safest approach?

March 2026

Quick Answer

Catch-all domains can be 50% of your list. Most teams take the moderate approach: send to catch-all from reputable enterprise domains, exclude from unknown domains, cap catch-all at 20% per batch, and monitor bounce rates daily against the 2% threshold. Use second-pass verification (BounceBan) to filter the worst catch-alls.

Recently updated
1 weeks ago

1 Answer

Catch-all domains are the biggest unsolved problem in email outbound. They can make up 50% of lead lists, so excluding them entirely means losing half your addressable market.

What catch-all actually means: The domain's mail server accepts all emails, so verification tools can't confirm if the specific address exists. The email might work perfectly or bounce hard.

Strategy by risk tolerance:

Conservative (protect sender reputation at all costs):

Moderate (balanced approach, most teams land here):

  • Send to catch-all emails from reputable domains (e.g., enterprise companies)
  • Exclude catch-all from small/unknown domains
  • Cap catch-all at 20% of any sending batch
  • Monitor bounce rates daily and pause if approaching 2%

Aggressive (maximize volume):

Practical tip: Send catch-all emails from your warmest, most established domains. New domains should only send to verified-deliverable addresses until reputation is established.

AI GeneratedMarch 2026

Disagree or spot an error? Submit a correction here. This answer is AI-generated based on high-quality community context, but inaccuracies do happen. Your feedback helps us maintain the best information.

Add your take

Have experience with the tools discussed here? Share your honest opinion.