Email Verification — Sample Output (JSON)

Generated: 2026-06-06. Download: Download JSON

Source & provenance: Mock addresses used for illustration (no real personal data). Live runs verify the addresses you submit.

Sample addresses are mock. Verification reflects checks performed at run time and does not guarantee deliverability.

Sample output

[
  {
    "email": "jane.doe@example.com",
    "status": "valid",
    "reason": "accepted",
    "is_role_account": false,
    "is_disposable": false,
    "is_free_provider": false,
    "smtp_response_code": 250
  },
  {
    "email": "info@example.com",
    "status": "risky",
    "reason": "role",
    "is_role_account": true,
    "is_disposable": false,
    "is_free_provider": false,
    "smtp_response_code": 250
  },
  {
    "email": "user@mailinator.com",
    "status": "invalid",
    "reason": "disposable",
    "is_disposable": true,
    "is_free_provider": false
  }
]

Run it live

Open the actor on Apify → Pay-per-result, $5/month free credit. Live runs return current data.

Learn more: buyer guide · compare tools · cluster hub.

FAQ

Are these real emails?

No — they are mock addresses for illustration.

Does a 'valid' result guarantee delivery?

No verification can guarantee deliverability; it reflects syntax, MX, and SMTP checks at run time.

What gets flagged?

Disposable, role, catch-all, and free-provider addresses, with a status and reason.