Email Validator
Check whether an email address can actually receive mail. Tests syntax, the domain and its MX records, and flags disposable, role and catch-all addresses.
Enter the address you want to check — [email protected]. A mailto: link or a pasted "Name <address>" works too.
No message is ever sent to the address being checked. Short of delivering one, no check can promise a mailbox will accept mail — a good result means every obstacle we can see has been cleared.
Related tools
All Network tools →This tool queries an external service to answer your request. Only the value you enter — such as a domain or IP address — is sent. Your other data stays on your device.
This tool reads public records — DNS, WHOIS and certificate data that registries and servers publish openly. It sends nothing to the host you enter and changes nothing there. Use it on infrastructure you own or are authorised to look into.
About the Email Validator
Check whether an email address can actually receive mail before you send anything to it. Enter the address and get back a verdict, the reason behind it, and the handful of things worth knowing about the domain it belongs to.
The check happens in layers. First the syntax — whether the address is even well-formed. Then the domain: does it exist, and does it publish MX records, the DNS entries that say where its mail should be delivered? A domain with no MX records cannot receive mail at all, which is the single most common reason a typed address silently fails. Finally the address itself is tested against the receiving server.
Three things are flagged separately because they are not faults, but they change what you should do. A disposable address comes from a throwaway inbox provider and will stop working within hours. A role address — info@, support@, sales@ — reaches a team rather than a person, which matters for anything personal or contractual. A catch-all domain accepts mail for every address whether or not the mailbox exists, which is why some perfectly good addresses come back as "could not be determined" rather than confirmed.
Nothing here sends a message to the address. That is deliberate, and it is what makes the tool safe to run against an address you do not own — no test mail lands in a stranger's inbox, and nobody learns you were checking. It also sets the honest ceiling on the answer: short of delivering a message, no check anywhere can promise a mailbox will accept one. A good result means every obstacle we can see has been cleared.
How to use the Email Validator
-
Enter the address
Type or paste the full email address. A mailto: link or a "Name <address>" copied out of a mail client both work — the extra wrapping is stripped for you.
-
Run the check
Complete the verification check and press Validate address. The lookup takes a second or two and never sends mail to the address.
-
Read the verdict
The headline says whether the address looks deliverable. Below it, the reason and any signals — disposable, role, catch-all, free webmail — explain what is behind that verdict.
-
Act on the signals, not just the verdict
A valid address that is disposable or a role account may still be the wrong one to use. Copy the full result if you need to record what was checked and when.
Frequently asked questions
Does this send an email to the address?
No, and that is the point. The check inspects the address syntax, the domain, and the MX records the domain publishes, then asks the receiving mail server about the address without delivering anything to it. No message arrives in anyone's inbox, which is what makes it safe to run against an address you do not own.
It says "could not be determined". What does that mean?
Almost always that the domain is configured as a catch-all, which means it accepts mail addressed to anything at all — existing mailbox or not. A catch-all server answers "yes" to every address, so its "yes" carries no information and we will not report it as a confirmation. The address may well be fine; the server simply refuses to tell anyone either way.
What is a disposable email address?
An address from a service that hands out temporary inboxes, usually to get past a signup form without giving out a real address. They work for minutes or hours and then stop, so anything you send later — a receipt, a password reset, an invoice — will bounce or vanish. Flagging them is useful when you are cleaning a signup list.
Why is a role address like info@ flagged?
Because it goes to a shared mailbox that several people read, or sometimes to a ticketing system that nobody reads directly. It is perfectly valid and often the right address to write to, but it is the wrong one for anything personal, confidential or contractual — and mailing-list providers frequently treat role addresses as a deliverability risk.
Can I check a whole list of addresses at once?
Not here — this tool checks one address per run. Every check is a paid lookup on our side, and a bulk upload form is exactly the shape of page that turns a metered service into an unbounded bill. For a one-off address, or for spot-checking the handful in a list that look wrong, this is the faster route anyway.
Why is there a verification check before I can use this?
Because every validation is a paid API call on our side, and an email checker is precisely the page someone points a script at to grind through a stolen address list. Without a gate the cost of that would be ours. For an ordinary visitor the check is usually invisible and needs no action.