Skip to main content

​
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.
Typically configured as ALLOW or FLAG since role emails can be legitimate for business signups.

​
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

{
  "checks": {
    "roleEmail": {
      "pass": false,
      "latency": 0.5
    }
  }
}
​
pass
boolean
false if role email detected, true if personal email
​
latency
number
Check execution time in milliseconds

​
Configuration

ALLOW

Most applications ALLOW role emails since businesses legitimately use them.

​
Next Steps

Syntax

Validate email format

Disposable

Block temporary emails