A new subscriber, an address a customer typed at checkout, an old contact you want to write to again: before you send, you want to know whether the address works. Sending a test message is the slowest and riskiest way to find out. You can check an email address without sending anything, and the five methods below go from the quickest to the most thorough.
What makes an email address valid
"Valid" can mean three different things, and each one needs its own check:
| Level | The question | How to check it |
|---|---|---|
| Syntax | Is the address written correctly? | Formatting rules (method 1) |
| Domain | Can the domain receive email at all? | Its MX records (method 2) |
| Mailbox | Does this exact mailbox exist? | Asking its mail server (method 3) |
An address can pass the first two and still bounce. firstname.lastname@gmail.com is perfectly formatted, on a domain that receives mail, and may belong to nobody. Only the third check answers the question you actually care about. Methods 4 and 5 then tell you whether a "yes" can be trusted, and whether the address is worth keeping.
Method 1: Check the syntax
An email address is a local part, an @ and a domain: jane.doe@example.com. The main rules:
- exactly one
@, and no spaces; - letters, digits and some symbols such as
.,_,-and+before the@, with no dot at the start or the end and no two dots in a row; - a domain with at least one dot, ending in a top-level domain that exists (
.com,.ma,.co.uk…).
| Address | Valid syntax? | Why |
|---|---|---|
jane.doe@example.com |
Yes | |
jane.doe+news@example.com |
Yes | A +tag is allowed; Gmail, Outlook and many other providers deliver it to jane.doe@ |
jane doe@example.com |
No | A space |
jane@@example.com |
No | Two @ |
jane.@example.com |
No | A dot right before the @ |
jane@gmail,com |
No | A comma instead of a dot |
jane@example.con |
Formatted, but no | .con is not a top-level domain |
The last two are typos rather than bad addresses, and they are common on sign-up forms. A good checker suggests the fix (gmail.com, .com) instead of only rejecting the address.
Syntax checks are instant and can run anywhere, even in the browser. But they only catch typing mistakes: they cannot tell a real mailbox from an invented one.
Method 2: Check that the domain receives email
Every domain that receives email publishes MX records, the names of its mail servers. Look them up in a terminal:
nslookup -type=mx example.com
dig +short mx example.com
Or use the free MX lookup. There are three possible outcomes:
- MX records found: the domain receives mail. Go on to method 3.
- No MX record, but the domain has an address (an A record): sending servers fall back to that address, so mail can still be delivered.
- A "null MX" (
0 .), or no domain at all: the domain receives no mail, and every address on it is invalid.
This check catches expired domains, abandoned company domains and invented ones. It is still only about the domain: nobody-here@gmail.com passes it.
Method 3: Ask the mail server if the mailbox exists
This is the check that answers the real question, and it works without sending an email. A verifier starts the same conversation (SMTP) that a sending server would, and stops before the message itself:
220 mx.example.com ESMTP
HELO verify.example.org
250 mx.example.com
MAIL FROM:<check@example.org>
250 2.1.0 OK
RCPT TO:<jane.doe@example.com>
250 2.1.5 OK
QUIT
221 2.0.0 Bye
The answer to RCPT TO is the result. 250 means the server accepts mail for that mailbox; 550 5.1.1 means it does not exist (see what 550 5.1.1 means). The conversation ends with QUIT before any message is sent, so nothing reaches the inbox and the person is not notified.
You can try it by hand with telnet, but it rarely works from a laptop:
- most home connections and cloud servers block outgoing port 25;
- large providers slow down or refuse checks from unknown servers, especially without a proper reverse DNS name (what a PTR record is);
- checking many addresses from your own IP can get it blocklisted, and then your real email suffers too.
That is the job of an email verifier: servers with a clean reputation and correct DNS, which retry when a mail server asks them to wait.
Method 4: Check whether the domain accepts every address
Some mail servers answer 250 to every address, real or not. These are catch-all (or accept-all) domains, common at companies. On them, the "yes" from method 3 proves nothing.
A verifier detects them by asking the same server about a random address that cannot exist, such as zq8x7k2@company.com. If that one is accepted too, the domain accepts everything, and the address is reported as catch-all: it may be deliverable, but it is not confirmed. How to handle those addresses: catch-all email addresses.
In MailQuell, this extra probe is part of every standard check, at no extra cost: 1 credit per address. Only the quick mode and the free checker skip it, to answer faster.
Method 5: Look at what kind of address it is
A mailbox can exist and still be a poor address to keep:
- Disposable addresses come from temporary inbox services and expire within hours. People use them to get past a sign-up form. See disposable email addresses, or test a domain with the disposable email checker.
- Role addresses such as
info@,support@orsales@reach a team, not a person. They are real, but engagement is lower and complaints are more frequent. See role-based email addresses. - Typos on popular providers (
gmial.com,hotmail.con) are better fixed than rejected: suggest the correction while the person is still on your form.
Why not just send a test email?
It works for one address, and it is the worst option for more than a handful:
- every hard bounce counts against your sender reputation (hard and soft bounces explained);
- a catch-all server accepts the test and may drop it, so silence proves nothing;
- some servers bounce hours later, after you have moved on.
Searching the address on Google or social networks tells you whether someone published it, not whether the mailbox works today.
The fast way: an email checker
An email checker runs these checks in a few seconds. MailQuell's free email checker tests the syntax, the domain and its MX records, then asks the mail server about the mailbox. It flags disposable and role addresses and free providers, and suggests a fix for common typos. You get 3 free checks a day without an account; the address is not stored and no email is sent.
For more addresses:
- A whole list: upload it and download the part you can send to (how to verify a list in bulk).
- Every new sign-up: check addresses as people type them, with the API or on WordPress, Wix and Ghost forms.
- The free plan: 200 checks every month, plus 100 welcome credits once you confirm your email.
What the results mean
| Result | What it means | What to do |
|---|---|---|
safe |
The mail server confirmed the mailbox exists | Send |
invalid |
The domain does not exist, has no mail server, or the mailbox does not exist | Remove it |
disabled |
The mailbox exists but is disabled or suspended | Remove it |
inbox_full |
The mailbox exists but is over its storage quota | Do not send now; check again later |
catch-all |
The domain accepts every address, so this one cannot be confirmed | Send with care |
disposable |
A temporary inbox | Remove it, or ask for another address |
role |
A shared address such as info@ |
Send with care |
risky |
Deliverable, but other signals lower the score | Send with care |
unknown, timeout, blocked |
The server gave no clear answer, or refused the check | Check again later |
In MailQuell,
unknown,timeoutandblockedresults are free: the credit is given back.
Frequently asked questions
Can I check if an email address exists without sending an email?
Yes. The mailbox check (method 3) stops before any message is sent. The person is not notified and nothing lands in their inbox.
Is a regular expression enough to validate an email address?
For the format, yes; for the rest, no. A regex catches a missing @ or a space, but anything@gmail.com passes it. Use it on your form for instant feedback, then check the domain and the mailbox before the address goes into your list.
Why does a verified address still bounce?
Time passes between the check and the send, catch-all servers accept first and bounce later, and some bounces are about your sending setup rather than the address. Here are 7 common reasons.
How accurate is an email checker?
As accurate as the mail server's answer. For most domains that answer is clear. For catch-all domains and servers that refuse checks, no tool can confirm the mailbox, and a good one says so instead of guessing.
How do I check a whole list at once?
Upload it to a bulk verifier. How to verify an email list in bulk walks you through it.
Check an address now
- Try one with the free email checker: 3 checks a day, no account.
- Create a free account to check a list or your sign-up form: 200 checks every month, no card needed.