Article

Deep vs Standard Email Verification: What Each Check Actually Catches

By Unlimited Verifier Team ·

Diagram of the four email verification layers, showing standard checks for syntax, domain and MX records and deep SMTP mailbox check as the final layer.

Summary

Standard email verification checks syntax, domain and MX records, so it confirms an address is well formed and its domain can receive mail. Deep verification adds a live SMTP check that asks the mail server whether the specific mailbox exists, which catches deleted mailboxes at healthy domains. Most teams standard-check every address and deep-check only their riskiest segments.

Deep email verification runs a live SMTP check that asks the recipient's mail server whether a specific mailbox exists, using RCPT TO and reading the reply code (250 accepts, 550 rejects). Standard verification stops earlier, at syntax, domain and MX records, so it cannot see a deleted mailbox at a healthy domain.

Quick answer

For the full pipeline behind both methods, see how email verification works.

What is the difference between deep and standard email verification?

Verification is a stack of checks, and each layer tells you more than the one below it. Standard verification covers the first three layers. Deep verification adds the fourth, which asks the mail server about the mailbox itself. Vendors use different labels ("SMTP verification," "real-time check," "deep scan"), so compare what each one tests rather than its name.

  1. Syntax. Is the string shaped like an address? maria..lopez@company.com fails on the consecutive dots. See syntax checks in detail.
  2. Domain. Does the domain exist and is it set up to receive mail? See domain acceptance checks.
  3. MX records. Does DNS list a mail server for the domain? Without one, no mail can arrive.
  4. SMTP mailbox check. The verifier connects, introduces itself, names a sender and issues RCPT TO for the recipient, then disconnects before sending any message. RFC 5321 defines these commands. What RCPT TO means and how a verifier tests an address walk through the exchange.

Layers one to three test the domain. Only layer four tests the person.

This is the general model. Check Unlimited Verifier's documentation for its exact mapping of checks to each mode before you rely on it for compliance records.

Bottom line: Standard verification proves an address is well formed and its domain can receive mail. Deep verification asks the server whether that specific mailbox exists.

Why does standard verification miss dead mailboxes?

A company domain with working MX records passes every standard check, even after the employee behind jsmith@ has left and the mailbox has been deleted. The domain is healthy. The person is gone.

The bounce arrives later. The receiving server replies with an enhanced status code such as 5.1.1, meaning no such mailbox. RFC 3463 defines these codes. This is why a standard-only audit can look clean and still be followed by bounces: the dead addresses pass the checks standard runs.

Bottom line: Standard verification tests the domain, and the dead addresses that cause bounces often sit on domains that pass.

How does a deep check work, and where does it break?

A deep check is a short exchange with the recipient's mail server. The verifier sends SMTP commands and reads the reply after each one.

  1. Connect to the highest-priority MX host on port 25.
  2. Greet the server with EHLO.
  3. Declare a sender with MAIL FROM. Servers generally require this before they evaluate recipients.
  4. Ask about the recipient with RCPT TO.
  5. Read the reply. 250 means the server will accept mail for that recipient at that moment. 550 (such as 550 5.1.1) means no such mailbox. 4xx means a temporary deferral.
  6. Quit with QUIT. A well-behaved verifier never sends a message body.

A 250 is weaker than it looks. It shows the server was willing at check time, not that a person reads the mail. Treat Valid as "safe to try," not "confirmed reader."

The results are not always clean:

Disposable and role-based addresses like info@ are a separate question from existence. Disposable domain detection explains how they are flagged.

Bottom line: Deep verification is the only layer that tests the mailbox, and its answers are clearest on business domains.

How do deep and standard verification compare?

Both methods feed the same three buckets: Valid, Risky and Invalid. What differs is what each method can see.

Dimension Standard verification Deep verification
What it checks Syntax, domain, MX records Everything in standard, plus the live SMTP mailbox check
What it reliably catches Malformed strings, nonexistent domains, domains with no mail server Nonexistent mailboxes at live domains
What it can't settle Whether the mailbox exists Catch-all mailboxes and masked answers from some providers
Catch-all domains Domain and MX pass; no mailbox-level answer Server accepts any address, so the mailbox can't be confirmed
Quota on Unlimited Verifier Unlimited on every plan 750 a month (Free), 25,000 a month (Pro)
Speed Fast; no mail-server exchange Slower; each address needs a live SMTP exchange
Best for First pass on any list, large volumes, forms Pre-send audits, old or imported lists, account reviews

Our suggested handling for each reply type:

Result What it usually means Suggested handling
Syntax or domain failure Malformed address, or no mail-receiving domain Suppress
550 5.1.1 on a deep check Mailbox does not exist at a live domain Suppress
250 on a non-catch-all domain Server confirmed the recipient at check time Valid; send in your ramp
250 on a catch-all domain Server accepts anything, so the mailbox is unconfirmed Hold as Risky; send last
4xx after retries Deferral or rate limit Re-check later; don't treat as Invalid

