How to Verify an Email Address: 6 Checks Before You Send, and What Catch-All Results Mean

Publish date: Nov 10, 2026
To verify an email address, run six checks in order: spelling, domain, MX record, mailbox, catch-all and address type. A verifier tool runs all six in seconds. You can run the first five yourself from a terminal, and this post shows the exact commands.
The result is one of four labels: valid, invalid, catch-all or unknown. In Hunter's guide, valid means "the email address exists, so your email is safe to send". Invalid means it "doesn't exist and your email will not reach the recipient". Catch-all is the label that trips sellers up: the server said yes, but it says yes to every name.
Verification cuts bounces. It does not end them. In one Spona delivery test on German professional-services executives, 137 of 19,247 sends to verified addresses still hard bounced. If you do not have the address yet, start with how to find a business email address, then come back here before you send.
Get thousands of leads in 4 minutes.
Stop stitching tools together.
Start with verified sales data, delivered in minutes.
No contracts · No setup · No onboarding
How to verify an email address: the 6 checks
A verifier asks the questions a mail server asks before it accepts a message, and stops before any message goes out. Each check catches one kind of bad address. Run them in order, because a domain that does not exist makes every later check pointless. The mailbox check is the one that matters, and the catch-all check tells you how far to trust it.

1. Check the syntax and spelling
An address is a local part, an @ and a domain. RFC 3696 caps the local part at 64 characters. The domain takes at most 255, and a verified erratum puts the whole address at 254. Letters, digits, dots, hyphens, underscores and plus signs are all legal before the @.
So a format pass means little on its own. An address at gnail.com is well formed and will never reach a Gmail user. Typo domains are also where spam traps live: Mailgun names ".con instead of .com, or gnail instead of gmail" as examples of typo traps. Check the domain against the company's website before you move on.
2. Confirm the domain exists
Look the domain up in DNS: no record, no mail. Some domains exist and still refuse mail on purpose. A null MX record, written "MX 0 .", announces that the domain "accepts no mail", and RFC 7505 says delivery attempts "fail immediately". A verifier marks every address on such a domain invalid.
3. Look up the MX records
Mail finds its server first by the MX record, then by an A or AAAA record as a fallback. The MX record names the host that accepts mail for the domain. Often that is a Google Workspace or Microsoft 365 host, not the company's own server.
Hunter treats a domain with no MX record as dead and marks every address on it invalid. Write the MX host down, because the next check talks to it.
4. Ask the mail server about the mailbox
This is the check that matters, and the one a DNS lookup cannot do. The verifier connects to the MX host on port 25 and starts a delivery, then stops before any content goes out. It names a sender, names the recipient and reads the reply.
A 250 reply means the server accepts that recipient. A 550 reply means it does not, and RFC 5321 says the server typically adds a string such as "no such user".
Enhanced codes say more: the code 5.1.1 means "the mailbox specified in the address does not exist". The same RFC says resending is unlikely to fix any 5.X.X failure. SMTP has a VRFY command built for this exact question, but servers may "disable either or both" VRFY and EXPN. So the reply to RCPT TO is what verifiers read.
Microsoft adds a twist. When every recipient of a domain lives in Exchange Online, Microsoft rejects unknown names at the service network perimeter. The reply is "550 5.4.1 Recipient address rejected: Access denied", a clean invalid.
5. Test for a catch-all domain
A 250 for your prospect proves little if the server says 250 to everyone. So the verifier sends a second RCPT TO with a made-up name on the same domain. If that name also gets a 250, the domain is catch-all. Hunter calls it accept-all: the server responds positively whether or not the given email address exists.
Companies set this up on purpose. Google Workspace lets an admin route mail sent to "non-existent or incorrect email addresses in your domain" into one catch-all mailbox. In Microsoft's setup steps, edge blocking starts when an admin switches a domain from "Internal relay" to Authoritative. Our inference is that a domain kept as Internal relay answers yes to any name, and a verifier reads that as catch-all.
The check stops here. The server accepted your address but did not confirm it. The results section below says what to do with it.
6. Flag role, disposable and free addresses
The last check reads the address, not the server. Role addresses are shared mailboxes such as info@, sales@ or support@, names that RFC 2142 standardized in 1997. They pass every server check and still hurt you. ZeroBounce says they "strongly correlate to people reporting emails sent to them as spam and abuse". Our post on role-based email lists covers the difference between a role address and a person.
ZeroBounce says disposable addresses "are temporary and become invalid after a set period". Free-mail domains such as gmail.com or outlook.com are normal for a consumer and a weak sign for a B2B prospect.
Purchased lists carry a risk no check can see. Amazon SES warns that they "can contain spamtrap addresses", dormant mailboxes "used exclusively to lure unsolicited email". Such a trap can pass every check above. The only defense is knowing where the address came from.
How to verify if an email address is valid by hand
You need a terminal and two commands: nslookup to find the mail host and telnet to talk to it. Replace example.com with your prospect's domain and example.org with your own. Microsoft's Exchange guide documents the same dialog, and the replies below come from it.
| Step | What you type | A pass looks like |
| 1. Find the mail host | nslookup -type=mx example.com | One or more "mail exchanger" lines; use the host with the lowest preference number |
| 2. Connect | telnet mx1.example.com 25 | A 220 greeting |
| 3. Say hello | EHLO example.org | 250, then the server's options |
| 4. Name a sender | MAIL FROM:you@example.org | 250 2.1.0 Sender OK |
| 5. Name the recipient | RCPT TO:prospect@example.com | 250 2.1.5 Recipient OK; a fail reads 550 5.1.1 User unknown |
| 6. Probe for catch-all | RCPT TO:zq7notaperson@example.com | 550 means the domain rejects unknown names; 250 means catch-all |
| 7. Leave | QUIT | 221 2.0.0, and the connection closes |
Never type DATA. The moment you send content, you have sent an email. Hunter calls a test email "not recommended", because "email bounces are a major negative factor for your sender reputation".
Three things break the by-hand method:
- The Telnet client is off on most Windows machines. Microsoft's guide says "by default, the Telnet Client isn't installed" in most versions of Windows. Turn it on under Windows Features first.
- Cloud machines often block that port. AWS "blocks outbound traffic on port 25" for all its EC2 instances by default, so a telnet from a server hangs.
- Greylisting. A server that does not know your IP may send a temporary 4yz reply and expect you to come back. The greylisting standard, RFC 6647, gives an example minimum age of 30 minutes. Retry windows run "from one minute to 24 hours", and the RFC admits greylisting "can interfere" with address checks.
Do this for one address when you must. Do not do it for a list. AtData warns that a manual ping can get your own IP address "blacklisted". A verification service takes that risk instead of you.
Email verification results: valid, catch-all, invalid, unknown
Every tool prints its own labels. Here is how three of them line up, and what to do with each result.
| Result | Hunter | ZeroBounce | Email Hippo | What to do |
| The server confirmed the mailbox | valid | valid | OK | Send |
| The server accepts every name | accept-all | catch-all | Unverifiable (catch-all) | Send a small share and watch the bounces |
| The server rejected the mailbox | invalid | invalid | Bad | Remove |
| The server would not answer | unknown | unknown | Unverifiable | Retry in a few days; do not send |
ZeroBounce puts the expectation for valid addresses plainly: they "will have a very low bounce rate of under 2%". Email Hippo's catch-all reason describes the check itself: the domain "accepts all incoming mail but doesn't confirm individual mailboxes".
Catch-all: accepted, but not confirmed
Hunter ran the test everyone wonders about. It sent to 100 accept-all addresses and 100 verified ones. The accept-all group bounced at 27%, the control group at 1%. Hunter's advice: catch-all addresses "shouldn't be discarded automatically", but cap them at 2 to 5% of a campaign.
ZeroBounce agrees: a catch-all is "impossible to validate without sending a real email and waiting for a bounce". Its advice is to "segment them into a catch-all group". Our guide shows how to send to catch-all addresses without hurting your domain.
Unknown: the server would not answer
Unknown means the check timed out or got a temporary reply. ZeroBounce's sub-statuses name causes such as antispam system, greylisted, mail server did not respond and timeout exceeded. ZeroBounce claims "80% of unknowns are invalid" and does not charge for them. Hunter's advice is to retry "after a couple of days".
Do not send to an unknown in the meantime. A greylisting server that later answers 550 hands you a hard bounce you could have avoided.
How often verified email addresses still bounce
Spona ran a recorded delivery test on one segment: executives at German professional-services firms. Executive means owner, founder, C-level, VP, director or head. Professional services covers NACE divisions 69 to 75, which include legal, accounting, consulting, architecture, engineering, R&D, advertising and market research. Spona searched unique profiles, checked one candidate address per profile found, then sent one email per verified recipient.
The whole funnel, over a recent quarter:
| Step | Count | Share |
| Profiles searched | 21,683 | |
| Address found and checked | 21,197 | 97.76% of profiles |
| Passed | 20,683 | 97.58% of checked |
| Catch-all | 327 | 1.54% of checked |
| Other rejected | 187 | 0.88% of checked |
| Emails sent | 19,247 | one per verified recipient |
| Hard bounces | 137 | 0.71% of sends |
Pass, catch-all and rejected are mutually exclusive shares of the checked total. So the check held back 514 addresses, or 2.42%, before any send; that sum is our arithmetic. The bounce denominator is attempted sends to verified recipients, not the checked total.
First, verification did its job: 0.71% of sends hard bounced, against the 2% red flag Hunter sets for cold outreach. Second, 137 bounces still came from addresses that had passed the check. A mailbox can close between the check and the send, and a 250 is a promise the server does not always keep.
Third, this is one segment, and a low one for catch-all, since shares differ by country, role and industry. Spona's catch-all guide prints far higher shares for its country samples, Germany included. Hunter found 38% of the domains in its sample accept all mail, a share of domains rather than of addresses. Do not read 0.71% as a general Spona bounce rate.

