Article

Does a Valid Email Result Mean It Will Be Delivered? What the Check Proves

By Unlimited Verifier Team ·

Diagram showing the four email delivery gates, where email verification only tests the mailbox existence gate.

Summary

A valid email result means the receiving server accepted the address with an SMTP 250 reply when checked, so the mailbox likely existed at that moment. It does not guarantee delivery, because mailbox state, filtering, sender authentication and engagement all happen after the check.

A valid result does not guarantee delivery: it means the recipient's mail server accepted the address with an SMTP 250 reply when the verifier checked it, so the mailbox probably existed at that moment. Inbox placement depends on what happens after that check, including filtering, mailbox state, sender authentication and engagement.

Delivery is a chain of four gates. The mailbox must exist, the server must accept the message, filters must let it through, and the message must reach the inbox rather than spam. Verification tests the first gate and only part of the second. For how accurate those results are, see our pillar on email verifier accuracy.

Quick answer

What does a valid result actually prove?

A valid result proves that a receiving server was willing to accept mail for an address at one moment. Most mailbox-level verifiers use SMTP, the protocol defined in RFC 5321 for moving mail between servers. The verifier connects to the domain's mail exchanger (MX) and issues a RCPT TO command naming the address. A 250 reply means the server will accept mail for that recipient. A 550-series reply is a rejection. Enhanced codes such as 5.1.1, which means bad destination mailbox, are defined in RFC 3463 and mark a permanent failure.

Verifiers generally stop after the recipient step, before any message body is sent, so the check does not put anything in an inbox.

The reply is a snapshot. It records willingness at that second and says nothing about what follows: a mailbox filling up, an account closing, a filter routing your message to spam, or a recipient who never wanted it. A Valid address that later bounces is a false positive, as explained in what is a false positive in email verification.

Bottom line: A valid result is evidence of existence at the time of the check. It is not a prediction of inbox placement.

Why can a valid address still fail to deliver?

A valid address fails at the later gates because the check never sees those conditions. Each failure has a different cause.

Bottom line: Valid tells you the mailbox existed at the check. Inbox placement depends on what happens afterwards, most of which you control through sending practice.

Which verification signals prove deliverability, and which don't?

Only the SMTP response speaks directly to existence. The other signals describe the address type, your sending identity or the recipient's behaviour. When you compare best email verification tools, check whether each one reports these signals separately, because a single Valid label hides them. Our guide on how to choose an email verifier lists the questions to ask.

Signal What it proves What it cannot prove Effect on delivery
Syntax check Format is legal That the address exists Removes typos; little value alone
Domain and MX check Domain can receive mail That a specific mailbox exists Catches dead or parked domains
SMTP mailbox response Server accepted the recipient at check time Future state, filtering, inbox placement Strongest existence signal; weaker on some providers
Catch-all detection Domain accepts any address Whether this mailbox exists Should move the address to Risky
Disposable and role flags Address type Consent or intent Predicts low engagement and complaints
Engagement history Recent interest Current validity Predicts opens and complaints better than verification does
SPF, DKIM and DMARC Your sending identity is authenticated Recipient address quality Required for bulk senders; separate from list checks

The last row is the one most teams skip. Because authentication is set on your domain, a clean list still underperforms if the mail it carries is unauthenticated.

Bottom line: Only the SMTP response speaks to existence. Engagement, authentication and filtering decide whether an existing mailbox actually sees your message.

How should you act on Valid, Risky and Invalid results?

Send to Valid contacts first, test Risky contacts with a small batch, and suppress Invalid contacts permanently. The table gives a practical default for each tier.

Result What it usually means Delivery expectation Action
Valid Mailbox accepted at check time Highest existence confidence Send first, to recently engaged contacts
Risky Existence can't be confirmed, for example catch-all, disposable or role-based Uncertain; may bounce or be filtered Hold back; test with a small send
Invalid Mailbox rejected or domain unusable Likely undeliverable Suppress permanently and keep a copy

Catch-all domains need the most care. A catch-all server accepts every address, so a Risky result there means the mailbox could not be confirmed, not that it is fine. Unlimited Verifier sorts results into these three buckets and flags disposable and role-based addresses separately, so an info@ address can be handled differently from a catch-all personal inbox. Catch-all email verification explains how those addresses are treated.

Some verifiers return an "unknown" category instead of Risky. If many results come back that way, read why does my verifier return so many unknowns before deciding what to send.

Bottom line: Valid is where sending starts. Risky is where you test. Invalid is where you stop.

How do you turn valid results into delivered mail?

