What does catch-all status establish?
Catch-all behavior means a domain may accept mail for addresses that do not identify real mailboxes. That limits what a basic acceptance test can establish. Keep person, role and address evidence separate, and preserve uncertainty in the record. A positive server response does not establish permission or inbox placement.
Apollo’s email-status documentation describes catch-all as a distinct category. Use the category as an uncertainty signal, not a claim that every address at the domain is invalid. A real person may use an address there; the problem is that domain behavior alone does not settle the question.
Require evidence about the actual person and address where it is available through permitted sources. Record the method, scope and check date. Do not quietly relabel unknown records as verified to make a report look better, or send speculative mail simply to turn your campaign into a verification experiment.
Sources: Apollo email status definitions
How should uncertain rows enter the cost model?
Price uncertain rows by the additional work needed to resolve them and the share that becomes usable after review. Do not assume all uncertain rows will pass or fail. A review budget makes the tradeoff visible while keeping the acquisition invoice separate from the cost of preparing a campaign.
Hypothetical cohort: 100 rows cost $300, with 20 held for additional address evidence. Reviewing those 20 takes five minutes each at $60 per hour, adding $100. If ten become usable and the other ten remain on hold, the final usable count is 90. Cost per usable row is $400 / 90 = $4.44.
Without the extra review, 80 rows would be usable at $300 / 80 = $3.75. The additional ten cost $100 / 10 = $10 each at the margin. That does not make the review wrong; it tells you what recovering those specific contacts costs. None of these figures is a measured provider result.
| Scenario | Usable rows | Total cost | Cost per usable row |
|---|---|---|---|
| Keep 20 held | 80 | $300 | $3.75 |
| Review; recover 10 | 90 | $400 | $4.44 |
| Incremental recovery | 10 | $100 | $10.00 |
Sources: Apollo email status definitions
What should a research brief say about uncertain addresses?
Define how uncertain address evidence should be labeled, reviewed or excluded before ordering the file. State whether the campaign requires confirmed evidence for every row or allows a separate hold queue. That agreement is more useful than a broad quality adjective that hides different verification methods behind one label.
Specify the required fields and acceptable evidence in the brief. Keep the source, method and date attached to the row, and use a separate status for unresolved cases. Your import should preserve the hold state so a later tool cannot silently turn it into a send-ready contact.
HEED’s terms define accepted records and the review process. Compare an actual delivery against that agreement rather than substituting assumptions about an unrelated platform’s status names. If you need a different evidence standard, make it part of the order discussion before purchase. Verification is a scoped observation, not consent to contact.
- Count unresolved rows separately in both cost and readiness reports.
- Do not infer a person’s mailbox from domain acceptance alone.
- Review whether recovered contacts justify the marginal effort.
Sources: HEED service and record acceptance terms
Define a B2B research briefSpecify the audience, required fields and exclusions before choosing a batch.
Common questions
Are all catch-all addresses bad?
No. The domain behavior limits the evidence from an acceptance test. It does not prove that every individual address is false. Keep the uncertainty explicit.
Can we count unresolved rows as campaign-ready?
Only if your actual acceptance rules support that classification. For a workflow requiring stronger evidence, keep them held until resolved; do not let a CSV import erase the status.