Loading...
Tool briefWhat this tool offersCheck whether an email address is deliverable before you send to it, or find a work address from a name, a LinkedIn profile or a company domain.

What it does

  • A single check returns a 0 to 100 confidence score and a status of valid, invalid, catch-all or unknown.
  • Six signals are evaluated: syntax, MX records, disposable provider, role-based address, catch-all and the confidence score, and no email is sent.
  • Finder modes include name plus company domain, LinkedIn profile URL, or a plain-language prompt.
  • Bulk checks handle up to 100 addresses per batch and return results as a table.

Why it is different

  • A catch-all domain is reported as catch-all, never as valid.
  • The finder verifies every candidate address before returning it.
  • Validate, find by name, find by LinkedIn and find by domain sit in one tool with one API.

How to use it

  1. Paste an email address and run the check.
  2. Switch to LinkedIn URL, Name plus domain, or AI prompt to find an address.
  3. Read the verdict and the confidence score.
  4. For a list, switch to bulk and paste up to 100 lines.

You provide: An email address, a LinkedIn profile URL, a first and last name with a company domain, or a list of up to 100 lines.

You get: A status and a 0 to 100 confidence score per address, or a found address; the API returns JSON.

Limits, API and MCP details are in the full brief: /email-validator.md

What an email check actually tells you

This tool takes an address and returns a deliverability confidence score in a couple of seconds, without sending anything to it. Everything it uses is externally observable: syntax, whether the domain publishes mail servers, whether the provider is disposable, whether the address is a role account, and whether the domain accepts everything. You can check one address, paste up to 100 at once, or work the other way and find an address from a first name, last name and company domain, with each candidate pattern verified before it comes back. No account. 10 validations and 10 finds a day, free.

The signals

Six checks, no email sent

Syntax

Is the address well formed under the RFC rules, before anything more expensive runs.

MX records

Does the domain publish mail servers at all. A domain with no MX cannot receive mail, whatever the local part says.

Disposable

Is it a temporary or burner provider, the kind used to get past a signup form once.

Role-based

Addresses like info@, admin@ and support@ reach a shared inbox rather than a person, which changes what the address is worth to you.

Catch-all

Does the domain accept every address at it. If it does, an individual address cannot be confirmed or ruled out from the outside.

Confidence score

The signals above resolved into one 0 to 100 number and a status: valid, invalid, catch-all or unknown.

Questions

Straight answers

How does email validation work here?

By checking what is observable from outside: whether the address parses, whether the domain publishes mail servers, whether the provider is a disposable one, whether the local part is a role address, and whether the domain accepts everything sent to it. No message is ever sent to the address, which is why the result is a confidence score rather than a guarantee.

Is it free, and is there a limit?

Free, and no account is needed. It is metered rather than unlimited: 10 validations and 10 finds a day. Signing in does not reduce that, and paid plans raise it.

Can I validate a list at once?

Yes, up to 100 addresses in one batch, one per line, returned as a table you can export. Larger jobs are what the REST endpoint is for.

Can I find an email from a name and a company?

Yes. Give a first name, a last name and a domain, and the common address patterns are generated and then verified, so what comes back has been checked rather than guessed.

What is a catch-all domain?

A domain configured to accept mail sent to any address at it, existing or not. That means an outside check cannot confirm one specific mailbox, so the result is reported as catch-all rather than valid. It is information, not a failure: mail will very likely be accepted, but you cannot prove the mailbox exists.

Is there an API?

Yes, and it needs no key: POST an address to /api/v1/email/validate, or a name and domain to /api/v1/email/discover. CORS is open so it works from a browser. There is also an MCP server, so an assistant can call it directly.