Every verdict BounceShift can return, what it means, and whether it's safe to send — plus HTTP codes and the exceptions each SDK raises.
Every result carries a status and a 0–100 confidence score. An address is safe to send when its status is valid or catch_all. We report an honest unknown rather than a false valid when a probe is inconclusive — see how we measure accuracy.
| Status | Meaning | Safe to send? |
|---|---|---|
valid |
The mailbox exists and is safe to send to. | Yes |
invalid |
Confirmed undeliverable — bad syntax, no MX records, or no mailbox. Remove it. | No |
risky |
Deliverable but elevated risk — for example a catch-all with no positive signals. | No |
catch_all |
An accept-all domain: the individual mailbox cannot be confirmed. Confidence reflects deliverability likelihood — send with caution. | Yes |
unknown |
We could not determine deliverability: the mailbox provider would not confirm the mailbox, or the receiving server deferred, refused, or did not answer our check. Not the same as invalid, and never charged — the sub_status says which. | No |
disposable |
A throwaway address from a temporary-mail service. | No |
spamtrap |
A spam trap used to catch poor list hygiene. Never send. | No |
abuse |
A known complainer / abuse address. Never send. | No |
do_not_mail |
A forwarding service or an address you should not mail. | No |
Because status is a strict machine value (and risky covers both "unverifiable junk" and "seen delivering reliably, just not SMTP-verified"), every response also includes a plain-English recommendation, a 0–100 quality_score, and an explanation sentence. Use recommendation to decide what to do:
| Recommendation | What it means |
|---|---|
deliverable |
This mailbox is real and can receive mail — safe to send. |
send_with_caution |
Positive signals but not fully verified — reasonable to send, watch for bounces. |
risky |
Little or negative evidence — sending is likely to bounce or hurt your reputation. |
undeliverable |
Confirmed not safe to send — do not mail. |
unknown |
We could not determine deliverability — you are not charged for this. |
An address seen delivering reliably in our network with no bounces returns status: risky but recommendation: send_with_caution with a high quality_score — it is a real, active mailbox, not a warning to avoid it.
Alongside the headline status, each result includes a granular sub_status explaining why. Each description below is the exact sentence a single-address check (POST /v1/validate/single) returns in explanation for that value. In batch results, the sentence about the background re-check queue appears only while that row is still in the queue. Common values include:
smtp_verified — The mailbox accepted mail during a live SMTP check — it exists and can receive email.m365_mailbox_verified — This domain's mail is hosted on Microsoft 365, and Microsoft confirmed an account exists for this exact address — the mailbox is real, even on a domain that accepts every address.delivery_history_strong — Seen delivering reliably in our network with no bounces or complaints — very likely a real, active mailbox. Graded (not directly SMTP-verified) rather than guaranteed.catch_all_unverifiable — An accept-all domain on an established business mail platform, so the individual mailbox cannot be verified — send with caution.mailbox_not_found — The mail server rejected this recipient — the mailbox does not exist.m365_mailbox_not_found — This domain's mail is hosted on Microsoft 365, and Microsoft reports no account for this exact address in that organisation — the mailbox does not exist. Do not send. If you built the address from a name pattern, try another format.msa_mailbox_not_found — Microsoft reports that no Outlook, Hotmail or Live account exists for this address — it is free to register — so the mailbox does not exist. Do not send.no_mx_records — The domain has no mail servers, so it cannot receive email.failed_syntax_check — The address is not correctly formatted.microsoft_accept_all — Microsoft accepted our check, but its consumer mail service (Outlook, Hotmail, Live) accepts every address, real or not, once it starts limiting a verifier — so the accept does not prove this mailbox exists. Reported as unknown, not charged.greylisted — The mail server temporarily deferred our check (greylisting), so we could not confirm the mailbox yet. It says nothing bad about the address. Not charged. This address is in our background re-check queue for up to 7 days after the check (at most 3 attempts). If a re-check settles it, the result in your dashboard updates. Through the API, validate the address again later to get the new answer.host_paced — We postponed this check ourselves: we limit how many checks any one mail server gets from us per minute, so it does not start blocking us, and this server had reached that limit. It says nothing about the address. Not charged. This address is in our background re-check queue for up to 7 days after the check (at most 3 attempts). If a re-check settles it, the result in your dashboard updates. Through the API, validate the address again later to get the new answer.timeout_exceeded — The mail server did not respond in time, so we could not verify the mailbox.smtp_blocked — The mail server blocked our verification IP, so we could not check this mailbox — not the address's fault.mailbox_full — The mailbox exists but is over quota — mail to it would bounce right now.mx_only_unverified — The domain can receive mail, but we could not verify this specific mailbox.mx_lookup_failed — We could not look up the domain's mail servers in time (a slow or unresponsive nameserver) — this says nothing about the address, so we report unknown rather than invalid. Not charged. This address is in our background re-check queue for up to 7 days after the check (at most 3 attempts). If a re-check settles it, the result in your dashboard updates. Through the API, validate the address again later to get the new answer.google_not_probed — We did not run a live check on this mailbox. Large consumer mail providers (Gmail, Outlook/Hotmail, Yahoo, iCloud) do not reliably confirm whether a single mailbox exists, and checking them at volume gets verification servers blocked, so we limit how often we check them — and nothing in our delivery history settles this address either way. Reported as unknown, not charged. This address is in our background re-check queue for up to 7 days after the check (at most 3 attempts). If a re-check settles it, the result in your dashboard updates. Through the API, validate the address again later to get the new answer.microsoft_not_probed / yahoo_not_probed / apple_not_probed — We did not run a live check on this mailbox. Large consumer mail providers (Gmail, Outlook/Hotmail, Yahoo, iCloud) do not reliably confirm whether a single mailbox exists, and checking them at volume gets verification servers blocked, so we limit how often we check them — and nothing in our delivery history settles this address either way. Reported as unknown, not charged.google_unverifiable / google_workspace_unverifiable / microsoft_unverifiable / yahoo_unverifiable / apple_unverifiable — The mailbox provider rejected our check, but the large providers (Google, Microsoft, Yahoo, Apple — including company mail on Google Workspace and Microsoft 365) also reject real addresses when they are checked, to stop address harvesting, so the rejection does not prove this mailbox is missing. Reported as unknown, not charged.did_you_meanEvery response carries a did_you_mean field. It is a corrected address when the domain is within one or two character edits of a major provider, and null otherwise:
{
"email": "grace@gmil.com",
"status": "disposable",
"did_you_mean": "grace@gmail.com"
}
Two things worth knowing about it.
First, it is advisory and never changes the verdict. We validate the address you sent, not the one we suggest — the mailbox at the misspelled domain may genuinely exist. Do not substitute the suggestion silently; show it to the person who typed it and let them confirm. At a signup form, that is a "did you mean grace@gmail.com?" prompt before submit.
Second, it is populated whatever the status, including on addresses we return as valid or disposable. That matters because the misspellings that hurt most are the ones that resolve: gmil.com and hotmial.com are registered and accept mail, so they never bounce and never appear in a bounce report. The suggestion is the only signal you will get about them.
Batch results carry the same value in a did_you_mean column in the results CSV, and the batch view in the dashboard summarises how many addresses had one.
| Code | Meaning |
|---|---|
200 | Success — the address was validated. |
400 | Bad request — invalid parameters, or no organization selected. |
401 | Unauthorized — invalid or missing API token. |
402 | Payment required — insufficient credits. |
403 | Forbidden — the token lacks the required permission, or the organization is invalid. |
404 | Not found — the resource does not exist. |
422 | Unprocessable entity — request validation failed. |
429 | Too many requests — rate limit exceeded (60 requests/minute). |
The official SDKs map error responses to typed exceptions so you can catch each case:
| HTTP | PHP / Laravel | Node |
|---|---|---|
401 | AuthenticationException | AuthenticationError |
402 | InsufficientCreditsException | InsufficientCreditsError |
403 | ForbiddenException | ForbiddenError |
429 | RateLimitException | RateLimitError |
| other | ApiException / BounceShiftException | ApiError / BounceShiftError |
Rate-limit errors expose the retryAfter value; both SDKs also retry 429 and 5xx automatically with a clamped backoff.
Related terms
Upload a CSV and get back the addresses that are safe to send. 100 free credits to start, no card, and no charge for the ones we can't verify.