role

The username is a role account rather than a person

info@, support@, billing@ and the rest of the open role-address list name a function, so the inbox may be shared, filtered or unread.

risk weight: +30
dataset: role-addresses
reads from: role
verdict reason: role, no_reply

What it means

The open role list of around a thousand usernames is matched against the plus-tag-free username. A no-reply pattern counts as a role too, even when the list lacks the spelling, and role_type names the family: support, sales, billing, postmaster, no_reply and so on.

It reads from the role field and comes with the role verdict reason — unless the address is a no-reply one, which gets its own reason and whose weight is added on top of this one.

What to do

Send transactional mail freely; keep marketing lists to personal addresses, and let the sending policy block the families you do not want.

Example response

{
    "email": "[email protected]",
    "deliverable": "risky",
    "reason": "role",
    "role": true,
    "role_type": "support",
    "risk_signals": [
        {
            "signal": "role",
            "weight": 30,
            "dataset": "role-addresses"
        }
    ]
}

Abbreviated: a real answer carries all 46 fields, listed in the verify-email reference. The risk_signals entry shown is the one this signal adds; the weights of every entry in the list sum to risk_score.

markdown version: /docs/signals/role.md

role

What it means

What to do

Example response

Related