Email Verifier & Finder

The Email Verifier & Finder checks every address in your list and tells you which ones are safe to send to. It flags bounces, disposable inboxes, role accounts, and catch-all domains, and gives each row a clear status and a confidence score so you are not guessing.

It does two things most checkers don't. It recovers addresses that are missing or that bounce, by rebuilding them from the email pattern it learns from other confirmed addresses on the same company. And it gives catch-all domains, the ones most tools shrug at, a real confidence score instead of an "unknown".

Your original file is never modified. Verification adds new columns at the right of your data and writes a new output file.

You pick how far to take the check before you run. Full verification confirms every address and costs credits. Quick clean screens the list for free and costs nothing, but it does not confirm whether real-looking addresses exist.

Every checked row gets one of these statuses in the email_status column. This is the verdict you sort and filter on.

Alongside the status, every checked row gets a confidence score from 0 to 100 in the email_score column. It's there so you can set your own threshold instead of relying on a binary verdict: send to anything above your line, hold the rest for review.

Catch-all domains get a score but never a clean verdict, because the server accepts every address and won't confirm a mailbox. A catch-all is flagged for review, not marked valid, and never labeled "verified".

Where the score does its most detailed work is in the Finder. When Operelio rebuilds a missing or failed address that lands on a catch-all domain, it scores that rebuilt address from the signals it can see (its fit against the company's pattern, whether the name matches, the domain's mail setup) and lists the evidence in plain language, for example "matches company pattern" or "name match". You get a number you can act on with the reasons behind it. See Recovering missing and failed addresses below.

When a row has no email, or the address you uploaded bounces, the Finder can rebuild a likely address and check it. You start it with one click on the results page (Refine list) after the first pass has run.

Here is how it works. Operelio learns the dominant email format for each company from the addresses in your file that already verified (for example first.last@ or flast@). For a row that's missing or failed, it rebuilds the most likely address from the person's name and that learned format, then verifies the rebuilt address. Each newly confirmed address strengthens that company's pattern, which can push a company that was just short of the threshold over the line, so another pass may recover more. It repeats until a full pass finds nothing new.

Two limits keep this honest. It only ever builds from patterns already present in your own file, never from an outside contact database, and it works only on the rows in your job. And a rebuilt address that lands on a catch-all domain is scored, never marked verified, exactly like any other catch-all. It rebuilds addresses from a pattern. It never invents a person.

Every row also gets a send-readiness score from 0 to 100 in the email_send_readiness column. It ranks rows by how ready they are to send, so you can export a clean cut without reading every status.

A confirmed verification ranks highest. A rebuilt address from the Finder is deliberately capped below the verified floor, because a good guess is still a guess and should never outrank a real verification. Risky, catch-all, role, and disposable rows rank lower in turn, and rows with no usable address rank at the bottom.

On the results page, drag one slider to the confidence line you're comfortable with. The count updates live ("export N of M"), and the download gives you just the rows at or above your line. Set it high for a conservative send, lower it to include more borderline rows.

Verification tells you what's likely to bounce before you send. Bounce feedback closes the loop afterward: once you've actually sent, you tell Operelio what happened, and it uses that to sharpen your future checks.

On a finished Email Verifier job, find the "Track how your send went" panel. Upload a CSV of your send results, with the email address and whether each one delivered or bounced. The columns can be in any order, and Operelio matches on the email address. It reads which addresses delivered, which bounced, and which drew a complaint, and records the outcome for each one against that job. You can come back to the same job anytime to add more results.

Here is what it does with them. For addresses that sit on catch-all domains, where verification can't confirm a mailbox and Operelio gives a graded confidence score instead, your own bounce history makes the score more cautious. If a domain has burned you before in your own sends, a new guess on that domain scores lower next time, and the reason shows up in plain language as "bounced before in your list". It only ever adjusts those probabilistic catch-all guesses. It never changes a confirmed verification.

Two things stay true, and they matter. The learning is per-workspace. Your send results sharpen your account's future checks and nobody else's, they are never pooled into a shared database, and there is no cross-customer model. And it's optional: an admin can turn the calibration off for the workspace in Team settings, and you'll still keep the bounce analytics.

Every send result you record also feeds an analytics view, under Analytics and History, on the Analytics tab. It's a running scorecard on the tool against your own real sends, for your workspace only.

You get your delivered, bounced, and complaint totals and your overall bounce rate, a weekly bounce-rate trend, and a breakdown of where bounces concentrate by recipient domain so you can see which domains are dragging your deliverability down. The most useful view is the credibility check: of the addresses Operelio called valid or recovered, how many actually bounced. Lower is better, and pattern guesses are expected to bounce more than confirmed addresses. It's the honest measure of how well the tool is working for your lists.

Filter by date range, and pick the view from the dropdown at the top. The analytics are available to whoever holds the bounce-upload permission.

Your original file with new columns added at the right. You can sort and filter on any of them.

Verification runs on a single pool of verify credits. There is one currency, whether a row goes through the first check, escalates to the deeper second check, or gets recovered by the Finder.

You're billed once for each distinct address that gets a verdict, whether that verdict comes from a fresh check or from one Operelio already holds. A row escalated from the first check to the second still costs one credit, not two. A new candidate the Finder builds for a failed row costs one; re-checking the same address costs nothing. Catch-all scoring makes no provider call, so it costs nothing.

Verifications that can't return a definitive result, the true unknowns where the server won't say, aren't counted against your balance. And Operelio shows the credit cost and your remaining balance before you run, so there are no surprise overages mid-batch.

The Email Verifier & Finder is on every paid plan. Each plan includes a monthly allowance of verify credits shared across the workspace.

Full email verification runs up to your plan's daily limit: 2,500 rows per day on Pro, 8,000 on Team, and 25,000 on Agency.

A few situations the tool puts you in, and how to handle each.