How to Check If an Email Address Exists Without Sending a Message
You can find out whether a mailbox exists without emailing it. Here are the methods, what each can prove and where they fall short.
Sending a test message to find out whether an address works is the worst way to do it: a bad address bounces and counts against your reputation. There are better methods that do not send anything.
Method 1: look at the domain first
Before anything else, check that the domain can receive mail at all. An MX lookup shows the mail servers of a domain. No MX record usually means no mail can be delivered there, so every address on that domain is invalid.
Method 2: ask the mail server (what a verifier does)
Mail servers answer a short conversation: who is sending, and is this recipient accepted? A verifier starts that conversation and stops before the message body. A reply of "accepted" is a good sign. A reply of "user unknown" (code 550 5.1.1) means the mailbox does not exist.
Method 3: use an email checker
The easiest way is a checker that does the steps above and adds more: syntax, typo hints, disposable providers and risk labels. Paste the address into the free email checker and read the result.
Why a plain "accepted" is not always proof
- Catch-all domains accept every address, real or not. The honest result is *risky*, not *valid*.
- Some providers protect their users by not revealing whether a mailbox exists. The honest result is *unknown*.
- Mailboxes change: valid today, closed next month.
Methods that do not work
- Guessing from a name: [email protected] might not be how the company writes its addresses.
- Sending a message and waiting for a bounce: slow and harmful to your sender reputation.
- Regular expressions alone: they only prove the format.
Checking many addresses
For more than a handful, upload a file to bulk email verification and filter the results by status. Plans and the free monthly allowance are on the pricing page.
Quick answers
- Is it legal? Verifying an address you hold lawfully is a normal data-quality step. Sending marketing to it still needs a valid legal basis.
- Does the person get notified? No. No message is sent.
What the server actually says
When a verifier asks about a recipient, the reply is a short code and a sentence. The common answers are:
- 250: the recipient is accepted. On a normal server this suggests the mailbox exists.
- 550 5.1.1: the mailbox does not exist. See 550 5.1.1 explained.
- 552 5.2.2: the mailbox exists but is full. See 552 5.2.2.
- 451 4.7.1: the server asked the sender to try again later, often greylisting. See 451 4.7.1.
How accurate can this be
It is accurate for most business and consumer mailboxes, with three honest limits. Catch-all domains say yes to everything, some large providers refuse to disclose whether a mailbox exists, and a server can be slow or down at the moment of the check. A good checker returns *risky* or *unknown* in those cases instead of guessing.
A short routine you can follow
- Check the domain with the MX lookup.
- Run the address through the free email checker.
- If the result is *risky*, decide by context: a person you know can be sent to, a cold prospect should wait for a second signal.
- Save the result so you do not check the same address again next week.
When you have a list, not one address
Do not check them one by one. Upload the file to bulk email verification and filter by status. The free monthly allowance covers small lists and plans for larger ones are on the pricing page.
