Skip to content
BEAD

Email Address List Parser

Parse RFC 5322 address lists with display names, quoted strings, comments, and validation.

TextDeveloper
7 parsed · 6 valid · 1 invalid · 7 final
  • Invalid addresses:
  • not-an-email
RFC 5322 list (6)
Alice O'Brien <alice@example.com>, bob@example.com, Carol Smith <carol@example.com>, dave@example.com, Eve <eve@subdomain.example.com>, "Frank, Jr." <frank@example.com>
Email-only (one per line)
alice@example.com
bob@example.com
carol@example.com
dave@example.com
eve@subdomain.example.com
frank@example.com
JSON
[
  {
    "name": "Alice O'Brien",
    "email": "alice@example.com",
    "valid": true
  },
  {
    "name": "",
    "email": "bob@example.com",
    "valid": true
  },
  {
    "name": "Carol Smith",
    "email": "carol@example.com",
    "valid": true
  },
  {
    "name": "",
    "email": "dave@example.com",
    "valid": true
  },
  {
    "name": "Eve",
    "email": "eve@subdomain.example.com",
    "valid": true
  },
  {
    "name": "Frank, Jr.",
    "email": "frank@example.com",
    "valid": true
  }
]
By domain
  • @example.com — 5
  • @subdomain.example.com — 1

Forms understood

  • alice@example.com
  • Alice <alice@example.com>
  • "Alice O'Brien" <alice@example.com>
  • Comma- or semicolon-separated lists, including newlines
  • Comments in parentheses are dropped

Outputs

Structured JSON, deduped address-only list, formatted RFC 5322 list, and a breakdown by domain.

You might also like