Email Verification Online & Bulk Email List Validation

uChecker is an online service for verifying email addresses and cleaning mailing lists. Each job handles up to 9 million addresses and returns the result as three lists: Good, Bad and Unknown. List cleaning removes non-existent and full mailboxes, domains with no MX records, and addresses on domains that sit on public blocklists, so your campaigns reach only real subscribers.

Why check whether an email address exists before you send? Every major ESP ( Unisender, Mailchimp, Sendsay, Brevo, SendPulse ) tracks your bounce rate and throttles deliverability when your list has too many dead addresses. A high bounce rate damages your domain and IP reputation, pushes messages into spam, and drives unsubscribes. One pass through the email validator typically removes 15-40% of junk and restores your inbox placement rate.

How the uChecker email validator works

The service checks each address through a cascade of validations. First comes syntax validation: is the format valid, are there any forbidden characters? Next is DNS validation and MX record check: does the domain have a working mail infrastructure? Then comes SMTP verification: we open a connection to the mail server and ask whether the mailbox exists, without sending any message. Major providers are handled by dedicated methods: Mail.ru, for one, answers «accepted» to almost any address, so an ordinary SMTP probe lies about it.

What email list cleaning finds

• Non-existent mailboxes produce hard bounces that fail on every send and hurt your reputation.
• Full and frozen mailboxes, where the server takes the connection but never delivers the message.
• Domains with no MX records and domains whose mail servers never answer.
• Domains on public blocklists such as DNSBL, Spamhaus and URIBL.
• Misspelled domains: gmal.com, yandx.ru, mial.ru. The domain fails to resolve, so the address is rejected.

A separate matter is catch-all domains, role-based addresses and disposable email. An SMTP probe gives no conclusive answer on any of them, and that is a limit of the protocol rather than of one service. What they are and how to handle them on your own side is covered in the glossary.

Who needs email list validation

Email marketers before a campaign, B2B teams before cold outreach, and any product that collects email addresses at registration. Anyone who cares about deliverability and sender reputation. Cleaning your list before importing it into a new ESP saves money: you stop paying to send to dead addresses, and a high percentage of valid subscribers gives your domain a strong warm-up from day one.

How much does email verification cost

The price starts at $3 per 1,000 addresses on the smallest plan and drops to $0.63 per 1,000 at a million addresses. The first 100 are free, which is enough to run a test sample from your own list and see the validator's accuracy for yourself. You can sign up in the web dashboard or through the Telegram bot @uchecker_bot; no credit card required.

The difference between email validation and email verification

In practice the terms are used interchangeably. Technically, there are three distinct levels:

• Syntax validation checks the address format against RFC 5321/5322 with a regex. Fast, but the weakest level of assurance.
• DNS and MX validation confirms that the domain has a working mail server. MX record checks cut out dead domains.
• SMTP mailbox verification connects to the mail server and confirms the address exists without sending a message (HELO/EHLO, MAIL FROM, RCPT TO).

How to read the results

A report splits addresses into five groups rather than two, and the distinction determines what you do with each. For deliverable addresses the server confirmed the mailbox exists and you can send. For undeliverable ones it rejected them, and those come out of the list permanently and go onto the suppression list.

Catch-all means the domain accepts mail at any address, so confirmation proves nothing. These are not discarded: catch-all is common on corporate domains, which is where the contacts you want tend to live. Segment them and send in small batches, watching actual bounces rather than predicted ones.

A disposable mailbox exists right now and will stop existing within the hour, so sending is pointless. Role-based addresses like info@ or support@ exist and are read, but nobody behind them opted in, so a marketing message there will very likely draw a complaint. Keep them for transactional mail and exclude them from campaigns.

The fifth group is unknown, and it holds addresses where the server gave no clear answer because of greylisting or a rate limit; the extended status marks them as risk. We do not charge for unknown, because billing for the answer "no idea" is not right. Watch this share separately, since zero unknowns does not mean perfect accuracy, it means the ambiguous cases were quietly filed as deliverable.

How often to re-check

A one-off cleaning solves today and not tomorrow. Lists decay on their own: people change jobs and lose corporate addresses, providers delete unused mailboxes, someone opens a new account and forgets the old one. Around twenty percent of addresses go stale in a year.

A working rhythm has three parts. Validate at the point of signup, where typos are caught before they enter the list. Validate before any large campaign if the list has been idle for a month or more. And clean the whole database twice a year regardless of sending frequency.

One important caveat: validation confirms an address exists and says nothing about consent. A technically clean list of people who never subscribed is still spam, and providers detect it through behaviour: low opens, complaints, spam trap hits. Checking addresses treats a different problem from the one causing it.

What happens to the list after a check

The report is where the work starts, not where it ends. Undeliverable addresses come out immediately and go onto a suppression list so they cannot return on the next import from your CRM. That matters more than it sounds: dead addresses usually re-enter a campaign precisely because the list is cleaned in one place and exported from another.

The suppression list has to be shared across every sending channel. The classic failure is keeping it inside the marketing platform while transactional mail goes out through a separate server. The address is suppressed for campaigns and still receives order notifications, bounces keep accruing, and nothing in the marketing reports explains why.

Soft bounces get a counter: three to five in a row on one address means the mailbox has been full for a long time or is no longer served. A single soft bounce is ignored, since that is ordinary network noise rather than a signal.

Why a high bounce rate does real damage

Bounces are harmful less in themselves than in how the receiving side reads them. To a provider, a high rate says plainly that the sender does not know who they are writing to. That conclusion attaches to the domain, not just to the campaign that triggered it.

Then accumulation takes over. Domain reputation has inertia: it degrades in one bad send and recovers over weeks of careful sending. Preventing the spike is far cheaper than working it back.

Acceptable rates depend on message type. Transactional mail should bounce at close to zero, because a live person typed that address minutes ago. Half a percent there is a reason to inspect the form, which most likely has no validation. For marketing to an accumulated list, up to two percent is normal; above five means the list has not been cleaned in a long time.

A note on spam traps

The most awkward kind of dead address is the one that is technically alive. Providers convert abandoned mailboxes into traps: the MX is in place, SMTP answers affirmatively, the syntax is valid. Any validator calls it deliverable, because it is deliverable. The only difference is that nobody is behind it.

So validation reduces the risk without removing it. It clears dead addresses and thereby slows the future supply of recycled traps. Against one that already exists, only hygiene helps: double opt-in at signup, regular pruning by engagement, and removing anyone who has not opened a message in a year.

API integration for validation in your product

Beyond the web dashboard and the Telegram bot, uChecker offers a REST email validation API for embedding checks in a registration form, CRM (Bitrix24, amoCRM, HubSpot), or ESP. Asynchronous processing of large lists is supported via webhook. Full developer guide in the uChecker API blog post.

Want to go deeper on email validation terms, deliverability, and authentication (SPF, DKIM, DMARC)? Browse our email marketing and validation glossary (100+ articles covering SMTP, SPF, DKIM, DMARC, BIMI, bounce codes, domain warm-up, and mail protocols) and the email marketing blog.