Role account checker
Paste your addresses and see which ones reach a department instead of a person. Each one is matched against the 66 role names ZapBounce flags, as you type, in your browser.
One per line or comma-separated. Each local part is matched against the 66 role names ZapBounce flags.
The short version
- Every role address is listed with the role name it matched, such as sales@ or noreply@.
- You also get the list with the role addresses taken out, ready to copy.
- Plus tags are ignored, so sales+eu@ still counts as sales@.
- Role is a flag, not a verdict. A role inbox can be valid, so decide by what the list is for.
How the check works
The checker splits your paste on new lines, commas, semicolons and tabs. For each entry it takes the local part, the text before the last @, drops any plus tag and lowercases it. If that exact word is on the role list, the address is flagged.
Exact matching keeps you from losing real people. info@ is a role, while information.desk@ or a person named Hi Chen at hi.chen@ is not. Entries with no usable @ are listed as skipped, so nothing disappears silently.
The list is the same one ZapBounce's engine uses for its role flag. What you see here is what you'll see in a verified file, row for row.
| Role name | Usually reaches |
|---|---|
| info@ | A shared inbox on the website contact page |
| sales@ | The sales team, or a routing tool in front of it |
| support@ | A helpdesk queue that opens a ticket |
| admin@ | IT or whoever set up the domain |
| billing@ | Finance, often an accounts system |
| noreply@ | Nobody. It exists to send, not receive |
| hr@ | The people team, often filtered hard |
| marketing@ | A shared team inbox |
| postmaster@ | The mail admin, required by RFC 5321 |
| webmaster@ | Whoever runs the site, if anyone |
When to keep them and when to cut them
For cold email, cut them. A role inbox wasn't the person you researched, and several people may see your message and one may mark it as spam. A single complaint costs your domain more than that lead is worth. Our answer on whether to remove role accounts covers each list type.
For newsletters, look at how the address joined. If someone typed team@ into your signup form, they chose it, so keep it. For invoices and receipts, keep it: billing@ is exactly where that mail should go.
Whatever you decide, check that the addresses you keep can receive mail. ZapBounce verifies each one over SMTP and returns valid, invalid, catch-all or unknown with the role flag beside it, so one pass covers both questions. See the role-based email definition for how filters treat them.
Questions people ask
What is a role-based email address?
A role-based address names a job or a department instead of a person, such as info@, sales@, support@ or admin@. Mail sent to it usually lands in a shared inbox that several people read, or that nobody reads at all.
Should I remove role accounts from my email list?
For cold outreach and marketing, usually yes, because role inboxes rarely engage and the person who opens one never signed up. For a customer or billing list, keep the ones a customer gave you on purpose, such as accounts@ for invoices.
Are role-based emails invalid?
No. A role address can be a working mailbox that accepts mail. That's why ZapBounce reports role as a flag next to the result, so info@acme.io can be valid and still be flagged as a role account.
Which prefixes count as role accounts?
The checker matches the part before the @ against the list ZapBounce's engine uses, including info, sales, support, admin, noreply, billing, hr and postmaster. The match is exact, so information@ or sales.team@ are treated as personal.
Flag roles and check mailboxes in one pass
Every verified row carries role and disposable flags next to its result. Unknowns and duplicates are never billed.