Email Verifier
Validate any email address in real time. We check syntax, run a live MX lookup, detect disposable domains, and flag role-based addresses that rarely convert.
What email verification actually catches
An email verifier runs four checks: syntax (does it look like an email per RFC 5322), MX records (does the domain accept mail at all), disposable-domain detection (is this a throwaway mailbox), and role-based detection (is this a generic alias like info@ or support@). Together they catch roughly 95 percent of bad addresses without ever sending a real message.
The remaining 5 percent are spam traps, catch-all domains, and inboxes that look valid at the DNS layer but bounce on actual send. Catching those requires SMTP-level verification, which most providers no longer support reliably because greylisting and anti-recon defenses make the answers unreliable.
Why bounce rate matters more than you think
Gmail, Outlook, and Yahoo aggressively penalize senders with bounce rates above 2 percent. Hit 5 percent and you risk a permanent reputation hit that takes weeks of warm-up to recover from. Verifying your list before sending pushes bounce rate down from a typical 5 to 15 percent on scraped lists to under 1 percent on cleaned lists.
The math is brutal: a 10 percent bounce rate on a 5,000-email send is 500 hard bounces. That alone can flag your sending IP at the major receivers. Multiply across daily sends and a single dirty list can cost you 2 to 3 weeks of inbox placement.
Status types and what to do with them
Deliverable: clean address with valid MX and no risk flags. Send normally.
Risky: address is technically valid but flagged as disposable or role-based. Reply rates are typically 5 to 10x lower than verified personal addresses. Either skip in cold outbound or send a more cautious sequence with stronger opt-out language.
Undeliverable: domain has no MX records or syntax is broken. Hard bounce guaranteed. Remove from any active list. These should never be sent to, period.
Invalid: address fails RFC 5322 simplified pattern matching. Likely a typo or fake entry. Remove or, if from a form, prompt the user to re-enter.
Bulk vs single verification
Single verification (this tool) is for spot-checking. For lists of 100+, use a bulk verifier with deduplication, catch-all detection, and CSV upload (Navigent customers get bulk verification built into the workspace at no per-email cost).
Run bulk verification before every send, not once at import. Contacts change jobs, domains get retired, addresses go stale. A list verified six months ago is roughly 25 percent stale today on average B2B data.
Frequently asked questions
Is this email verifier free?
+
Yes, completely free for single-address verification with no signup. Bulk verification (CSV upload, 100+ addresses) is available inside Navigent for customers.
How accurate is the email verifier?
+
DNS-level checks (MX, syntax, disposable, role) catch around 95 percent of bad addresses with zero false positives on valid ones. The remaining 5 percent (spam traps, catch-all bounces) require SMTP-level verification, which is unreliable in 2026 due to widespread greylisting.
What is a disposable email address?
+
A disposable address is a temporary mailbox from a service like Mailinator, Guerrilla Mail, or 10 Minute Mail. Used by people who do not want to give a real address. Mail technically delivers but the recipient almost certainly will not see it. Skip these in cold outbound.
What is a role-based email address?
+
A role-based address is a non-personal alias like info@, support@, sales@, admin@, noreply@. They typically route to a shared inbox or autoresponder. Reply rates run 5 to 10x lower than personal addresses. Spam complaints from role-based addresses also count harder against sender reputation.
Why does my email verifier say MX found but the email still bounces?
+
MX records confirm the domain can receive mail. They do not confirm the specific mailbox exists. The mailbox could be retired, suspended, full, or a catch-all that bounces selectively. Catch-all verification requires sending and watching for the bounce, which is no longer reliable.
Does verifying an email send the recipient any kind of notification?
+
No. The verifier only performs DNS lookups (MX, syntax pattern matching, domain list comparison). No SMTP connection is made and no message is sent. The recipient has no way to know you checked their address.
Can I verify catch-all domains?
+
Not reliably. A catch-all domain accepts mail at any address regardless of mailbox existence. The address could be valid (real person) or invalid (typo or made up). We flag MX presence but cannot distinguish without an SMTP probe, which most providers now greylist.
How does verification affect cold email deliverability?
+
Verifying drops bounce rate from a typical 5 to 15 percent on scraped lists to under 1 percent on cleaned lists. Below 2 percent is the threshold for healthy sender reputation at Gmail and Outlook. Above 5 percent risks a reputation hit that takes weeks of warm-up to recover from.
Stop guessing, start shipping.
Navigent runs deliverability, lead-data, and multichannel outreach in one workspace. Start free, no credit card.