I once watched a client’s cold outreach campaign get flagged for spam after just 200 emails — not because the message was bad, but because a third of the list was full of dead addresses. Bounce rates like that tank your sender reputation fast. The good news is you can check whether an email address is real before you ever hit send, and it only takes a few minutes once you know where to look.
What You’ll Need Before You Start
Email validation ranges from a 10-second manual check to running a full list through a dedicated tool. Depending on how deep you want to go, here’s what helps:
- A terminal or command prompt, if you want to check MX records or run an SMTP test yourself
- Access to a free MX lookup site like MXToolbox for a no-install option
- A bulk verification tool (like NeverBounce, ZeroBounce, or MillionVerifier) if you’re checking more than a handful of addresses
Step 1: Check the Syntax First
This sounds almost too basic, but it catches more bad addresses than people expect. A valid email needs exactly one @ symbol, a local part before it (letters, numbers, and a limited set of special characters like periods, underscores, and hyphens), and a domain after it that includes at least one dot, like gmail.com or outlook.com.
Watch for the small stuff: double dots (john..doe@example.com), a trailing dot right before the @ symbol, or spaces that snuck in during a copy-paste from a spreadsheet. I’ve cleaned up plenty of “bad” lists where the real problem was just stray whitespace.
Step 2: Look Up the Domain’s MX Records
Syntax only tells you the address is well-formed, not that it’s real. The next check is whether the domain can actually receive mail at all. Every domain that accepts email publishes MX (Mail Exchange) records in its DNS settings, pointing to the servers responsible for handling its inbound mail.
On a Mac or Linux machine, open a terminal and run:
On Windows, use nslookup -type=mx example.com in Command Prompt instead. If you’d rather skip the command line entirely, paste the domain into MXToolbox’s MX Lookup tool and it’ll show you the same result in a browser. No MX records at all means the domain can’t receive mail, which means every address on it is dead, no matter how correct it looks.
Step 3: Run an SMTP Handshake Check
This is the closest you can get to “asking” a mail server whether an address is real, without actually delivering anything. Mail servers exchange a series of commands before a message is sent — and you can stop that exchange right before the final step, which means no email ever gets sent or received.
Here’s the basic sequence, run manually via telnet on port 25 against the domain’s MX server:
- Connect to the mail server and issue HELO (or EHLO) with your own domain
- Issue MAIL FROM: with any valid sender address
- Issue RCPT TO: with the address you’re checking
- Read the server’s response code, then issue QUIT instead of DATA — this is the step that stops a message from actually being sent
A 250 response after RCPT TO generally means the mailbox exists and is willing to accept mail. A 550 or similar 5xx response means it doesn’t. It’s a genuinely useful trick, but honestly, doing this by hand for more than a few addresses gets tedious fast — and that’s exactly what bulk verification tools automate for you.
Step 4: Use a Verification Tool for Bulk Lists
If you’re checking anything more than a dozen addresses, don’t do this by hand. Dedicated verification services run the syntax check, MX lookup, and SMTP handshake automatically, plus they maintain their own reputation data on providers that block manual probing.
| Tool | Best for | Notes |
|---|---|---|
| ZeroBounce | Marketing lists | Includes spam-trap detection |
| NeverBounce | CRM integrations | Real-time API for form validation |
| MillionVerifier | Budget bulk checks | Lower cost per address on large lists |
I’d lean toward whichever tool integrates with wherever your list already lives — most connect directly to Mailchimp, HubSpot, or a plain CSV upload. They’ll return a status for each address, usually something like “valid,” “invalid,” “risky,” or “unknown,” so you can filter before you ever send a campaign.
Step 5: Watch for Catch-All Domains
Some domains, especially smaller business ones, are configured as “catch-all,” meaning the mail server accepts every address sent to that domain regardless of whether a matching mailbox actually exists. That completely defeats the SMTP handshake check from Step 3 — you’ll get a 250 “accepted” response even for addresses that don’t exist.
Good verification tools flag this as “catch-all” or “accept-all” rather than a flat “valid,” which is a meaningful distinction. Treat catch-all results as unconfirmed rather than trustworthy — they’re a coin flip, not a green light.
Pro Tips for Accurate Verification
Common Mistakes to Avoid
- Trusting a catch-all “valid” result at face value. Treat it as unconfirmed, not confirmed.
- Skipping the syntax check. It’s the fastest filter and catches a surprising number of bad entries for free.
- Running heavy SMTP probing from your main sending IP. This can quietly damage your sender reputation before you’ve sent a single real campaign.
- Verifying once and never again. Email lists decay steadily — a list verified a year ago isn’t a list you can trust today.
Quick Recap
Check syntax, confirm the domain has MX records, run an SMTP handshake and stop before DATA, and use a bulk tool for anything beyond a handful of addresses. Watch for catch-all domains, which can make a dead address look valid.
Wrapping Up
Between syntax checks, MX lookups, and the SMTP handshake trick, you now have a real toolkit for spotting dead addresses before they ever touch your sender reputation. For a handful of addresses, doing it manually takes a few minutes. For a full list, hand it to a verification tool and let it do the heavy lifting. Either way, a clean list is one of the simplest things you can do to keep your emails landing in inboxes instead of bouncing.