Verify every email before it reaches your CRM

Operelio uses a two-stage check. The first stage handles the bulk of your list at high speed. Risky and catch-all addresses escalate to a second, deeper check that runs extended validation against the receiving server. Most single-check tools return a shrug on those, and the escalation is what turns them into a usable answer. Your own accuracy is measured on the Analytics tab: of the addresses Operelio called valid or recovered, how many actually bounced.

Quick clean is free and available on every plan, including Free. It runs the free signal checks only: it removes addresses that can't receive mail (broken syntax, no mail server) and flags disposable and role accounts. It does not confirm whether a real-looking address actually exists, so those come back marked "unverified". It costs zero credits. Full verification, on Pro and up, is the complete check. The free signal checks run first and skip provable junk for free, then every deliverable address is verified, the uncertain ones (risky, unknown, catch-all) get a deeper second check, and the Finder can rebuild addresses that are missing or bounce. Full verification costs verify credits, one per row whatever happens to it. Use Quick clean to screen a list for free, and Full verification when you need a confirmed verdict on every address.

A catch-all domain accepts mail at any address whether the mailbox exists or not. They are common on B2B lists. Most simple checks return "unknown" on these and you're left guessing. Operelio escalates catch-all addresses to a second, deeper check, then flags them with a confidence score so you can make the call rather than getting a shrug. It never labels a catch-all "verified". And when the Finder rebuilds a missing or failed address that lands on a catch-all domain, it scores that address with plain-language evidence behind the number, for example "matches company pattern" or "name match".

Most files finish in a few minutes. Bigger lists take longer, and so do lists with a lot of catch-all or risky addresses that need the deeper second check, because those run in stages and each stage waits its turn behind other jobs. You don't have to wait on the page. The job lands in your notifications when it's done. Verification runs up to your plan's daily limit: 2,500 rows a day on Pro, 8,000 on Team, and 25,000 on Agency.

Verification uses credits. Pro includes 1,000 verify credits each month, Team includes 4,000 shared across the workspace, and Agency includes 12,000 shared. Beyond the included quota, you buy a pack: 2,500 credits for $30, 10,000 for $100, 50,000 for $400. Packs never expire. You can also add a pack as a recurring top-up, billed monthly on its own date, which costs less than buying the same pack one-time. Verifications that can't return a definitive result (true unknowns where the server won't say) aren't counted against your balance.

Yes, the tool will verify any list you upload. You're responsible for making sure you have a lawful basis to contact the people on it under GDPR and equivalent regimes. Verification is a quality check, not a consent check. Worth knowing: scraped lists usually have high bounce rates, and verification will tell you the size of that problem but it won't fix it.

Your original file with new columns added at the right. The verdict columns are email_status (one of valid, risky, invalid, disposable, role, catch-all, or unknown), email_score (a 0 to 100 confidence number, populated for every checked row), email_provider (which check produced the verdict, either verification for the first pass or deep check for the second), email_reason (a short code like low_quality, catch_all, or role_account), and email_rechecked (yes when the deeper second check looked at that row). Then come the context columns: email_mx (yes, no, or unknown for whether the domain has a mail server), email_type (business, freemail, role, or disposable), email_typo_suggestion (a likely-correct domain when the one you entered looks like a typo, left blank otherwise, and only ever a suggestion), and email_recommended_action (send, review, or exclude). You can sort and filter the file on any of these.

Yes, two ways. Drag the send-readiness slider in the Download panel to the confidence line you want and export just the rows above it. Or use the Split by status download, which gives you three CSVs (valid.csv, risky.csv, invalid.csv) zipped together: send the valid list to your campaign tool, hold the risky list for a manual review, and throw away the invalid list. You can also push the valid rows straight to HubSpot, Salesforce, or Pipedrive through Operelio's CRM Formatter.

Operelio verifies each email and stores the verdict, the confidence score, and a one-way hash of the address for 7 days, so a recent verdict can be reused instead of re-checking the same address. That hash can't be turned back into an address, and it carries nothing about you or your file. The raw address is held only for the standard file-retention window on your plan (30 days on Pro and Team, 90 days on Agency), then deleted. We don't sell or resell your list, and your list itself is never shared with another customer. See the security page for the full details.

You can download the enriched file, split it into valid, risky, and invalid CSVs, or send the valid rows straight into CRM Formatter for direct push to HubSpot, Salesforce, or Pipedrive. You can also chain the Email Verifier & Finder into a saved workflow that runs every time a new list lands.

For your account, yes. After a send, upload the results (which addresses delivered and which bounced) on that job's page. Operelio records the outcome for each address and uses your workspace's own bounce history to score future catch-all guesses on those domains more cautiously. A generic verifier checks an address in isolation and never learns what happened after you hit send. Operelio can, because you tell it. Two things stay true: it only tunes the probabilistic catch-all guesses, never a confirmed verification, and the learning is per-workspace. Your send results never get pooled with other customers, and there is no shared cross-customer model. You can also turn the calibration off per workspace in Team settings while still keeping the bounce analytics.

Under Analytics & History, the Analytics tab shows your delivered, bounced, and complaint totals, your bounce rate over time, where bounces concentrate by domain, and the one that matters most: of the addresses Operelio called valid or recovered, how many actually bounced. It's a running scorecard on the tool against your own real sends. Available to whoever you give the bounce-upload permission to.