Skip to content
Docs

Reference

Reference for every email verification result, risk level and check, how the 0–100 score is calculated, and what to do with each kind of address.

Updated Oct 9, 2026

Every verification returns a result, a risk level, a score and the individual checks behind them. This page explains each value so you can decide which addresses to keep, review or remove. The same fields appear in the dashboard, the API and list exports.

Results

Emailit picks the first result in this table that applies, from top to bottom:

Result Dashboard label When Mode
invalid Invalid The address isn’t correctly formed, or its domain doesn’t exist or has no MX records. Both
unknown Unknown The domain’s DNS couldn’t be looked up, so nothing could be checked. Both
disposable Disposable The domain belongs to a temporary or throwaway email service. Both
disabled Disabled The recipient’s server said the mailbox exists but is disabled or inactive. full
inbox_full Inbox full The recipient’s server said the mailbox is full or over its quota. full
invalid Invalid The recipient’s server said the mailbox doesn’t exist. full
catch_all Catch-all The server accepts mail for any address on the domain, including one Emailit made up, so this mailbox can’t be confirmed. full
unknown Unknown The server didn’t give a clear answer: it blocked the check, kept deferring it, timed out or couldn’t be reached. full
role Role The mailbox exists and belongs to a role or team rather than a person, such as info@, support@ or sales@. full
safe Safe The server accepted the mailbox and rejected an address Emailit made up on the same domain. full
role Role A role or team address, such as info@, support@ or sales@. fast
safe Safe None of the above, and the score is 70 or higher. The mailbox itself wasn’t checked. fast
unknown Unknown None of the above, and the score is below 70. Several weaker signals add up, for example a random-looking mailbox on a free provider. fast

In full mode, safe always means the mailbox was confirmed. In fast mode, Emailit never contacts the mail server, so safe only means the address passed the checks that don’t need the mail server. Use full mode when you need to know that a mailbox exists.

How the mailbox check works

In full mode, Emailit connects to the domain’s highest-priority mail server and asks it to accept mail for the address, then stops before anything is sent. It reads the server’s reply, including the extended status code (for example 5.1.1 for an unknown mailbox) and every line of the message.

When the server accepts the address, Emailit asks about a made-up address on the same domain in the same connection. If the server rejects the made-up one, the mailbox is confirmed and the result is safe (or role). If it accepts that one too, the domain is catch-all and the result is catch_all. If the made-up address gets no clear answer, the mailbox isn’t confirmed and the result is unknown. The same goes for a backup server that accepts both addresses when the highest-priority server can’t be reached: backup servers often accept all mail and pass it on later.

A rejection is only counted against the mailbox when it’s about the mailbox. When the server refuses the connection itself, for example because of a blocklist or a policy, the result is unknown, never invalid.

Some servers defer unknown senders for a few minutes (greylisting), and some are briefly unreachable. In a verification list, Emailit checks those addresses again after 5 minutes and after another 15, and only settles on unknown if there’s still no clear answer. Single verifications answer right away, so they return unknown in that case.

Risk

Risk When
high The result is invalid, disabled or disposable, or the score is below 50.
medium The result is catch_all, inbox_full or unknown and the score is 50 or more, or the result is safe or role and the score is from 50 to 79.
low A safe or role address with a score of 80 or more.

Score

The score runs from 0 (certain to fail) to 100 (very likely good). Addresses that can’t receive mail score 0: invalid syntax, a domain that doesn’t exist or has no MX records, a mailbox the server rejected and a disabled mailbox. For everything else, Emailit starts at 100, applies these adjustments and keeps the result between 0 and 100:

Condition Change
Disposable domain −60
Inbox full (full mode) −50
Catch-all domain (full mode) −45
Mailbox not confirmed (full mode) −45
DNS lookup failed −45
Random-looking mailbox (gibberish) −25
Role account −15
Free email provider −5
Has MX records +5
Domain at least 30 days old +10

