What does the small status badge on the dashboard widget represent?
The Single Email Verifier on the dashboard returns a small coloured badge next to the verified address. The badge is the canonical status enum from the Valid Email Checker engine — Safe, Risky, Invalid, Disposable, Catch-All, Role Account, Spam Trap, Disabled, Inbox Full, or Unknown. Each status maps to a specific colour so you can scan a list of recent verifications at a glance without reading every label.
The status comes directly from the verification engine through the mapProviderStatusToDb function in our edge function code. Whether the underlying provider was Reoon or EmailListVerify, the badge always shows our canonical enum value — never a provider-specific label.
The colour key for the badge
| Status | Colour | What it means in one line |
|---|---|---|
| Safe | green | Mailbox confirmed; clean to send. |
| Risky | orange | Real mailbox but warning signals present. See Risky. |
| Invalid | red | Mailbox does not exist or syntax is broken. See Invalid. |
| Disposable | orange | Throwaway provider like Mailinator. See Disposable. |
| Catch-All | purple | Domain accepts any address; specific mailbox unverifiable. See Catch-All. |
| Role | indigo | Function mailbox like info@ or sales@. See Role. |
| Spam Trap | red | Honeypot address; do not send. See Spam Trap. |
| Disabled | gray | Mailbox turned off by the provider. See Disabled. |
| Inbox Full | yellow | Over quota right now. See Inbox Full. |
| Unknown | gray | No definitive answer. Credit auto-refunded. |
Clicking the badge opens the full result
The dashboard widget shows the badge as a quick summary; clicking it opens a modal with the complete breakdown. The modal shows the confidence score, the deliverability flag, syntax validity, whether MX records were found, whether the domain is catch-all, whether the address is a role account, whether it appears disposable, and a free-form reason field explaining the verdict.
The same data is available through the API if you are running verifications programmatically — see how to verify a single email with the API.
Why a colour-coded badge instead of plain text
Quick scanning matters when you are running 30 verifications in a session before a send. Plain-text labels force you to read each one; a coloured badge lets you spot the one orange Risky in a sea of green Safe in a fraction of a second. For accessibility, the colour is paired with the text label so colour-blind users see the same meaning through the text channel.
For the underlying confidence score that drives the badge colour, see what does the confidence indicator on results mean.
Related questions
Still stuck? Email support
