Article

Is Apollo's Built-In Email Verification Good Enough?

By Unlimited Verifier Team ·

Flow diagram showing Apollo contacts labelled verified, then passing through a second email verification pass that separates valid addresses to send from invali

Summary

Apollo's built-in email verification is good enough for ranking contacts and dropping obviously dead addresses, but it is not reliable enough on its own for large cold sequences. Its status label blends finding an address with judging whether it still receives mail, so a bounce cannot tell you what went wrong. Verify a sample with a second tool and calculate invalid rates per Apollo status before you decide.

Apollo's built-in email verification is good enough to triage prospects and catch obvious dead addresses, but for cold sequences it is not enough on its own: keep bounces under 2% by running a second, independent verification pass before you send.

Quick answer

What does Apollo's built-in email verification actually do?

Apollo shows a status next to each email address on a contact record, and most users read that status as "verified." Treat it as a field in Apollo's database, not as an audited mailbox check. Apollo's public documentation, as we read it, doesn't set out the checks behind each status or publish an independent accuracy figure, so the label is best understood as Apollo's own estimate.

The label bundles two jobs. The first is finding an address, which can come from data sources or from a naming pattern such as first.last@company.com applied to a name. The second is judging whether that address still receives mail. A pattern-generated address can look fine and still fail, and a correct address can belong to someone who left the company last spring. Because the label blends the two, a bounce doesn't tell you which one failed.

Bottom line: Apollo's status is a useful prospecting signal, but it bundles finding with judging, so it can't tell you why an address failed.

Is Apollo's email verification good enough for cold outreach?

For a small, low-stakes list, usually yes. For a large cold sequence, usually not without a second check. What decides it is the cost of a bad address. A dead address wastes a few minutes of rep time. A bounce spike on a cold domain can hurt deliverability for every email that domain sends afterwards.

Mailbox providers set the bar. Google's email sender guidelines ask bulk senders to keep spam complaint rates below 0.10% and never reach 0.30%. Complaints and bounces are different metrics, but both feed the same sender reputation, and cold lists tend to produce both. Sources and platforms also disagree on exact bounce thresholds, and most platforms don't publish theirs. We recommend one planning number: 2% total bounces as the ceiling, with under 1% as the target for first sends.

Here is a rule of thumb. A verifier is enough when a bad address costs you minutes. It is not enough when a bad address costs you domain reputation. If you only prospect and don't mail at volume, the lighter approach in email verification for sales prospecting may be all you need. For a deeper look at when built-in checks suffice, see whether to use your platform's built-in verification.

Bottom line: For cold outreach at volume, treat Apollo's label as a starting point and add an independent check before the first send.

Where does Apollo's verification fall short?

Five failure modes matter most for cold email, and none of them are visible in the label alone.

A tool that keeps you prospecting has a commercial reason to mark more contacts as usable. That is an inference from incentives, not something Apollo has stated, but it is a good reason to test rather than trust.

Bottom line: Catch-all domains, stale data, spam traps, role addresses and probe limits are invisible in a label, so you have to test for them directly.

How do you test Apollo's labels against a second verifier?

Run a sample before you commit the whole list. For a file of this size, the test is a single session's work.

  1. Export your contacts with the status field intact and a clean email column.
  2. Draw 1,000 contacts at random, spread across Apollo statuses in proportion to their share of the list. If a status has fewer than 200 contacts in total, verify all of them instead of sampling.
  3. Verify the sample with the second tool.
  4. Build a cross-tab with Apollo status as rows and second-tool results (Valid, Risky, Invalid) as columns.
  5. Calculate the invalid rate for each Apollo status, not just the overall rate.
  6. Compare each rate with your 2% ceiling and decide what to do with each row. The decision table later in this guide covers this step.

A random sample of 1,000 gives an overall margin of error of about ±3 percentage points at 95% confidence, using the worst-case 50% rate. Per-status rates from smaller slices carry wider error bars, so treat them as estimates and verify the whole status whenever it is small. Should you double-verify your list with two tools? covers when a second check is worth the cost.

Bottom line: Calculate invalid rates per Apollo status, because an overall average is dominated by the largest status and hides the small segment that causes bounces.

