Email Verification Credits: What They Cost and How Many You Need

Verifying a list before you send to it is the cheapest insurance in email. A high bounce rate tells receiving providers that you don't know who your recipients are, and that judgement attaches to your domain rather than to the campaign that caused it — Google's sender guidelines are explicit that repeated invalid recipients hurt delivery. Email verification credits are how that check is priced here, and this page covers what they cost, how far they go, and when the deeper check is worth double.

What Email Verification Credits Buy

One credit verifies one address in standard mode. The check confirms the syntax is valid, the domain exists and accepts mail, and the mailbox itself responds — which is the part that separates real verification from a regular expression.

Deep mode costs two credits per address and goes further on the cases standard mode has to guess at. Some providers deliberately accept mail for every address at a domain, so a standard check can't distinguish a real mailbox from a catch-all that will swallow anything and bounce it later. Deep mode spends more effort on those, and on providers that rate-limit or delay verification attempts.

Both modes work on a single address or on a list. Bulk jobs run in the background, report progress, and produce a downloadable result you can feed straight back into whatever you're sending from.

The Price Ladder

Every plan includes a monthly allowance, and you can buy more at any point. The included figures:

Those cover ad-hoc checking rather than list cleaning. For real volume, purchased email verification credits run on a sliding scale that gets cheaper as the quantity grows:

At a million addresses the rate is a tenth of a cent each. That's the tier the pricing is really built around — the assumption is that people cleaning lists are cleaning large ones, and the ladder shouldn't punish them for it.

How Many Email Verification Credits You Actually Need

More than the size of your list, and the reason is worth understanding before you buy.

A list needs verifying when you acquire it and again when it goes stale, because addresses decay steadily as people change jobs and abandon accounts. A list verified eighteen months ago is no longer a verified list. So for an ongoing operation, budget the initial pass plus a re-check of anything older than six months.

If you're using deep mode, double the arithmetic. A sensible pattern is running standard mode across everything, then deep mode only on the addresses that came back ambiguous, which is usually a small fraction and keeps the cost near the standard rate while resolving the cases that matter.

Buying in one larger block rather than several small ones is materially cheaper. Ten thousand email verification credits at once is $29; the same ten thousand bought a thousand at a time is $50, so the ladder rewards deciding your volume up front.

Using the Platform Only for Verification

Plenty of people want the verifier without wanting the mail hosting, and that works. The free plan includes email verification credits, so an account that hosts nothing can still buy and spend a balance.

Where the lists come from is your business, not ours. If you've bought a database and want to know which of those addresses exist before touching them, that's exactly what the tool is for. Our sending rules apply to mail sent through our servers, and verification isn't sending — the point of checking a list is to find out what's in it before deciding anything.

What we'd say plainly is that verification tells you an address exists. It doesn't tell you the person wants to hear from you, and no verifier can. Clean lists reduce bounces; they don't manufacture permission, and the reputation damage from unwanted mail is a separate problem with a separate cure.

The Things Verification Cannot Fix

Being clear about the boundary saves money and disappointment.

It won't rescue a domain that already has a poor reputation, because that judgement is based on sending history rather than list quality, and it takes consistent good behavior to reverse. It won't get you past a spam filter, which is assessing content and authentication rather than whether the address is real. And it won't detect an address that exists but is a spam trap, since traps are designed to look valid.

It also can't be perfect on catch-all domains. If a receiving server accepts everything, no external check can prove a specific mailbox is real — deep mode narrows the uncertainty rather than eliminating it, and any provider claiming otherwise is overstating what the protocol allows.

Verification is one input to deliverability. The others are authentication and behavior, covered in improving deliverability and what your bounce rate means.

Reading the Results

Verification doesn't return a simple yes or no, and treating it as though it does is how people throw away addresses that were fine.

Deliverable means the mailbox responded and accepted. Send to these.

Undeliverable means the domain or the mailbox refused. These are the ones costing you reputation, and removing them is the entire point of spending email verification credits in the first place.

Risky is the interesting category. It covers catch-all domains where nothing can be proven, role addresses like info@ or sales@ that are real but shared, and mailboxes that look disposable. None of these is invalid; each carries a different reason for caution. Role addresses in particular are frequently the correct contact for a business and frequently stripped out by people treating risky as a synonym for bad.

Unknown means the check couldn't complete — the server timed out, rate-limited, or refused to talk. Retrying later often resolves it, and treating unknown as undeliverable discards addresses that were never tested.

A sensible policy is to send to deliverable, discard undeliverable, decide about risky based on what the address is, and re-check unknown before doing anything with it.

At Capture or in Batches

There are two moments to spend a credit, and they solve different problems.

Verifying at the point of capture catches typos while the person is still in front of the form and can correct them. Somebody typing gmial.com gets told immediately, rather than never receiving anything and concluding you ignored them. This is by far the cheapest place to spend email verification credits, because it prevents a bad address entering the list at all.

Batch verification handles what's already there: a list you inherited, bought, or built before you had checking in place, plus anything that's aged. Both are needed. Capture-time checking alone leaves your existing list untouched, and batch checking alone means new typos keep arriving.

For anything automated, the verifier is reachable through the API and through MCP, so a signup form or an assistant can check an address without anyone opening the dashboard.

Compared With a Dedicated Verifier

The specializt services do this and only this, and it's fair to say where they're ahead.

They generally offer more integrations out of the box — direct connectors into major CRM and marketing platforms, which matters if your list lives in one of them and you'd rather not move data around. Some also publish accuracy benchmarks and offer guarantees, which is worth something if you're verifying at very large scale and need contractual comfort.

Where this arrangement wins is price at volume and not needing another account. A tenth of a cent per address at a million is competitive with anything, the balance sits in the account you already have, and the results come back in a form you can use immediately.

If verification is a core part of your business and you're processing millions monthly with deep platform integration, a specializt is probably the right call. If you need a list cleaned properly a few times a year without adding a vendor, email verification credits on an account you already hold is the simpler answer.

The Practical Sequence

For a list you're about to use: run standard mode across all of it, remove the invalid, run deep mode on the ambiguous remainder, and keep the result dated so you know when it stops being current.

For an ongoing program: spend email verification credits at the point of capture where you can, since a single address costs a credit and catches typos while the person is still there to correct them, then re-verify the older parts of the list on a schedule rather than waiting for bounce rates to tell you.

Email verification credits are cheap enough that the expensive mistake is nearly always under-verifying — one bad send costs more in reputation than several years of checking.