Role Account Checker
Role accounts such as info@, support@ or sales@ are shared by a team rather than owned by one person. ValidReach flags them so you can decide how to treat them.
How role accounts are detected
The part before the @ is compared with a curated list of common role names, locally and instantly. When an address matches, the result reports is_role as true and, if nothing riskier applies, the status "role".
The list is a practical subset, not complete: an address that is not on it can still be a shared mailbox.
Why teams care
Shared inboxes often have lower engagement, may be read by several people, and can have stricter consent expectations. Some products block them at signup; others accept them for B2B contact forms.
Role accounts are still deliverable in most cases, so the flag informs your rules rather than rejecting the address outright.
Combine with other flags
Use role together with free-provider and disposable flags: a role account on a company domain is usually a different case than a disposable address pretending to be one.
What it cannot tell you
- The role list is not exhaustive and is not localized for every language.
- A role flag does not say the mailbox is valid; verification of the mailbox is a separate check.
- Whether to block, allow or tag role accounts is your policy decision.