Back to blog

How to Verify an Email Address (Without Sending One)

Verify an email address before you send: check the syntax, the MX records, and probe the mailbox over SMTP. Here is how each step works, and a free tool to run it.

On this page · 3 sections

You have an address, say [email protected], and you want to know if mail sent there will land before you actually send it. Sending a test message is the worst way to find out: if the address is dead, you have just told the receiving server that you mail unknown people, which is exactly the behavior that hurts your sender reputation.

The good news is you can verify an address without ever delivering a message. Here is how each layer works, from cheapest to most certain.

The four checks, in order

1. Syntax. Does the address even have a valid shape? jordan@@acme, a trailing dot, a space in the local part: these fail before any network call. Syntax is free and instant, but it only rules out the obviously broken ones. A well-formed address can still be completely fake.

2. MX records. Every domain that receives mail publishes MX (mail exchange) records in DNS that say which servers handle its email. No MX (and no usable A-record fallback) means the domain cannot receive mail at all, so every address there is undeliverable. This is a domain-level check: it tells you about acme.com, not about jordan.

3. The SMTP probe. This is the step that actually checks the mailbox. Your verifier opens a conversation with the receiving mail server and gets as far as RCPT TO:<[email protected]> without sending the message body. A real server usually answers 250 OK for a mailbox that exists and 550 No such user for one that does not. Nothing is delivered. Nobody gets an email.

4. The judgment layer. Real servers do not always answer cleanly. Catch-all domains say 250 OK to everything. Greylisting returns a temporary 450 to make you retry. Some providers cloak unknown users to defeat exactly this kind of probe. A good verifier turns those messy replies into one of four honest verdicts: deliverable, risky, undeliverable, or unknown.

The signal that matters is not a green checkmark. It is the server's actual reply. If a tool will not show you the 250 or the 550 it got, you cannot audit its verdict.

Reading the result

  • Deliverable means the mailbox accepted the probe. Safe to send.
  • Risky means it accepts mail but with a caveat, usually a catch-all domain or a role address like info@. Send with care.
  • Undeliverable means the server rejected it: bad mailbox, dead domain, or no MX. Cull it.
  • Unknown means the server would not give a straight answer (greylisting, an unreachable mailserver). It is honest to leave this as unknown rather than guess.

No verifier is perfect. Real-world accuracy on a mixed list is around 91 to 93 percent, and any tool claiming 99 percent is rounding away the catch-all and greylisting cases that genuinely cannot be resolved without sending.

Check one address now

You can run all four checks on a single address, free and with no account, using the free email verifier. It shows you the syntax result, the MX record it found, and the raw SMTP reply behind the verdict, so you can see exactly why an address passed or failed.

For a whole list, the same engine runs over a CSV: see how to clean an email list, or read how to check if an email is valid for more on the underlying signals.

Try it

Start with 500 free validation credits. No credit card.

Both Free and Pro run the same scan engine — full SMTP probe, MX lookup, typo, disposable, domain checks, and the evidence chain on every verdict. The difference is the monthly credit pool (Free=500, Pro=100,000) plus Pro's API and MCP access.

Found a mistake? Email [email protected]. Tags · email-validation · deliverability · verify-email · evidence-chain