SMTP Email Verification: How It Works and Where It Fails
SMTP email verification checks a mailbox by talking to its mail server, without sending a message. Learn the steps, reply codes and limits.

SMTP email verification checks whether a mailbox exists by talking to the recipient's mail server, without sending a real message. It is the core step behind most email verifiers, and it catches many bad addresses that a syntax check misses. It is not perfect, though. This guide explains how the method works, what the reply codes mean and the cases where the answer cannot be trusted.
TL;DR#
- The verifier looks up the domain's mail servers, opens an SMTP session and asks if it would accept the address.
- A
250reply toRCPT TOmeans accepted. A550reply usually means the mailbox does not exist. - Catch-all servers, greylisting and rate limits can make the result unclear.
- Use a verifier that reports these cases as "unknown" or "risky" instead of guessing.
What is SMTP email verification?#
SMTP is the protocol mail servers use to hand messages to each other. It is defined in RFC 5321. During a normal delivery, the sending server tells the receiving server who the message is from and who it is for. The receiver can accept or refuse each recipient before any message content is sent.
SMTP email verification uses that early step. It starts the conversation, asks about the recipient and stops before the message body. No email arrives in the inbox.
The steps of an SMTP check#
A full verification has several stages. The SMTP session is the last one.
- Syntax check. Does the address follow the basic format, with one
@and valid characters? Our email checker covers this first pass. - Domain check. Does the domain exist in DNS?
- MX lookup. Which mail servers accept mail for the domain? The MX records list them in priority order.
- SMTP session. The verifier connects to the best MX host and runs the commands below.
A simplified session looks like this:
S: 220 mail.example.com ESMTP
C: EHLO verifier.example.net
S: 250 mail.example.com
C: MAIL FROM:<check@verifier.example.net>
S: 250 OK
C: RCPT TO:<jane@example.com>
S: 250 OK
C: QUIT
The decisive line is the reply to RCPT TO. The verifier then closes the session with QUIT, so no message is ever sent.
What the SMTP reply codes mean#
SMTP replies begin with a three-digit code. The first digit sets the class.
- 2xx (success): the server accepts the recipient.
250is the usual reply. - 4xx (temporary failure): the server asks the sender to try later. This is common with greylisting or a busy server.
- 5xx (permanent failure): the server refuses the recipient.
550often means the mailbox does not exist, but the same class is used for policy blocks, too.
Read the text after the code as well. "User unknown" points at a bad mailbox. "Blocked by policy" means the server rejected the verifier, not the address.
Where SMTP email verification gives wrong answers#
The method is only as good as the server's replies, and some servers do not tell the truth.
Catch-all domains#
A catch-all server accepts mail for any local part. It will say 250 to anything@example.com, real or not. The check passes, but the address may bounce later or be silently dropped. See our guide to catch-all email verification for ways to handle these domains.
Greylisting#
Some servers answer a first-time sender with a temporary 4xx error and expect a retry after a delay. This is called greylisting. A verifier that gives up on the first try will mark good addresses as failed. A careful tool retries or reports the result as unknown.
Blocking and rate limits#
Large mailbox providers watch for connections that start sessions without sending mail. They may refuse the connection, slow it down or answer with a generic reply. When that happens, the verifier cannot tell whether the mailbox exists.
Accept-then-bounce servers#
Some servers accept every recipient during the session and bounce the message later. From the outside, they look like catch-alls, and SMTP alone cannot see through them.
The VRFY command#
SMTP has a VRFY command meant for checking a user, but most servers disable it for privacy and security reasons. Verifiers rely on RCPT TO instead.
How to read verification results#
Good tools return more than "valid" or "invalid". Look for these states:
- Valid: the server accepted the mailbox and it does not look like a catch-all.
- Invalid: the server clearly rejected the mailbox or the domain has no mail server.
- Risky or catch-all: the server accepts all addresses, or the address is a role account or temporary mailbox.
- Unknown: the server did not give a usable answer.
Plan your sending around those states. Send to valid addresses, review risky ones in small batches and leave out invalid ones.
Best practices for SMTP email verification#
- Verify close to the send date. Mailboxes change, and an address valid months ago may be gone.
- Verify at collection. Check addresses when they enter your form or CRM, not only before a campaign.
- Do not use your sending domain's mail servers to probe. Heavy checks can hurt reputation. Use a service built for it.
- Watch the bounce rate after sending. Your results show how well verification worked for your list.
- Treat unknown as unknown. Do not turn it into valid.
Verify with Tomba#
You can run SMTP email verification without building the infrastructure yourself. Paste a single address into the Tomba Email Verifier to see its status, or use the bulk tool for a whole list. If your product needs verification at the point of sign-up, the Tomba API exposes the same check for your code.
Frequently asked questions#
Does SMTP email verification send an email?#
No. The verifier ends the session before the message body is sent, so the recipient sees nothing.
Is SMTP email verification accurate?#
It is accurate for most servers. It is less reliable for catch-all domains, greylisting servers and providers that block verification traffic. Good tools label those cases.
What does a 550 error mean?#
It is a permanent refusal. It often means the mailbox does not exist, but read the text, as it can also signal a block based on policy.
Can I do SMTP verification myself?#
You can with a script, but running it at scale takes care. You need good IP reputation, retry logic, and rules for each large provider. Most teams use a verification service.
Why does a valid email show as unknown?#
The server may use greylisting, rate limits or privacy settings that hide the real answer. Try again later or send a small test batch.
Next step#
Check an address now with the Tomba Email Verifier and see exactly which state it falls into.
// start free
See who Tomba finds at any company
Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.
Free plan · No credit card required · GDPR & CCPA