The product

Email verification that tells you the truth

Kluno cleans your list against a 12-layer engine: real SMTP checks, provider-aware logic, catch-all and role detection. When an address genuinely can't be confirmed, we say unknown instead of guessing "valid" to pad our numbers.

12
Verification layers
3
Honest verdicts
<2s
Typical response
API
+ Clay & CSV

Everything you need to clean a list

One engine, many ways to use it. Verify a single address, drop in a CSV, or wire the API into Clay and your existing stack.

🔎

Real SMTP verification

We open a live conversation with the receiving mail server, not a database lookup. That's what separates a real check from a guess.

ðŸĒ

Provider-aware logic

Microsoft 365, Google Workspace, and Gmail each behave differently. Kluno reads each provider on its own terms instead of one blunt rule.

ðŸŠĪ

Catch-all & role detection

Flags catch-all domains, role accounts (info@, sales@), disposable inboxes, and likely spam traps, the addresses that quietly hurt deliverability.

✍ïļ

Typo & did-you-mean

Catches gmial.com-style mistakes and suggests the intended address, so you recover leads instead of dropping them.

🔌

API, Clay & CSV

A clean REST API with per-key auth, a Clay-ready HTTP column, and bulk CSV upload in the dashboard. Fits the workflow you already run.

ðŸŸĄ

The honest "unknown"

When a mailbox genuinely can't be confirmed, we tell you. No inflated "valid" rate that blows up in your bounce report two weeks later.

A 12-layer engine, not a lookup table

Most "verifiers" match your address against a stale list of known-good and known-bad. Kluno actually checks. Every layer runs on every address.

1
Syntax & typo repair
RFC-valid format check plus did-you-mean correction for common domain typos.
2
DNS, MX & disposable
Confirms the domain can actually receive mail and screens out throwaway inboxes.
3
Provider-specific probing
Tailored handling for Microsoft 365, Google Workspace and Gmail, each read on its own behavior.
4
SMTP conversation & scoring
A live mailbox check, then a confidence verdict: valid, invalid, catch-all, or unknown.
Walk through all 12 layers →
kluno.xyz/app (single check)
jordan@acmecorp.com Valid
Status
valid
MX found
yes
Provider
Google
Role based
no
Free email
no
Did you mean
-

"Unknown" is a feature, not a failure

Roughly half of all business email runs on Microsoft 365, which deliberately answers "OK" to every address to stop attackers from mapping a company's mailboxes. No verifier on earth can confirm those with certainty.

Competitors hide this. They stamp those addresses "valid" (or bury them as "catch-all") so their accuracy number looks better. Kluno tells you the truth: unknown. You decide whether to send, and your bounce rate stays honest.

kluno.xyz/app (single check)
sarah@contoso.com Unknown
Status
unknown
Sub status
undeliverable_unknown
Provider
Microsoft
MX found
yes
Role based
no
Did you mean
-

Kluno vs. the "99% accurate" crowd

Every verifier hits the same physics ceiling on Microsoft 365. The difference is whether they admit it.

  Kluno Typical verifier
Real live SMTP checksYesSometimes
Returns an honest "unknown"YesNo, guesses "valid"
Provider-aware (M365 / Google)YesPartial
Catch-all & role flaggingYesYes
Inflated accuracy marketingNever"99%+"
API + Clay + CSVYesVaries

Good to know

Because a false "valid" is worse than an honest "unknown." If a verifier guesses "valid" on an address it can't actually confirm, you send, it bounces, and your sender reputation takes the hit. "Unknown" hands you the decision with the real risk labelled.
A catch-all domain accepts mail to any address, so we can confirm the domain but not the specific mailbox. "Unknown" is when the provider (usually Microsoft 365) refuses to reveal anything about the mailbox at all. We separate the two so you can treat them differently.
Yes. Upload a CSV in the dashboard for bulk verification, or wire the API into Clay with a single HTTP column. The same 12-layer engine runs behind all three surfaces.
Most addresses return in under two seconds. Some providers are slower to answer an SMTP conversation, so a small share take longer. We'd rather wait for a real answer than return a fast guess.
Create a free account and your key is in the dashboard. Pass it as ?key= or an x-api-key header. Full details are in the API docs.

Clean your list the honest way.

Start free with 500 verifications a month, no credit card. Bring your own list and see the difference an honest verdict makes.