Check an email address before you send to it. We test the format, look up the domain's MX records and mail provider, and flag disposable, role-based and likely trap addresses. No signup.
An address goes through the same steps whether you check it here or in the dashboard. This page runs the first four. The last two need an account. None of them sends an email.
The address is parsed against the email standard, including the 64-character limit on the part before the @ and 254 on the whole address.
Learn more →A domain one or two letters away from a major provider (gmial.com, hotmial.com) gets a suggested correction.
We look up the domain's mail servers in DNS and read which provider runs them: Google, Microsoft, a forwarding service, or the company's own server.
Learn more →The domain is matched against our list of temporary-mail providers, and the local part against role names (info@, sales@) and known spam-trap patterns.
Learn more →The full check connects to the mail server and asks whether this exact mailbox exists. It stops before any message is sent. For Microsoft 365 domains it can also ask Microsoft whether the account exists.
Learn more →It tests whether the domain accepts every address, and checks the address against bounce and delivery outcomes reported into our network by connected senders.
Learn more →Plenty of free checkers will tell you a mailbox exists. Some of them are right. The ones that check Gmail or Outlook at volume tend to be wrong more often than they let on, because the large providers protect themselves against address harvesting: they slow down, refuse, or accept every address once a verifier asks too many questions. A server that says yes to everything tells you nothing.
We run the mailbox check from a small set of mail servers whose reputation we look after, and we only run it for accounts. That keeps it working for the people who rely on it, and it means nobody can use this page to find out which addresses at a company are real. When a server won't give a straight answer, the full check says "unknown" and doesn't charge for it. We would rather tell you we don't know than call a dead address valid and put a bounce on your record.
How we grade the engine against real delivery outcomes, and why we report abstentions instead of guessing, is in how we measure email-validation accuracy. The step-by-step version of a full check is in how email verification works.
A full check gives each address a status, a sub-status saying why, and a confidence score from 0 to 100. These are all nine statuses, with what to do about each.
valid
Safe to send
The mailbox exists and accepts mail, confirmed by a live check or by strong delivery history.
What to do: Send.
invalid
The address can't receive mail: bad syntax, a domain with no mail servers, or a mailbox the server says doesn't exist.
What to do: Remove it. Sending will produce a hard bounce.
risky
Elevated risk. Some risky results have some clean delivery history behind them; others are accept-all domains with warning signs, or addresses that look machine-generated.
What to do: Read the sub-status. Send only the ones with delivery history, and watch the bounces.
catch_all
Safe to send
The domain accepts mail for every address, so the server won't say whether this particular mailbox exists. The confidence score says how likely delivery is.
What to do: Send with care, ideally to engaged contacts first.
unknown
We couldn't get an answer either way: the server deferred, timed out, blocked the check, or the provider doesn't confirm single mailboxes. It is not a verdict that the address is bad.
What to do: Never charged. Re-check later, or hold back from your first sends.
disposable
A temporary-mail address that works for minutes or days and then disappears.
What to do: Don't add it to a list. Ask for a permanent address at signup.
spamtrap
An address that looks like a spam trap: it accepts mail without bouncing and exists to catch senders who mail lists they didn't collect properly.
What to do: Never send. One hit can get your sending domain or IP blocklisted.
abuse
This address has marked mail as spam before, according to delivery outcomes reported into our network.
What to do: Don't send marketing mail to it.
do_not_mail
Mail to this domain goes through a forwarding service that accepts everything, so the real mailbox behind it can't be checked; or the domain is on a mail blocklist; or it is a registered misspelling of a major provider that accepts every address.
What to do: Avoid, unless the contact has engaged with you recently.
Each sentence below is the one the dashboard and the API return for that code. The full list is in the status code reference.
smtp_verifiedm365_mailbox_verifiedverified_mailbox_recentdelivery_history_stronglimited_delivery_historystale_delivery_historymailbox_not_foundm365_mailbox_not_foundno_mx_recordsno_mail_routefailed_syntax_checkpossible_typocatch_all_unverifiablecatch_all_domain_deliverscatch_all_high_risk_domaincatch_all_suspicious_patterndisposable_emailspam_trapknown_complainermx_forwardlookalike_domaindomain_blocklistedgreylistedtimeout_exceededsmtp_blockedmailbox_fullmx_lookup_failedgoogle_unverifiablemicrosoft_not_probedChecking addresses one by one is fine for a signup you're unsure about. For a list, upload a CSV of up to 100,000 addresses and get every row back with its status, sub-status and confidence, ready to import. Unknowns are refunded. For up to 50 addresses without an account, paste them into the bounce checker.
Yes. Format, typo, MX, mail provider, disposable, role and spam-trap checks are free with no signup and no credit card. A full check, which asks the mail server whether the exact mailbox exists, is free on an account: you get 100 credits a month, and results we can't settle (unknown) are never charged.
Not on this page. Confirming a mailbox means connecting to the domain's mail server and asking about that address. We only do that for signed-in accounts, because an open page that answers "does this mailbox exist?" for anyone is exactly what address harvesters look for, and mail providers block verifiers that get used that way.
Run it through a checker like this one first: it reads the address and the domain's DNS and sends nothing. The full check goes one step further and talks to the receiving mail server, stopping before any message is handed over, so nothing lands in anyone's inbox.
The address is well formed, the domain publishes mail servers, and nothing marks it as disposable, a role account or a likely trap. Most real addresses look like this, and so do many dead ones, because a mailbox that was closed last year sits on a domain that still accepts mail.
No. The address is checked in real time and isn't saved to our database. If you click through to sign up, it travels in the sign-up link and is kept in your session only, so the dashboard can open on it.
This page checks one address. The free bounce checker takes up to 50 pasted addresses. For a whole list, upload a CSV of up to 100,000 addresses on a free account, or call the API.
The checks on this page are deterministic: a domain either publishes MX records or it doesn't. The full check is where accuracy matters, and we report "unknown" rather than guess when a server won't give a clear answer. How we measure that against real delivery outcomes is written up in our accuracy guide.
Upload a CSV and get back the addresses that are safe to send. 100 free credits to start, no card, and no charge for the ones we can't verify.