Bottom line: Standard is the cheap filter for everything. Deep is the precise check for addresses where a bounce would cost the most.

Which one does your list need?

Choose by how addresses entered your list and how recently they engaged. Source and age predict dead mailboxes better than list size does. Ecommerce and SaaS teams with mixed sources often need both methods; see email verification for ecommerce and SaaS.

List situation Recommended approach Why
Double opt-in signups from the last 30 days Standard, plus a deep pilot Mailboxes are current; a pilot confirms the dead rate
Opted-in list, last mailed within 90 days Standard on all; deep pilot on a sample Measures risk before you spend quota
Imported, purchased or trade-show leads Deep on everything No engagement history; mailboxes often stale
Dormant list untouched for 12+ months Deep before any send Mailboxes churn; standard misses the deleted ones
Account under bounce review Deep on the full list Reviewers look for mailbox-level evidence
Live sign-up forms Standard at submit, via real-time email validation Deep checks are too slow for a form submission

Verification supports email verification compliance and hygiene, but it doesn't replace consent records.

Bottom line: Imported and dormant lists get deep checks. Recent opt-ins get standard plus a measured pilot.

The two-pass method

  1. Segment the list by source and last engagement.
  2. Run standard on everything. This pass is unlimited, so it uses no deep quota.
  3. Deep-check imported and dormant segments in full. The table above already decides these.
  4. Pilot recent opt-ins with 1,000 to 2,000 random addresses at deep level.
  5. Apply the decision rule. If the pilot's Invalid rate exceeds 2%, deep-check the rest of the segment, riskiest first.
  6. Bucket and export. Send Valid, hold Risky, suppress Invalid.
  7. Re-verify on a schedule. Email list maintenance best practices sets a cadence.

A pilot is a signal, not a measurement. Assuming random sampling, a 500-address pilot at a true 2% rate could read anywhere from about 0.8% to 3.2%. At 2,000 addresses the range narrows to about 1.4% to 2.6%. When a pilot lands near 2%, lean toward deep-checking the whole segment.

The 2% threshold is a practitioner's rule, not a platform requirement. Amazon SES has publicly described a 5% bounce rate as the point where it reviews an account (Amazon SES documentation), and other platforms may act sooner. Staying under 2% leaves room.

Bottom line: Clear the cheap failures with standard, then spend deep quota on the segments where risk is measured or assumed.

How much deep verification does each plan allow?

Standard verification is unlimited on every plan, so the quota constrains deep checks and list size.

Plan Price Lists Max emails per list Deep verifications per month Standard verification API access Results kept
Free $0 25 per month 150 750 Unlimited No 24 hours
Pro $29/month, or $25/month billed annually Unlimited 25,000 25,000 Unlimited Yes, 100,000 emails per month 30 days

Results expire after 24 hours on Free and 30 days on Pro, so export as soon as a run finishes. For how per-check costs compare across vendors, see email verification pricing. For automated pipelines, Pro includes 100,000 API emails a month, with bulk requests of up to 10,000 emails. See email verification API and automation and the API keys page.

Bottom line: The deep quota is the constraint to plan around. Standard is effectively unmetered.

How much does a 40,000-address audit cost on Pro?

This example is hypothetical. The plan limits and arithmetic are real.

The list: 40,000 contacts.

Pass 1: standard on everything (no deep quota used). Because of the 25,000-per-list cap, Segment A uploads as 25,000 and 3,000, and Segment B fits in one file. Suppose 1,600 addresses fail: 500 in Segment A and 1,100 in Segment B.

Pilot: deep on 2,000 random addresses from Segment A. Suppose 46 are Invalid.

The pilot is above 2%, so Segment A needs more deep checks.

Deep on all of Segment B: 10,900 addresses. Suppose the results are:

Sending Segment B unchecked would bounce about 10% of it, roughly five times the 2% ceiling. That is the case for the deep pass.

Quota check:

Cost: 12,900 of 25,000 deep checks is about 52% of the quota. On monthly that is $2.25 per 1,000 used. On annual, $1.94.

Bottom line: The deep pass on Segment B found 1,090 addresses that would have bounced. Pilots decide where the quota goes; they don't replace it.

