Role-based email addresses (info@, sales@): what role: true means

valid role: true

The address belongs to a function or team (info@, sales@, support@), not to one person.

What it means

Role-based addresses are shared by a team or forwarded to several people. They can be perfectly valid and safe_to_send can be true, so EEV reports role: true as a signal, not as a verdict.

They tend to have lower engagement in marketing campaigns, and several people can see the email, so a spam complaint is more likely if nobody on the team asked for it.

Why it happens

• Contact addresses taken from company websites.
• Forms filled in with a generic company address.

What to do

• For B2B outreach and transactional email, keep them: support@ or billing@ may be exactly who you need.
• For newsletters and promotions, consider a separate segment, and keep only those that opted in.

Example API response

{
    "email": "sales@example.com",
    "result": "valid",
    "reason": "accepted_email",
    "disposable": false,
    "accept_all": false,
    "role": true,
    "free": false,
    "user": "sales",
    "domain": "example.com",
    "mx_record": "mx1.example.com",
    "mx_domain": "example.com",
    "safe_to_send": true,
    "did_you_mean": "",
    "success": true,
    "message": "Processing time: 812 ms",
    "http_code": "200"
}

Try it without an account: the API has a free sandbox key, eev_sandbox_key, that returns fixed answers for test addresses such as valid@, invalid@, unknown@ and catchall@sandbox.easyemailverification.com.

Check an address for freeClean a whole list