// Research
Email bounce rates by data source
Last verified · 2026-06-24
The short answer
Public deliverability guidance generally treats a hard-bounce rate under roughly 2% as healthy, with many email providers flagging or pausing senders above the 2–5% range. The single biggest public-cited driver of bounces is data age: addresses scraped once and reused months later bounce far more than addresses verified close to send time. That is an argument for continuous re-verification, not a Trackyr measurement.
What counts as a 'healthy' bounce rate publicly
Across publicly available deliverability guidance from major email service providers and verification vendors, the commonly repeated threshold is that a hard-bounce rate below roughly 2% is considered healthy, and that sustained rates above the 2–5% band put sender reputation at risk. These are published guidance ranges, not laws of nature — different mailbox providers weight bounces differently — but the consensus direction across public sources is consistent: bounces are a leading reputation signal, and senders are judged on them.
It helps to separate hard bounces (the address does not exist or the domain is invalid — a permanent failure) from soft bounces (a temporary condition like a full mailbox or a transient server issue). Public guidance treats hard bounces as the reputation-critical category, because a high hard-bounce rate is read by mailbox providers as a signal that the sender does not maintain its list.
Why data source is the variable nobody controls for
Most public bounce benchmarks are reported per send, not per data source. That hides the most important variable. The same outreach copy sent to a freshly verified list versus a list scraped twelve months ago will produce very different bounce rates — and the difference is the data, not the campaign. Public deliverability writing repeatedly attributes elevated bounces to stale or unverified lists rather than to message content.
Roughly grouped by how the public literature talks about each source, the typical bounce-rate posture looks like this. These are illustrative industry-typical ranges synthesized from public guidance, not measured Trackyr figures:
| Data source posture | Industry-typical bounce range (public, illustrative) | Why |
|---|---|---|
| Verified at or near send time | Low — commonly cited under ~2% | Address checked against live mail-server signals immediately before use |
| Recently verified list (weeks old) | Low-to-moderate | Some natural decay since verification, but most addresses still live |
| Scraped once, reused months later | Moderate-to-high — frequently cited above the healthy threshold | No re-check; job changes and deprovisioned mailboxes accumulate |
| Old purchased / unverified list | High — public guidance often warns of double-digit rates | Unknown provenance, no freshness signal, possible spam traps |
The mechanism: addresses rot, they do not stay verified
A verification is a snapshot, not a permanent property of an address. The moment a list is verified, decay begins: people change jobs, companies deprovision mailboxes, domains lapse, and roles get reassigned. Public research on B2B data decay (covered in our separate decay study) consistently puts annual contact churn in the tens of percent. That means a list verified once and reused a year later has, by the public numbers, lost a meaningful fraction of its deliverable addresses — and those losses show up as bounces.
- Verification is time-stamped truth, not durable truth — it expires.
- Bounce rate is, in large part, a proxy for how long ago your data was last checked.
- A low historical bounce rate on a list says nothing about its bounce rate today.
- The cheapest way to lower bounces is almost always fresher data, not better copy.
What the public data implies for how you should buy data
If bounce rate tracks data age, then a contact platform's most useful property is not how many records it holds but how recently each record was confirmed — and whether it re-confirms them on an ongoing basis rather than at one point of capture. This is the honest, public-data-grounded case for continuous re-verification: not because any single vendor's internal numbers prove it, but because the publicly stated relationship between data age and bounce rate makes a 're-verify before reuse' model the logical design.
Trackyr is built around that logic — a single contact pool that is re-checked over time rather than sold as a one-time scrape — but we make no claim to a measured bounce advantage yet. We are pre-scale, and any such claim would be fabricated. What we can say honestly is that the public benchmarks point toward continuous verification as the right answer, and that is the model we chose.
How to use these benchmarks responsibly
- Treat the ~2% healthy threshold as a published guideline, and confirm the exact tolerance with your own ESP — providers differ.
- Measure bounce rate against data age, not just per campaign, so you can see decay rather than blame copy.
- Re-verify before reusing any list older than a few weeks; the older the data, the larger the expected gap.
- Distinguish hard from soft bounces in your reporting — only hard bounces are the reputation-critical figure.
// Common questions
Answered.
What is a good email bounce rate?+
Public deliverability guidance from major ESPs and verification vendors commonly treats a hard-bounce rate under roughly 2% as healthy, with risk rising in the 2–5% band and above. This is a published industry guideline, not a Trackyr-measured figure, and exact tolerances vary by mailbox provider — confirm with your own sending platform.
Why do scraped email lists bounce more than verified ones?+
Because a scrape is a one-time snapshot. After capture, addresses decay as people change jobs and companies deprovision mailboxes, but a scrape-once list is never re-checked, so those dead addresses stay on it and bounce. Public guidance consistently attributes elevated bounces to list age rather than to message content.
Are these bounce-rate numbers measured by Trackyr?+
No. Trackyr is new and pre-scale and has no proprietary bounce dataset to report. Every figure in this study is a publicly published industry benchmark or an illustrative typical range, clearly labeled as such. We synthesize public deliverability knowledge and reason from it; we do not present any internal Trackyr measurement.
Does re-verifying a list actually reduce bounces?+
The public relationship between data age and bounce rate strongly implies it should: re-verifying replaces a stale snapshot with a current one and removes addresses that have gone dead since capture. We frame this as the logical implication of public benchmarks rather than a measured Trackyr result.
Put it into practice.
Verified creator + B2B contacts, one shared pool, paid only for what you use.
Start hunting →