A catch-all (or accept-all) domain accepts mail for any address, real or not. Send to jane@company.com or zzz@company.com and the server says yes to both. That makes it impossible to confirm, from the outside, that a specific mailbox exists.
For enrichment this matters because "verified" usually means "a verification service checked the mailbox". On a catch-all domain that check cannot succeed or fail. The address might be perfect. It might bounce.
Why bounces cost more than the email
Mailbox providers watch sender reputation closely. Google asks bulk senders to keep their user-reported spam rate below 0.1% and never reach 0.3% (Google sender guidelines). Repeated bounces tell providers your list is unmaintained, which pushes future mail toward spam. A cheap email that bounces can be expensive.
Questions to ask your vendor
- Do you mark catch-all results separately, or fold them into "verified"?
- Do you charge for a catch-all result, and at what price?
- Do you charge for an address that fails verification?
- Can I export catch-all rows separately so I can send to them more carefully?
A sensible policy
- Send first to addresses verified as deliverable.
- Send to catch-all addresses in small batches, from a warmed domain, and stop if bounces rise.
- Never send to addresses that failed verification.
In Kiln, an email guess that fails verification counts as a miss: the waterfall moves to the next provider and you are not charged. Each cell records which provider answered and how confident it was, so you can filter before you send.