Skip to content

Free tool

Role Email Checker

Check whether an address is a shared inbox such as info@, sales@ or support@ rather than a person. Paste up to 1,000 addresses and see the category of every hit, matched against the 253 patterns our verification engine uses.

Check

Matches the local part against the same role patterns the RocketVerifier engine uses. Runs in your browser: nothing is sent to a server.

What the role email checker does

A role email checker flags addresses that belong to a function or team instead of one person, such as info@, sales@, support@, billing@ or noreply@. This tool matches the part before the @ against the 253 role patterns RocketVerifier uses, including numbered and hyphenated variants like support2@ and help_desk@, and shows each hit's category. Role addresses that accept mail are risky, not undeliverable.

How it works

How the Role Email Checker works

  1. Paste addresses

    Check one address, or switch to Bulk and paste up to 1,000, one per line. Everything runs in your browser.

  2. Match 253 role patterns

    The part before the @ is matched exactly, with trailing digits removed (support2) and with hyphens and underscores removed (help_desk).

  3. Split the list

    See the category of every hit, then copy the personal and role addresses as separate lists.

Reading your result

What the result means

  • Role-based

    A shared inbox such as sales@ or support@. In a RocketVerifier verification a role address that accepts mail is risky with the role_based sub-status, not undeliverable, so you decide whether to mail it.

  • Personal

    No role pattern matched, so the address reads as one person's mailbox. It still needs a mailbox check to prove it exists.

  • Role and undeliverable

    When the mailbox behind a role address does not exist, a full verification returns undeliverable like any other address. The role flag never hides a bounce.

What is a role-based address? Role-based address in the glossary

The 253 patterns, by category

The same groups our verification engine checks, with a few examples from each.

  • Generic contact

    admin@ administrator@ contact@ info@

    16

  • Support

    support@ help@ helpdesk@ help-desk@

    13

  • Sales and marketing

    sales@ sell@ selling@ business@

    16

  • Technical and IT

    tech@ technical@ it@ sysadmin@

    21

  • Finance and billing

    billing@ accounts@ accounting@ finance@

    15

  • HR and recruiting

    hr@ humanresources@ human-resources@ jobs@

    14

  • Legal and security

    legal@ law@ counsel@ attorney@

    17

  • Press and media

    press@ media@ pr@ news@

    13

  • System and no-reply

    noreply@ no-reply@ donotreply@ do-not-reply@

    23

  • Team and department

    team@ all@ everyone@ staff@

    14

  • Orders and ecommerce

    orders@ order@ shop@ store@

    12

  • Other

    spam@ junk@ test@ demo@

    17

  • Non-English role word

    kontakt@ vertrieb@ verkauf@ buchhaltung@

    63

FAQ

Role email checker FAQ

What is a role-based email address?

An address that belongs to a function or a team rather than one person: info@, sales@, support@, billing@, hr@, legal@, press@, noreply@ and similar. Several people may read it, or nobody, and nobody in particular signed up with it.

Should I remove role-based addresses from my list?

It depends on why they are there. A billing@ address that asked for invoices should keep getting them. On a marketing or cold outreach list, a role address reaches a team instead of a decision maker who opted in, so most senders suppress them for campaigns and keep them for transactional mail.

How does the checker catch variants like support2@ or help_desk@?

It applies the same three matches as our engine: the local part as typed, the local part with trailing digits removed, and the local part with hyphens and underscores removed. The 253 patterns include common role words in German, Spanish, Portuguese, Italian, French, Dutch, Polish and the Nordic languages, such as kontakt, ventas and vendas.

Does RocketVerifier mark role addresses as invalid?

No. A role address that accepts mail is returned as risky with the role_based sub-status. If the mailbox does not exist, the result is undeliverable, the same as any other address. You get both facts, and you choose what to send.

Are the addresses I paste uploaded?

No. The pattern list ships with the page and the matching runs in your browser, so the addresses never leave your device.

Keep going

More free email tools

Flag role inboxes and dead mailboxes in one pass

A RocketVerifier verification marks every role address and checks each mailbox over SMTP, so you keep the inboxes that work and drop the rest.

Start free Bulk verification

100 free credits · No card required · Credits never expire