Company Size Predicts Catch-All Rates Better Than Industry
When sales teams talk about catch-all domains, the conversation usually stays general. Roughly 30 percent of businesses use catch-all email configurations. Between 15 and 40 percent of B2B email database addresses sit on catch-all domains. These numbers are useful as benchmarks, but they hide an important pattern: catch-all prevalence scales almost linearly with company size.
Knowing this changes how you plan verification budgets, estimate list quality, and set expectations for outreach campaigns. A startup-focused SDR team faces a completely different catch-all landscape than an enterprise sales rep.
Startups (1 to 50 Employees): 5 to 10 Percent Catch-All
Small companies and early-stage startups have the lowest catch-all rates in B2B. Most startups use Google Workspace or Microsoft 365 with default configurations, and neither platform enables catch-all by default. The IT setup at a 20-person startup is usually handled by a founder or a part-time ops person who follows the standard setup wizard without customizing mail routing.
Google Workspace makes catch-all an optional setting that requires deliberate configuration. Most small companies never touch it. They create individual mailboxes for each employee and leave it at that. If someone emails a nonexistent address at a startup domain, the server returns a clear rejection, which makes standard email verification highly effective.
For sales teams targeting startups, this is straightforward. Your standard verification tool will handle the vast majority of addresses correctly. The 5 to 10 percent that are catch-all typically come from startups using custom email hosting or with a tech-savvy admin who enabled catch-all intentionally.
Verification strategy for startup-focused lists: standard verification is usually sufficient. Catch-all specific verification is a nice-to-have but not critical at these volumes.
SMBs (51 to 200 Employees): 15 to 25 Percent Catch-All
The small-to-medium business segment is where catch-all starts to become a real factor. Companies in this range are big enough to have dedicated IT staff but not big enough for enterprise-grade email security. Some SMBs enable catch-all as a simple way to ensure no inbound email gets lost. A 150-person company with 10 departments might set up catch-all so that misspelled addresses or emails to former employees still reach someone.
Microsoft 365 shared mailboxes and distribution lists create a similar effect in some configurations. An SMB might route all unmatched addresses to a shared inbox that the office manager monitors. From a verification perspective, this behaves identically to a true catch-all: the server accepts everything.
At the 15 to 25 percent catch-all range, you start to see a measurable impact on list quality. On a prospect list of 2,000 SMB contacts, 300 to 500 addresses will be catch-all. If you discard all of them, you lose a significant chunk of pipeline. If you send without catch-all verification, you introduce unnecessary bounce risk.
Verification strategy for SMB lists: standard verification plus catch-all verification for the catch-all segment. The ROI is moderate but positive, especially for teams sending at volume.
Mid-Market (201 to 1,000 Employees): 25 to 35 Percent Catch-All
Mid-market companies represent the transition point where catch-all becomes a serious issue. These organizations have IT departments with actual email policies, and many of those policies include catch-all configurations for specific operational reasons.
At this size, companies often have catch-all enabled for security monitoring. The IT team wants to see what addresses are receiving inbound email, including addresses that do not correspond to real mailboxes. This helps them detect phishing attempts, social engineering, and reconnaissance activity. A catch-all configuration lets them capture and review these messages rather than having them rejected at the server level.
Mid-market companies also tend to have more complex email routing. Multiple departments, regional offices, and project-specific aliases create a web of addresses that is easier to manage with catch-all than with strict per-mailbox configuration.
For sales teams, this segment is where catch-all verification transitions from nice-to-have to essential. On a list of 3,000 mid-market prospects, 750 to 1,050 addresses are catch-all. Standard verification will flag all of them as unresolvable. Specialized catch-all verification can recover 75 to 90 percent of those as confirmed deliverable, adding 560 to 945 valid contacts back to your sendable pool.
Enterprise (1,000+ Employees): 40 Percent and Above
Enterprise domains have the highest catch-all rates, and the gap between enterprise and smaller segments is significant. Over 40 percent of enterprise domains use catch-all configurations, and in regulated industries like finance, healthcare, and government, the rate can be even higher.
The reasons are structural. Large enterprises use Secure Email Gateways (SEGs) like Proofpoint, Mimecast, or Barracuda that sit in front of the actual mail server. These gateways accept all inbound email for inspection before routing it internally. From an external verification perspective, the SEG responds with an acceptance for every address, making the entire domain appear as catch-all even if the internal mail system has strict per-mailbox routing.
Enterprise on-premise Exchange servers also behave differently from cloud-hosted email. Administrators often configure catch-all at the transport layer for compliance and archival purposes. Every message that enters the organization is captured, regardless of the target address.
Government domains (.gov addresses) and many educational institutions (.edu) show similar patterns. The combination of security requirements, compliance mandates, and legacy infrastructure creates catch-all configurations by default rather than by choice.
For enterprise-focused sales teams, this means nearly half of your prospect list may be catch-all. On a list of 5,000 enterprise contacts, 2,000 or more addresses will not resolve through standard verification. If you discard them, you are cutting your addressable market almost in half. If you send blindly, the bounce rates from nonexistent mailboxes behind catch-all domains will damage your reputation quickly.
Verification strategy for enterprise lists: catch-all verification is non-negotiable. The sheer volume of catch-all addresses means that skipping this step leaves too much pipeline on the table and introduces too much deliverability risk.
How This Affects Your Verification Budget
Understanding catch-all prevalence by company size lets you budget verification costs more accurately. Here is a framework:
- Startup-focused campaigns: Budget for standard verification on 100 percent of your list. Catch-all verification on the 5 to 10 percent flagged as catch-all. Total catch-all verification cost for a 5,000-lead list: roughly $1.25 to $3.50 (250 to 500 catch-all addresses at $0.005 to $0.007 each).
- SMB-focused campaigns: Standard verification plus catch-all verification on 15 to 25 percent of your list. For 5,000 leads: $3.75 to $8.75 for catch-all verification (750 to 1,250 addresses).
- Mid-market campaigns: Standard verification plus catch-all verification on 25 to 35 percent. For 5,000 leads: $6.25 to $12.25 (1,250 to 1,750 addresses).
- Enterprise campaigns: Standard verification plus catch-all verification on 40 percent or more. For 5,000 leads: $10 or more (2,000+ addresses).
Even at enterprise volumes, the total catch-all verification cost is trivial compared to the value of the recovered contacts. At $0.005 per verification, you are paying $10 to recover potentially 1,500 to 1,800 valid enterprise contacts. Each of those contacts represents a potential deal worth tens or hundreds of thousands of dollars.
Adjusting Your Outreach Strategy by Segment
Beyond verification, company size should influence your sending strategy for catch-all-verified addresses.
For startup contacts, catch-all verified addresses can be treated the same as standard verified. The catch-all rate is low enough that the handful of catch-all-verified addresses are not going to meaningfully affect your deliverability metrics.
For enterprise contacts, consider sending to catch-all-verified addresses in a separate segment with slightly lower daily volume. This gives you early warning if any addresses start bouncing, allowing you to pause that segment before it impacts your overall domain reputation. Start with 50 to 70 percent of your normal daily send rate for the catch-all-verified segment, and increase after confirming low bounce rates over the first few days.
For mid-market and SMB segments, a blended approach works well. Mix catch-all-verified addresses into your regular sending but monitor bounce rates more closely for the first 48 hours of a new campaign.
Planning Your List Sourcing Volume
When you are planning a campaign and estimating how many leads you need to source, factor in the catch-all rate for your target segment. If you need 3,000 sendable contacts and you are targeting enterprise accounts, you should source at least 5,500 to 6,000 raw contacts to account for the addresses that will be flagged as catch-all and the subset within that group that will not verify as deliverable.
Conversely, if you are targeting startups, 3,500 raw contacts will probably yield 3,000 sendable addresses after standard verification alone. The catch-all adjustment is minimal.
This kind of segment-aware planning prevents the common scenario where a team sources a list, verifies it, loses a third to catch-all, and then scrambles to find more contacts mid-campaign. Know the catch-all rate for your target segment upfront, and plan your sourcing volume accordingly.
