Understanding Results

Field	Meaning
`is_valid`	`true` when the address is deliverable (upstream `status` is `Valid` or SMTP code `250`).
`status`	Upstream verdict, e.g. `Valid` or `Hard Bounce`.
`message`	Human-readable explanation.

Bulk results include extra signals per address:

Field	Meaning
`is_valid`	Deliverable or not.
`is_disposable`	Address is on a known disposable/temporary domain.
`is_role_based`	Role mailbox (e.g. `info@`, `support@`).
`smtp_check`	Whether the SMTP probe ran.
`score`	`100.0` for valid, `0.0` otherwise.
`mx_records`	MX hosts found for the domain (when available).
`reason`	Explanation string.

Valid → safe to send.
Hard Bounce / not valid → remove from your list to protect sender reputation.
Disposable → typically low-value signups; consider blocking at form submission.
Role-based → deliverable but often shared inboxes; segment accordingly.

Field	Meaning
`is_valid`	`true` when the address is deliverable (upstream `status` is `Valid` or SMTP code `250`).
`status`	Upstream verdict, e.g. `Valid` or `Hard Bounce`.
`message`	Human-readable explanation.

Bulk results include extra signals per address:

Field	Meaning
`is_valid`	Deliverable or not.
`is_disposable`	Address is on a known disposable/temporary domain.
`is_role_based`	Role mailbox (e.g. `info@`, `support@`).
`smtp_check`	Whether the SMTP probe ran.
`score`	`100.0` for valid, `0.0` otherwise.
`mx_records`	MX hosts found for the domain (when available).
`reason`	Explanation string.

Valid → safe to send.
Hard Bounce / not valid → remove from your list to protect sender reputation.
Disposable → typically low-value signups; consider blocking at form submission.
Role-based → deliverable but often shared inboxes; segment accordingly.