What does a 12,000-contact Apollo export look like after a second check?

All figures below are hypothetical. The arithmetic is checked.

A team exports 12,000 contacts for a cold sequence. Apollo labels 9,100 as verified, 1,800 as catch-all or unknown, and 1,100 as unverified or other. The Free plan's lists are capped at 150 emails, so this file needs Pro. Pro's 25,000-per-list cap fits the whole file in one upload.

After the second check, the cross-tab looks like this:

Apollo status Contacts Valid Risky Invalid Invalid rate
Verified 9,100 7,900 800 400 4.4%
Catch-all / unknown 1,800 300 1,300 200 11.1%
Unverified / other 1,100 200 100 800 72.7%
Total 12,000 8,400 2,200 1,400 11.7%

Three findings stand out.

  1. Mailing all 12,000 would be expected to produce about 11.7% invalid addresses (1,400 ÷ 12,000), almost six times the 2% ceiling.
  2. Mailing only the 9,100 "verified" contacts would still be expected to produce 4.4% invalid (400 ÷ 9,100), more than double the ceiling. The label alone isn't sufficient.
  3. Mailing only the 8,400 contacts the second check marks Valid leaves zero addresses flagged Invalid. That is 70% of the file (8,400 ÷ 12,000).

The 2,200 Risky contacts stay out of the first sends. The 1,800 catch-all or unknown contacts go through deep verification as a separate step, which uses 1,800 of Pro's 25,000 monthly deep verifications. Anything that comes back Valid can join the send list. Pro costs $29 for the month, so for this file alone the cost is about $2.42 per 1,000 contacts ($29 ÷ 12,000 × 1,000).

Bottom line: The "verified" label alone would leave 400 Invalid addresses in the send list, while the second check's Valid segment leaves none.

How does Apollo's built-in verification compare to a dedicated bulk verifier?

Built-in status answers "is this contact worth working?" A dedicated bulk verifier answers "can I safely mail this file?" The table shows where those answers diverge. Each side has a specific weakness: Apollo's is that you can't audit its status, and Unlimited Verifier's is that it adds an export-and-re-import step.

Criterion Apollo built-in status Unlimited Verifier (bulk)
Primary purpose Keeps contact records usable for prospecting Checks a list file and sorts each address
Output Status field on each contact Valid, Risky or Invalid per address, plus flags
Catch-all handling Not described in the public material we reviewed Detects catch-all domains
Role and disposable flags Not described in the public material we reviewed Flags role-based and disposable addresses
Input Contacts inside Apollo CSV or Excel up to 10MB; email column detected automatically
Export Depends on your Apollo plan and export limits CSV, Excel or JSON
Automation Within Apollo's platform REST API with API keys; bulk batches of up to 10,000 emails per request
Result retention Stored with the contact record Free: 24 hours. Pro: 30 days. Export what you need to keep
Cost model Bundled with your Apollo subscription; check plan terms for usage limits Unlimited standard verification on every plan; deep verifications capped at 750 a month (Free) or 25,000 a month (Pro)
Accuracy disclosure No accuracy figure in the public documentation we reviewed Company states 99.5% accuracy for deep verification

The retention row is the one teams miss. On the Free plan, results are kept for only 24 hours, so export on the day you verify. For a broader set of selection criteria, see which email verifier features actually matter and questions to ask before buying an email verifier. For a shortlist of options, read our roundup of the best email verification tools, and if you already use a verifier and are weighing a change, see how to switch email verification providers. The framework for picking a vendor is in how to choose an email verifier.

Bottom line: Use built-in verification to prioritise contacts and a dedicated bulk verifier to decide what gets mailed.

How should you decide which Apollo contacts to mail?

Decide by segment, using the label and the second check together. The table below is your rule set.

Apollo label Second-check result Action
Verified Valid Send, in the first wave
Verified Risky Hold back; review by domain
Verified Invalid Drop and suppress
Catch-all / unknown Valid Send, but re-check before large sends
Catch-all / unknown Risky Hold; test only if the domain is worth the risk
Catch-all / unknown Invalid Drop and suppress
Unverified / other Valid Send after a manual look
Unverified / other Risky or Invalid Drop

