Know when an address belongs to a team, not a person
Addresses like info@, sales@ and support@ reach a shared inbox. They can deliver, but nobody in particular reads them. We flag them as Risky.
- Six checks on every address
- A plain reason with every result
- Slow servers never cost a second credit
- 200 free credits, no card
Examples
What it looks like in your results
Result rows with the category and the reason you will see.
How it works
How we detect it
This check runs on every address, as part of the same credit.
- 01
Read the part before the @
We match it against a list of over 900 team prefixes such as info, sales and support.
- 02
Flag it early
Role addresses are flagged before we contact the mail server, so the check stays fast.
- 03
Give the reason
Role addresses come back Risky with the reason code role_address and the reason "This is a shared role address, like info@ or sales@, not a person."
What to do
What to do with these addresses
Every result comes with the reason, so you can decide row by row.
Find a person instead
For outreach, look for a named contact at the same company.
Keep for transactional mail
Receipts and notices to support@ or billing@ are usually fine.
Send separately
Keep role addresses out of personalised cold campaigns.
Related checks
Part of all six checks
Every address goes through all of them, in order.
Catch-all detection
Some domains say yes to any address, so no one can confirm the mailbox.
Learn moreFAQ
Role-based email questions
Short answers about this check.
Still have a question? Talk to us.
Check your list before you send it
Start with 200 free credits. Pay per credit after that.