The Email Verifier returns several values for each address. This article explains what they mean and recommends how to handle them in your mailing list or form.
status: can I send?
| status | Meaning |
|---|---|
valid |
You can send to this address. This includes addresses where result is risky, such as catch-all domains and role addresses. |
risky |
Delivery is uncertain. |
invalid |
The mailbox or domain doesn't accept email, or the address is invalid. Messages would bounce. |
disposable |
A throwaway address that only exists briefly. |
unknown |
It couldn't be determined. |
result and reason: the finer assessment
| result | Meaning |
|---|---|
safe |
Deliverable. |
risky |
Deliverable, but with some uncertainty. |
invalid |
Not deliverable. |
unknown |
Could not be determined. Not charged. |
The reason field gives the cause:
| reason | Meaning |
|---|---|
accepted |
The mailbox passed the check. |
catch_all |
The domain accepts every address. |
role_account |
A role address such as info@ or support@. |
disposable |
A disposable domain. |
low_quality |
The address has low deliverability. |
rejected |
The mailbox was rejected. |
invalid_domain |
The domain has no mail server. |
null_mx |
The domain explicitly declares that it accepts no email. |
invalid_syntax |
The address format is wrong. |
unverifiable |
The mailbox could not be checked. |
dns_unavailable |
The domain's mail server could not be looked up just now. |
processing_objected |
The person concerned has objected to the processing of their data. |
How to handle them
A proven grouping, also used by FlowSend's list cleaning, is based on status:
| Group | status | Our recommendation |
|---|---|---|
| Valid | valid |
Keep. |
| Invalid | invalid |
Remove or mark as bounced. |
| Disposable | disposable |
Remove, and ideally don't accept them at sign-up. |
| Risky | risky |
Decide case by case. |
| Unknown | unknown |
Decide case by case, never delete for this reason alone. |
This is a recommendation, not a hard rule. For Risky and Unknown there are good options:
- For newsletter sign-ups you send a confirmation email anyway (double opt-in). Anyone who confirms has a working address.
- For existing lists, put risky addresses in a separate list and email them less often instead of deleting them.
- In forms, show a friendly hint such as "Please check your email address" for
riskyorunknown, but still allow the form to be submitted.
If you want to be stricter than status, use result: with "result": "safe" you also filter out catch-all and role addresses that count as valid in status.
Why is a catch-all address still valid?
Some domains accept every address, even made-up ones like xyz123@company.example. From the outside there's no way to tell whether the individual mailbox really exists. Messages are delivered rather than rejected, so status is valid. Because it's uncertain whether a person reads them, result is risky and reason is catch_all. Role addresses work the same way.
What should I do with unknown?
unknown says nothing about the address. Treat it as Unknown. With the reasons unverifiable and dns_unavailable you can try again later. These requests are not charged.
Why do I keep getting the same result?
A result is stored and reused for a while: safe and invalid for 90 days, risky for 30 days and unknown for 3 days. You can tell by "source": "DB". This makes repeat checks fast, but it also means that if a mailbox has changed since, you'll keep seeing the old result until that period ends. You can't force an early re-check of a single address.
For an important address, the simplest option is to ask the person directly or send a confirmation email.
Good to know
- How to call the check is explained in How do I check an email address with the Email Verifier?.
- You can check and clean whole newsletter lists without any code directly in FlowSend, see Verify and clean a list.