Then work through these steps.

  1. Set the rule. Only addresses the second check marks Valid enter your first send.
  2. Review catch-all groups by domain, not by contact, so one decision covers a whole company.
  3. Validate at capture. Once the list is clean, check new contacts at entry with real-time email validation, so bad addresses don't reach Apollo in the first place.
  4. Re-verify on a schedule. Re-check before each new campaign, and at least quarterly for active prospecting lists. The difference between one-off and recurring checks is covered in email verifier for one-time cleanup vs ongoing hygiene and email list maintenance best practices.
  5. Investigate weak sources. If one Apollo status keeps failing the second check, stop treating that status as a sending signal and look at where the data came from.

Bottom line: Decide by segment rather than by list, and re-verify on a schedule because B2B contacts decay.

How do you verify an Apollo export with Unlimited Verifier?

  1. Export from Apollo. Open your list or saved search and use Apollo's export option. Menu names change, so check the current steps in the Apollo help center. Keep the status column in the file.
  2. Clean the file in a spreadsheet. Trim spaces, lowercase every email and remove duplicate rows. Without this, "John@Acme.com" and "john@acme.com" count as two addresses and inflate your numbers.
  3. Create an account. Sign up for free. A 12,000-row file needs the Pro plan, because the Free plan's lists are capped at 150 emails.
  4. Upload the file. On the upload page, add your CSV or Excel file (up to 10MB). The email column is detected automatically, so confirm it points to the right column. If the file is larger than 10MB, split it.
  5. Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all, disposable and role-based addresses are flagged.
  6. Read the three buckets. Valid addresses are safe for the first sends. Invalid addresses should be suppressed. Risky addresses, including catch-all and role-based flags, should be held back.
  7. Export the results as CSV, Excel or JSON. Free results are kept for 24 hours, so save the file the same day. Pro keeps results for 30 days.
  8. Merge with Apollo's status. Match the two files on the lowercased email column with XLOOKUP or VLOOKUP, then build a pivot table with Apollo status as rows and verification result as columns.
  9. Re-import only the Valid segment into your sequencing tool as a new list, and add the Invalid addresses to its suppression list.
  10. Spot-check key contacts. For an important account that came back Risky, use the free email checker before deciding.

There is no native Apollo integration, so this export-verify-re-import workflow is the path. Teams that want to automate can call the email verification API from their own scripts. API access is included on Pro only, at 100,000 emails a month. For more on automation patterns, see email verification API and automation.

Bottom line: The merge step is where most of the time goes, so plan for a session rather than a quick click.

What does double-checking Apollo cost?

Unlimited Verifier's Pro plan is $29 a month, or $25 a month billed annually, which comes to $300 a year. The Free plan allows 25 lists a month of up to 150 emails each (at most 3,750 emails a month through list uploads), plus 750 deep verifications and no API access. Standard verification is unlimited on every plan, so your cost is driven by deep verifications and by how many lists you run. For background on how verification is priced across vendors, see email verification pricing.

Two worked numbers show how the cost moves. One 12,000-contact list on Pro costs about $2.42 per 1,000 contacts, as shown earlier. Three lists of 12,000 in the same month (36,000 contacts, each within the 25,000-per-list cap) bring the cost down to about $0.81 per 1,000 ($29 ÷ 36). The more lists you run through one subscription, the lower the cost per contact.

Bottom line: The saving comes from not mailing the invalid segment, and the subscription is the smaller number in that calculation.

Does verifying an Apollo list make cold email compliant?

No. Verification supports email verification compliance and hygiene, but it doesn't establish a lawful basis for sending. In the US, the FTC's CAN-SPAM compliance guide requires accurate header information, a valid physical postal address, a clear opt-out, and honouring opt-out requests within 10 business days. A verified address satisfies none of these.

In the UK, electronic marketing is governed by PECR and UK GDPR, and the ICO publishes guidance on B2B marketing. As we read it, B2B email to corporate subscribers generally has more latitude than email to individual addresses, but it still requires an identified sender and an opt-out. Check the current guidance for your own case before you send.

Bottom line: A valid address is a deliverable address, not a consenting one.

