Free tool
Email Validator
Check the syntax, the domain's mail servers and the usual warning signs of an email address, without contacting anyone.
This email validator checks that an address is written correctly, that its domain publishes mail servers (MX records) and whether it is a known temporary-mail domain or a role address like info@. It never connects to the recipient's mail server, so it cannot say that a mailbox exists; for that you need a real inbox that actually receives a message.
What does this email validator check?
Four things, each shown as pass, warning or fail with a plain explanation. Syntax is checked in your browser and again on our server with the same code: the length of each part, the characters allowed, where dots may go, and the shape of the domain, including internationalised domains that are converted to their ASCII form for lookup.
Then the domain: we look up its MX records, and if there are none, its address records, which mail systems fall back to. A domain that declares a null MX, a single dot with priority 0, is telling the world it accepts no email at all. Finally two quick signals, whether the domain is a known throwaway service and whether the name is a role such as admin@, support@ or noreply@.
- Syntax: length, characters, dots, domain pieces and top-level domain.
- Typos: a suggestion when a common provider is misspelled, such as gmial.com. We only suggest; we never change what you typed.
- Domain receives mail: MX hosts, the address fallback, or a null MX.
- Temporary-mail domain and role address: warnings, never hard failures.
Can a tool tell if an email address really exists?
Not honestly. The only way to know a mailbox exists is to ask the recipient's mail server, and the usual trick of opening a connection and asking whether it would accept the address has two problems. Many servers accept every address and sort it out later, which is called a catch-all, so a yes means nothing. And a server that sees strangers probing addresses will often block the sender's IP, which is why we do not do it.
So this validator stops at what can be known for certain from public information. If a page promises to confirm that a mailbox exists, treat the result as a guess. The reliable test is to send a message to a real inbox and see it arrive, which is what a free temp inbox is for.
What makes an email address valid?
An address is a name part, an @ and a domain. The rules come from RFC 5321 for delivery and RFC 5322 for the format, and they are looser than most sign-up forms in some places and stricter in others.
| Rule | Limit or detail | Example that breaks it |
|---|---|---|
| Name part length | Up to 64 characters before the @ | 65 letters, then @example.com |
| Whole address length | Up to 254 characters | A very long name plus a long domain |
| Dots in the name | Not first, not last, never two in a row | .user@example.com, us..er@example.com |
| Name characters | Letters, digits and ! # $ % & ' * + / = ? ^ _ ` { | } ~ - | user name@example.com |
| Domain pieces | Letters, digits and hyphens, up to 63 characters, no hyphen at either end | user@-example.com, user@exam_ple.com |
| Top-level domain | At least two characters, not only digits | user@example.c |
| Quoted name | Legal, but many forms reject it | "john doe"@example.com |
What is an MX record, and what if a domain has none?
An MX record is a line of DNS that says which servers receive mail for a domain, each with a priority. Senders try the lowest number first. When a domain has several, delivery still works if one is down.
No MX does not always mean no mail. The standard says to fall back to the domain's own address record, which is called an implicit MX, so we report it as a warning: it can work, but it is unusual and often a sign of a domain that was never set up for email. A null MX is different: it is a deliberate statement that the domain never receives mail, so we report it as a fail. If a lookup times out, we say so rather than guess. To inspect a domain in depth, use the MX lookup and the email health check.
Tricky email addresses for testing forms
Sign-up forms disagree with the standard in both directions, so a good test suite includes addresses that are legal but unusual and addresses that look almost right. Every example below uses a reserved name (example.com, example.net, example.org and the .example, .test and .invalid domains), so none of them can reach a real person. Paste any of them into the validator above to see how it is judged.
| Address | Per RFC 5321/5322 | Forms usually accept it? | Note |
|---|---|---|---|
| simple@example.com | Valid | Yes | The baseline every form accepts. |
| first.last@example.com | Valid | Yes | Dots between words are fine. |
| user+news@example.com | Valid | Usually | A tag after +; Gmail delivers it to the base address, some forms reject +. |
| USER@EXAMPLE.COM | Valid | Yes | The domain is case-insensitive; almost every provider ignores case in the name too. |
| user@mail.sub.example.org | Valid | Yes | Mail can go to a subdomain. |
| a@example.net | Valid | Usually | One-letter names are legal, a few forms demand more. |
| x-y_z.1@example.test | Valid | Yes | Hyphen, underscore and digits are plain atext characters. |
| user!#$%&'*/=?^_{|}~@example.com | Valid | Sometimes | All of these symbols are legal unquoted; many forms use a stricter pattern. |
| 64 × a @example.com | Valid | Sometimes | Exactly at the limit for the part before the @. |
| 65 × a @example.com | Invalid | No | One character over the 64 limit. |
| "john doe"@example.com | Valid | Rarely | Legal in quotes; most forms and many servers refuse it. |
| "user@home"@example.com | Valid | Rarely | A quoted name can even contain an @. |
| user@bücher.example | Valid | Sometimes | Domain is stored as xn--bcher-kva.example for DNS. |
| üser@example.com | Valid only with SMTPUTF8 | Rarely | Needs RFC 6531; many servers cannot deliver to it. |
| user@[192.0.2.1] | Valid | Rarely | An IP number instead of a domain; almost never accepted. |
| user@example | Legal syntax, cannot receive mail | No | No dot, so no top-level domain: it never reaches the public internet. |
| user@example.c | Legal syntax, cannot receive mail | No | Real top-level domains have two or more characters. |
| user@example.com. | Invalid | No | A dot at the end of the domain is not allowed in an address. |
| .user@example.com | Invalid | No | The name part cannot start with a dot. |
| user.@example.com | Invalid | No | The name part cannot end with a dot. |
| us..er@example.com | Invalid | No | Two dots in a row are not allowed. |
| user@@example.com | Invalid | No | Only one @ is allowed outside quotes. |
| user name@example.com | Invalid | No | Spaces need quotes, which turns this into a different address. |
| user@-example.test | Invalid | No | A domain piece cannot start with a hyphen. |
| user@exam_ple.test | Invalid | No | Underscores are not allowed in host names. |
| user@example..test | Invalid | No | An empty piece between two dots. |
When is a disposable or role address a problem?
A temporary-mail address is fine for a one-off download or a test, and a poor choice for an account you want to keep: the inbox may be public, short-lived or blocked by the site. That is why the validator warns instead of failing. Our own inbox domains are on the list too, marked as what they are: a temporary inbox anyone can open, or a private inbox for signed-in members.
Role addresses such as info@ or support@ reach a team, so they are often refused at sign-up and rarely get a reply to a cold message. They are perfectly good as a published contact address. If you are collecting emails for a list, ask for a personal address.
How do I test with an address that really receives mail?
Reserved domains like example.com are safe because mail sent there goes nowhere, which is also why they cannot test delivery. For a sign-up that sends a confirmation code you need an inbox that receives it. Open a free temp inbox and use that address; the message shows up on the page in seconds. The safe test data page collects reserved domains, IP ranges and phone numbers for everything else, the random identity generator builds a whole test person, and the password generator makes the password.
Frequently asked questions
Is this email validator free?
Yes. It is free, needs no sign-up and the address is not saved, logged or shared. It is checked in memory and the result is returned to you.
Does it check that the mailbox exists?
No, and it says so. It never connects to the recipient's mail server, because many servers accept every address and probing gets IP addresses blocked. It confirms the syntax and that the domain can receive mail.
Why does a valid address get a warning?
A warning means the address is legal but may cause trouble: a quoted name part, an international domain, a temporary-mail domain or a role name. It is information for you to weigh, not an error.
What does "no MX records" mean?
The domain does not list mail servers. Mail may still reach its web address through the implicit MX fallback, but it is unusual. If the domain also has no address record, or declares a null MX, it cannot receive mail.
Why is my address marked as a temporary-mail domain?
Its domain is on our short list of known throwaway services, which includes our own inbox domains. Some sites block these. The list is not complete, so an address that is not flagged may still be disposable.
Can I validate a list of addresses?
This page checks one address at a time. For a list, use the syntax rules in the table above in your own code, or create real test addresses in bulk.
Why do some forms reject a valid address?
Most forms use a simpler pattern than the standard, so they refuse quotes, plus signs, long names or international domains. The tricky-address table shows which ones usually pass.
Related
Need an address that really receives mail? A temp inbox is live in one click, and a free account keeps a private one.