An email verifier confirms whether a specific mailbox is real and deliverable before you send. Done right, it protects your sender reputation, cuts bounces, and never delivers a test message. Here is how real verification works, and how to do it for free.
Verification happens in two layers. First the domain must be able to receive mail (MX) and ideally be authenticated (SPF/DMARC). Then the mailbox itself is probed in real time over SMTP — up to the recipient step — and the server’s answer is read, then the connection is closed. No email is sent.
Why the mailbox step matters: across our live scan of 50,000 domains, 80.6% accept mail — but a domain accepting mail says nothing about whether alice@that-domain exists. Provider behaviour varies wildly too: DMARC p=reject rates range from single digits to 61.8% depending on the host — which is exactly why you test the real server, not a guess.
Prefer to start with the domain? Use the free deliverability analyzer to see its MX/SPF/DMARC first:
Real-time verification opens an SMTP conversation with the recipient’s mail server up to the RCPT step, reads the server’s answer (accept / reject / unknown), then stops. No message is ever delivered. MailTester Ninja does exactly this and stores nothing.
A clear "accepted" means the mailbox exists and is deliverable; "rejected" means it does not. Honest verifiers also return "catch-all / uncertain" for domains that accept everything, and "unknown" when a server greylists — instead of guessing.
Because providers behave differently: some accept every RCPT then bounce later, some greylist first contact, some rate-limit probes. A verifier that tests against the real receiving server (and retries intelligently) beats one that guesses from the domain alone.
It can be. MailTester Ninja processes the address in memory to return a verdict and stores no email address or content — verification without building a database.
Related: Email checker · Deliverability Analyzer · Insights · Email Infrastructure Index.