> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vouch.expert/llms.txt
> Use this file to discover all available pages before exploring further.

# Role Email Detection

> Detect generic organizational email addresses

## Overview

Role email detection identifies generic organizational email addresses like admin@, support@, or info@ that belong to a group or function rather than an individual person.

<Note>
  Typically configured as **ALLOW** or **FLAG** since role emails can be legitimate for business signups.
</Note>

## Common Role Prefixes

* `admin@` - Administration
* `support@` - Customer support
* `info@` - General inquiries
* `sales@` - Sales team
* `noreply@` - Automated systems
* `contact@` - Contact forms

## Why Detect Role Emails

* **Lower engagement**: Shared inboxes have lower engagement rates
* **Not personal**: Can't identify a specific individual
* **Compliance**: Some services require personal email addresses

## API Response

```json theme={null}
{
  "checks": {
    "roleEmail": {
      "pass": false,
      "latency": 0.5
    }
  }
}
```

<ParamField path="pass" type="boolean">
  `false` if role email detected, `true` if personal email
</ParamField>

<ParamField path="latency" type="number">
  Check execution time in milliseconds
</ParamField>

## Configuration

<Card title="ALLOW" icon="check" color="#10b981">
  Most applications ALLOW role emails since businesses legitimately use them.
</Card>

## Next Steps

<CardGroup cols={2}>
  <Card title="Syntax" icon="code" href="/validation/syntax">
    Validate email format
  </Card>

  <Card title="Disposable" icon="trash" href="/validation/disposable">
    Block temporary emails
  </Card>
</CardGroup>