Catch-all, disposable and role addresses: what they are and what to do with them

Run any list through a verifier and you'll get back more than just "valid" and "invalid." The middle categories are where senders get stuck, because the right answer depends on what the list is for.

This is a plain-language breakdown of the three that come up most.

Catch-all addresses

A catch-all domain is configured to accept mail sent to any address at that domain. Send to nobody-in-particular@example.com and the server says "sure, I'll take it" rather than rejecting it.

That's convenient for the company (nothing gets lost to a typo) but it means a verifier can't tell whether a specific mailbox exists. The server would say yes either way.

What it means for you: the address might be perfectly good, or it might be a ghost that will silently be discarded on the other end. There's no way to know from the outside.

What to do: treat them by age and source. A catch-all address someone typed into your form last month is almost certainly real. One from a list you bought or an export from 2019 is a coin flip. Keep the recent ones, and be conservative with the rest if your sender reputation matters more than reaching a few extra people.

Disposable addresses

Disposable (or "temporary") addresses come from services like Mailinator, Guerrilla Mail, 10minutemail and thousands of similar domains. They exist for people who want to get past a sign-up gate without giving you a real inbox.

The addresses are technically valid. The mail is delivered. Nobody ever reads it.

What it means for you: every disposable address on your list is a real person who specifically didn't want to hear from you. They cost you a send credit and contribute nothing.

What to do: remove them. There's no scenario in which sending marketing email to a disposable inbox helps you. If you see a lot of them, it usually means your sign-up form is gating something people want badly enough to fake an address for, which is worth knowing.

Role addresses

Role addresses are the generic inboxes a company sets up for a function rather than a person: info@, sales@, support@, admin@, billing@, hello@.

They're real and they're monitored, but often by several people, or by a ticketing system, or by whoever happens to be on shift. The person who signed up for your newsletter is rarely the person reading that inbox today.

What it means for you: role addresses have low engagement and high complaint rates. Someone who didn't sign up sees your email in a shared inbox and hits "report spam." Mailbox providers count that complaint against your domain exactly as they would any other.

What to do: it depends on the list. For a B2B product where procurement@ is genuinely who you need to reach, keep them. For a newsletter, drop them or move them to a separate, lower-frequency segment. Many email platforms refuse to send to role addresses at all for exactly this reason.

The short version

Category	Real mailbox?	Someone reading it?	Default action
Catch-all	Unknown	Unknown	Keep if recent, drop if old
Disposable	Yes	No	Remove
Role	Yes	Sometimes	Segment or remove

None of these are as bad as an address that hard-bounces, which is why verifiers separate them out rather than lumping them in with "invalid." The point is to give you the decision, with enough context to make it well.

ListBouncer labels each of these buckets separately in every report and lets you download them as their own CSVs, so you can act on one category without touching the others.