Stop guessing on
4 in 10 business emails.

Real verification against the live mail server. No account, no card.

Used by B2B demand-generation and lead-gen teams processing millions of records a month. Every figure below can be evidenced from processing logs.

32M+
Records validated to date
2M+
Per month, largest single account
1,000+
Records per minute, sustained
<1s
Single-address response, typical

Four words, and what to do about each.

The verdict is the product, so here is the whole vocabulary. No fifth category, no hedging.

VerdictWhat it meansDo this
deliverable The mail server confirmed this exact mailbox exists. Send
risky It accepts mail, but we could not prove this one inbox is real. The score says how much proof we have. Send to warm contacts, or check nearer the send
undeliverable Positive proof it bounces. Not a guess, a rejection we saw. Drop
unknown A mail server blocked or stalled the check. We will not invent a verdict to fill the gap. Hold and retry

And this is the file that comes back.

Every row carries the verdict, the score and the reason it scored that way, so your team can act on the file instead of taking it on trust.

emailverdictscorecatch_allproviderreason
j.doe@acme.comdeliverable96falseGoogleMail server accepted this recipient and rejects unknown ones.
sales@acme.comrisky62falseGoogleShared inbox, not a person. Deliverable, but rarely read.
r.patel@northwind.iorisky84trueMicrosoft 365Domain accepts every address. Matches the format used by confirmed staff.
t.nguyen@northwind.iorisky41trueMicrosoft 365Domain accepts every address and nothing corroborates this local part.
old.hire@zenith-eng.comundeliverable3falseZohoServer replied 550, no such mailbox. Will hard bounce.
k.mills@fortress.counknownBarracudaGateway refused the probe. Held for retry, no verdict invented.

An illustration of the export format. Column set is the real one.

How one address gets its verdict.

Cheapest checks first. We only escalate when the answer is still in doubt.

01
Is it even a valid address?Spelling, structure, and a did-you-mean fix for obvious typos
02
Does this company receive mail at all?We look up the mail servers the domain publishes
03
Does this exact mailbox exist?We ask the mail server, and stop before any message is sent
04
And if the server says yes to everything?The hard case. We resolve it from the naming pattern we have learned for that company, plus corroborating signals
05
One verdict, and whyDeliverable, risky, undeliverable or unknown, with a score and a reason
ZeMailThe part that is actually hard

The addresses every other tool gives up on.

Somewhere between a third and four in ten business domains are catch-all: their mail server says yes to any address you ask about, real or invented. Ask it whether j.doe@ exists and it says yes. Ask it about asdfgh@ and it says yes to that too.

So a mail-server check alone cannot answer these, and most tools hand the whole pile back as “unknown”. That pile is your enterprise accounts.

ZeMail keeps going. It learns the naming pattern each company actually uses, corroborates against signals outside the mail server, and returns a scored verdict you can act on. When even that is not enough, it says so rather than guess.

Same address, same catch-all domain

A plain mail-server check returns

unknown

Accepted, but this domain accepts everything. No further information.

ZeMail returns

risky · 84

Domain accepts every address. This local part matches {f}.{last}, the format used by five confirmed mailboxes on this domain.

The difference is a row your team can work, instead of a row they have to throw away.

Upload a list. Get that file back.

Drop in a CSV or pull it from your own storage. Progress is live, rows are deduped, and you can download any single verdict on its own.

Download by verdict

Take just the deliverable rows for the send, just the risky ones for a closer look, and leave the rest. One file per decision.

A health score for the file

One number for the list plus the breakdown, so you know what it is worth before you send to it, not after the bounces land.

Big files do not queue behind each other

Bulk runs on fair scheduling, so one large upload cannot starve everyone else, and a single check never waits behind a list.

Proof, without the logo wall.

Our clients’ lists are their competitive advantage, so we do not name them. What follows can be evidenced from processing logs on request.

A B2B demand-generation client runs over two million records a month through the Zeplinix platform, continuously, on a dedicated workspace.

Demand generation · North America · under NDA

Running at that kind of volume, or need a workflow of your own?

Free and unlimited.

Verify and find as much as you need. No card, no seat limits, no quotas. If you need dedicated throughput or a workflow of your own, talk to us and we will set it up.

Security and data handling

We learn domain-level shapes. We do not keep your contacts’ addresses, and your list is never used to build a product we sell to anyone else.

  • TLS 1.2+ in transit · encrypted at rest
  • SOC 2 aligned. GDPR compliant.
  • Data Processing Agreement available on request
Security overview →

Questions we get asked.

What is a catch-all domain, and why does it matter?

Its mail server accepts mail addressed to anything, so asking the server whether one particular mailbox exists tells you nothing. Somewhere between a third and four in ten business domains behave this way, and most tools return “unknown” for all of them. That is usually the enterprise end of your list.

What happens when you cannot determine an address?

We return it as unknown and tell you which signal was missing. We would rather say we do not know than hand you a guess.

Do you store our contact data?

We retain domain-level patterns, not your contacts’ addresses. Your list is not our product. A Data Processing Agreement is available on request.

How fast is it at volume?

Single-address checks typically return in under a second on common domains. Bulk lists run on fair multi-tenant scheduling so one large file cannot starve everyone else’s.

What accuracy do you claim?

We are not publishing a number yet. The only accuracy figure worth quoting is one measured against real send outcomes, with the catch-all domains reported separately from the easy cases, and we would rather answer this late than publish a blended figure that flatters us. What we will commit to in the meantime: a verdict is only undeliverable if we saw the rejection, and never a guess dressed as a confirmation. Test it on a list whose outcomes you already know.

How does this relate to LeadQC?

They solve different problems and are sold separately. ZeMail answers whether an address is real. LeadQC validates whether the whole record (person, title, company, location) is still true. Teams running purchased lists usually need both.

Run your own list through it.

Bring your worst catch-all domains. Those are the ones worth testing.

hello@zeplinix.com · +91 92700 85057