Stop guessing whether an
email really exists
CleanContact verifies email addresses against the mail servers that own them β not a guess from a regex. Clean your lists, cut your bounce rate, and protect your sender reputation before you hit send.
Validate an email right now
Type any address below. This form runs a real check through the CleanContact network and returns the same result our API does.
Runs a live check against our validation network. Returns Good, Bad, or Unknown.
Validation that actually knocks on the door
Most tools stop at the format and the MX record. CleanContact keeps going until it knows whether a human can receive your message.
Real mailbox checks
We go beyond syntax and MX lookups. CleanContact opens an SMTP conversation with the receiving mail server to confirm the inbox actually accepts mail.
Catch-all intelligence
Catch-all providers accept anything at the door. For the most popular domains β mail.ru, yandex.ru, gmail.com β we use provider-specific checks to tell a live inbox from a phantom one.
Distributed network
Validations are spread across a fleet of independent nodes with per-node cooldowns, so checks stay fast and your sender IPs never get rate-limited.
One simple endpoint
A single authenticated GET request returns a clear verdict and a human-readable reason. No SDK lock-in, no webhooks to wire up.
Keys you control
Issue, rotate, and revoke API keys from the admin console. Attach a captcha to public-facing keys and keep server keys clean and fast.
Reputation first
Cleaning your list before you send protects your domain reputation, lifts deliverability, and keeps you out of spam traps and blocklists.
How a validation flows
From one request to a confident answer in four steps.
Send the address
POST or GET a single email to the /validate endpoint with your API key. That is the entire integration.
We route it intelligently
A master node checks syntax and blocklists, then hands the address to the first free validation node. Cached results return instantly.
The right probe runs
We check that the domain actually has a mail server, that the specific mailbox exists, and that the address is not a disposable one β matching it against our DEA blacklist.
You get a verdict
Good, Bad, or Unknown β each with a detail string explaining exactly why, so you can decide what to keep.
Three answers, no ambiguity
Every check resolves to exactly one of these.
The mailbox exists and is accepting mail. Safe to send.
The address does not exist or is rejected by the server. Drop it from your list.
The server would not give a definitive answer in time. Retry later or treat with caution.
Ready to clean your list?
Start pay-as-you-go in minutes, or commit to a daily volume and save.