Bulk email verification for lists you did not build yourself
Upload a CSV, get back every row with a status, a reason and the checks that produced it. Deduplication and the suppression list run first, so you never pay to check the same address twice.
From a CSV you do not trust to a list you can send
Four steps, and you can stop after any of them.
1. Upload the file
Drop in a CSV of addresses, or a CSV of names and company domains if you want the addresses found first. We map your columns, and the file can carry any extra columns you need back on the other side.
2. Deduplicate and suppress
Identical addresses collapse into one row. Anything on your suppression list, including addresses that failed a previous job and anyone who asked to be erased, is removed before a single check runs.
3. Verify every remaining row
Each address goes through syntax, domain and MX, the mailbox at the server, catch-all detection, role address detection and disposable domain detection. Rows are processed in parallel and a large file finishes without you sitting on the page.
4. Export what passed
Download the deliverable rows, the risky rows and the failures as separate files, or push the deliverable ones straight into HubSpot, Pipedrive or Salesforce. Your original columns come back with them.
What fits in a job
Only rows that come back deliverable count against the monthly limit. Undeliverable, catch-all, suppressed and duplicate rows are processed and reported, and they cost nothing.
| Plan | Rows per bulk job | Deliverable rows counted each month |
|---|---|---|
| Starter | 1,000 | 1,000 |
| Growth | 10,000 | 5,000 |
| Scale | 50,000 | 20,000 |
| Enterprise | Custom | Custom |
A clean list goes stale on its own
People change jobs, companies retire mailboxes and domains move their mail. A list that was clean in January is not clean in June, and nothing about it looks different until the bounces arrive.
On Growth and above you save a list and set it to re-verify on a schedule. Rows that stopped being deliverable are flagged before your next send rather than after it, and the re-check of an address you already verified does not spend your limit again inside the same period.
- Re-verify the CRM export before a quarterly campaign.
- Re-verify a badge scan list the week after an event, not the day of it.
- Re-verify before moving to a new sending domain, because a new domain has no reputation to spend on bounces.
Every row comes back with a reason
A status on its own leaves you guessing about the ones in the middle. Each row carries the status, the specific check that decided it, the catch-all flag and the time of the check, so you can set your own threshold instead of accepting ours.
- Status: deliverable, undeliverable, catch-all or risky
- Deciding check: which of the six checks produced that status
- Catch-all flag: whether the server accepts every address on the domain
- Role address flag: whether the mailbox belongs to a department
- Verified at: the timestamp of the check, so you know how old the answer is