Article
Email Verification Steps Explained for Beginners: The Six Checks in Order
By Unlimited Verifier Team ·

Summary
Email verification runs six automated checks (syntax, domain, MX records, SMTP mailbox, catch-all and risk flags) to sort each address into Valid, Risky or Invalid. The checks run from cheapest to most expensive, so bad addresses are removed before slow network probes run.Email verification is a sequence of six automated checks (syntax, domain, mail server, mailbox, catch-all and risk flags) that sorts every address on your list into Valid, Risky or Invalid before you send. Beginners often treat it as a one-click cleanup, but each check answers a different question, and the order you run them in determines how much time and money you spend.
This guide walks through each step in the order a verifier runs them, explains how to read the results, and includes a hands-on tutorial and a worked example sized for a real list. For the concept in general, start with how email verification works.
Quick answer
- Run six checks in order: syntax, domain, MX (mail server) records, SMTP mailbox, catch-all detection and risk flags such as disposable and role addresses. Cheap checks go first, so the slow network checks only handle addresses that already look plausible.
- Act on three buckets: send to Valid, work through Risky, and suppress Invalid permanently.
- Verify on import and before major sends. Lists decay, so a list that was clean last year may not be clean today.
- Expect losses on older data. In the worked example below, 6.7% of a 12,000-row list is Invalid. That figure is illustrative, but older lists that haven't been checked often lose a meaningful share this way.
- Verification is not consent. It shows an address can receive mail, not that the person wanted to hear from you.
Why do you need to verify email addresses before sending?
You verify because a bad address produces a hard bounce, and enough hard bounces can damage your sending reputation and, at scale, your sending account. A hard bounce is a permanent rejection. The SMTP enhanced status code 5.1.1 means "bad destination mailbox address" (RFC 3463).
Mailbox providers and ESPs read bounce and complaint patterns as signals of list quality. Amazon SES's documentation states that accounts are reviewed at a 5% bounce rate and may be paused at 10%. Other platforms often act earlier and rarely publish their thresholds. We recommend keeping hard bounces under 2% of any send, which leaves room before most automated triggers. Google's sender guidelines say bulk senders should keep user-reported spam rates below 0.10% and avoid reaching 0.30%.
Bounces and complaints are different signals, but old lists generate both. Dead addresses bounce, and forgotten subscribers mark you as spam.
For ecommerce and SaaS teams, the problem compounds. Signup forms, free trials and imported leads add addresses every week, and email verification for ecommerce and SaaS is largely about catching bad addresses at the point of entry.
Bottom line: Verification protects your sending reputation before the send, when a bad address can still be removed at no cost to your deliverability.
What are the six steps of email verification, in order?
The six checks run from cheapest to most expensive, and each stage removes addresses before the next, slower check runs. Running a mailbox probe on a malformed address wastes a network round trip, and frequent probes to one server can get your verifier's requests blocked.
| Order | Check | Question it answers | Relative cost | What it catches |
|---|---|---|---|---|
| 1 | Syntax | Is this shaped like an email address? | No network needed | Missing @, spaces, illegal characters |
| 2 | Domain | Does the domain exist? | One fast DNS lookup | Unregistered or misspelled domains |
| 3 | MX records | Does the domain have servers that accept mail? | One fast DNS lookup | Domains with no mail infrastructure |
| 4 | SMTP mailbox | Does the receiving server accept this recipient? | Slowest, depends on the server | Nonexistent mailboxes |
| 5 | Catch-all | Does the domain accept any address at all? | Extra probes needed | Results that can't be trusted |
| 6 | Risk flags | Is it disposable or a shared role inbox? | Lookup against known lists | Throwaway and team inboxes |
Bottom line: Run the cheap local checks first so the network checks only handle addresses that already look plausible.
What does each step actually check, and why does it matter?
Syntax: is it shaped like an address?
Syntax validation tests an address against the general format rules in RFC 5322: a local part, an @ sign and a domain, using permitted characters. It catches errors like jsmith@@acme.com or name@acme, which has no top-level domain. Practical verifiers are stricter than the RFC, which allows unusual forms such as quoted local parts that almost no real mailbox uses. A high pass rate at this stage tells you very little, because a perfectly formatted address can still be dead. More detail is in syntax validation rules.
Domain and MX records: can this domain receive mail?
The domain check confirms the domain exists. MX records name the servers that accept mail for it. RFC 5321 allows a sending server to fall back to the domain's address record when no MX record exists, so a missing MX is a warning sign rather than proof of failure. Good verifiers weigh it that way. The method is covered in how verifiers check whether a domain accepts mail.
You can run this check yourself. On Windows, use nslookup -type=mx example.com. On macOS or Linux, use dig MX example.com.
SMTP mailbox: will the server accept this recipient?
This is the step most people mean by "verification." The verifier opens a session with the receiving server and issues a RCPT TO command for the address. It does not send a message body. Under RFC 5321, a 250 reply means the recipient is accepted, a 550 means the mailbox is unavailable, and a 4xx reply is a temporary deferral. Temporary codes matter: a full mailbox or a server that greylists unknown senders may return one, which is why a deferral is not the same as a rejection. What RCPT TO means in practice walks through the exchange, and how a verifier checks whether an address exists puts the steps in order.
Catch-all: can the result be trusted?
A catch-all domain accepts mail for any local part, so a 250 response says nothing about a specific person. A common method is to probe a random address that cannot plausibly exist at that domain. If the server accepts it, the domain is catch-all, and its addresses can't be confirmed individually. The method is explained in how catch-all domains are detected. An alternative, with different trade-offs, is covered in send-based catch-all checks.
Risk flags: disposable and role addresses
Disposable addresses come from temporary inbox services and usually signal a throwaway signup. Disposable domain lists are how verifiers spot them. Role addresses such as info@, sales@ and support@ are usually valid, but they reach a team rather than a person. They can suit some B2B programs and fit poorly with personal outreach.
Bottom line: Each step answers one question. The mailbox probe is the real test, but its results need interpreting, not just reading.
How do you read the Valid, Risky and Invalid buckets?
Verification produces three buckets, and each needs a different action.
| Bucket | What it means | What to do | Typical reasons |
|---|---|---|---|
| Valid | Passed the checks and the mailbox was accepted | Send, starting with the most engaged | Mailbox accepted, no risk flags |
| Risky | Can't be confirmed | Hold back, triage, test in small batches | Catch-all domain, disposable or role address, unresolved probe |
| Invalid | Failed a check | Suppress permanently and don't re-import | Bad syntax, no domain, no mail server, mailbox rejected |
Risky is the bucket beginners mishandle, because it contains several different problems. Split it:
- Catch-all addresses usually belong to real organisations. Send these last, to your most engaged contacts, in a small test batch. If that batch's bounce rate climbs above your 2% ceiling, stop and hold the rest.
- Disposable addresses have little value for most programmes. Suppress them unless you have a specific reason to keep them.
- Role addresses suit some B2B programmes and poor personal outreach. Decide by purpose.
- Unresolved probes (timeouts or temporary deferrals) are unknown, not invalid. Re-check a sample later, or run a deep check on high-value contacts.
For what a "deliverable" result does and doesn't promise, see what deliverable means in email verification.
Bottom line: Valid is your send list, Invalid is your suppression list, and Risky is a queue you work through rather than a pile you ignore.
Which verification method should a beginner choose?
For any list more than a few dozen addresses, bulk CSV verification is the practical choice. The other methods have narrower jobs.
| Method | Best for | Where it falls short | Cost model |
|---|---|---|---|
Manual checks (nslookup, dig, a test email) |
Learning the steps, or checking two or three addresses | No mailbox checks at scale, no catch-all detection, slow | Free, but expensive in time |
| Free single-email checker | Spot-checking one VIP or suspicious contact | One address at a time, so it's unsuitable for lists | Free |
| Bulk CSV verification | Lists from a few hundred up to 25,000 rows | A snapshot in time, and you must export and re-import | Standard verification unlimited on every plan |
| Verification API | Checking addresses at signup or from your own scripts | Needs developer time; the Free plan has no API access | API access on Pro |
| Deleting past bounces only | First aid after one bad campaign | Leaves every untested address in place | Free, but incomplete |
Bulk CSV verification fits most beginners. Unlimited Verifier accepts CSV and Excel files up to 10MB, detects the email column automatically, sorts every address into Valid, Risky or Invalid, flags catch-all domains, and exports results as CSV, Excel or JSON. Its verification engine is also open source on GitHub, so technical teams can read how the checks are implemented. When you compare options, the best email verification tools are the ones whose output you can act on, not just the ones with the lowest sticker price. How to choose an email verifier gives a fuller checklist.
Bottom line: Use bulk verification for lists and the single-address checker for spot checks. Treat deleting past bounces as a stopgap, not a clean list.
How do you verify your first list, step by step?
Follow these steps on your first pass. Most of the time goes into reading results, not running them.
- Export the list as a CSV from your sending tool or CRM. Include an engagement column, such as last open, last purchase or signup date. You'll need it in the re-entry step.
- Save an untouched copy and name it with the date and source, for example
newsletter_2024-05_export.csv. This is your audit trail. - Tidy the file. Remove blank rows and make sure there is one clearly labelled email column. The tool detects it automatically, but a clear header avoids surprises.
- Create a free account. The Free plan covers 25 lists a month of up to 150 emails each, with 750 deep verifications a month. It keeps results for 24 hours, so download them the same day.
- Upload and verify a list. Choose your CSV, confirm the email column is detected, and start the run.
- Record the summary counts for Valid, Risky and Invalid before doing anything else.
- Triage the Risky bucket using the split described above: catch-alls, disposable addresses, role addresses and unresolved probes.
- Export the results as CSV, Excel or JSON, and keep the summary counts in a spreadsheet beside the audit copy.
- Re-import the Valid contacts into your sending tool as a new segment. There are no native ESP, CRM or Zapier integrations, so this step is manual. Add the Invalid addresses to your suppression list.
- Spot-check edge cases with the free single-email checker, such as a key customer who landed in Risky.
Bottom line: Export, verify, record the counts, triage Risky, and re-import only Valid. Keep the original file and the counts.
Worked example: what does verifying a 12,000-row list look like?
This example is illustrative, but the arithmetic and plan limits are real. A B2B newsletter has 12,000 contacts: a mix of organic signups and an event list imported two years ago that has never been checked.
Choosing a plan. On the Free plan, each list holds 150 emails, so 12,000 addresses would need 80 lists (12,000 ÷ 150 = 80). The Free plan allows 25 lists a month, which caps a month at 3,750 addresses (25 × 150). The list won't fit on Free in one month. On Pro, each list can hold up to 25,000 emails, so all 12,000 fit in one upload. Pro costs $29 a month, or $25 a month billed annually.
Hypothetical results:
| Bucket | Count | Share of 12,000 |
|---|---|---|
| Valid | 9,300 | 77.5% |
| Risky | 1,900 | 15.8% |
| Invalid | 800 | 6.7% |
Check: 9,300 + 1,900 + 800 = 12,000.
Deep verification budget. Running all 1,900 Risky addresses through deep verification uses 7.6% of the Pro plan's 25,000 monthly deep verifications (1,900 ÷ 25,000 = 0.076), leaving 23,100. Standard verification of the full list is unlimited, so the deep budget only needs to cover the contacts where extra certainty matters.
Send impact. If you had sent to all 12,000 untouched, most of the 800 Invalid addresses would have bounced hard, a bounce rate of about 6.7% on that send. Amazon SES's documentation describes account review at 5%, so that one send would have crossed the line. After cleaning, the Invalid addresses are off the list, and the Risky addresses go out in small test batches.
Cost. One Pro month at $29 works out to about $2.42 per 1,000 addresses ($29 ÷ 12,000 × 1,000 ≈ $2.42). On the annual plan, $25 a month is about $2.08 per 1,000 for each run ($25 ÷ 12,000 × 1,000 ≈ $2.08). Cleaning this list monthly on the annual plan costs $300 a year.
A smaller case. A 140-row local-business list fits on one Free list (140 is under the 150-email limit). The 750 monthly deep verifications cover any Risky addresses you want to check closely.
Bottom line: The arithmetic tells you which plan you need, how much deep-check budget to set aside, and the bounce rate you'd have taken by sending untouched.
Does verification email my subscribers?
No. A verifier doesn't deliver your message, and it doesn't send a message body to anyone on your list. It opens an SMTP session with the recipient's server, asks whether the server would accept that recipient (RCPT TO), and closes the session without sending content. The mailbox owner typically sees nothing.
Some servers refuse these probes, rate-limit them or never answer. A refused probe doesn't prove the mailbox is dead, which is why unresolved results belong in Risky rather than Invalid. Why some mail servers block verification probes explains the common reasons.
Bottom line: Verification asks questions of mail servers, not of your subscribers. Its results are a snapshot, so treat them as a current reading rather than a permanent guarantee.
How often should you verify, and what does it cost?
Verify every new import before its first send, and verify any list untouched for three months or more before a campaign. For high-churn B2B lists, monthly checks are a reasonable target. For stable consumer lists, quarterly is often enough. These are recommendations, not industry standards. Lists decay because people change jobs and providers close accounts. A maintenance schedule turns this into routine.
On cost, email verification pricing generally depends on how many addresses you check and how much deep verification you use. Some per-credit tools charge again on every re-check, which makes frequent re-verification expensive. Unlimited Verifier includes unlimited standard verification on every plan, including Free, with no per-email fees. Deep verifications are metered at 750 a month on Free and 25,000 a month on Pro.
Bottom line: Verify on import, before major sends and on a schedule. Budget for deep verifications rather than for every standard check.
Is email verification enough for compliance?
No. Verification is list hygiene, not consent. The FTC's CAN-SPAM compliance guide for US commercial email requires, among other things, honouring opt-out requests within 10 business days. It does not require verification. Consent rules outside the US differ, so check your lawful basis with a privacy professional. Keep records of how each address was collected, and use verification as one layer of your broader email verification compliance and hygiene process.
Bottom line: A Valid address can still belong to someone who never asked for your mail. Verification fixes deliverability; consent records protect you on permission.
How do you connect verification to your sending tool?
There are two practical patterns. The first is export, verify and re-import, which suits existing lists and scheduled clean-ups. The second is an API call from your own scripts or signup forms. The email verification API supports single-address checks and bulk batches of up to 10,000 emails per request. The Pro plan includes 100,000 API emails a month, and the Free plan has no API access.
For checks at the point of entry, see real-time validation at signup. Teams that want automated workflows can read more under email verification API and automation.
Bottom line: Use the CSV workflow for lists you already have and the API for addresses that arrive every day.
What are the common mistakes beginners make?
- Treating Valid as "will be delivered." Valid means the checks passed. It doesn't guarantee inbox placement. See what deliverable means.
- Sending bulk campaigns to Risky addresses first. Catch-all and unresolved addresses belong at the end of your send order, in small batches.
- Re-verifying the same file without fixing the source. A verifier can't repair a broken signup form or a flawed import process.
- Forgetting the retention window. Free keeps results for 24 hours and Pro for 30 days. Download and save results on the day you run them.
- Uploading a 26,000-row list to Pro without splitting it. Each list is capped at 25,000 emails on Pro, so split larger files first.
- Treating timeouts as Invalid. A server that refuses or defers a probe isn't necessarily rejecting the mailbox.
- Over-reading accuracy claims. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. Applied to 12,000 rows, it implies up to about 60 misclassified addresses, and the hardest cases are most likely to sit in the Risky bucket.
- Losing your suppression history when you export or migrate. Keep a copy of everything you've removed, so you don't re-import it later.
- Assuming verification proves consent. It doesn't.
Bottom line: Most beginner errors come from reading the buckets too literally or skipping the steps that protect your history.
How we compared (and limitations)
This guide is based on public documentation: the RFCs for SMTP and message syntax, Google's sender guidelines, Amazon SES's published thresholds and the FTC's CAN-SPAM guide. We haven't run controlled tests of verification accuracy or of any provider's review process. Thresholds and server behaviour vary by provider and change over time. The 99.5% figure is Unlimited Verifier's stated accuracy for deep verification, not an independent benchmark. The worked example's percentages are illustrative, and the arithmetic uses only the plan limits listed above.
Action by verification bucket
| Bucket | Meaning | Action |
|---|---|---|
| Valid | Passed all checks | Send normally |
| Risky | Catch-all, disposable, role or unclear result | Segment, send low volume or re-verify |
| Invalid | Failed syntax, domain, MX or mailbox | Suppress permanently |
Frequently asked questions
What is the difference between email verification and email validation?
The terms are generally used interchangeably. Both describe checking whether an address is formatted correctly, has a working domain and mail server, and can receive mail. Some vendors use validation for the format and domain checks and verification for the mailbox probe, so check each tool's definition.
What does a hard bounce mean?
A hard bounce is a permanent delivery failure, usually because the mailbox doesn't exist or the domain can't receive mail. The SMTP code 5.1.1 means the destination mailbox address is bad. Hard-bounced addresses should be removed from your list and not emailed again.
What is a catch-all domain?
A catch-all domain accepts mail sent to any address at that domain, real or not, so a mailbox probe cannot confirm whether a specific person exists. Verifiers label these addresses Risky because delivery is uncertain and bounces may come later.
Is a disposable email address the same as an invalid one?
No. A disposable address is usually deliverable but comes from a temporary inbox service that people use to avoid giving a real address. Verifiers flag these as risk signals, and many senders choose to exclude them from marketing lists.
Why do verifiers use SMTP probes?
An SMTP probe opens a conversation with the recipient's mail server and asks whether it would accept mail for an address, without sending a message. It is the only step that tests the mailbox itself, which is why it is slower and more likely to be rate-limited.
How often should I verify my email list?
Verify on import, before major campaigns, and periodically for older lists. Addresses decay as people change jobs, close accounts or abandon inboxes, so a list that was clean last year may contain new bad addresses today.
Does email verification guarantee inbox placement?
No. Verification only shows that an address can likely receive mail. Inbox placement also depends on content, authentication such as SPF, DKIM and DMARC, engagement and sender reputation.
What should I do with Risky addresses?
Treat them as a separate segment rather than sending to them with the main list. Options include re-verifying later, sending a low-volume re-engagement message, or removing them if they show no recent engagement.
Can I verify addresses without sending any email?
Yes. Verification checks are performed without delivering a message to the recipient. The mailbox probe opens a mail-server handshake that stops before any message body is transmitted.
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.