Guide
High Bounce Rate Account Suspension: Thresholds, Recovery Steps and How to Prevent It
By Unlimited Verifier Team ·

Summary
Most ESPs review or suspend accounts when hard bounces climb past roughly 2–5% of sent mail. Amazon SES publishes the clearest thresholds: review at 5% and a possible pause at 10%. To recover, stop sending, verify and clean the offending list, then appeal with before/after evidence.Most email service providers (ESPs) review or suspend an account once hard bounces climb past roughly 2–5% of sent mail. Amazon SES documents the clearest line: an account goes under review at a 5% bounce rate, and sending may be paused at 10%. Most marketing ESPs don't publish one number, and in practice many act well below 5%. If you're already suspended, the way back is the same everywhere: stop sending, find which list caused the bounces, verify and clean it, then appeal with evidence.
This guide is the hub for the whole topic. It covers the thresholds, why ESPs enforce them, what each major platform does, a step-by-step recovery and appeal process, a hands-on cleaning tutorial, and how to make sure it never happens again. Each subtopic links to a deeper article.
Quick answer
- Safe ceiling: keep hard bounces under 2% per send and aim for under 1%. Above 5% you're in formal review territory at Amazon SES and very likely flagged elsewhere.
- Most common cause: sending to an old, imported, or migrated list that was never verified. Lists decay steadily, and studies generally put that at roughly a fifth to a third of addresses per year.
- If you're suspended: pause all sends, export the list, verify every address, remove Invalid, treat Risky separately, then appeal with before/after numbers.
- Verification fixes list-quality bounces (5.1.1 "user unknown"), not reputation blocks (5.7.x policy rejections). Diagnose which one you have before acting.
- Prevention: verify at the point of capture via API, re-verify before any send to a list older than ~3–6 months, and sunset unengaged contacts.
What bounce rate gets your ESP account suspended?
There is no single universal number. Amazon SES is the only major ESP that publishes explicit bounce-rate thresholds in its public documentation: review at 5%, possible pause at 10%. Marketing platforms like Mailchimp, HubSpot, Klaviyo and Brevo enforce thresholds too, but they generally don't publish one fixed figure. Expect action at lower rates on shared-IP marketing platforms.
The reason for the gap is structure. SES is infrastructure: you usually bring your own list and sending logic, so AWS defines the guardrails explicitly. Marketing ESPs pool thousands of customers on shared IPs. One bad import from one account can damage delivery for everyone on that pool, so they review earlier and judge case by case.
Bounce rate thresholds by provider
| Provider | Publicly documented bounce threshold? | What typically happens | Deep dive |
|---|---|---|---|
| Amazon SES | Yes: 5% → under review, 10% → sending may be paused (bounce rate over a representative volume) | Account status changes in the console; you're asked to fix the root cause | SES bounce limits, explained |
| Mailchimp | No single public number | Automated abuse-prevention review can suspend a campaign or account | Mailchimp suspension recovery |
| HubSpot | No single public number | Email sending can be suspended for the account | HubSpot sending suspended |
| Twilio SendGrid | No single public number | Account placed under compliance review | SendGrid under review |
| Klaviyo | No single public number | Account flagged; sending may be restricted pending review | Klaviyo flagged accounts |
| Brevo | No single public number | Account suspended or campaigns blocked pending review | Brevo suspension |
| Constant Contact | No single public number | Account review/suspension by compliance team | Constant Contact suspension |
| Mailgun | No single public number | Warnings, then possible sending restrictions | Mailgun bounce warnings |
| Postmark | Strict policy; check current docs | Transactional focus means low tolerance for bad addresses | Postmark bounce limits |
How we compared (and limitations): This table is based on each provider's public documentation and policies as generally available. We did not test any account against these limits. Providers change policies, apply judgment, and weigh other signals alongside bounces (complaints, unsubscribes, spam-trap hits, content). Treat any number not marked "Yes" as unknown, not as zero risk. For the full breakdown, read which bounce rate triggers ESP suspension.
What bounce rate should you actually aim for?
Sources disagree. SES draws its formal line at 5%. Many deliverability practitioners treat 2% as the warning line and under 1% as healthy.
We recommend under 2% per campaign as the hard ceiling and under 1% as the target, for three reasons:
- Shared-IP ESPs act before 5%.
- A bounce rate above 2% usually means some part of the list is stale, and stale lists also tend to contain recycled spam traps, which never bounce at all.
- Mailbox providers like Gmail judge reputation on their own signals, independent of your ESP's thresholds.
| Hard bounce rate on a send | What it means | What to do |
|---|---|---|
| Under 1% | Healthy, normal decay | Keep routine hygiene |
| 1–2% | A segment or source is degrading | Find the source, verify that segment |
| 2–5% | Clear list-quality problem; likely flagged at marketing ESPs | Stop sending to that list; verify before next send |
| 5–10% | SES review territory; suspension likely elsewhere | Pause all bulk sends; full clean; prepare appeal |
| Over 10% | SES may pause; near-certain action at most ESPs | Treat as an incident; see what to do at 10% |
Bottom line: Plan around 2%, not 5%. The published SES number is the last line of defense, not a target.
Why do ESPs suspend accounts for high bounce rates?
ESPs suspend accounts for high bounces because bounces are the strongest public signal that a sender is mailing addresses it didn't collect properly. Mailbox providers punish the sending IPs and domains for it, and on shared infrastructure that punishment lands on other customers too.
Four mechanics are at work:
- Mailbox providers read bounces as a list-quality signal. A legitimate sender's list contains people who recently opted in, and those addresses mostly exist. A list with 15% nonexistent addresses looks bought, scraped or abandoned. Gmail and Yahoo's bulk sender requirements focus on authentication, unsubscribe and spam rates, but their filtering also weighs how often you hit dead mailboxes.
- Shared IP pools spread the damage. On most marketing ESPs, your mail leaves from IPs shared with other customers. Your bad import lowers the reputation of IPs other people depend on, which is why suspension is fast and often automatic.
- Bounces travel with spam traps. Old lists contain recycled spam traps: abandoned addresses that a mailbox provider reactivated to catch senders who don't clean their lists. Those don't bounce, so a high bounce rate is a proxy that you probably hit traps too.
- Blocklists. Operators of public blocklists watch trap hits and abusive patterns. A listing affects every domain and IP involved. The M3AAWG best-practice documents explain why the industry treats list hygiene as a baseline obligation.
Can a single campaign ruin your sender reputation?
Yes. One campaign to a badly decayed list can trigger an ESP suspension within hours and lower your domain reputation at Gmail or Microsoft. Whether it "ruins" you depends on what happened before and after. A sender with a long clean history and good engagement recovers faster than a new domain whose first big send bounced at 12%. The full analysis is in whether one campaign can sink your reputation.
How long does one high-bounce campaign hurt deliverability?
Plan on weeks, not days. ESP account status can be restored within days of a successful appeal. Mailbox-provider reputation is computed from rolling history, so a bad send keeps weighing on you until enough clean, engaged sends replace it. Watch domain reputation in Google Postmaster Tools during recovery. See how long a high-bounce send lingers for a recovery timeline.
Bottom line: Suspension isn't punitive bureaucracy. It's the ESP protecting shared infrastructure from a signal that mailbox providers are already punishing.
What counts as a bounce? Hard vs. soft vs. block bounces
Not all bounces count the same. Hard bounces (permanent 5xx failures) drive suspensions. Soft bounces (temporary 4xx failures) usually count only after repeated failures. Block bounces (policy rejections) point to a reputation problem that verification alone won't fix.
SMTP's enhanced status codes (RFC 3463) tell you which one you're looking at:
| Code (example) | Type | Meaning | Fixed by list verification? |
|---|---|---|---|
| 550 5.1.1 | Hard | Mailbox doesn't exist ("user unknown") | Yes. This is exactly what verification catches |
| 550 5.1.2 / domain errors | Hard | Domain doesn't exist or has no mail server | Yes, via domain/MX checks |
| 452 / 4.2.2 | Soft | Mailbox full or over quota | Partly; retry, then suppress if persistent |
| 421 / 4.7.0 | Soft (deferral) | Temporary throttling | No; slow down sending |
| 550 5.7.1 (and similar 5.7.x) | Block | Rejected for policy or reputation | No. Fix authentication, reputation, content |
Here's what practitioners learn the hard way. Open your bounce log and sort by code before you do anything else. If 90% of your bounces are 5.1.1, you have a list problem and cleaning will fix it. If a large share are 5.7.x from one mailbox provider, you have a reputation or authentication problem. Cleaning the list won't stop those, and your appeal needs to address SPF, DKIM and DMARC instead.
Bottom line: Count the 5.1.1s. They tell you how much of the problem verification can remove.
Why did my bounce rate suddenly spike?
Sudden spikes almost always trace back to a change in what you sent to, not how you sent: a new import, an old segment brought back, a provider migration, or a broken signup form letting in typos and bots.
Spike diagnosis checklist
- Filter bounces by list or segment. If bounces cluster in one import or tag, you've found the source.
- Filter by signup date. Bounces concentrated in contacts added years ago point to decay. Bounces concentrated in last week's signups point to form abuse or typos.
- Filter by domain. One corporate domain bouncing everything usually means that company changed mail systems or shut down. One consumer provider bouncing with 5.7.x codes means a reputation block.
- Check what changed in the last 30 days: new lead source, migration, form redesign, removed CAPTCHA, new co-registration partner.
The full triage flow is in what to do when bounce rate spikes. The condensed incident version is in five steps after a spike.
Why did bounces jump right after importing a list?
Imported lists are the number one cause of bounce suspensions. Your ESP has never seen these addresses, so none of them are on its suppression list. A list exported from an old CRM, a trade-show scanner, a partner, or a previous tool contains every address that has died since collection. Some imports also include addresses that already bounced at your previous ESP. More in why imports spike bounce rates.
Why are emails bouncing after switching email providers?
When you migrate, your old ESP's suppression list usually stays behind. Every hard-bounced, unsubscribed and complained address you had suppressed comes back as a "fresh" contact in the new platform. The first campaign then re-bounces years of accumulated dead addresses at once, on a new account with no reputation history.
The fix is to export suppressions from the old provider, re-apply them in the new one, and verify the remainder before the first send. See bounces after switching providers.
What if 10% of your emails bounce?
At 10% you're at the Amazon SES pause threshold and past the point where almost any ESP will tolerate it. Stop all bulk sends immediately, including scheduled automations that draw from the same list. Then run the recovery framework below. A 10% rate also tells you the list is old enough that unverified spam traps are likely, so cleaning plus engagement-based sunsetting is required. See handling a 10% bounce rate.
Bottom line: Find the segment before you fix anything. A spike is almost never spread evenly across your whole list.
How each major ESP handles high bounce rates
Every platform follows the same broad pattern (detect, restrict, review, reinstate or terminate), but the mechanics and appeal paths differ.
Mailchimp
Mailchimp runs automated abuse-prevention checks on campaigns as they send. A campaign with high bounces can be halted mid-send, and the account suspended pending a compliance review. Mailchimp's policies prohibit purchased, rented and scraped lists, so the review usually asks where the list came from as well as what the bounce rate was. Expect to explain the list's opt-in source and show that you've removed invalid addresses. Step-by-step recovery: Mailchimp suspended my account — what now.
HubSpot
HubSpot can suspend email sending for the whole account when hard bounces or spam reports exceed what it tolerates, while the rest of the CRM keeps working. HubSpot automatically suppresses contacts that hard-bounced, so repeat bounces on the same address are rare. The usual trigger is new contacts: imports, form submissions or integrations. HubSpot's acceptable use policy prohibits purchased lists. Full guide: HubSpot sending suspended after bounces.
Twilio SendGrid
SendGrid places accounts under review when bounce and complaint patterns look abusive, and can restrict sending while compliance investigates. SendGrid keeps a Bounces suppression list. Repeat sends to known-bad addresses are blocked automatically, but every new address you add is still a risk. Developers often hit this when an app sends to unverified signups. Details: SendGrid account under review for bounces.
Klaviyo
Klaviyo monitors deliverability at the account level and can flag an account and restrict sending when bounce or spam rates exceed its tolerances. Ecommerce accounts tend to get flagged after importing historical customer lists from a store platform: customers who bought once, years ago, with addresses that have since died. Klaviyo suppresses profiles after hard bounces, but you'll need to clean the imported segments before resuming. See Klaviyo flagged for high bounces.
Brevo
Brevo (formerly Sendinblue) validates new accounts before the first campaign goes out and can suspend an account or block campaigns when hard bounces run high. Brevo's review typically asks about list origin and collection method. Plan to show verification results with your appeal. Recovery guide: Brevo suspended for high bounce rate.
Constant Contact
Constant Contact's compliance team reviews accounts when bounces or abuse reports exceed its standards. Like Mailchimp, it prohibits purchased lists and expects documented permission. Small businesses often trigger it by uploading a long-dormant customer spreadsheet. More: Constant Contact suspended for bounces.
Amazon SES
SES is the most transparent. According to the Amazon SES documentation, a bounce rate of 5% puts the account under review, and at 10% AWS may pause your ability to send. Complaint-rate thresholds are far lower: 0.1% for review, 0.5% for pause. The rate is calculated over a representative volume of recent sending, not one campaign, so a single bad batch can push you over and keep you there until enough clean volume dilutes it.
Two deep dives:
- Fixing an SES "under review" status covers the review process.
- The SES bounce rate limit explained covers how the rate is calculated.
Mailgun
Mailgun issues warnings when bounce rates climb and can restrict sending if they don't come down. Mailgun sells its own validation service, which tells you how seriously it takes pre-send list quality. You can use any verification provider to clean the list. Fix guide: resolving Mailgun bounce warnings.
Postmark
Postmark is built around transactional email and is known for low tolerance for bad addresses. Its model depends on keeping its IPs pristine for password resets and receipts. Marketing-style sends to unverified lists don't fit there. Check Postmark's current docs for the exact policy. Our summary: Postmark bounce limits explained.
Bottom line: The platforms differ in transparency and tone, but every reviewer asks the same two questions: where did this list come from, and what have you done to clean it?
What to do immediately after an account suspension: the 7-step recovery framework
Act on this within the first 24–48 hours. The order matters. Appealing before you've cleaned the list is the most common reason appeals fail.
- Stop everything that sends. Pause scheduled campaigns and automations (welcome series, abandoned cart, re-engagement), plus any API integrations writing to the same account. Continuing to send while suspended can turn a review into termination.
- Export the bounce report and the full list. Keep the bounce report with SMTP codes. You'll cite it in the appeal.
- Classify the bounces. Sort by code: 5.1.1 (list quality) vs. 5.7.x (reputation). If 5.7.x dominates, add an authentication audit (SPF, DKIM, DMARC) to your plan.
- Identify the source segment. Which import, form, date range or partner did the bounces come from? Reviewers want root cause, not just "we cleaned the list."
- Verify the entire list, not just the bad segment. Run every address through syntax, domain/MX and SMTP mailbox checks. Remove Invalid, isolate Risky, and remove disposable addresses.
- Write the appeal with numbers. Before/after counts, root cause, and the prevention changes you've made.
- Restart slowly. Once reinstated, send to your most recently engaged Valid contacts first and scale up over 1–3 weeks.
Each step has a dedicated guide:
- Cleaning a list after an ESP suspension covers steps 2–5.
- Getting an ESP account reinstated covers what reviewers look for.
- The 5 steps after a bounce rate spike covers the incident-response version when you haven't been suspended yet.
Bottom line: Clean first, appeal second. An appeal with verification evidence is a different conversation from an apology.
How to write an appeal to your ESP after a suspension
A successful appeal is short, factual and specific. It names the cause, quantifies the cleanup, and commits to concrete prevention. Reviewers handle many of these. Vague promises ("we'll be more careful") read as risk. Numbers read as competence.
Use this structure:
Subject: Appeal for account [ID]: root cause identified and list cleaned
On [date], our campaign "[name]" produced a [X]% hard bounce rate. We've identified the cause: [e.g., a 2022 customer export imported on (date) that had not been mailed since collection].
What we've done:
- Paused all sends and automations as of [date/time].
- Verified all [N] contacts (syntax, domain/MX, SMTP mailbox, catch-all detection).
- Removed [N] invalid addresses and [N] disposable addresses; suppressed [N] previously bounced addresses.
- Isolated [N] risky/catch-all addresses, which will not be mailed until we have confirmed engagement.
Prevention going forward:
- Real-time verification on all signup forms via API.
- Re-verification of any segment not mailed in 90 days before sending.
- Sunsetting contacts with no engagement in [X] months.
Restart plan: We'll resume with our [N] most recently engaged contacts and scale over [X] weeks.
Things to leave out: blaming the ESP, arguing the threshold is unfair, or claiming a purchased list was opt-in. Reviewers often ask follow-ups about list origin, and inconsistencies end appeals. The full template library with platform-specific variations is in writing an ESP appeal that works.
Bottom line: Lead with root cause, prove the cleanup with numbers, and commit to prevention you can actually show.
Hands-on tutorial: clean a suspended list with Unlimited Verifier
This walkthrough takes a beginner from "account suspended" to a cleaned, re-importable file. It uses Unlimited Verifier because standard verification is unlimited on every plan with no per-email fees. That matters when you have to re-verify an entire database during an incident and can't predict the final volume.
- Export your list from the ESP as CSV. Include the email column plus engagement fields (last open/click date, signup date, source) so you can segment later. Export the suppression/bounce list separately.
- Remove already-known bounces first. Delete any address on the ESP's hard-bounce or suppression export. There's no point verifying addresses you already know are dead.
- Split files to fit plan limits. On the Free plan, each list holds up to 150 emails (25 lists a month), which works for testing or small lists. On Pro ($29/month, or $25/month billed annually), each list holds up to 25,000 emails with unlimited lists. Files must be CSV or Excel up to 10MB.
- Create an account and upload. Sign up for a free account, then upload your list for verification. The email column is detected automatically, so you don't need to reformat the file.
- Let the checks run. Each address is checked for syntax, domain existence, MX records and the SMTP mailbox. Catch-all domains, disposable addresses and role-based addresses (info@, sales@, admin@) are flagged.
- Read the three buckets.
- Valid: the mailbox responded as deliverable. Safe to re-import.
- Risky: catch-all domains and other addresses that can't be confirmed. Don't bulk-send these during recovery.
- Invalid: bad syntax, dead domains, nonexistent mailboxes. Delete them, or add them to your ESP suppression list so they're never re-imported.
- Resolve the Risky bucket with deep verification. Catch-all servers accept every address at the SMTP stage, so a standard check can't tell real mailboxes from fake ones there. Run Risky addresses through catch-all email verification using your monthly deep-verification allowance (750 on Free, 25,000 on Pro). Unlimited Verifier states 99.5% accuracy for deep verification.
- Decide on role-based and disposable addresses. Remove disposable addresses outright. For role-based addresses, keep them only if the business relationship is real. They tend to draw more complaints because several people read the inbox.
- Export and re-import. Export results as CSV, Excel or JSON. Re-import only the Valid file (plus any Risky contacts you've confirmed) into the ESP, tagged so you can track the recovery cohort. Unlimited Verifier has no native ESP integrations, so the workflow is export → verify → re-import, or the API covered below.
- Save your evidence. Note the counts per bucket for the appeal. Free-plan results are kept 24 hours and Pro results 30 days, so download them promptly.
To spot-check a handful of addresses first, for example a few that bounced, the free single-address email checker runs the same kind of check with no upload. If you suspect a reputation problem rather than a list problem, the free domain blacklist checker shows whether your sending domain is listed.
Bottom line: Export, de-duplicate known bounces, verify everything, send only Valid. Keep the numbers for your appeal.
Worked example: recovering a 62,000-contact list after a 14% bounce rate
The following numbers are illustrative. Your list will differ, but the arithmetic is the method.
The situation: A marketing agency imports a client's 62,000-contact customer list into a new ESP account. The list was last mailed 26 months ago. The first campaign reaches 18,000 recipients before the ESP halts it. 2,520 hard-bounce, for a 14% bounce rate (2,520 ÷ 18,000). The account is suspended.
Step 1: Remove known bounces. The 2,520 addresses that just bounced are removed, leaving 59,480 contacts.
Step 2: Split for upload. On Pro, each list is capped at 25,000 emails:
- File A: 25,000
- File B: 25,000
- File C: 9,480
That's three lists, all within the unlimited standard-verification allowance. No per-email cost.
Step 3: Standard verification results (illustrative):
| Bucket | Count | Share of 59,480 |
|---|---|---|
| Valid | 43,420 | 73.0% |
| Risky (mostly catch-all) | 6,840 | 11.5% |
| Invalid | 9,220 | 15.5% |
Had the agency sent the remaining list uncleaned, the 9,220 Invalid addresses alone would have produced a 15.5% hard bounce rate, above SES's 10% pause line and far past any marketing ESP's tolerance. Some catch-all addresses would have bounced on top of that.
Step 4: Deep-verify the Risky bucket. 6,840 deep verifications fits within Pro's 25,000 monthly allowance, leaving 18,160 for the rest of the month. Illustrative outcome: 3,050 resolve to Valid, 1,190 to Invalid, and 2,600 stay Risky.
Step 5: Build the send list.
- Send-ready: 43,420 + 3,050 = 46,470 Valid.
- Held back: 2,600 Risky, to be mailed later in small batches only if the domain-level results look clean.
- Removed: 9,220 + 1,190 + 2,520 = 12,930 addresses (20.9% of the original 62,000).
Step 6: Project the post-clean bounce rate. Verification isn't perfect, and mailboxes can die between the check and the send. Assume a residual hard bounce rate of 0.5–1%. On 46,470 sends that's roughly 232–465 bounces, or 0.5–1%. That's comfortably under the 2% ceiling.
Step 7: Appeal and restart. The appeal cites:
- Root cause: a 26-month-old import.
- Cleanup: 12,930 removed; 2,600 held back.
- Prevention: API verification on forms, 90-day re-verification rule.
After reinstatement, the agency sends first to the ~8,000 customers who purchased within the last 12 months, then scales up in stages.
Cost math: The whole cleanup fits inside one month of Pro, at $29, or $25/month billed annually. With credit-based tools, per-1,000 costs typically fall as volume rises, but every re-check during an incident costs extra. With unlimited standard checks, re-running a file after fixing a column mistake costs nothing.
Bottom line: A list that looks "mostly fine" can hide 15–20% dead addresses after two years. Verification turns a suspension-level send into a sub-1% send.
How to send to an old list safely after cleaning
Cleaning removes dead addresses. Warming up the list rebuilds the engagement signals mailbox providers use to decide inbox vs. spam. You need both.
Is it safe to email a list that's two years old?
Not without verification. A two-year-old list will typically contain a double-digit percentage of invalid addresses, and the abandoned ones may include recycled spam traps. After verification it can be mailed safely, but only in stages, starting with the contacts most likely to engage. The risk analysis by list age is in whether a two-year-old list is safe.
How do you send to an old email list safely?
Follow this order:
- Verify the whole list.
- Send a short, recognizable re-permission or "still interested?" message to a small engaged slice first.
- Watch bounces and complaints after each batch.
- Expand only when each batch stays under ~1% bounces and complaints stay low. Google's bulk-sender guidance asks senders to keep spam rates under 0.3%, and Amazon SES reviews at 0.1%.
The full playbook: sending safely to an old list.
How do you warm up an old list after cleaning?
Segment by recency of engagement, not alphabetically or by import order. An illustrative two-week ramp for 46,000 cleaned contacts:
| Days | Segment | Approx. volume |
|---|---|---|
| 1–2 | Engaged or purchased in last 6 months | 3,000–5,000/day |
| 3–5 | Engaged 6–12 months ago | 5,000–8,000/day |
| 6–9 | Engaged 12–24 months ago | 8,000–10,000/day |
| 10–14 | Never engaged but verified Valid | Remaining, in small batches |
Pause and reassess if any batch exceeds 2% bounces or shows a jump in complaints. Contacts who still don't engage after the re-engagement sequence should be sunset, not mailed forever. Details: warming up a list after cleaning.
How do you avoid suspension when importing old lists in the first place?
Verify before import, never after. Import only Valid addresses, tag the import cohort, and send to it gradually rather than in one blast. Re-apply suppression lists from any previous platform. Step-by-step: importing old lists without getting suspended.
Bottom line: Cleaning makes a list safe to mail. Warming it up by engagement recency makes it safe to mail at volume.
How to prevent high bounce rates permanently
Prevention means stopping bad addresses at three gates:
- At capture: real-time verification on forms.
- Before import: batch verification of any list from outside your ESP.
- Over time: re-verification and sunsetting as the list ages.
Most suspensions happen because only one of these gates exists, or none.
Verify at the point of capture with an API
Typos (gmial.com), fake signups and disposable addresses enter through forms. Checking them in real time stops them before they reach your ESP. Unlimited Verifier's REST API supports single-email checks for forms and bulk batches of up to 10,000 emails per request for nightly jobs. Pro includes API access for 100,000 emails a month. Generate a key on the verification API keys page. For a deeper look at architectures, such as verifying on submit, queuing for batch checks, or verifying CRM syncs before they hit the ESP, see our guide to email verification API and automation and the companion walkthrough on automating verification workflows.
Because the verification engine is open source (on GitHub), technical teams can inspect how checks are performed before wiring them into a signup flow.
Ecommerce and SaaS: the two highest-risk patterns
Ecommerce stores accumulate one-time buyers whose addresses quietly die, then import them all into a new email tool during a platform switch.
SaaS products face fake trial signups and disposable addresses that inflate bounces on onboarding sequences. In SaaS, those onboarding emails often go through a transactional ESP with strict limits, like Postmark or SES.
Both patterns are covered in email verification for ecommerce and SaaS, with a practical playbook in verification strategies for stores and software companies.
Hygiene and compliance routines
A practical cadence:
- Re-verify any segment not mailed in 90 days before sending to it.
- Run a full-list verification at least twice a year for active lists.
- Suppress hard bounces immediately.
- Sunset contacts with no engagement in 6–12 months after one re-engagement attempt.
Hygiene also overlaps with legal obligations. The FTC's CAN-SPAM compliance guide and GDPR's data-accuracy principle both reward keeping lists accurate and honoring opt-outs. Read more on email verification compliance and hygiene and the operational detail in building a list hygiene routine.
Authentication and broader deliverability
Verification fixes the 5.1.1 problem. Authentication fixes much of the 5.7.x problem. Gmail and Yahoo require SPF, DKIM and DMARC plus easy one-click unsubscribe for bulk senders. Yahoo's sender best practices and Google's guidelines are the two documents to read. Our complete email deliverability guide ties authentication, reputation and list quality together.
The revenue case for prevention
A suspension stops all email revenue for the days or weeks it lasts, including automated flows that often drive a large share of email income. Measured against that, verifying before every risky send is cheap. See how list quality feeds through to returns in measuring email marketing ROI.
Bottom line: Verify at capture, verify before import, re-verify as lists age. Three gates, and suspensions mostly stop.
Choosing an email verification tool to prevent suspensions
Any reputable verifier will catch nonexistent mailboxes. The differences that matter for suspension prevention are how catch-all and risky addresses are handled, how pricing behaves when you need to re-verify large lists urgently, and how results get back into your ESP.
If you're new to the category, start with what is email verification. Our explainer on how verification checks work walks through syntax, MX and SMTP steps in detail.
Comparing common options
| Tool | Notable differentiators (from public documentation) | Specific limitations to weigh |
|---|---|---|
| Unlimited Verifier | Unlimited standard verification on every plan, no per-email fees; Valid/Risky/Invalid sorting with catch-all, disposable and role-based flags; REST API with 10,000-email batches; open-source engine; states 99.5% deep-verification accuracy | No native ESP/CRM integrations (CSV round-trip or API); per-list cap of 25,000 on Pro; Free plan has no API and keeps results only 24 hours |
| ZeroBounce | Detailed status categories (e.g., catch-all, spamtrap, abuse, do_not_mail); offers an AI-based scoring product | Credit-based: every re-check consumes credits, which adds up during incident re-verification |
| NeverBounce | Owned by ZoomInfo; emphasizes integrations with ESPs and CRMs | Integration-led workflow is most useful if your stack matches their connectors; pay-per-verification pricing |
| Kickbox | Results as deliverable/undeliverable/risky/unknown, plus a "Sendex" quality score | Sendex is a score, not a verdict, so you have to choose your own cutoffs; credit-based pricing |
| Hunter | Primarily an email-finding tool with verification built in | Verification is secondary to prospecting; credits shared across finding and verifying |
How we compared (and limitations): Based on each vendor's public documentation and positioning, not hands-on benchmarking. Vendor accuracy claims are the vendors' own and use different methodologies, so they aren't directly comparable. Features and pricing change; check current pages before buying.
For a fuller comparison, see our roundup of the best email verification tools and the in-depth verifier comparison.
Why pricing models matter during a suspension
During an incident you often verify the same data more than once: the full list, then a corrected export, then a re-check before the restart. Under credit-based email verification pricing, each pass is billed. Under a flat plan with unlimited standard checks, repeat passes are free. The trade-offs, including when credit packs make sense for one-off jobs, are in comparing verification pricing models.
Bottom line: For suspension recovery and ongoing hygiene, pick a tool whose pricing doesn't punish you for re-verifying. That's where Unlimited Verifier's flat, unlimited standard verification fits best.
Common mistakes that turn a bounce warning into a permanent ban
- Appealing before cleaning. Reviewers ask what you've changed. "Nothing yet" gets the appeal denied or delayed.
- Leaving automations running. You paused the campaign, but the welcome or win-back flow keeps sending to the same bad imports and the bounce rate keeps climbing.
- Verifying only the segment that bounced. The rest of the list is usually the same age and source. Verify everything you plan to mail.
- Treating Risky as Valid. Catch-all domains accept mail at SMTP and can bounce afterward. Bulk-sending to a large unresolved Risky bucket during recovery can push you straight back over the line.
- Assuming verification fixes 5.7.x blocks. Policy rejections are about reputation and authentication. Cleaning won't fix them, and your appeal should address SPF/DKIM/DMARC.
- Opening a new ESP account to dodge the suspension. ESPs share signals, and a new account sending the same uncleaned list fails faster, now with an evasion question attached. It may also breach the original provider's terms.
- Forgetting suppression lists when migrating. The single most avoidable cause of post-migration bounce spikes.
- Restarting at full volume. Even a perfectly clean list needs a staged ramp after a reputation hit.
- Believing a purchased list can be "cleaned" into compliance. Verification removes dead addresses. It doesn't create consent. Mailchimp, HubSpot and Constant Contact all prohibit purchased lists regardless of bounce rate.
- Verifying once and stopping. Lists decay continuously. A list verified a year ago is a partly unverified list today.
- Letting results expire. Free-plan results are kept 24 hours and Pro results 30 days. Download exports immediately so you have evidence for the appeal.
Bottom line: Most permanent bans come from repeating the same mistake after the first warning. Fix the root cause, prove it, and ramp slowly.
Putting it all together
High bounce rate suspensions follow a predictable script. A stale, imported or migrated list meets an ESP that has to protect shared infrastructure, and bounces cross a threshold somewhere between 2% and 5%; Amazon SES puts the formal lines at 5% and 10%. The recovery script is just as predictable:
- Stop sending.
- Diagnose by bounce code and segment.
- Verify the full list.
- Appeal with numbers.
- Restart in stages.
Prevention comes down to three verification gates: capture, import and aging.
Unlimited Verifier is built for exactly this job. Unlimited standard verification means you can re-check a whole database mid-incident without counting credits. Valid/Risky/Invalid sorting with catch-all detection tells you what to send now and what to hold back. CSV/Excel upload and the REST API cover both the emergency clean and the long-term prevention workflow. Start with whichever guide below matches where you are right now:
- Already suspended? Start with cleaning your list after a suspension, then getting reinstated.
- Bounce rate climbing but not suspended? Follow the spike response guide.
- About to import or migrate a list? Read avoiding suspension with old lists before you click import.
5-step suspension recovery framework
- Pause all scheduled campaigns and automations immediately.
- Diagnose the bounce codes: 5.1.1 'user unknown' points to list quality, while 5.7.x points to policy or reputation.
- Isolate the list or import that caused the spike.
- Verify and clean every address: remove Invalid, segment Risky, and suppress hard bounces.
- Appeal with before/after bounce numbers and your prevention plan (verification at capture, re-verification of lists older than 3–6 months, sunsetting unengaged contacts).
Frequently asked questions
How long does an ESP account suspension for bounces last?
It usually lasts until you fix the cause and the provider accepts your appeal, so there is no fixed duration. Simple cases are often resolved within a few business days once you show a cleaned list. Repeat offenses or very high bounce rates can take longer or end in permanent termination, so respond quickly and supply clear evidence of remediation.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure, such as a nonexistent address or a 5.1.1 'user unknown' error. A soft bounce is temporary, such as a full mailbox or a busy server. ESPs weigh hard bounces most heavily in suspension decisions. Suppress hard-bounced addresses immediately, and remove addresses that soft-bounce repeatedly across several sends.
Does a high soft bounce rate count toward suspension?
It can, but usually less directly than hard bounces. Most ESPs focus on permanent failures. Persistent soft bounces, though, often signal stale addresses or reputation problems, and many platforms automatically convert repeated soft bounces into hard bounces. Monitor both rates and investigate any sustained rise in soft bounces before it escalates.
Can I just move to another ESP after being suspended?
Moving the same unclean list rarely works. The new provider will likely see the same bounces and suspend you as well, and some ESPs screen new accounts for this pattern. Clean and verify the list first. Once your list is healthy, you can switch providers if you want to, but the underlying list problem has to be fixed either way.
How do I calculate my bounce rate?
Divide bounced emails by emails sent, then multiply by 100. For example, 300 hard bounces out of 10,000 sent gives a 3% hard bounce rate. Some providers calculate the rate over delivered or attempted messages, or over a rolling window. Amazon SES, for example, evaluates bounce rate over a representative sending volume. Check your ESP's own definition.
Will email verification remove spam traps?
It removes some, but not all. Verification reliably catches invalid and nonexistent addresses and can flag known risky or role-based addresses. Pristine spam traps are designed to look valid and are hard to detect. The best defense is to combine verification with confirmed opt-in and to sunset contacts who never engage.
What should I include in a suspension appeal?
Explain the root cause, the fix, and how you will prevent a repeat. Include your list source, the verification tool you used, the before and after counts of invalid addresses, the suppression of hard bounces, and the prevention steps you now follow, such as API verification at signup and sunset policies. Keep the appeal concise and factual.
How often should I re-verify my email list?
Re-verify before sending to any list segment that hasn't been mailed in about 3–6 months, and periodically for active lists. Lists decay steadily as people change jobs and abandon addresses. Real-time verification at signup prevents most new bad addresses from entering your list, which reduces how often you need to bulk-clean.
Do purchased lists cause account suspensions?
Yes, and they are among the most common causes. Purchased and rented lists typically contain invalid addresses and spam traps, and the recipients never consented to hear from you. Most ESPs prohibit them in their acceptable use policies, so a bounce spike from a bought list can lead to termination rather than a temporary suspension.
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.