Sequencers and lead databases now bundle a check. You press verify inside the tool, it spends credits from your plan, and each lead gets a label. Instantly, for example, labels results valid, invalid or risky/unknown, and says risky is often because the domain is catch-all (instantly.ai, read 24 September 2026). Its verification comes out of bundled plan credits rather than a price per check.
That merged label is where you lose information. A catch-all domain accepts every address, while an unknown means the server never gave an answer. You'd treat them differently: a catch-all at a real company is often a real person and worth a separate batch, and an unknown is worth a retry. A dedicated verifier keeps the two apart, so you decide row by row.
Bundled credits also hide the unit cost. ZapBounce prints it: $5 for 1,000 checks, $25 for 10,000 and $139 for 100,000, with unknowns and duplicates never billed. Put that next to what your plan credits cost and you know what each check really costs you.
Independence matters too. A tool that finds an address and then grades it is marking its own homework. When you run the export through a separate check, you see how many addresses the source got wrong before they reach your sending domain. The Apollo and Instantly guides show the CSV and API route in and out.
A built-in pass is enough when you top up a warm campaign a few leads at a time. For a cold list of thousands, every bounce lands on the domain you send from. Around 28% of a typical B2B list sits on catch-all domains, so one clean pass through bulk verification before import is the cheaper order of work.
Related questions
Is a built-in verifier enough for cold email?
For a small list mailed inside the same tool, often yes. For thousands of cold addresses, run a dedicated check first, so catch-all and unknown rows come back apart and no failed check is billed.
Why does my sequencer mark so many leads risky?
Risky usually groups catch-all domains with servers that gave no answer. Instantly's own page says risky is often because the domain is catch-all, read on 24 September 2026. Around 28% of a typical B2B list sits on catch-all domains.
Can I verify an Apollo export before importing it?
Yes. Export the list as CSV, upload it to ZapBounce and import the download back. You pay $5 per 1,000 checks, and unknowns and duplicates are free.
Do I need both a built-in and a dedicated verifier?
No. Run the dedicated check once before the list goes into your sequencer, and skip the in-tool pass on those rows so you don't pay twice.