ON THIS PAGE
There are six ways to check whether an email address is real, and they are not equal: some catch typos, some catch dead domains, and exactly one confirms the mailbox itself. Here is each method ranked by what it actually proves, with free tools for the ones worth using.
Why validity checks matter
Mailbox providers judge senders by bounce rate. Cross roughly 3% and your domain reputation starts sliding; near 10% and you are in the spam folder within days. Meanwhile our verification data shows about 40% of a raw, unverified list is dead or risky. Those two numbers together are the whole argument: check first, send second.
The 6 methods, ranked by what they prove
Method 1: Syntax check
A regex pass answers one question: is this string shaped like an email? It catches missing @ signs, double dots and stray spaces. Every decent form and verifier does this automatically. It costs nothing and proves almost nothing: a perfectly formed address can still be dead.
Method 2: MX record lookup
An MX lookup asks DNS whether the domain has mail servers at all. No MX records means nothing can ever be delivered there, so the address is invalid regardless of the mailbox. This filters expired domains and typo domains (gmial.com) in milliseconds. What it cannot tell you: whether john@ that domain exists.
Method 3: SMTP handshake (the real one)
This is the method that matters. A verifier opens a connection to the domain's mail server and starts a delivery conversation: HELO, MAIL FROM, then RCPT TO with the target address. The server answers whether it would accept mail for that exact mailbox. The verifier then disconnects without sending anything. No email is delivered, nobody is notified, and you get a definitive valid / invalid / risky answer.
Try it now: paste any address into the free email verifier and you get the SMTP verdict in seconds. If you need to find the address first, the free email finder tests 8 corporate patterns with the same handshake and returns the one that verifies.
Method 4: Catch-all detection
Some domains accept mail for every address, real or not. The server says yes to anything@company.com, so a naive check marks everything valid. Proper verifiers probe with a deliberately fake address: if the server accepts that too, the domain is flagged catch-all and the specific mailbox is unconfirmable. In our 383K-address dataset, 16.7% of addresses sat on catch-all domains. Treat them as a separate, capped segment in campaigns, never as confirmed contacts.
Methods 5-6: Bulk verification, and the one to skip
Bulk verification is the SMTP handshake industrialized: upload a list, get back valid / invalid / catch-all / unknown for every row. Run it before every campaign, even on lists you verified months ago; addresses decay a few percent every month as people change jobs. Getlead's bulk verification is unlimited on paid plans, so there is no per-check anxiety.
Sending a test email is the method to skip. It burns reputation on every bounce, tells you nothing a handshake would not, and at list scale it is indistinguishable from spamming.
FAQ
How do I check if an email is valid without sending anything?
Use an SMTP verification tool. It asks the recipient's mail server whether the mailbox exists during a normal delivery conversation, then disconnects before any message is sent.
Is a syntax check enough?
No. Syntax plus MX confirms the address could exist on a working domain. Only the SMTP handshake confirms the mailbox itself, and about a quarter of well-formed addresses on raw lists fail it.
What result does a catch-all domain give?
The server accepts every address, so the mailbox cannot be confirmed. Good verifiers flag it risky. Send to catch-alls sparingly and monitor bounces closely.
How often should I re-verify a list?
Before every campaign. B2B addresses decay a few percent per month as people change roles, so even a 90-day-old verified list has fresh dead mailboxes in it.