Choosing the best email verification API: what to test before you buy
How to pick an email verification API: accuracy, catch-all handling, pricing model, API design, integrations and data handling, plus a test plan you can run.
Syntax, DNS, MX, SMTP and normalization: what each check catches and what it misses.
How to pick an email verification API: accuracy, catch-all handling, pricing model, API design, integrations and data handling, plus a test plan you can run.
Put a small serverless function between your website form and your CRM: verify each lead's email, push real leads with their status, and keep junk out.
What each email verification status and reason code means, which ones you can trust, and what to do with the address: send, suppress, segment or retry.
How email typo detection works, why gmial.com passes every format check, and the UI copy that gets people to fix the address without silently changing it.
A practical cleaning schedule by list type: verify at entry, re-check before big sends and sequences, and react to bounce and complaint signals in between.
How Gmail, Google Workspace and Microsoft 365 answer mailbox checks, why some tenants accept every address, and how to read risky and unknown results.
How email verification fits GDPR: lawful basis, legitimate interest, data minimisation and processor contracts, plus what pingutil stores and for how long.
Greylisting makes mail servers temporarily refuse unknown senders, so verifiers get a 4xx instead of an answer. What RFC 6647 says and how to handle unknown results.
What accuracy claims from email verifiers usually measure, why catch-all and unknown results exist, and how to test a verifier's accuracy on your own list.
Catch typos, throwaway addresses and dead mailboxes in webinar and event signups before the confirmation and reminder emails go out, without adding friction.
Timeouts, retries, caching, rate limits and what to do with unknown results: the checklist for wiring an email verification API into signup, CRM and outbound tools.
Bad addresses waste sequence steps, rep time and sending reputation. A worked example with hypothetical numbers shows how to estimate the cost on your own list.
Pristine, recycled and typo spam traps explained, why no verifier can reliably flag them, and the list hygiene habits that keep you off blocklists.
Clean an exported lead list before importing it into a sequencer: dedupe, verify every address, split by result, and keep risky contacts out of the main sequence.
Real-time email verification checks one address as it is entered; bulk verification cleans a list before a send. When to use each, and why most teams need both.
What to remove from a newsletter list before a send: disposable and dead domains, provider typos, system addresses and sometimes role addresses. With a script.
Verify email at signup in real time: catch typos with a did-you-mean prompt, block only what is certainly bad, and warn instead of blocking on everything else.
Work email addresses die when people change jobs and companies change domains. How B2B email list decay happens, how to spot it, and a re-verification cadence.
Invalid addresses cause hard bounces and spam trap hits, which providers read as a sign of a bad list. What Gmail, Yahoo and SES say, and how to fix it.
Hard bounces are permanent 5xx failures, soft bounces are temporary 4xx ones. How to read SMTP and enhanced status codes, and which addresses to suppress.
A good email bounce rate is under 2% of hard bounces. Here is where that number comes from, which providers publish limits, and what drives bounces up.
Why to verify a prospect list before it enters a sequence, how to sort valid, invalid, risky and unknown results, and what to do with each bucket.
A practical email risk score for signups: which signals to use, hard rules vs points, score bands, and how to calibrate it against your own abuse data.
A signup domain that receives mail but has no website is a useful fraud signal, not a verdict. What DNS shows, the innocent cases, and how to score it.
A catch-all domain accepts mail for any address, so verifiers can't confirm a mailbox. How detection works, why it's common in B2B, and how to treat it.
Why jane.doe+trial2@gmail.com and janedoe@googlemail.com are one inbox, and how to build a canonical email key that catches duplicates without breaking login.
What an SMTP mailbox probe really tests, the six ways its answers mislead you (VRFY, catch-all, greylisting, port 25 blocks), and what to use instead.
Handle addresses like jane@bücher.de: convert the domain to punycode with UTS 46, leave the local part alone, and avoid the traps that split one domain in two.
Run MX, A and AAAA lookups from edge functions and serverless runtimes with the Cloudflare and Google DoH JSON APIs: request format, status codes and gotchas.
How to tell from DNS whether a domain accepts mail: MX lookups, the implicit MX fallback, null MX, and which DNS errors should never block a signup.
A regex can only tell you an email address is shaped right. What to match, what to deliberately reject, and the checks a pattern can never replace.
Validation checks that an address could work. Verification proves someone receives mail there. What each layer catches, misses, and where it belongs.
SPF and DMARC show whether a domain's owner set up outbound mail authentication. How to look them up over DNS, what they prove, and what they don't.
RDAP replaced WHOIS for generic TLDs in 2025. How the two protocols differ, how to query RDAP in code, and where you still need WHOIS for country-code domains.
Verification services check if a mailbox will accept mail. Classification APIs tell you what kind of address it is. Which job needs which, and when to use both.
Free tiers of ZeroBounce, Abstract, Hunter, MailboxValidator, Emailable and Kickbox compared: quotas, resets, SMTP checks, and where a usage-based API like pingutil fits.