Account registration
Explain why you need an individual address if shared access would affect account recovery.
Check whether an address belongs to a shared role like support@, sales@, info@ or admin@ instead of an individual person.
Addresses such as sales@company.com and support@company.com can be perfectly deliverable, but they often reach a shared inbox or multiple people. For outreach and lead enrichment, it can be useful to separate them from person-specific addresses.
No. EmailValidly treats role status as a risk signal, not proof that the address cannot receive mail. Use the main email checker when you also need DNS, MX, disposable-domain and mailbox signals.
This checker looks for common functional local parts, like sales or billing. A match describes an address pattern. It does not identify an owner, measure engagement or establish whether the inbox works.

Use the supplied address so syntax can be checked first.
The checker recognises a set of common shared-inbox names.
A billing inbox may be appropriate for invoices even if it is unsuitable for an individual signup.
Illustrative scenarios, not live results for the addresses or records shown. Open a scenario to see the next action.
The local part matches a name commonly used by a team.
Next action Check whether a team inbox suits your purpose.
This checker checks the base local part before the plus tag.
Next action Preserve the full address when contacting it.
A person-like name does not prove that one person owns the inbox.
Next action Keep ownership checks separate.
Explain why you need an individual address if shared access would affect account recovery.
Keep appropriate department contacts while marking them separately from named people.
No. They are often intentional and useful.
No. Pattern matching cannot identify the owner.
No. Use the full checker for DNS and mailbox signals.