How do you run a two-pass audit in Unlimited Verifier?

  1. Export your contacts as CSV with the email column and a signup or last-engaged date.
  2. Split the file by risk: recent opt-ins in one file, imported or dormant contacts in another.
  3. Check the plan cap. Free allows 150 emails per list and Pro allows 25,000. Split anything larger.
  4. Sign up or log in.
  5. Upload your first file. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
  6. Run the standard pass on every file. It is unlimited on every plan.
  7. Record the Invalid count from pass one. These are the cheap failures.
  8. Pilot 1,000 to 2,000 addresses from each recent opt-in segment with deep verification. Calculate the Invalid and Risky percentages.
  9. Deep-check imported and dormant files in full. Deep-check the rest of an opt-in segment only if its pilot exceeds 2%. Keep the total within the monthly deep quota and carry the remainder to next month.
  10. Read the three buckets. Valid goes to sends, Risky is held back, and Invalid is suppressed permanently.
  11. Export results as CSV, Excel or JSON before retention ends, and save the summary counts.
  12. Re-import Valid contacts into your sending platform as a new segment, and add Invalid addresses to its suppression list. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so this step is manual or done through the API.

For single-address spot checks, the free email checker is quicker than a full upload. If your list has many catch-all domains, the catch-all email verification page explains how those results are handled.

Bottom line: Standard clears the cheap failures, a pilot measures the risk, and deep checks go where the measurement says they are needed.

What should you ask any vendor about its deep check?

Deep verification is not standardized, so ask these questions of any vendor, including this one:

Unlimited Verifier publishes its verification engine as open source on GitHub. Check that the hosted service behaves the way the repository describes. For a broader buyer's checklist, see how to choose an email verifier.

Bottom line: A headline accuracy figure tells you little until you know how the vendor counts catch-alls and deferrals.

What are the most common mistakes with deep and standard verification?

Bottom line: Most mistakes come from treating one check as the whole answer. Use standard for coverage, deep for precision, and the buckets to decide what gets sent.

How we compared (and limitations)

This article is based on public documentation: the SMTP and enhanced status-code RFCs, Google's sender guidelines, Yahoo's sender requirements and Amazon SES's published guidance. We have not run tests against any provider's mail servers or any verification vendor. The description of deep checks reflects general SMTP practice, which individual servers may implement differently.

To compare other vendors, start with the best email verification tools.

Bottom line: The method is well documented, but the numbers in any audit depend on your list. Measure with a pilot before you commit the quota.

Practical verification rule

  1. Run standard verification on every address to remove malformed and dead-domain entries.
  2. Export only Valid addresses for sending.
  3. Deep-check the highest-risk segments: old imports, contacts with no engagement in 12+ months, and bounced-before addresses.
  4. Hold Risky addresses out of primary campaigns and monitor a small sample.
  5. Suppress Invalid addresses permanently.

Example: a 10,000-row list passes standard checks at 9,200 rows. Deep-checking the 3,000 oldest rows removes 400 dead mailboxes, so the send list shrinks to 8,800 with fewer bounces.

Frequently asked questions

What is deep email verification?

Deep email verification is a live SMTP check that connects to the recipient's mail server and issues RCPT TO for the specific mailbox without sending a message. The server's reply code shows whether that mailbox accepts mail. It catches deleted mailboxes at domains that still have healthy DNS records.

What is standard email verification?

Standard email verification checks that an address has valid syntax, that its domain exists and accepts mail, and that DNS lists an MX record. It confirms the address could receive mail but does not confirm that the particular mailbox still exists.

Is deep email verification more accurate than standard?

Yes for mailbox existence, because only the SMTP check tests the individual mailbox. Standard checks cannot detect a deleted mailbox at a live domain. Accuracy figures vendors publish are their own claims, so test a sample of your list before relying on them.

Why do some mail servers return a valid result for every address?

Some servers are configured as catch-all and accept mail for any address on the domain, so an SMTP check cannot prove a specific mailbox exists. Verifiers usually label these addresses as risky or unknown rather than valid.

Does deep verification send an email to the address?

No. The verifier opens an SMTP session, names a sender, issues RCPT TO for the recipient and disconnects before any message body is transmitted. No email is delivered to the mailbox.

Which email verification method should I use for a large list?

Run standard verification on the full list because it is cheap and removes malformed and dead-domain addresses. Then apply deep verification to the segments with the highest bounce risk, such as old imports or contacts untouched for a long time.

What does a 550 reply code mean during verification?

A 550 reply to RCPT TO means the receiving server rejected the recipient, usually because the mailbox does not exist. An enhanced code such as 5.1.1 typically confirms no such user. Treat it as invalid and suppress the address.

What should I do with Risky addresses?

Hold them out of primary campaigns rather than deleting or sending blindly. Risky results often mean catch-all domains or greylisting, so monitor engagement and bounces on a small sample before deciding whether to keep them.

Does standard verification catch typos like gmial.com?

Only if the domain lacks valid MX records. A typo domain that happens to have an MX record passes standard checks. Deep verification can catch some of these when the SMTP check rejects the mailbox, but results vary by domain.

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.