Examples in full mode:

Address What the server said Calculation Score Result Risk
ada@gmail.com Accepted, made-up address rejected 100 − 5 (free) + 5 (MX) + 10 (old domain) 100 safe low
info@acme.com Accepted, made-up address rejected 100 − 15 (role) + 5 + 10 100 role low
ada@acme.com Accepted every address 100 − 45 (catch-all) + 5 + 10 70 catch_all medium
ada@acme.com Blocked the check 100 − 45 (not confirmed) + 5 + 10 70 unknown medium
x7kq2vz9@gmail.com Mailbox doesn’t exist 0 invalid high
ada@mailinator.com Accepted every address 100 − 60 (disposable) − 45 (catch-all) + 5 + 10 10 disposable high
ada@acme.invalid Not asked: no MX records 0 invalid high

In the dashboard, the score bar is green at 80 and above and shifts toward red as the score drops.

Checks

Each verification includes a checks object. A check is null when it didn’t run or got no clear answer: in fast mode, the checks marked full are always null.

Check Type Mode Meaning
valid_syntax boolean Both The address follows email syntax rules, including international characters.
has_mx_records boolean or null Both The domain publishes MX records, so it can receive mail. null when the DNS lookup failed.
domain_age integer or null Both Age of the domain in days, from WHOIS. null when it can’t be determined.
disposable boolean Both The domain, or a domain it belongs to, is a known temporary or throwaway email service.
role_account boolean Both The mailbox is a role address, such as info, admin or support.
free_email boolean Both The domain is a free email provider, such as Gmail or Yahoo.
gibberish boolean Both The mailbox looks randomly generated.
smtp_connect boolean or null full The domain’s mail server answered Emailit’s connection.
deliverable boolean or null full true: the server accepted the mailbox and rejected a made-up one. false: the server rejected the mailbox, or the domain can’t receive mail. null: not confirmed, for example on a catch-all domain or when the server didn’t answer clearly.
disabled boolean or null full The server said the mailbox is disabled or inactive.
inbox_full boolean or null full The server said the mailbox is full or over quota.
catch_all boolean or null full The domain accepts mail for any address, so the specific mailbox can’t be confirmed.

In the dashboard, a check that didn’t run in fast mode shows Not checked, and one without a clear answer in full mode shows Unknown.

Other fields

Field Description
id Starts with ev_ for single verifications and evr_ for addresses in a list.
email The address you verified.
status pending, processing, completed or failed. Single verifications return completed. A list item is failed when an error stopped the check; its result is then error, and it’s counted in the list’s failed_verifications, not in results.
mode fast or full.
address.mailbox The part before @, without any + tag. For ada+news@acme.com, that’s ada.
address.domain The part after @.
address.suffix The + tag, such as news, or null.
address.root The address without the + tag, such as ada@acme.com.
did_you_mean A suggested correction for a likely typo in the domain, such as ada@gmail.com for ada@gmial.com, or null.
mx_records The domain’s MX records, each with priority and exchange, sorted by priority.
created_at, updated_at Timestamps. Results are deleted 30 days after created_at.
Result What to do
safe Send.
role Fine for transactional and business mail. For marketing, send only if the address opted in, and watch complaints.
catch_all The domain takes everything, so a bounce can still come later. Send if the address opted in, keep catch-all addresses out of the first sends on a new domain, and watch bounces from that domain.
unknown Verify again later. If it stays unknown, send with care and leave it out of the first sends on a new domain.
inbox_full Pause sending and verify again later. Remove it if it stays full.
invalid Remove the address. At sign-up, ask the person to correct it, and show did_you_mean if there is one.
disabled Remove the address. The mailbox no longer accepts mail.
disposable Don’t add it to marketing lists. At sign-up, ask for a permanent address.
Verify in the dashboard or with the API.
Check up to 10,000 addresses and export them.
What happens when an address bounces.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.