A bounced email costs more than one email.
Send to enough addresses that don't exist and mailbox providers start treating you as a spammer. Then your good emails go to spam too.
So before a cold email goes out, it's worth knowing whether the address is real. You can find out most of it without sending anything. Here's how verification works, step by step, and what I've learned running it on every contact in Adamlead.
The five checks
Every email verifier, free or paid, runs some version of these five. They go from cheap and certain to expensive and fuzzy.
1. Is it shaped like an email?
The syntax check. One @, something before it, a domain with a dot after it, no spaces.
It sounds too basic to matter, but it catches the copy-paste mistakes: a trailing full stop, "mailto:" stuck on the front, two addresses run together, a space in the middle. Clean these up before anything else.
Catches: typos and junk. Costs: nothing.
2. Does the domain exist?
Look up the domain in DNS. If it doesn't resolve, nothing sent to it can arrive.
This catches companies that shut down, rebranded and let the old domain lapse, and misspellings like "gmial.com".
Catches: dead and misspelled domains. Costs: nothing.
3. Does the domain accept email?
This is the MX record check, and it's the most useful free one. A domain's MX records say which servers accept mail for it. No MX record (and no fallback address record) means no mail.
Here's what it looks like in practice. Adamlead has run this check on 3,110 work emails at funded startups:
- 3,085 domains had working mail servers.
- 25 had none, so those emails were marked invalid without ever sending.
Under 1%, but every one of them would have been a guaranteed bounce.
The MX records also tell you who hosts the mail. Of the 2,823 startup domains we've looked at, 72% use Google Workspace and 16% use Microsoft 365. That matters later.
Catches: domains that can't receive mail. Costs: nothing.
4. Is it a risky kind of address?
Some addresses exist but aren't worth sending to:
- Disposable addresses (temporary inboxes that vanish in an hour). Not a buyer.
- Role addresses like info@, sales@, support@, admin@. Real, but shared, rarely read by the person you want, and more likely to report you.
- Free providers like Gmail or Outlook.com on a B2B list. Not wrong, but it's not a work email, so it's often old or personal.
Each is a list lookup. Startup data is very clean on this, by the way: across our 3,110 checks, we found 1 role address, 1 free provider and no disposable ones. A scraped list from somewhere else will look very different.
Catches: addresses that are real but bad for cold email. Costs: nothing.
5. Does the mailbox exist?
The real question, and the hard one.
A verifier connects to the company's mail server and starts sending a message, the way a real mail server would: it says who it's from, then asks to deliver to jane@acme.com. The server answers yes or no to that address. Then the verifier hangs up before sending anything.
When it works, it's the strongest signal you can get without an actual email. But three things get in the way:
- Catch-all domains. Some servers say yes to every address, real or not, and sort it out later. A verifier can only report "accept-all": the domain is fine, the person is unknown.
- Greylisting and rate limits. Some servers say "try again later" to strangers, or block anyone asking about lots of addresses.
- Big providers protect themselves. Google and Microsoft are very good at spotting this kind of probing, and some setups don't reveal much.
This is why paid verifiers exist. They run this check from servers with a good reputation, spread out over time, and they've seen millions of results. It's also why no verifier is right 100% of the time, whatever the landing page says.
Catches: most addresses that don't exist. Costs: usually a fraction of a cent to a cent per address.
What our own checks do, honestly
Adamlead's in-house verifier runs checks 1 to 4 on every contact: syntax, domain, MX lookup, and the disposable, role and free-provider lists. It never opens a connection to the mail server, so on its own it can only get an address to "probable", never "verified". "Verified", the top status, comes from the data sources we import contacts from, not from these in-house checks.
Every address then gets one of three statuses and a confidence score from 0 to 100. As of October 26, 2026, of 3,103 work emails on file:
| Status | Emails | Share | Median confidence |
|---|---|---|---|
| Verified | 2,667 | 86% | 92 |
| Probable | 104 | 3% | 55 |
| Unverified | 332 | 11% | 35 |
We show the status and the score next to every email instead of calling everything verified. If an address is a guess, you should know it's a guess.
You can run the same free checks on any address with our free email verifier. No sign-up.
What no verifier can tell you
Even a perfect check only says the mailbox exists. It can't tell you:
- Whether they still work there. People leave; their address keeps accepting mail for a while, sometimes forwarding, sometimes into a void. At startups, check the person's LinkedIn before a big send.
- Whether it reaches the inbox. That depends on you: your domain, your authentication, your content and how many people mark you as spam.
- Whether they'll care. That's the email's job.
A simple routine before every send
- Clean the list: trim spaces, lowercase, remove duplicates.
- Drop syntax failures and dead domains.
- Drop disposable addresses. Move role addresses to a separate, gentler list.
- Run a mailbox check on whatever's left if the list is new or old.
- Send to "verified" first. Send to "accept-all" and "probable" in smaller batches and watch the bounces.
- Stop and look if bounces go over about 2%. That's a common rule of thumb, and well before you're in trouble.
And set up your own domain properly. Google and Yahoo have required SPF, DKIM and DMARC from bulk senders since 2024, and they expect spam complaints to stay under 0.3%. Since most startups are on Google Workspace, Google's rules are the ones that matter for your list.
What's your bounce rate on cold email right now, and do you verify before you send?