Article
Smartlead Bounce Rate Too High? How to Fix It Step by Step
By Unlimited Verifier Team ·

Summary
A Smartlead bounce rate above 2% is too high for cold email. Pause the campaign, split bounces by mailbox and lead source, suppress every hard bounce, verify remaining leads, and restart at a lower daily volume per mailbox.A Smartlead bounce rate above 2% is too high, and the fix is to pause the campaign, split bounces by mailbox and lead source, suppress every hard bounce, verify the remaining leads, and restart at a lower daily volume per mailbox. Smartlead sends only to the leads you load, through the mailboxes you connect, so the cause is usually your list or your sending setup.
Quick answer
- Pause first. Every further send to a bad address adds hard bounces while you investigate, and it pushes the rate higher.
- Split the numbers. Bounces concentrated on one mailbox point to sending reputation or volume. Bounces concentrated on one lead source point to the list.
- Suppress and verify. Block every hard bounce across all campaigns, verify the rest, and send only to Valid addresses until the rate is back under 2%.
- Slow down and check authentication. Lower daily volume per mailbox, re-warm weak mailboxes, and confirm SPF, DKIM and DMARC are set up on each sending domain.
Why does my Smartlead bounce rate suddenly spike?
Most spikes come from addresses that never existed, or have since stopped working, or from one mailbox sending more than its reputation supports. Bounce rate is hard bounces divided by attempted sends, and you should measure it per campaign and per mailbox.
Cold lists are riskier than newsletter lists because they are often built from enrichment, scraping or guessed address patterns such as first.last@company.com. Our Apollo verified-versus-guessed guide explains why a label on a lead is not proof that the mailbox exists. Spikes often trace back to one batch loaded all at once, not gradual decay. Lists also decay as people change jobs and domains lapse, so a list that performed well six months ago can bounce badly today.
Two measurement points matter here:
- Count hard bounces for the ratio. Soft bounces are temporary failures, such as a full inbox, and many clear on retry. Counting them as permanent failures inflates the rate and sends you chasing the wrong problem.
- Wait before judging a campaign. Most hard bounces return at send time, but delayed bounce notices can arrive later. Check the final rate a day after sending.
Bottom line: A spike usually traces to one bad batch or one overloaded mailbox, and hard bounces alone should drive your ratio.
What bounce rate is too high?
Above 2% is too high for a cold list, and you should aim for under 1% on your first sends after a fix. The public sources differ, because each platform sets its own triggers:
- Amazon SES documents a review at a 5% bounce rate and a possible pause at 10%, per its documentation.
- Google focuses its published sender guidance on spam complaints, which it asks bulk senders to keep below 0.3%, per its sender guidelines. It does not set a fixed bounce ceiling in that guidance.
- Many cold email teams use 2% as a working ceiling, because platform triggers can act on unproven lists well below published numbers.
We recommend a 2% hard ceiling and a 1% target for re-entry. Treat Amazon's 5% figure as the point where a platform is likely to step in, not as a safe operating level.
Bottom line: Act above 2%, and scale only when a list stays under 1%.
How do I tell whether the list or the mailbox is causing the bounces?
Split the bounces by mailbox and lead source before you change anything, because the pattern tells you which fix you need. Cleaning a list does nothing for a damaged mailbox, and slowing a mailbox does nothing for dead addresses.
| What you see | Most likely cause | What to check first |
|---|---|---|
| One mailbox runs far above the others | Sending reputation or volume too high for that mailbox | That mailbox's daily count, warm-up history and domain DNS |
| One lead source bounces, the others are clean | List quality | Verify that source, and review how its emails were found |
| Bounces spread evenly across mailboxes and sources | Broad list decay | Verify the full list, and check your sending domain for blacklisting |
| Most bounces carry code 5.1.1 | Dead destination addresses | Remove and verify |
| Most bounces carry 5.7.x codes | Reputation or authentication, not the list | Authentication, volume and content; verification alone won't fix this |
The codes come from RFC 3463. Class 5 means a permanent failure. Within it, 5.1.1 means the destination mailbox is invalid, which verification catches. A 5.7.x code means the receiving server refused your mail on security or policy grounds, which a clean list cannot fix.
Two patterns are easy to miss. First, when volume is spread across many mailboxes, one sick mailbox gets diluted into the campaign total, so the overall rate looks tolerable. Check per-mailbox rates every time. Second, catch-all domains accept messages at the SMTP stage whether or not the mailbox exists, so some addresses look fine until a bounce arrives later. Catch-all leads belong in the Risky bucket, not Valid.
Bottom line: Proportional bounces mean a list problem; one mailbox running hot means an infrastructure problem. Split the data first.
How do I bring a Smartlead bounce rate down? (7 steps)
Work through these steps in order: pause, diagnose, suppress, verify, send only proven addresses, slow down, then monitor each mailbox every day.
- Pause the campaign and related sequences. Check whether the same leads sit in other campaigns. A contact in a second sequence keeps bouncing your domain until you remove it.
- Split the numbers. Record bounce rate per mailbox and per lead source, using the table above. Write the finding in one sentence, because it determines your fix.
- Suppress every hard bounce everywhere. Block each bounced address across all campaigns, not just the one where it failed. Keep the list as your own evidence of what failed.
- Verify everything not yet proven. Run the remaining leads through bulk verification. Deep verification draws on a monthly allowance, so spend it first on the riskiest source, such as enriched or guessed leads.
- Send Valid first, hold Risky, remove Invalid. Valid addresses have passed the mailbox check. Risky addresses (catch-all, disposable and role-based) can be tested later in small batches. Load the clean list into a new campaign rather than restarting the old one, so you don't re-add leads you have just removed.
- Lower volume and check authentication. Reduce daily sends per mailbox and re-warm any weak mailbox. Confirm SPF, DKIM and DMARC on each sending domain. Google's sender guidelines require authentication for senders who deliver more than 5,000 messages a day to Gmail, and it is good practice regardless of volume. Keep cold outreach on separate domains from your main company domain, so a reputation hit on a cold domain doesn't reach your business mail.
- Set a tripwire. Check bounce rate per mailbox daily during the ramp, and pause any mailbox that passes 2%. Check Smartlead's current documentation for whether your plan offers automatic bounce-based pausing or a global block list, and confirm before you rely on either. Don't treat automation as a substitute for checking the numbers yourself.
Bottom line: Pause, split, suppress, verify, send only proven addresses, slow down, and monitor each mailbox.
Which verification approach fits a cold email workflow?
Bulk verification before import repairs an existing list, and real-time checks at capture stop new bad addresses from entering. Enrichment labels are a starting point rather than proof.
| Approach | How it works | Differentiators | Where it falls short |
|---|---|---|---|
| Bulk verification before import (e.g., Unlimited Verifier) | Upload a CSV or Excel list; each address is checked for syntax, domain, MX records and the SMTP mailbox, then sorted into Valid, Risky or Invalid | Separate catch-all, disposable and role-based flags; export as CSV, Excel or JSON; REST API for scripted batches on Pro | No native Smartlead integration, so you export, verify and re-import, or call the API |
| Verification labels inside an enrichment tool | Tags leads as verified or guessed during lookup | Runs inside the data-gathering step, so no separate file | The label reflects the vendor's own definition, so confirm with an independent check before a large send |
| Real-time validation at capture | Checks an address when it is entered or imported | Stops new bad addresses before they reach a campaign | Covers only new entries; it does nothing for the list you already hold |
For a broader comparison, see the best email verification tools and our guide to how to choose an email verifier. Our email finder vs verifier breakdown explains why finding an address and checking it are separate jobs. If you're evaluating platforms with checks built in, see best cold email tools with built-in verification.
Bottom line: Verify before import to repair the list, and use real-time checks to stop the problem returning.
How do I export, verify and re-import Smartlead leads?
Unlimited Verifier has no native Smartlead integration, so the workflow is export, verify and re-import, or a scripted API call. Plan a short session for a few thousand leads.
- Export the leads. Download the affected campaign's leads as a CSV. Save the bounce list separately as your record, and note hard and soft bounces apart.
- Create an account. Sign up for free. The Free plan covers 25 lists a month of up to 150 emails each, plus 750 deep verifications a month, but has no API access. The Pro plan is $29/month, or $25/month billed annually, and covers unlimited lists of up to 25,000 emails each, with 25,000 deep verifications a month and API access for 100,000 emails a month.
- Upload the file. Use the upload and verify a list page to submit your CSV or Excel file, up to 10MB. The email column is detected automatically. If a list exceeds 25,000 rows on Pro, split it first.
- Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Standard verification is unlimited on every plan, with no per-email fees, so re-checks cost nothing extra. Use deep verification on your riskiest source.
- Read the three buckets. Valid addresses are safe for your first sends. Invalid addresses should be removed. Risky addresses include catch-all domains, which accept every address, so mailbox existence can't be confirmed. Disposable and role addresses such as info@ also land here. The catch-all email verification page explains how these results are handled.
- Export the results right away. On the Free plan, results are kept for 24 hours, so download them immediately. On Pro, results are kept for 30 days. Export as CSV, Excel or JSON, and save the summary counts for your records.
- Rebuild the list. Create a new list from the Valid file only. Add the Invalid addresses to your suppression list, and hold Risky addresses in a separate list. Re-adding the original export is how bounced addresses come back.
- Spot-check edge cases. For a single high-value contact that returned Risky, use the free email checker.
- Automate later (optional). API access requires Pro. Generate keys on the email verification API page to verify batches from your own scripts before each import. The REST API handles single checks and batches of up to 10,000 emails per request. For workflow patterns, see our guide to email verification API and automation.
Bottom line: Export, verify, rebuild from Valid only, and suppress the rest.
Worked example: an 8,000-lead campaign across three mailboxes
The lead counts and results below are illustrative. The arithmetic and plan limits reflect the real product.
The problem. A team loads 8,000 leads from two sources into a campaign running on three mailboxes. Source A (5,000 leads) was enriched using guessed patterns. Source B (3,000 leads) came from a directory export.
- Source A: 480 ÷ 5,000 = 9.6%
- Source B: 96 ÷ 3,000 = 3.2%
- Overall: 576 ÷ 8,000 = 7.2%
Bounces were spread roughly evenly across the three mailboxes (about 192 each), so the list is the problem, not one mailbox. Source B is still above 2%, so it needs cleaning too.
Cleaning.
- Remove the known bounces. Source A leaves 4,520 and Source B leaves 2,904, a total of 7,424 addresses.
- Check the plan limit. On the Free plan, 7,424 addresses at 150 per list needs 50 lists (7,424 ÷ 150 = 49.5, rounded up), but the Free plan allows 25 lists a month, so it doesn't fit. On Pro, all 7,424 addresses fit in one list under the 25,000 cap.
- Spend the deep allowance deliberately. Deep verification on Source A's 4,520 addresses uses 4,520 of 25,000 monthly deep verifications, leaving 20,480. Source B uses standard verification, which is unlimited.
- Cost: one Pro month at $29, or $25/month if billed annually. See our email verification pricing overview for how plans compare.
Hypothetical results:
| Source | Checked | Valid | Risky | Invalid |
|---|---|---|---|---|
| A | 4,520 | 3,500 | 680 | 340 |
| B | 2,904 | 2,650 | 180 | 74 |
| Total | 7,424 | 6,150 | 860 | 414 |
Invalid addresses make up 414 ÷ 7,424 = 5.6% of the remaining list. Removing them before sending means they never count as bounces.
Re-entry plan. Mailbox capacity is the bottleneck, not leads. At 30 sends per mailbox per day across three mailboxes (90 a day), the 6,150 Valid addresses take about 68 days, roughly ten weeks.
- Week 1: 20 sends per mailbox per day, 60 a day, 420 sends in total. Target no more than 4 bounces (under 1%). Start with Source B's Valid addresses, which had the lower raw bounce rate.
- Week 2: 30 per mailbox per day, 90 a day, 630 sends. Target under 1%.
- Weeks 3 onward: Keep ramping only while each mailbox stays under 1%. Test a small batch of Risky addresses last, once Valid performance is stable.
If you need the Valid pool sooner, add mailboxes rather than raising daily volume on the ones you have.
Bottom line: For $29 and a short session, the team turns a 7.2% problem into a verified list and a measurable ramp.
How do I keep bounce rates from coming back?
Verify at the point of entry, verify before each import, re-verify on a schedule, and keep your suppression list as a permanent record. Each layer catches a different source of bad data.
- At capture: Use real-time email validation on forms and imports, so bad addresses never reach a campaign.
- Before every import: Verify each batch before it reaches a sending platform. Our sales prospecting verification guide covers the full workflow. If your leads come from LinkedIn, the Sales Navigator guide shows how to verify them first. If you build lists in Clay, see the Clay table guide. Apollo exports follow the same rule, covered in our Apollo list verification guide.
- On a schedule: Re-verify active lists monthly or quarterly, because job changes make B2B lists decay. The list maintenance guide covers the cadence.
Expect the rate to improve on your next clean campaign. Mailbox reputation, however, typically takes several weeks of low-bounce sending to rebuild, so plan for a slower ramp than you'd like.
Bottom line: Verify at entry, before import and on a schedule, and the spike is far less likely to return.
What mistakes keep bounce rates high?
Most repeat bounce problems come from reusing unverified data or raising volume before the list and mailboxes are healthy.
- Re-adding the original list. Rebuild from the Valid file, or the bounced addresses return. Reusing an old list is the most common reason a fix fails.
- Fixing one campaign and leaving leads elsewhere. A contact in another sequence keeps generating bounces against your domain.
- Blaming the mailbox without checking the data. A list problem looks different from a reputation problem, and the wrong fix wastes weeks.
- Sending Risky addresses first. Catch-all and role addresses belong at the end of the ramp, when your Valid performance is already stable.
- Raising volume to hit a quota. Pushing more sends through a damaged mailbox deepens the reputation problem and slows its recovery.
- Treating a clean list as consent. Verification shows that a mailbox exists, not that the person wants your email. For US rules, see the FTC's CAN-SPAM compliance guide. If you email UK or EU contacts, check the ICO's guidance on electronic marketing and get advice for your jurisdiction. Our compliance and hygiene overview covers how the two fit together.
- Verifying once and forgetting. A list verified last year has decayed, and the bounce rate will show it.
Bottom line: Clean data and paced volume prevent most repeat problems, and treating verification as consent is the mistake with the largest legal cost.
How we compared (and limitations)
This guide draws on public documentation: Google's sender guidelines, Amazon SES's published thresholds, RFC 3463's status codes and the FTC's CAN-SPAM guide. We have not run controlled tests against Smartlead or any other platform. Smartlead's features and limits can change, so check its current help documentation before you act on any setting.
Unlimited Verifier's figures come from its own published plan details. It states 99.5% accuracy for deep verification. That is the company's stated figure, not an independent benchmark. The worked example uses hypothetical results and illustrative lead counts, but the plan limits and arithmetic reflect the real product.
Bottom line: Use the thresholds here as a conservative starting point, and verify your own mailbox and list data before scaling.
Restart checklist after a bounce spike
- Pause the campaign and stop all sends.
- Export bounces and tag each as hard or soft.
- Group hard bounces by mailbox and by lead source.
- Suppress every hard-bounced address across all campaigns.
- Verify remaining leads and send only to Valid addresses.
- Lower daily volume per mailbox and re-warm weak mailboxes.
- Confirm SPF, DKIM, and DMARC on each sending domain.
- Restart and check the rate a day later. Scale only while it stays under 1%.
Frequently asked questions
What is a good bounce rate for Smartlead cold email?
A good bounce rate for cold email is under 1%, and 2% is the ceiling most teams treat as too high. Aim for under 1% on re-entry after a fix. Measure hard bounces only, divided by attempted sends, per campaign and per mailbox.
Do soft bounces count toward my bounce rate?
Soft bounces usually should not count toward your hard bounce ratio because they are temporary failures, such as a full inbox. Many clear on retry. Track them separately so you do not chase the wrong problem.
Why do delayed bounces show up after a campaign ends?
Most hard bounces return at send time, but some bounce notices arrive late. Check the final rate about a day after sending before deciding whether a campaign passed or failed.
Should I remove hard-bounced leads from all campaigns?
Yes. Suppress every hard-bounced address across all campaigns, not just the one where it bounced. Continuing to email the same dead address in another campaign adds bounces and hurts mailbox reputation.
How do I know if a mailbox is causing the bounces?
If bounces cluster on one sending mailbox while other mailboxes using the same list perform normally, the mailbox is the likely cause. Check its daily volume, warm-up status, and reputation before restarting.
How do I know if the lead list is the problem?
If bounces cluster on one lead source or batch across several mailboxes, the list is the likely cause. Guessed or scraped addresses are the usual culprits, so verify them before sending again.
Should I check SPF, DKIM, and DMARC for bounce problems?
Yes, confirm SPF, DKIM, and DMARC are configured on each sending domain. Authentication gaps mostly hurt deliverability and spam placement rather than causing hard bounces, but they are worth checking during any reputation recovery.
How long should I wait before restarting a paused Smartlead campaign?
Restart only after suppressing hard bounces and verifying the remaining list. Begin with a low daily volume per mailbox and confirm the bounce rate stays under 1% before scaling back up.
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 standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
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.