Verification clears the first gate and part of the second. The six steps below cover what it cannot.

  1. Read the definitions in your tool. Confirm what Valid, Risky and Invalid mean and which flags sit behind each one. Verifiers disagree on edge cases, as explained in why different email verifiers give different results.
  2. Suppress known failures first. Remove past hard bounces, unsubscribes and complaints before anything else. A fresh verification does not undo a history of complaints.
  3. Segment Valid contacts by engagement. Send first to people who opened or clicked in the last 30 to 90 days. Engaged recipients complain less, and complaints can hurt you as much as bounces.
  4. Confirm authentication before the first send. Check that SPF or DKIM passes and that DMARC is published for your sending domain, as RFC 7489 describes.
  5. Ramp and measure each send. Increase volume in stages and track bounces and complaints per send, not only in aggregate.
  6. Re-verify on a schedule. Our rule of thumb is to re-verify active lists every 90 days, and any list older than six months before a large send. This is a practitioner guideline, not an industry standard. For a fuller operating plan, see email list maintenance best practices.

Bottom line: Verification gets you to the first gate. Engagement, authentication and ramping get you through the rest.

How do you verify a list and sort the valid addresses?

You can take a CSV from export to a suppression-aware re-import in about seven steps. Teams running email verification for ecommerce and saas programmes often repeat this monthly. The steps below use Unlimited Verifier, but the logic applies to any verifier that accepts CSV or Excel.

  1. Export your contacts as a CSV. Include the email column and, if you have them, a last-engaged date and a source field. The source field helps you trace where bad addresses came from later.
  2. Sign up for a free account. The Free plan covers 25 lists a month, each up to 150 emails, plus 750 deep verifications a month. Standard verification is unlimited on every plan, with no per-email fees. Free has no API access.
  3. Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. As a rough estimate, a row with an email and a few short fields is about 60 bytes, so 25,000 rows is around 1.5MB. Your file will vary.
  4. Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged.
  5. Sort the results. Move Valid contacts into a send-now segment, hold Risky contacts in a separate segment, and suppress Invalid contacts in your ESP.
  6. Export and save the results. Download the file as CSV, Excel or JSON and store the counts with the date. Free plan results are kept for 24 hours and Pro for 30 days, so save your own copy.
  7. Re-import, or automate. There are no native ESP, CRM or Zapier integrations, so re-import the Valid segment and suppression list manually. For checks at signup or on every import, use the email verification API and automation through your API keys. The API supports single-email checks and bulk batches of up to 10,000 emails per request, and Pro includes API access at 100,000 emails a month. For signup forms, real-time email validation explains the trade-offs. For a one-off check of a single address, the free email checker is quicker.

Bottom line: Export, verify, sort, save and re-import. The saved counts are what let you prove the list was cleaned.

What does a 25,000-contact list look like on the Pro plan?

A 25,000-row list fits in one Pro upload, and in the illustrative split below about 84% of it is sendable on the first day. The figures are illustrative, but the plan limits are real.

Starting point: A 25,000-row list. Pro allows lists of up to 25,000 emails, so the whole file goes up in one pass.

Illustrative results:

Check: 21,000 + 2,600 + 1,400 = 25,000.

What the arithmetic shows:

A 60,000-contact list needs three Pro uploads: 25,000 + 25,000 + 10,000. Via the API, the same list would take six requests of 10,000 emails each (60,000 ÷ 10,000) and use 60,000 of Pro's 100,000 monthly API emails. On the Free plan, the list limits are 150 emails per list and 25 lists a month, so the most you can upload in list form is 3,750 emails a month (25 × 150). That is why the 25,000-row example needs Pro.

Bottom line: Splitting the list into Valid, Risky and Invalid turns a 5.6% bounce risk into a sendable segment of 84% of the list, with a clear audit trail.

Does a valid result mean the contact has opted in?

No. Verification tests whether an address can receive mail, not whether the person agreed to hear from you. Those are separate questions, and confusing them is a common email verification compliance and hygiene error.

In the United States, the FTC's CAN-SPAM guide sets the baseline for commercial email, including accurate headers, a working opt-out and honouring opt-out requests within the legal timeframe. In the UK and EU, consent rules for marketing email are generally stricter, so a Valid result carries even less compliance weight there. Check the current guidance for your jurisdiction.

Bottom line: Valid means reachable, not permitted. Keep consent records and opt-out handling separate from your verification results.

What bounce rate should valid addresses produce?