What are the most common mistakes?

Bottom line: Most failed cold campaigns trace back to averaging away the risky segment or skipping the second check.

How we compared (and limitations)

This article draws on Apollo's public documentation and Unlimited Verifier's published plan facts. We haven't run controlled tests of Apollo's verification, and nothing here is an independent accuracy benchmark. The 12,000-contact example uses hypothetical figures, and the arithmetic has been checked. The 99.5% accuracy figure is Unlimited Verifier's own stated number for deep verification, not an independent result. Apollo's status labels, export options and plan terms change over time, so confirm current details in Apollo's help center before you rely on them. No verification tool can confirm an individual mailbox on a catch-all domain, and any single address can change status after it is verified.

Four-step Apollo verification test

  1. Export a sample of about 1,000 contacts from Apollo, keeping the email status column.
  2. Verify the sample with a second tool and record Valid, Invalid, or Unknown for each address.
  3. Group results by Apollo status and calculate the invalid rate for each group, such as verified, unverified, and pattern-generated.
  4. If any group exceeds your 2% total bounce ceiling, send only addresses the second check marks Valid and treat the rest as a separate, unmailed segment.

The average can hide the problem segment, so always compare groups rather than relying on one overall number.

Frequently asked questions

Does Apollo verify email addresses?

Yes, Apollo shows a status next to each email address on a contact record, and users commonly read it as verified. Apollo's public documentation, as read for this article, does not fully describe the checks behind each status, so treat the label as Apollo's own estimate rather than an independently audited mailbox check. It is useful for prospecting but should be confirmed before large sends.

How accurate is Apollo's email verification?

Apollo's public documentation, as read for this article, does not publish an independent accuracy figure for its email statuses. The only reliable way to judge it for your list is to verify a sample with a second tool and compare invalid rates for each Apollo status. Results will vary by industry, region, and how old your contact data is.

Can I trust emails marked verified in Apollo?

Partly. A verified label is a reasonable signal for ranking and for small, low-stakes sends. For a large cold sequence, it is safer to run a second verification pass, because the label bundles finding an address with confirming it still receives mail, and a correct-looking address can belong to someone who has left the company.

Why do Apollo emails still bounce?

Bounces happen because the label does not separate two failure types. An address may have been generated from a naming pattern such as first.last@company.com and never existed, or it may have been correct but is now inactive because the person left. Either way, a verified label can coexist with a dead mailbox, which is why bounces appear even after an Apollo check.

What bounce rate is acceptable for cold email?

A common planning ceiling is 2% total bounces, with under 1% as a target for first sends. Mailbox providers do not publish one universal bounce threshold, so these are working guidelines rather than official limits. Keep bounce rates low on cold domains, since bounce spikes can affect sender reputation for later emails from that domain.

How do I test Apollo's email verification?

Export a sample of about 1,000 contacts, verify them with a second tool, and then group results by the Apollo status each contact carried. Calculate the invalid rate for each status. If the verified group shows a meaningful invalid share, the built-in label is not enough for cold sends, and you should add a second check before mailing.

Should I verify emails before a cold sequence?

Yes, for any list you plan to mail at volume. Verification is cheapest before the first send, when a bad address costs only minutes of rep time. Once bounces hit a cold domain, the damage can extend to every email that domain sends afterwards, so a second pass before sending is a low-cost safeguard.

Is a second verification tool worth using with Apollo?

It is worth using when a bad address would cost you domain reputation, such as in volume cold outreach. Apollo's label is fine for triage, but an independent check can catch addresses that the label marks as acceptable. If you only prospect and do not mail at volume, a lighter approach may be enough.

What should I do with addresses that fail the second check?

Drop them from the send rather than trying to mail them anyway. Keep a record of which Apollo statuses produced failures, because that pattern shows which segments of your data need more scrutiny. Re-verify contacts periodically, since people change jobs and mailboxes go inactive over time.

Does Apollo's verification replace a dedicated email verifier?

For most cold outreach at volume, no. Apollo's built-in status is best treated as a prospecting signal. A dedicated verifier adds an independent judgment step that the bundled label does not provide, which matters most when a bounce could damage sender reputation.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.