Email delivery in three steps
To understand verification, start with how email actually travels. First, the sending server asks DNS which server handles mail for the domain — the part after the @ — by querying its MX records. Second, it opens an SMTP connection to that server (or the next one responsible if it's unavailable) and transfers the message. Third, the recipient picks the message up from their mailbox via IMAP, POP3, or webmail.
Email verification walks the same path but stops before the transfer. It performs every check a real delivery would trigger — and then politely disconnects, so no email is ever sent and the address owner never knows.
The verification pipeline
Syntax and normalization
Everything starts with structure. The verifier validates the address against RFC syntax rules, strips formatting accidents, and catches obvious typos. ELV's engine goes further with a did-you-mean layer that recognizes gmial.com for gmail.com and suggests the fix instead of just rejecting.
Domain intelligence
Next, DNS: does the domain exist, does it publish MX records, and do those point at servers that actually respond? This pass also screens for risky top-level domains and high-risk keywords that correlate with abuse — our risk validator — and removes addresses on dead or parked domains outright.
Reputation databases
Before any live check, the address is matched against proprietary databases: known spam traps (addresses that exist only to catch careless senders), known complainers (people who habitually mark legitimate mail as spam), and disposable providers whose mailboxes evaporate within minutes. Any hit removes the address before it can hurt you.
The live SMTP conversation
Finally, the decisive test: the verifier connects to the recipient server and issues the same commands a real delivery would, watching the response codes. A 250 means the mailbox exists; a 550means it doesn't. Done well, this check is completely untraceable. Done carelessly — too fast, from burned IPs — it gets the verifier blocked and the results turn to noise. This is where verification services genuinely differ.
The hard cases are the whole game
Any tool can verify [email protected]. Accuracy is decided at the margins: greylisting servers that temporarily reject unknown connections (we wait and retry instead of guessing), catch-all domains that accept everything (we classify honestly as Accept-all rather than inflating our deliverable count), and throttling providers that demand patient, well-paced checks. Handling these properly is why ELV claims 99%+accuracy — and why we're comfortable backing every result with a 100% money-back guarantee.
Verification in practice
There are three moments to verify, and ELV covers all of them. Verify before a campaign with bulk list cleaning — upload a file, get back six clean segments. Verify at the point of capture with the real-time API, so typos and fakes never enter your database. And verify continuously with automated list cleaning, which re-checks your connected CRM lists on a near-daily cycle.
However you verify, the economics are the same: every bad address you remove is postage you stop wasting and reputation you stop burning. See exactly what your volume costs on the pricing page, or check how we compare with Emailable and Bouncer.