Email Verifier
Check whether an email address is real without ever sending it a message. The verifier tests syntax, looks up the domain's MX records, and probes the mailbox at the SMTP level.
About Email Verifier
This email verifier answers a common question, does this address actually exist, in three progressive checks. First it validates the syntax to confirm the address is well-formed. Then it queries DNS for the domain's MX (mail exchanger) records to confirm the domain is set up to receive mail at all, and it returns the MX hostnames it finds in priority order. If there are no MX records, the address cannot receive email and the check stops there.
The final stage is a live SMTP conversation with the domain's highest-priority mail server. The tool opens a connection on port 25, greets the server with EHLO, issues MAIL FROM and then RCPT TO for the address being checked, and reads the server's response code. Crucially, it stops at that point and sends QUIT, so no message is ever delivered, no DATA is transmitted and the recipient sees nothing in their inbox. A 2xx acceptance for the recipient indicates the mailbox exists; a rejection indicates it does not, and the numeric code is reported.
To avoid false positives, the verifier also runs a catch-all test. Many domains accept mail for every possible address, so the tool probes a random, non-existent mailbox on the same domain. If that fake address is also accepted, the domain is flagged as catch-all and the result honestly reports that this specific mailbox cannot be confirmed, rather than pretending it exists. Results distinguish between exists, does not exist, and cannot be determined.
Email verification has real-world limits worth knowing. Some servers use greylisting or anti-abuse measures that defer or reject probes regardless of whether the mailbox exists, and catch-all domains inherently hide individual mailboxes. Because this stage needs outbound port 25 and DNS, it runs on our EU servers rather than in your browser. No email is sent, only the address you enter is checked, and the query is processed on European infrastructure without third-party trackers.
How to use it
- 1Enter the full email address you want to verify.
- 2Run the check and let the tool validate the syntax and look up the domain's MX records.
- 3Review the SMTP probe result: whether the mailbox was accepted, rejected, or is on a catch-all domain.
- 4Read the reason line and MX list to understand the verdict before acting on it.
Common use cases
- -Cleaning a mailing list to remove dead addresses and cut bounce rates before a campaign.
- -Validating a sign-up or lead-form address to catch typos and fake domains at the point of entry.
- -Sales and outreach teams sanity-checking prospect addresses without sending a test email.
- -Email and deliverability admins confirming that a domain has working MX records and an SMTP server.
- -Reducing hard bounces that damage sender reputation and inbox placement.
Frequently asked questions
- How does email verification work without sending an email?
- The tool connects to the domain's mail server and simulates the start of a delivery: EHLO, MAIL FROM and RCPT TO. It reads whether the server accepts the recipient, then sends QUIT before the message body. No email is ever delivered, so the mailbox owner sees nothing.
- What does a catch-all domain mean for verification?
- A catch-all domain accepts mail for every possible address, so an SMTP probe cannot prove that one specific mailbox exists. The verifier detects this by testing a random fake address; if it is also accepted, the domain is flagged catch-all and the result is reported as undeterminable.
- Can an email checker always tell if an address exists?
- No. Catch-all domains, greylisting and anti-abuse filtering can make a valid mailbox look uncertain or a probe get rejected. The tool reports mailbox exists, does not exist, or cannot be confirmed, and explains the reason rather than guessing.
- Does verifying an email send a message to that address?
- No message is sent. The check ends the SMTP session with QUIT before any message content is transmitted, so the recipient receives nothing and there is no trace in their inbox.
- What are MX records and why do they matter for email verification?
- MX (mail exchanger) records are DNS entries that name the servers responsible for receiving a domain's email. If a domain has no MX records, it cannot accept mail, so the address is invalid; the verifier lists the MX hosts it finds in priority order.
- Is the email verifier private and GDPR-friendly?
- The check runs on EU servers, uses only the address you submit, and involves no third-party trackers. Because it needs outbound SMTP and DNS, it runs server-side rather than in your browser, and it never sends mail to the address.