Where do the bounce lines sit? Amazon SES tells senders to "keep your hard bounce rate below 5%" and puts an account under review at 5% or greater. At "10% or greater", SES may pause sending. Only hard bounces count, and SES notes the target "isn't a universal rule across all ISPs".
Yahoo's rule is one line: "Remove invalid recipients from your list promptly". SES goes further: when an address hard bounces, "immediately remove that address from your lists". A hard bounce is a permanent 5xx failure such as 550, not a 4xx soft bounce, and only the hard kind counts here. Our cold email deliverability guide explains what bounces do to sender reputation.
When to check email addresses, and which tools to use
Addresses rot. Hunter re-verified a list of 1,278 North American addresses every week. After 8 weeks, 5.5% of the list was no longer valid. Of the list, 2.3% had become invalid and 3.2% had turned accept-all.
ZeroBounce's annual report, built on more than 11 billion addresses, says "at least 23%" of an email list decays yearly. Only 62% of what it checked was valid. Our post on data decay covers the job-change side of the same problem.
Three moments to check:
- Before import. Verify a bought or scraped list before it touches your CRM, so a bad address never enters a sequence.
- Before send. Hunter's advice from its decay test: "verify your mailing list shortly before targeting it with a campaign". A list you verified last quarter is not a verified list.
- Every quarter for the rest. Decay of 23% a year is about 6% a quarter, our arithmetic. That alone can push a clean list past the 2% red flag inside a quarter.
For a single address, every tool below offers some free checks. For a whole list, our email list cleaning post prices eleven verifiers at 10,000 and 100,000 addresses.
| Tool | Free checks | After the free tier |
| Hunter | 50 credits a month; a check costs 0.5 credit, so up to 100 checks | Credit plans, from the Starter tier |
| ZeroBounce | 100 a month, with a business email domain | Pay as you go from $39 for 2,000 addresses |
| NeverBounce | Free list analysis and test credits; the count is not stated | $8 per 1,000 credits; credits expire 12 months after purchase |
| QuickEmailVerification | 100 credits a day | Paid credit packs on its site |
| Email Hippo | Your first list of up to 100 emails | No price published on its tool page |
Where Spona fits, and where it does not
Spona is not a verifier for a list you already own. It is a lead finder that verifies every lead before it delivers the list. You describe your buyer in a chat, Spona builds the list, and every search starts with a free sample of leads.
The delivery test above is what that verification looked like in one segment. Leads cost from $0.008 to $2.00 each, depending on the search type and the plan, and the price per lead shows at checkout.
Where Spona fits:
- You need new, verified addresses for a segment, not a check on addresses you already have.
- You want the verification cost inside the lead price rather than a second tool and a second invoice.
- You hold contacts without emails. Data Enrichment adds the missing work email to your own records, charged only when a result returns.
Where it does not:
- Checking a single address. Use the by-hand method above or a free tier from the table.
- Cleaning an existing list. ZeroBounce and NeverBounce do that in bulk; Data Enrichment adds missing fields, it does not re-verify addresses you already hold.
- Comparing finders before you buy. Our best email finder tools post covers the field.
Get thousands of leads in 4 minutes.
Stop stitching tools together.
Start with verified sales data, delivered in minutes.
No contracts · No setup · No onboarding
Email address verification FAQ
How do I verify a B2B email address?
The same six checks, with three differences. Company domains set their own mail rules, and many accept every name, so expect more catch-all results than on free mail. Drop role addresses such as info@ or sales@ even when they pass. And when Microsoft 365 rejects a name at its edge, trust the invalid result; that reply is a clean no.
Why can't my email address be verified?
From the verifier's side, two things stop a check. The domain is catch-all, so the server says yes to every name and the tool refuses to call that a pass. Or the server would not answer: greylisting, an anti-spam system or a timeout, which tools label unknown. Retry an unknown after a couple of days; a catch-all stays catch-all, so treat it as the results section describes.
How to identify a legitimate email?
For a message in your inbox, check the sender's domain letter by letter against the company's real website. The FTC says to contact the company "using a phone number, email, or website you know is real". The UK's NCSC gives the same rule, "use the details from their official website". The six checks above tell you whether an address can receive mail, not whether its owner is honest.
How to identify a fake email address?
Four signs give a fake away. A disposable domain, which verifiers list separately, or a typo domain such as .con or gnail. A gibberish local part, which Hunter flags as "very likely to bounce", or a role address posing as a person. Run the six checks; a made-up address usually fails at the domain or the mailbox step.
Can you verify an email address for free?
Yes, two ways. By hand, with nslookup and telnet as shown above, which costs nothing but time and works for one address at a time. Or with the free tiers in the table above: Hunter, ZeroBounce and QuickEmailVerification each give a free monthly or daily allowance without a paid plan.
Is validation the same as verification?
Not quite, though some tools use the two words loosely. Validation checks the format and the domain without asking a mail server anything, which is what a signup form does when it rejects a missing @. Verification goes further and asks the domain's mail server whether the mailbox exists. Our post on B2B data validation covers the wider process for every field in a record, not only the email.
Share this article
GET FREE LEADS





