Email Verifier & Finder

To find and verify the work email addresses in a list, upload it to the Email Verifier & Finder and run Full verification (Starter and up): each address is checked and gets a status and a send-readiness score from 0 to 100. For rows with no address or one that failed, Find emails rebuilds a likely address from the pattern of the company's confirmed addresses and checks it; on a catch-all domain, where no check can confirm the inbox, it scores the guess and shows the evidence.

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 send-readiness 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 at the same company. And when it rebuilds an address on a catch-all domain, where no check can confirm the inbox, it scores that guess and shows the evidence behind it instead of calling it verified.

Your original file is never modified. Verification adds new columns at the right of your data and writes a new output file. Verify that output again and its old result columns are replaced, not added a second time.

To check a single address, use the Check a single email box under the upload area on the Email Verifier & Finder tool page, or the one on operelio.com/email-validation. It runs in your browser, spends no credits, and checks the format, common typos, placeholders, disposable domains and whether the domain has a mail server. It can't confirm the inbox exists; Full verification does that.

You pick how far to take the check before you run. Full verification confirms every address and costs credits. Quick clean screens the list on every plan, using one job and no credits, 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.

Every row gets a send-readiness score from 0 to 100 in the email_send_readiness column. It's the email_send_readiness column in the results preview and the number the Minimum send-readiness slider uses, so it's the one to decide what to send by.

It ranks each row by its verdict: valid 95, risky 35, catch_all, unknown and unverified 25, role and disposable 15, invalid 3, and 0 for a row with no usable address. A Finder guess on a catch-all domain, or an address that needs fixing first (a likely typo, or extra text pasted around it), is capped below 95, because a guess should never outrank a real verification. A rebuilt address that verifies ranks with the verified ones.

Your file also keeps email_score, the raw number from whichever check ran: a fixed number per verdict from the first check, 0 to 100 from the deeper second check, or the Finder's graded score for a guess on a catch-all domain. It's there for anyone who wants the raw number.

To export, click Change beside the Send-ready file and drag the Minimum send-readiness slider to the lowest score you'll accept (after a Quick clean, Change is beside the Look real file). It is offered when the result is a CSV. The row count updates live, 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.

When a row has no email, or its address failed (invalid, risky or unknown), the Finder can rebuild a likely address and check it. You start it from the results page after the first pass has run: Find emails on the Find missing emails card, or Find N emails on Email patterns in this list when the run learned its companies' patterns. It doesn't replace an address that came back catch_all.

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. You pick how many passes to run, 1 to 10; each pass tries one more address per contact, the likeliest first.

When a rebuilt address lands on a catch-all domain, no check can confirm the inbox, so the Finder scores it instead, 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, for example "matches company pattern" or "name match". It shows as Pattern guess and is never marked verified.

Two limits. 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. It rebuilds addresses from a pattern. It never invents a person.

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

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 score future Finder guesses on catch-all domains more cautiously.

On a finished Email Verifier job, find the "Track how your send went" panel. Upload a CSV or Excel file 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. If it can't tell which column holds the result, name that column Result or Status. 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.

When the Finder rebuilds an address on a catch-all domain, it scores the guess, and your own bounce history makes that score more cautious. If a domain keeps bouncing in your own sends, a new guess on it scores lower next time, and the reason shows up as "bounced before in your list". It only ever adjusts those Finder guesses. It never changes a confirmed verification.

Two things to know. The learning is per-workspace. Your send results adjust your own workspace's Finder guesses and nobody else's, they are never pooled into a shared database, and there is no cross-customer model. And it's optional: on Pro and Agency, an admin can turn off Learn from bounce results in Settings, Team, and you'll still keep the bounce analytics.

Every send result you record also feeds an analytics view: Bounce feedback, on Home's 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.

Pick the view from the list on the left and the date range at the top. The analytics are available to whoever holds the bounce-upload permission.

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 one credit for each row that gets checked, whether the result 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. Scoring a Finder guess on a catch-all domain makes no provider call, so it costs nothing.

Blank cells, broken syntax, dead domains, placeholders and disposable addresses cost nothing. And Operelio shows the credit cost and your remaining balance before you run, so there are no surprise overages mid-batch.

The Quick clean screen runs on every plan, including Free. Full verification against live mail servers is on every paid plan, and each paid 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 Starter, 8,000 on Pro, and 25,000 on Agency. A file with more rows than your daily limit is refused for full verification, so split it first.

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

Once the settings are right for the files you get every week, a trail can run them for you. A trail watches a folder and verifies every email address on every file that lands there, then pushes the result into HubSpot, Salesforce or Pipedrive, with nine always-on safety checks, two more you set, and approval built in. Set it up once and the cleanup, the verification, the lead routing and the CRM import are automated from then on.

Trails run on Starter and above.