accepted_email: the mail server accepted the address
valid reason: accepted_email
The receiving SMTP server accepted the mailbox.
What it means
During the SMTP conversation, the domain's mail server accepted the recipient address. The check stops before any message is sent, so the person receives nothing.
On a catch-all domain the server accepts every mailbox, even ones that do not exist, so the acceptance proves nothing about this specific mailbox. In that case EEV does not return valid with accepted_email: the result is unknown with the reason accept_all, accept_all: true and safe_to_send: false.
What to do
- Read
disposable,roleandsafe_to_sendtogether with this reason before you decide. - If all of them are clean, the address is safe to send to.
Example API response
{
"email": "jane.doe@example.com",
"result": "valid",
"reason": "accepted_email",
"disposable": false,
"accept_all": false,
"role": false,
"free": false,
"user": "jane.doe",
"domain": "example.com",
"mx_record": "mx1.example.com",
"mx_domain": "example.com",
"safe_to_send": true,
"did_you_mean": "",
"success": true,
"message": "Processing time: 812 ms",
"http_code": "200"
}
Try it without an account: the API has a free sandbox key, eev_sandbox_key, that returns fixed answers for test addresses such as valid@, invalid@, unknown@ and catchall@sandbox.easyemailverification.com.
Check an address for freeClean a whole list
Related result codes
valid: The receiving mail server confirmed that the mailbox exists and accepts mail.accept_all: The domain accepts mail for any address, so this specific mailbox cannot be confirmed.rejected_email: The domain is real and receives mail, but its server said this mailbox does not exist.- All result codes
- Email glossary: MX records, SPF, DKIM, DMARC, spam traps and more