Keep total hard bounces under 2% and aim for under 1% on your first sends after cleaning. Sources disagree on the exact threshold. AWS documents 5% as the level at which SES accounts go under review and 10% as a pause trigger. Google's guidance for bulk senders is framed around spam complaints rather than bounces, at 0.1% and 0.3%. Many other platforms act earlier and don't publish their thresholds. We recommend the 2% ceiling because it leaves room before any platform's automated trigger.

Bounces on a cleaned list are the real test of your verifier, so break them out by segment:

Symptom Likely cause Action
Bounces concentrated in Risky or catch-all sends Catch-all domains accepting mail that is never delivered Hold back, or test with a small send
Bounces on Valid addresses verified within the last 30 days Mailbox closed or filled after the check Read the reason code; suppress 5.x codes, retry 4.x codes later
Bounces on Valid addresses verified six or more months ago List decay Re-verify before the next large send
Valid addresses landing in spam Authentication gaps, complaints or unengaged contacts Check SPF, DKIM and DMARC; send to engaged segments first
Microsoft 365 addresses giving mixed results Some providers return ambiguous answers to SMTP checks Treat as Risky; see how accurate verifiers are on Microsoft 365 addresses

For expected results across a full clean, see what bounce rate to expect after email verification.

Bottom line: If bounces on Valid addresses stay under 1%, verification is doing its job. If they climb past 2%, look at decay and catch-all domains before blaming the tool.

What mistakes make valid results misleading?

Most disappointing outcomes come from treating Valid as a promise instead of a snapshot.

Bottom line: Treat Valid as a dated snapshot, keep your own records, and fix authentication and engagement alongside the list.

How we compared (and limitations)

This article is based on public documentation: RFC 5321, RFC 3463, RFC 7489, Google's sender guidelines, AWS's SES documentation and the FTC's CAN-SPAM guide. We have not run controlled delivery tests across mailbox providers, and we have not benchmarked any verifier's results against inbox placement. Platform thresholds change without notice, so check current documentation before you set a policy.

The 99.5% accuracy figure is Unlimited Verifier's own stated figure for deep verification, not an independent benchmark. The verification engine is published as open source on GitHub, so its checks can be read directly, though open source does not by itself show accuracy. The worked example uses illustrative results and an assumed residual bounce rate, not measured data. For independent comparisons, see the independent email verifier accuracy benchmark 2026, and for the wider picture, read how accurate is email verification really?

Bottom line: Use the figures here as a starting point, then measure the bounce rate on your own Valid segment.

Worked example: valid result, failed delivery

Step What happened Gate affected
Jan 5 Verifier gets SMTP 250, marks valid Gate 1 and part of Gate 2
Mar 10 Employee leaves, mailbox closed Gate 1 fails later
Mar 12 Campaign sends, server returns 5.1.1 Hard bounce
Result Address was valid in January, bounced in March Decay after check

Frequently asked questions

Does a valid email verification result guarantee delivery?

No. A valid result means the receiving server accepted the address with an SMTP 250 reply at the time of checking. Delivery still depends on mailbox state at send time, spam filtering, sender authentication and whether the recipient engages with your messages.

What does an SMTP 250 response mean?

An SMTP 250 response means the receiving server agreed to accept mail for the address when the verifier issued a RCPT TO command. It is a sign the mailbox existed at that moment, not a promise about where the message will land.

Why do valid emails bounce?

Valid emails can bounce because addresses decay after checking. People leave jobs, mailboxes fill up or close, and domains change. A check reflects one moment, so mail sent weeks later may hit a closed or full mailbox.

Can a valid email go to spam?

Yes. A valid address can still route mail to spam because of weak sender authentication, poor sending reputation, low recipient engagement or content that triggers filters. Verification does not measure any of these factors.

What is a good hard bounce rate?

Keeping hard bounces under 2% is a practical target. Amazon SES documents a 5% bounce rate as a review trigger, so staying well below it leaves room for normal list decay. Teams should monitor their own bounce trends.

Does verification send an email to the recipient?

Generally no. Mailbox-level verifiers stop after the RCPT TO step and do not send a message body, so nothing reaches the recipient's inbox during the check.

Is a valid email address the same as a consented contact?

No. Validity only shows the address exists and accepted mail at check time. You still need documented opt-in and must respect unsubscribes and your suppression history before sending.

What should I do with risky or catch-all results?

Treat them separately from valid results. Catch-all domains accept mail for any address, so the check cannot confirm a specific mailbox. Many senders send to them cautiously and monitor bounces and engagement closely.

How often should I re-verify my list?

Re-verify based on how fast your data decays. B2B lists often need more frequent checks because job changes are common. Re-check before major campaigns and after long gaps in sending.

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 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.