MailCheck opens a real SMTP conversation with the mail server to confirm a mailbox exists — then scores catch-all domains, flags disposables and finds missing addresses. Cut hard bounces and protect your sender reputation.
Syntax, DNS, reputation and the live mailbox — with the exact reason an address is good, risky or bad.
We open a real SMTP conversation and confirm the mailbox accepts mail — without ever sending an email.
Accept-all domains get a 0–100 score, not a shrug — so you can keep the ones worth sending to.
Block throwaway providers and known spam-trap patterns before they tank deliverability.
Turn a name + company domain into a verified address using the most common corporate patterns.
Upload up to a million emails per job with concurrency control and per-domain throttling.
One REST call returns clean JSON. Keys, rate limits, caching and a usage dashboard included.
Every address runs the full pipeline and returns a status plus a 0–100 confidence score.
RFC-grade format and normalization — before any network call.
Resolve mail servers, with implicit-MX fallback to A records.
Disposable, role and free-provider checks, plus typo suggestions.
Connect to the MX, confirm the mailbox at RCPT, detect catch-all.
Classify valid, invalid, catch-all, unknown or disposable.
Every result maps to one status, with sub-status detail and a score you can threshold on.
| Status | Meaning | Typical action |
|---|---|---|
| valid | Mailbox exists and accepts mail. | Safe to send. |
| invalid | Bad syntax, no MX, or the server rejected the mailbox. | Remove. |
| catch-all | Domain accepts every address — scored by confidence. | Send by threshold. |
| unknown | Greylisted, timed out, or temporarily deferred. | Re-check later. |
| disposable | Temporary / throwaway mailbox provider. | Remove. |
Have a prospect's name and company domain but no email? MailCheck generates the most-used corporate patterns, probes the mail server, and returns the address that actually exists.
first_name, last_name, domainA clean REST API with predictable JSON, API keys you manage yourself, per-key rate limits, and built-in result caching so repeat checks are instant and free.
How MailCheck compares to a typical hosted verifier.
| Capability | MailCheck | Typical verifier |
|---|---|---|
| Real-time SMTP mailbox probe | ✓ | ✓ |
| Catch-all confidence score (0–100) | ✓ | partial |
| Multi-IP rotation with matched rDNS | ✓ | — |
| Email finder included (not an add-on) | ✓ | — |
| Self-hosted / on-prem option | ✓ | — |
| Re-check pool for greylisted addresses | ✓ | — |
| No per-credit lock-in | ✓ | — |
“Typical verifier” reflects common behaviour of popular hosted services. Capabilities vary by plan.
Create an account and verify right away. Upgrade for higher volume and dedicated sending infrastructure.
RCPT TO stage — the same handshake a real mail server uses to decide if a mailbox exists. We never send a message, so the recipient sees nothing.Create a free account and verify your first emails in under a minute.