Why an email verification result is "unknown"
unknown
The verification could not reach a reliable answer. The address is neither confirmed nor rejected.
What it means
Unknown is not a polite word for invalid. It means the mail server did not give a usable answer: it did not respond in time, could not be reached, asked to try again later, or reported a temporary problem with the mailbox.
Some mail servers do this on purpose to slow down spammers, and corporate gateways often answer slowly. That is why a share of unknown results is normal in any list, especially for company domains.
Catch-all domains also return unknown, with the reason accept_all: the server accepts every address, so this specific mailbox cannot be confirmed. The email checker and the dashboard show this case as Risky (catch-all), to set it apart from the unknown answers that are free.
Credits: answers with no conclusion because of a timeout, an error or a block by the mail server do not use a credit, so verifying them again later costs nothing extra. Catch-all (accept_all) is the exception: it uses one credit, because the check ran and the domain answered.
Reasons that lead to it
timeout: the mail server did not answer in time. No credit is used.no_connect: the mail server could not be reached. No credit is used.temporarily_blocked: the server greylisted the check and asked to try later. No credit is used.unexpected_error: something failed during the check. No credit is used.unavailable_smtp: the mail server is temporarily not available for mail. No credit is used.accept_all: the domain is catch-all and accepts any address. Uses one credit.
What to do
- Do not treat unknown as valid or as invalid. Decide by risk: for a cold campaign, leave unknown addresses out or send to them in a small, separate batch; for a signup form, accept the address and confirm it by email.
- Verify again later. Timeouts and greylisting often turn into a definitive answer after a few hours.
- Watch the share of unknown in a list. If it is high for a single domain, that domain's server is probably blocking verification, and the answer will not improve by retrying in a loop.
Example API response
{
"email": "jane.doe@example.com",
"result": "unknown",
"reason": "timeout",
"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": false,
"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
timeout: The mail server did not answer the verification in time.temporarily_blocked: The mail server greylisted the check: it asked to try again later.no_connect: EEV could not open a connection to the domain's mail server. No credit is used.accept_all: The domain accepts mail for any address, so this specific mailbox cannot be confirmed.valid: The receiving mail server confirmed that the mailbox exists and accepts mail.- All result codes
- Email glossary: MX records, SPF, DKIM, DMARC, spam traps and more