Article
What Does Deliverable Mean in Email Verification? A Clear Definition
By Unlimited Verifier Team ·

Summary
In email verification, a deliverable address is one where the verifier found no evidence the recipient's mail server will reject mail, usually confirmed by a 250 reply to RCPT TO. Deliverable predicts server acceptance, not inbox placement, which depends on spam filtering, authentication and sender reputation.In email verification, deliverable means the verifier expects the recipient's mail server to accept mail for that address, usually confirmed by a 250 reply to the SMTP RCPT TO command. It predicts server acceptance, not inbox placement.
The word is overloaded. Vendors use "deliverable," "valid," "safe" or "good" for similar outcomes, and they draw the line in different places. This guide explains what the term measures, what it doesn't, how to read each category, and how to calculate a deliverable rate for your own list. For the wider mechanics, start with our pillar on how email verification works.
Quick answer
- Deliverable means the address passed the checks that predict server acceptance: well-formed syntax, a domain that accepts mail, and a mailbox the server did not reject at RCPT TO.
- Deliverable is not the same as inboxed. Verification can't see spam filtering, authentication, sender reputation or whether the person reads your mail.
- Most tools sort addresses into three buckets. Unlimited Verifier uses Valid, Risky and Invalid. Only Valid meets the definition on its own. Risky addresses are unconfirmed.
- Your deliverable rate is Valid ÷ total addresses checked. Track it per source, because one imported segment usually drags the whole list down.
What does "deliverable" mean in email verification?
A deliverable address is one where the verification run found no evidence that the server will reject mail for it. The verifier follows the same early steps a sending server would, then stops before any message body is transmitted.
A typical SMTP-level check runs in four stages:
- Syntax check. Is the string a well-formed address? Our guide to what syntax validation for email addresses covers explains the rules involved.
- Domain and MX lookup. Does the domain publish mail exchanger (MX) records that point to live servers? How verifiers check if a domain accepts mail walks through this step.
- SMTP handshake. The verifier connects to the server and sends
RCPT TO:<address>. What RCPT TO means in email verification covers this command in detail, and how an email verifier checks if an address exists covers the full sequence. - Response reading. A 250-class reply means the recipient is accepted. A 5xx reply is a permanent rejection. A 4xx reply is a temporary deferral.
RFC 5321 defines these reply classes. RFC 3463 adds enhanced status codes that give the reason. 5.1.1 means the destination mailbox doesn't exist, and 5.2.2 means the mailbox is full. A verifier that reads those codes can separate "this person doesn't exist" from "this person's inbox is full today."
Here is the practical catch. A 250 reply is strong evidence only if the server actually checks each recipient. Some domains accept every address, and for those the 250 proves nothing about the specific mailbox. An address is deliverable when the sequence ends in acceptance and no risk signal contradicts it.
Bottom line: Deliverable is a prediction about server acceptance, built from DNS and SMTP evidence. It stops short of the mailbox itself.
Why doesn't "deliverable" guarantee the email reaches the inbox?
Verification sees only the first of several layers between your send button and the reader's screen. Each layer needs its own fix, and only the first one is in a verifier's view.
| Layer | Question it answers | Can email verification see it? |
|---|---|---|
| Address syntax | Is the address well-formed? | Yes |
| Domain and MX | Does the domain accept mail? | Yes |
| Mailbox acceptance | Does the server accept this recipient at RCPT TO? | Mostly, but accept-all servers blur it |
| Authentication | Are SPF, DKIM and DMARC aligned for your sending domain? | No |
| Reputation and filtering | Does the message land in the inbox or the spam folder? | No |
| Engagement and consent | Did the person opt in, and do they open or click? | No, it needs your own data |
Complaints are where a deliverable list still hurts you. Google's sender guidelines recommend keeping the user-reported spam rate below 0.1% and warn against letting it reach 0.3%. That rate depends on consent and content, not on whether the address exists. A perfectly deliverable address on a list nobody opted into will still produce complaints. Yahoo's sender requirements set their own complaint expectations for bulk senders.
Verification also can't reliably identify spam traps, which are addresses that providers or blocklist operators use to catch senders who mail stale or purchased lists. A trap often answers like a live mailbox, so it can pass as deliverable. Consent and regular removal of inactive contacts protect you here far better than any single check.
Bottom line: Treat deliverable as the first gate, not the finish line. Authentication, content, engagement and consent decide whether the message is seen.
What do Valid, Risky and Invalid actually mean?
Each category reflects a level of confidence about acceptance. Read them as confidence levels, not as labels.
| Category | Typical evidence | Example reason | Counts as deliverable? | Recommended action |
|---|---|---|---|---|
| Valid | Mailbox accepted at RCPT TO, no risk flags | 250 at RCPT TO | Yes | Send |
| Risky | Accept-all domain, disposable or role address, temporary deferral, full mailbox | 4xx deferral; 5.2.2 mailbox full; accept-all server |
Unconfirmed | Test with small sends, or hold |
| Invalid | Permanent rejection, bad syntax, no working mail server | 550 5.1.1 unknown mailbox; no MX |
No | Suppress |
Some tools add an Unknown bucket for timeouts or servers that never finish the handshake. Treat Unknown like Risky, not like Valid.
Risky is where most mistakes happen, because it mixes situations that need different handling:
- Accept-all (catch-all) domains accept every address, so the server's answer says nothing about the specific mailbox. What accept-all means in an email verifier explains the term, and how verifiers detect catch-all domains covers detection. How bounce-based catch-all verification works shows how to get more signal from these domains.
- Disposable addresses come from throwaway providers. How verifiers detect disposable email domains explains the lists involved.
- Role addresses like
info@orsales@usually exist, but they are shared inboxes with lower engagement. - Temporary failures can clear on a retry. Greylisting, a busy server or a full mailbox can all look Risky on the first pass.
Unlimited Verifier sorts each address into Valid, Risky or Invalid and flags catch-all, disposable and role-based addresses, so you can see why something is Risky rather than guessing.
How do you check a catch-all domain before trusting a Valid result?
Practitioners often probe the domain with a made-up address, such as a random string at the same company domain. If the server accepts the made-up address, the domain accepts everything, and a Valid result on that domain tells you little about the individual mailbox. Those addresses belong in your test segment, not your first full send.
Bottom line: Valid is the category that meets the definition on its own. Risky needs a decision, and Invalid should be suppressed.
Which definition of deliverable should you use?
Decide what counts as deliverable for your use case before you count anything. Three definitions cover most situations.
| Definition | Counts as deliverable | Best for | Trade-off |
|---|---|---|---|
| Strict | Valid only | Cold outreach, lists after a suspension, purchased or scraped data | Lowest bounce risk, smallest audience |
| Balanced | Valid, plus Risky addresses with engagement in the last 90 days | Opted-in newsletters and product updates | Moderate risk; needs activity data |
| Inclusive | Valid plus all Risky | Transactional mail to customers who expect it | Catch-all bounces add up quickly |
Start strict. Plan around a bounce ceiling of 2% or lower on your first sends. Sources disagree on the exact limit. Amazon SES's documentation describes accounts coming under review at a 5% bounce rate and possibly being paused at 10%. Other platforms act earlier and publish no exact figure. The 2% planning target leaves room below those triggers, so use it as your default and widen the definition only after measured sends show a segment is safe.
Bottom line: Choose the definition by use case, then measure. Strict protects sender reputation, and inclusive protects reach.
How do you calculate your deliverable rate?
Your deliverable rate is the share of your list that verifies as Valid. It is the single number to track across sends:
Deliverable (strict) rate = Valid addresses ÷ total addresses checked × 100
Calculate it per source as well as for the whole list. A 75% overall rate can hide a 50% rate on one imported segment, and that segment is where your bounces will come from.
Also calculate the inclusive rate (Valid plus Risky). The gap between the two tells you how much of your list depends on unconfirmed addresses. A wide gap points to an accept-all problem, not an accuracy problem, and it is the number to watch when you decide whether to test Risky addresses.
Bottom line: Track two numbers per source, the strict rate and the inclusive rate. The gap between them is the share of your list that depends on Risky addresses.
How do you measure deliverability, step by step?
Use this sequence before any large send and after any bounce spike.
- Write your definition. Choose strict, balanced or inclusive, and record the reason in one sentence.
- Tag every address by source. Note where it came from: signup form, purchase, trade-show scan, old CRM export, partner list. Source tags are how you find the problem segment.
- Verify the full list. Check syntax, domain, MX and the SMTP mailbox, and flag accept-all, disposable and role addresses.
- Calculate rates by source. Work out the strict and inclusive rates for each tag.
- Route each bucket. Send Valid first. Suppress Invalid. Test Risky with a small batch and watch the result.
- Compare predicted with actual. After each send, set the bounce rate you observed against the rate you predicted from the strict and inclusive numbers. If they diverge, re-verify that segment, because the list has likely aged.
Re-verify on a schedule. People change jobs and mailboxes close, so a list verified six months ago is already out of date. Email list maintenance best practices covers cadence, and real-time email validation covers stopping bad addresses at the point of signup.
Bottom line: Measure by source, route by category, and compare predicted with actual bounces after every send.
How do you calculate your deliverable rate in Unlimited Verifier?
This takes about 15 minutes for a list under 25,000 rows.
Export your contacts as CSV. Include the email column, a source field and, if you have one, a last-activity date. The activity date helps you rank Risky addresses later.
Sign up. The Free plan covers 25 lists a month of up to 150 emails each, with 750 deep verifications. Test a small segment there before you commit to a larger run.
Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Confirm that the detected column is the one you expect.
Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Accept-all, disposable and role addresses are flagged.
Read the three buckets. Valid is deliverable. Risky needs routing. Invalid is suppressed.
Export the results as CSV, Excel or JSON. Results on the Free plan are kept for 24 hours, so export the same day. Pro results are kept for 30 days.
Calculate the rate in a spreadsheet. Suppose emails are in column A (rows 2 to 40,001) and the category is in column D. Then:
- Strict rate:
=COUNTIF(D2:D40001,"Valid")/COUNTA(A2:A40001) - Inclusive rate:
=(COUNTIF(D2:D40001,"Valid")+COUNTIF(D2:D40001,"Risky"))/COUNTA(A2:A40001)
Adjust the column letters and row range to match your export.
- Strict rate:
Repeat per source. Filter by your source tag and run the same formulas for each segment.
For a single address, such as a VIP contact that came back Risky, use the free email checker. To see how accept-all results are handled, read the catch-all email verification page.
Bottom line: Export, verify, filter by category, and calculate the rate per source before you send anything.
What does a deliverable rate look like on a real-sized list?
This example is illustrative. The results are hypothetical, but the arithmetic and plan limits are real.
The list: 40,000 contacts from a trade-show scan (15,000), a partner export (10,000) and website signups (15,000).
Splitting for the plan limit: The Pro plan allows lists of up to 25,000 emails each, so upload two files: 25,000 and 15,000. The Free plan can't do this in one month. It allows 25 lists of 150 emails, which caps out at 3,750 emails. Covering 40,000 would take at least 267 lists (40,000 ÷ 150 = 266.7, rounded up).
Hypothetical results:
| Category | Count | Share |
|---|---|---|
| Valid | 31,200 | 78.0% |
| Risky | 6,400 | 16.0% |
| Invalid | 2,400 | 6.0% |
Rates:
- Strict deliverable rate: 31,200 ÷ 40,000 = 78%
- Inclusive rate: (31,200 + 6,400) ÷ 40,000 = 94%
- Invalid share: 2,400 ÷ 40,000 = 6%
The Invalid share matters on its own. If you mailed those 2,400 addresses unfiltered, the hard bounces alone would put the send at 6%, above the 5% level where SES documentation describes review. Suppressing them is not optional.
Breaking down the Risky bucket: The 6,400 addresses split into 3,900 accept-all, 1,700 role and 800 disposable addresses.
- Disposable (800): Suppress. There is little reason to keep them.
- Role (1,700): Keep only if this is a B2B announcement list where a shared inbox is the intended recipient. Otherwise, hold them.
- Accept-all (3,900): Send a 200-address test batch to these domains first. If the batch bounces under 2%, widen the send. If not, hold the segment.
Deep-check budget: If you run deep verification on the 6,400 Risky addresses, that uses 6,400 of the Pro plan's 25,000 monthly deep verifications, leaving 18,600 for re-checks. Standard verification of the full 40,000 is unlimited and carries no per-email fee.
Cost: The Pro plan is $29 a month, or $25 a month billed annually. If you use all 25,000 deep verifications in one month, that is about $1.16 per 1,000 deep checks on the monthly plan ($29 ÷ 25), or $1.00 on the annual plan ($25 ÷ 25).
A smaller example on Free: A 3,000-row list needs exactly 20 files of 150 emails (3,000 ÷ 150 = 20). That fits inside the Free plan's 25-list monthly allowance, so you can verify it without paying. Export the results within 24 hours.
Bottom line: A 40,000-row list produced 78% strict and 94% inclusive deliverability in this example, and a $29 monthly plan covers the whole run.
Which verification approach fits your team?
The right approach depends on how often your list changes. A team importing leads every week needs checks at signup, while a team sending a quarterly newsletter can batch-verify before each send. Compare options using the best email verification tools guide and the buyer's checklist for choosing an email verifier.
| Approach | Best for | How it runs | Unlimited Verifier limits |
|---|---|---|---|
| Single-email checker | One-off checks, such as a disputed contact | Free web tool, one address at a time | Free email checker |
| Batch CSV or Excel | Periodic list cleans before a send | Upload, verify, export | Up to 150 emails per list on Free; up to 25,000 per list on Pro |
| REST API | Signup forms, continuous imports, automation | Single checks or batches of up to 10,000 per request | API access on Pro, with 100,000 emails a month; not on Free |
Standard verification is unlimited on every plan. Deep verification is metered, at 750 a month on Free and 25,000 a month on Pro. Deep email verification vs standard verification explains the difference. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. When you compare email verification pricing across tools, include the metering model. A low per-check price can cost more if you need to re-run lists often.
Teams running ecommerce or SaaS signups fit the API approach best. Teams with a spreadsheet-based workflow fit batch uploads best. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so the workflow is export, verify, and re-import, or calling the email verification API from your own scripts. Teams that rely on connectors will find that less convenient. For more on how these workflows fit together, see email verification API and automation and email verification for ecommerce and SaaS.
Bottom line: Batch uploads suit periodic sends. API checks suit signup and continuous imports, and both return the same three categories.
What mistakes make deliverable rates misleading?
- Treating Risky as Valid. Accept-all and role addresses can pass a handshake and still bounce or go unread. Route them separately.
- Assuming deliverable means consented. A valid mailbox isn't an opted-in one. Verification doesn't replace documented consent and unsubscribe handling, which is the core of email verification compliance and hygiene.
- Calculating one overall rate. The problem segment disappears inside a healthy average. Break rates down by source every time.
- Spending deep checks on addresses you already know. Deep verifications are metered, so reserve them for the Risky and high-value contacts where the extra check changes your decision.
- Losing results before export. Free-plan results are kept for 24 hours. Export the same day.
- Comparing rates across vendors. Two tools can label the same address differently. Compare your own runs against your own bounce data, not another vendor's labels.
- Ignoring data age. If a large share of your list is Yahoo or AOL, check how verification handles those domains before you trust the rate.
- Confusing an old verification with a current one. A list verified months ago has decayed. Re-verify before any major send.
Bottom line: Most misreadings come from merging categories, skipping source breakdowns, or trusting a snapshot that has aged.
How we compared (and limitations)
This article is based on public documentation: RFC 5321 and RFC 3463 for SMTP reply and status codes, Google's and Yahoo's sender guidance, and Amazon SES's published bounce thresholds. We have not tested any verifier against mailbox providers, and we have not measured how any provider classifies addresses.
Thresholds, status-code usage and provider behaviour change over time, and platforms define their limits differently. Use the 2% planning ceiling as a practical default, then confirm it against your own platform's rules.
Unlimited Verifier's 99.5% deep-verification accuracy is the company's stated figure. Its verification engine is open source at github.com/unlimitedverifier/free-email-verifier, so you can read the checking logic directly. The worked-example percentages are hypothetical. Plan limits and prices are the ones listed on the product pages.
To measure your own deliverable rate, upload a list and verify it, then compare the Valid share with your bounce data after the first send.
Reading verifier categories
| Result | Meaning | Deliverable on its own? |
|---|---|---|
| Valid | Server accepted RCPT TO, no risk signals | Yes |
| Risky | Catch-all, deferral or unconfirmed | No, unconfirmed |
| Invalid | Syntax error, no MX, or 5xx rejection | No |
Deliverable rate = Valid ÷ total checked × 100. Example: 8,200 Valid out of 10,000 checked = 82%.
Frequently asked questions
Is deliverable the same as valid in email verification?
Not always. Deliverable usually means the server accepted the address at RCPT TO. Valid is a vendor label that may use different thresholds, so check how each tool defines its categories before comparing results.
Does a deliverable email address mean it will reach the inbox?
No. Deliverable only predicts that the recipient's server will accept the message. Spam filters, authentication such as SPF, DKIM and DMARC, and sender reputation decide inbox placement.
What does a 250 response mean during verification?
A 250 reply to RCPT TO means the receiving server accepted the recipient. It is strong evidence only when the server checks each mailbox, because catch-all domains return 250 for any address.
What is a catch-all domain?
A catch-all domain is one whose mail server accepts mail for any address at that domain, real or not. Verifiers usually mark these addresses as risky because a 250 reply cannot confirm the specific mailbox exists.
What is a risky email address?
A risky address is one the verifier could not confirm either way. Common causes include catch-all domains, greylisting, temporary 4xx deferrals and servers that block verification probes. Risky addresses are unconfirmed, not proven bad.
How do you calculate deliverable rate?
Divide the number of Valid (deliverable) addresses by the total number of addresses checked, then multiply by 100. Calculate it per source list, since one poorly sourced import can lower the rate for the whole database.
Why does an address return 5.1.1 or 5.2.2?
These are enhanced status codes from RFC 3463. 5.1.1 means the destination mailbox does not exist. 5.2.2 means the mailbox is full. Reading the code separates a nonexistent person from a temporarily full inbox.
Can email verification guarantee an address is deliverable?
No verifier can guarantee delivery. Mailboxes can be deleted, filled or disabled after checking, and some servers hide their responses. Verification reduces risk and bounces but does not eliminate them.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.