What is SMTP verification?
SMTP verification (also called SMTP probing, mailbox probing, or RCPT TO verification) is a technique that connects to a mail server and simulates the beginning of an email delivery to determine whether a specific mailbox exists. It does this without actually sending a message: the probe reaches the point where the server confirms or denies the address, then disconnects.
Think of it as knocking on a door to see if someone is home, without going inside. The mail server’s response tells you whether the mailbox is valid (250 OK), invalid (550 User unknown), temporarily unavailable (450), or catch-all (accepts everything). For a complete reference of these codes, see the SMTP error codes list. This is the most reliable method of verifying that an email address can actually receive mail.
How SMTP verification works: the 6-step process
Every SMTP verification follows the same protocol sequence. Here is exactly what happens when a verification service checks an address:
| Step | Command sent | Server response | What it proves |
|---|---|---|---|
| 1. DNS lookup | Query MX records for the domain | MX record pointing to mail server IP | The domain has a mail server configured |
| 2. TCP connection | Connect to mail server on port 25 | 220 mail.example.com ESMTP ready | The mail server is online and accepting connections |
| 3. EHLO | EHLO verify.smtping.com | 250-mail.example.com (+ capability list) | The server recognizes the verifier and lists its capabilities |
| 4. MAIL FROM | MAIL FROM:<check@smtping.com> | 250 OK | The server accepts the verifier as a sender |
| 5. RCPT TO | RCPT TO:<target@example.com> | 250 OK or 550 User unknown | This is the verification step. 250 = address exists. 550 = it does not. |
| 6. QUIT | QUIT (or RSET + QUIT) | 221 Bye | Connection closed. No email was sent. |
The critical step is step 5 (RCPT TO). This is where the receiving server checks its user database and tells the verifier whether the address exists. The verification service never proceeds to the DATA command, so no message is transmitted. The entire exchange typically completes in under 2 seconds.
What each SMTP response means for verification
| Response code | Meaning | Verification result | Should you send? |
|---|---|---|---|
| 250 2.1.5 | Recipient OK | Valid: the mailbox exists and accepts mail | Yes |
| 550 5.1.1 | User unknown | Invalid: the mailbox does not exist | No (remove from list) |
| 550 5.1.2 | Domain not found | Invalid domain: no mail server exists | No (remove from list) |
| 550 5.7.1 | Rejected by policy | Blocked: server refuses your probe | Inconclusive (needs further investigation) |
| 450 4.2.1 | Temporarily unavailable | Greylisted or temporarily disabled | Retry later; likely valid |
| 452 4.2.2 | Mailbox full | Exists but full | Risky (may be abandoned) |
| 421 4.7.0 | Too many connections | Rate limited | Retry from different IP; likely valid |
| 250 (catch-all) | Accepts all addresses | Catch-all server: cannot confirm individual address | Your policy (see catch-all guide) |
Why SMTP probing alone is not enough
SMTP verification is the most important single check in email verification, but it has limitations. A comprehensive verification service combines SMTP probing with multiple additional checks:
| Check type | What it catches | SMTP alone catches this? |
|---|---|---|
| Syntax validation | Malformed addresses (missing @, invalid characters) | Yes (fails at MAIL FROM or RCPT TO) |
| DNS/MX lookup | Domains with no mail server | Yes (connection fails at step 1) |
| SMTP mailbox probe | Addresses that do not exist on the server | Yes (this IS the SMTP probe) |
| Catch-all detection | Servers that accept all addresses | Partially (needs a second probe with fake address) |
| Disposable email detection | Temporary/self-destructing addresses | No (DEA addresses pass SMTP probing because they are temporarily valid). Learn more about disposable email addresses and why they require separate detection. |
| Role address detection | info@, admin@, abuse@ addresses | No (role addresses are valid mailboxes) |
| Spamtrap detection | Known spam trap addresses | No (traps are valid addresses by design) |
| Typo domain detection | gmial.com, yahooo.com, outlok.com | No (typo domains often have no MX, but some do) |
| Free vs business domain | Gmail/Yahoo vs company domains | No (both types have working SMTP) |
SMTPing combines SMTP probing with 12 additional verification layers to produce 13 distinct result types. This multi-layer approach catches threats that SMTP probing alone would miss: disposable addresses that are temporarily valid, role addresses that are technically deliverable but toxic for marketing, and typo domains that happen to have a catch-all server.
Challenges and limitations of SMTP verification
| Challenge | What happens | How good services handle it |
|---|---|---|
| Greylisting | Server temporarily rejects the first connection from unknown senders | Automatic retry after delay (usually 5-15 minutes) |
| Rate limiting | Server limits connections per IP; returns 421 after too many probes | Distribute probes across multiple IPs and throttle per domain |
| Catch-all servers | Server accepts all addresses, making individual verification impossible | Detect catch-all with random-address probe and flag results accordingly. See what is a catch-all email address for details. |
| Anti-verification protection | Some servers (Microsoft 365, some enterprise) block RCPT TO probing | Use alternative techniques (API-based checks, historical deliverability data) |
| Temporary server issues | Server is down or overloaded at probe time | Queue for retry; mark as “unknown” if all retries fail |
Microsoft 365 domains deserve special mention: Microsoft has increasingly restricted SMTP probing on their infrastructure. A verification service that relies solely on SMTP RCPT TO checks will return inconclusive results for many Microsoft-hosted domains. SMTPing handles this by combining SMTP probing with alternative validation techniques for providers that restrict direct probing.
Frequently asked questions
Don’t forget to clean your list. Boost your inbox rate.
SMTPing catches what regex misses: disposable addresses, role-based emails, catch-all domains, syntax errors, and 9 more invalid types. Free tier renews every day, no card required.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
