Catch-all domain

Ordinary verification asks a receiving server whether an address exists and reads the answer. A catch-all answers yes to everything, so the check returns no information. Vendors then either drop the record, mark it accept-all, or — the expensive option — count it as valid, which is how a list with a good reported accuracy still bounces.

The failure is often silent. Mail to a nonexistent address at a catch-all domain is accepted and then discarded or routed to an unread tray, so it does not bounce and does not reply. It just quietly consumes sending capacity.

Do not treat catch-all as a synonym for bad. Plenty of well-run companies use one. Treat it as a record with weaker evidence and adjust what you do with it:

• Send to catch-all addresses in small batches, separately from your verified list, so a bad batch cannot move your headline bounce rate.
• Prefer records where the address is also published somewhere — that evidence is independent of the mail server's behaviour.
• Watch replies rather than bounces as the success measure. A catch-all cohort with no replies at all is a cohort of wrong addresses.

Even without visible bounces, sending into dead addresses at catch-all domains hurts. Engagement rates fall, and providers score placement on engagement. Some of those addresses are also recycled into spam traps, which is a much faster route to a domain-level block than a bounce is.

Keeping catch-all volume as a small, deliberate share of what a mailbox sends is the practical control.

SalesShift grades every pool address rather than presenting one verified badge, and enrichment writes discovered addresses as unverified. Per-mailbox caps and the bounce threshold that pauses a mailbox both work on what actually happened when you sent, which is the only measurement a catch-all cannot mislead.