role
A shared role inbox such as info@ or support@ rather than a person
The username is on the open list of role addresses. The inbox is shared, monitored unevenly, and rarely read by the person who filled in your form.
- appears in
- reason
- verdict
- risky
- risk weight
- +30
- credits
- 1 credit, like every deliverable or risky answer. Repeats of the same address are free for 7 days.
What it means
The local part matches the open role-address list (info, support, sales, admin, billing and around a thousand more), synced weekly. Role inboxes belong to a function rather than a person, get forwarded and filtered unpredictably, and carry higher complaint rates. role_type says which function: postmaster (the RFC 2142 family), support, sales, info, admin, billing, marketing, careers, legal, or other for a listed username outside those families; a no-reply shape gets its own reason, no_reply.
The mailbox is still probed, so mailbox_exists can be true for a role address; the verdict stays risky.
What to do
Accept role addresses on B2B forms where a shared inbox is expected, but keep them out of marketing sends and personalised sequences.
Example response
{
"email": "[email protected]",
"deliverable": "risky",
"reason": "role",
"role": true,
"risk_score": 30
}Abbreviated: a real answer carries all 46 fields, listed in the verify-email reference.
Related
- likely_typo · the domain is a known misspelling of a real mail provider
- parked_domain · the domain is parked or for sale, and still accepts mail
- disposable · the domain belongs to a disposable, temporary email provider
- mx_blocklisted · the domain's mail is served from a network on the threat blocklists
- implicit_mx · the domain has no MX record and relies on the address-record fallback
- mailbox_full · the mailbox is over its storage quota
- no_reply · a no-reply address: mail to it is discarded by design
- recycled_mailbox · the mailbox exists now, but once answered that it did not
- catch_all · the server accepts every address at the domain, so the mailbox cannot be confirmed
- unverified · the mailbox could not be confirmed
- role · signal · the username is a role account rather than a person (+30)
- All verdict reasons
- Verdicts and the risk score
- API reference
markdown version: /docs/reasons/role.md