Article

How to Get a SendGrid Account Out of Bounce Rate Review

By Unlimited Verifier Team ·

Flowchart showing the steps to resolve a SendGrid account under review for bounce rate: stop sending, find the bounce source, verify the list, reply with counts

Summary

A SendGrid account under review for bounce rate usually has a spike in hard bounces from one send or one imported list. SendGrid doesn't publish an exact threshold, so the fastest path is to stop sending, remove and verify bad addresses, and reply with specific counts and a staged re-entry plan.

A SendGrid account goes under review for bounce rate when hard bounces rise above a level SendGrid doesn't publish, so plan around a 2% total bounce ceiling: stop sending, verify your list, and reply with a remediation plan backed by exact counts.

SendGrid doesn't give a clean number because the review is a judgment call. It weighs the bounce spike alongside your complaint rate, your sending history and where your contacts came from. A reply that answers the specific signal named in the notice closes a review far more often than a general "we fixed the list" message.

Quick answer

For the broader picture of why ESPs suspend senders, see our pillar guide on high bounce rate account suspension.

What does "under review" mean on SendGrid?

"Under review" is an account-level hold. SendGrid's compliance team examines your sending before normal volume resumes. Escalation generally runs from a notice and a request for information, to a sending restriction, to suspension or termination if the problem persists. The exact stages vary, so the notice itself is your most important document.

Bottom line: An "under review" notice is a request for evidence about one specific signal. Answer that signal, not a general promise to do better.

Why does SendGrid review accounts for bounces?

SendGrid sends mail for many customers through shared infrastructure. Mailbox providers such as Gmail, Yahoo and Microsoft judge that sending pool as a whole, so one customer repeatedly mailing dead addresses can hurt delivery for everyone else. That's why the review looks at your list, not just your rate.

A hard bounce is a permanent failure, such as SMTP enhanced status code 5.1.1 (bad destination mailbox), defined in RFC 3463. Each one tells the receiving server you mailed an address that doesn't exist.

Three details change how you should read your numbers:

The most common shape of a review is one spike from a single send to a list that was imported or revived. A reply that identifies that source usually lands better than one that treats the whole account as suspect.

Bottom line: Suppression stops future bounces but doesn't erase past ones. Your reply has to show how the list was fixed, and it should name the source of the spike.

What bounce rate gets a SendGrid account flagged?

SendGrid doesn't publish a fixed bounce-rate trigger in its public documentation, so the benchmarks below are the best guide. They disagree, and the table shows where each number comes from.

Source Figure What it measures How to read it
Amazon SES documentation 5% bounce rate for review; 10% for a possible pause Bounces for an SES sending account Infrastructure-level limits for SES, not SendGrid's rules
Google sender guidelines Keep spam rate below 0.10%; never reach 0.30% Spam complaints, not bounces Shows how little tolerance providers have for list problems
SendGrid No fixed public bounce threshold Discretionary review Weighs your history, complaints and list source alongside bounces
Our recommendation 2% ceiling; under 1% target Total bounces ÷ messages accepted A margin below what most reviewers treat as a concern

Why the gap? SES publishes limits for its own infrastructure, and Google's figure measures complaints. A discretionary review combines several signals, so your own trend matters more than any single published number.

Calculate your rate as bounces divided by messages accepted for delivery in the same send. For example, 3,600 bounces ÷ 120,000 accepted messages = 3.0%. State your denominator in the reply so the reviewer can check your arithmetic.

Bottom line: Plan for a 2% ceiling and aim for under 1% on re-entry. The ESP's own threshold is less useful to you than a margin that keeps your re-entry sends clear of any reviewer's concern.

How do I find the cause in my SendGrid account?

Split bounces by campaign and by list source before you write anything. A single bad send and a systemic list problem need different fixes, and your reply depends on which one you have.

Three SendGrid views help:

Suppression list What adds addresses What it tells you What to do
Bounces Permanent (hard) failures The address doesn't exist or can't receive mail Keep the suppression. Find which list and send created it
Blocks The recipient's server rejected the message Often a reputation or authentication issue Check authentication and sending practices, not only the list
Invalid Emails Malformed addresses Errors in your source file Fix the file. These are generally rejected before a delivery attempt, so they may not appear in bounce counts
Spam Reports Recipients who marked you as spam A consent or relevance problem Remove the contact and review how they joined
Unsubscribes / Global Unsubscribes Opt-outs Opt-outs that must be honoured Confirm they stay suppressed. See the FTC's CAN-SPAM guidance

The practical insight here is that a bounce percentage can understate a list problem. If Invalid Emails are high but bounces look modest, the source file is the issue. Check that count alongside bounces every time you assess a list.

Bottom line: Locate the campaign and list source behind the spike before you draft anything. The cause sentence in your reply should come from this data.

Which list-cleaning method will satisfy a SendGrid review?

Only verification gives you a measured picture of the whole list. Other methods leave gaps that a reviewer can spot.

Method What it catches What it misses Strength in a review
Delete only the addresses that bounced Addresses in the failed send Dead addresses you didn't mail this time Weak. Reviewers know the rest of the list is untested
Re-engagement campaign Unengaged but valid contacts Mails unverified addresses, creating new bounces while under review Poor during review. Use it later as a hygiene step
Inactivity sunset (for example, no clicks in 12 months) Long-dormant contacts Recently added bad data. Opens are unreliable since Apple Mail Privacy Protection inflates them Moderate. A good policy, but not proof
Bulk verification, then segmentation Syntax errors, dead domains, missing MX records, nonexistent mailboxes, disposable and role addresses, catch-all domains Consent and intent, which verification can't prove Strong. Produces per-category counts you can cite

The strongest reply combines verification (is the address real?) with engagement segmentation (does this person want the mail?). Verification answers the first question and clicks answer the second. Our guide to email list maintenance best practices covers running both on a schedule.

Unlimited Verifier fits the verification step. It checks syntax, domain, MX records and the SMTP mailbox, detects catch-all domains, flags disposable and role-based addresses, and sorts every address into Valid, Risky or Invalid. Those buckets map directly onto the counts a reviewer asks for. Standard verification is unlimited on every plan, including Free, with no per-email fees.

Bottom line: Verify first, then segment. Verification proves the address exists; segmentation shows you should mail it.

How do I clean my SendGrid list before replying?

This tutorial assumes you've already pulled your bounce data. Start by signing up for a free account to test your file, then choose the plan that fits your largest list.

Free Pro
Price $0 $29/month, or $25/month billed annually
List size Up to 150 emails per list, 25 lists a month (3,750 emails at most) Unlimited lists of up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Results kept 24 hours 30 days

Standard verification is unlimited on both plans. The gap that matters for SendGrid cleanups is list size and deep-verification volume, which is where email verification pricing decisions usually come down to.

  1. Export your bounce data and contacts. Download the bounce suppression list from SendGrid's Suppressions section, or retrieve it through the Suppressions API. Export your contacts from Marketing Campaigns as CSV. Keep your own copy of the suppression file, because it's your evidence.
  2. Trim the file. Keep the email column and one identifier, such as a contact ID, so you can match results back to SendGrid. Extra columns don't help verification and make reconciliation harder.
  3. Split large lists. On Pro, each file can hold up to 25,000 emails. Split anything larger into files of 25,000 rows or fewer. On Free, each list is capped at 150 emails.
  4. Upload each file on the Upload and verify a list page. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
  5. Read the three buckets.
    • Valid: safe for re-entry, after the holdbacks described below.
    • Invalid: remove permanently and record the count.
    • Risky: includes catch-all domains, which accept any address and so can't confirm a mailbox; disposable addresses; and role accounts such as info@. Hold these back. The Catch-all email verification page explains how these results are handled.
  6. Spot-check edge cases. Use the free single-email checker on a valuable contact that came back Risky before you decide what to do with it.
  7. Export and save the counts. Results can be exported as CSV, Excel or JSON. Save the summary counts for your reply, and export promptly, because Free keeps results for 24 hours and Pro for 30 days.
  8. Update SendGrid. Remove Invalid contacts from your lists, and re-import Valid contacts as a new segment. Leave SendGrid's bounce suppressions in place. Deleting them to resend to known-bad addresses is one of the fastest ways to lose a review.

There's no native SendGrid integration, so the workflow is export, verify, re-import. If you have engineering support, you can use an email verification API and automation workflow instead: single-email checks, or bulk batches of up to 10,000 emails per request, with API access on Pro. Create your key through the API keys page.

Bottom line: Export, trim, split, verify, keep Valid, suppress Invalid and hold back Risky. Then save the counts for your reply.

What does a real SendGrid cleanup look like, with numbers?

The scenario below is illustrative. The percentages are hypothetical, but the arithmetic and plan limits are accurate.

The send: A retailer mailed 120,000 contacts. Of these, 40,000 came from an old event list imported last year. The campaign produced 3,600 bounces:

3,600 ÷ 120,000 = 3.0% overall bounce rate

Most of the damage sat in the imported segment:

2,900 ÷ 40,000 = 7.25% on imported contacts 700 ÷ 80,000 = 0.875% on the rest of the list

That split is the most useful finding in the reply. It shows the problem came from one list source, not general list rot.

Cleaning:

  1. Remove known bounces and opt-outs. 120,000 − 3,600 = 116,400. Removing 180 unsubscribes and complaints (all assumed to come from the non-imported group) leaves 116,220.
  2. Track what remains by source. Imported: 40,000 − 2,900 = 37,100. Non-imported: 80,000 − 700 − 180 = 79,120. Check: 37,100 + 79,120 = 116,220.
  3. Check the Free plan. 116,220 ÷ 150 = 775 lists. Free allows 25 lists a month, so Pro is required.
  4. Split for Pro. 116,220 ÷ 5 = 23,244 rows per file, under the 25,000 cap.
  5. Allocate deep verification. Pro includes 25,000 deep verifications a month. Use them on 25,000 of the 37,100 imported contacts, the highest-risk group. That leaves 12,100 imported contacts without a deep check this month.
  6. Hypothetical results (standard verification across all 116,220 addresses):
    • Valid: 103,000 (88.6%)
    • Risky: 8,200 (7.1%)
    • Invalid: 5,020 (4.3%)
    • Check: 103,000 + 8,200 + 5,020 = 116,220
  7. Hold back the 12,100. Assume all of them came back Valid, which is the worst case for the ramp. Re-entry then draws from 103,000 − 12,100 = 90,900 contacts.
  8. Cost: One Pro month at $29 on monthly billing.

Re-entry plan (most engaged first, with a per-send bounce ceiling):

Day New recipients Running total Bounce ceiling for that send Audience
1 8,000 8,000 0.5% (≤ 40 bounces) Clicked or opened in the last 30 days
3 15,000 23,000 1% (≤ 150) Engaged in the last 90 days
7 22,000 45,000 1% (≤ 220) Remaining engaged Valid contacts
14 30,000 75,000 1% (≤ 300) Remaining Valid, non-imported
21 15,900 90,900 1% (≤ 159) Remaining Valid, including deep-verified imports

Set a stop rule: if any send exceeds its ceiling, pause and investigate before the next send. Risky contacts stay out until the main list has shown stable results. A small test batch of the strongest catch-all addresses can follow at the end.

Bottom line: In this example, one $29 month and a few hours of work turn "we cleaned the list" into a 116,220-row audit with exact counts, a held-back segment and a ramp with a stop rule.

What should my reply to SendGrid include?

Keep the reply short and factual, so a reviewer can check each claim against a number. Cover five points, and send the reply through the channel the notice names, which is usually a support ticket or the review thread.

Offer to share per-send bounce metrics during the ramp. That commitment gives the reviewer something to verify, which is often what moves a review forward.

Bottom line: Lead with the cause, quote the counts and commit to a measurable ceiling.

How long does a SendGrid review take, and can the account be closed?

SendGrid doesn't publish a review timeline. In practice, reviews slow down when follow-up questions arrive, usually about list source and consent. A complete first reply is the most effective way to shorten the wait.

Outcomes vary. An account can be restored, restored with sending limits, or terminated. Termination is more likely when the list was purchased or scraped, or when the problem recurs after a warning.

Reputation recovery is a separate clock. Restoring your account doesn't immediately restore inbox placement, which is why the re-entry ramp matters. Read more in our article on how long deliverability takes to recover. If the notice came from a different platform, the flow is similar but the rules differ. See our guides to Klaviyo flagged accounts, Constant Contact suspensions and Mailchimp suspensions.

If you move to a new provider instead, don't carry the same unverified list across. The new provider will see the same bounces. Read our guide to bounces after switching email providers before you migrate.

Bottom line: A complete first reply shortens the wait. Moving providers without cleaning the list only repeats the problem.

How do I keep SendGrid bounce rate under control?

Prevention means verifying at every point where addresses enter your system. Most suspensions trace back to one of three entry points: forms, imports and old lists.

SendGrid offers its own address validation product. When you compare it with third-party options among the best email verification tools, ask four questions: how results are categorized, whether catch-all and disposable addresses get their own flags, how it fits your signup and import workflow, and how much work an integration takes. Our buyer's checklist for choosing an email verifier covers the rest.

For governance, document each verification run, its date and its counts. That record supports both your deliverability and your email verification compliance and hygiene obligations.

Bottom line: Validate at signup, verify imports and monitor bounces on every send. Most reviews are avoidable.

What are the most common mistakes in a SendGrid bounce review?

Bottom line: Most failed replies come from sending too soon or claiming a clean list without evidence.

How we compared (and limitations)

This article is based on public documentation: SendGrid's product documentation, Amazon SES's published guidance, Google's sender guidelines, RFC 3463 and the FTC's CAN-SPAM compliance guide. We haven't tested SendGrid's review process directly, and SendGrid doesn't publish its thresholds or timelines, so treat those as unknowns rather than rules.

The 2% ceiling and 1% target are our recommendations, not SendGrid's stated limits. Thresholds change without notice, so check current documentation before you act.

Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's own stated number, not an independent benchmark. Plan limits reflect the company's published facts at the time of writing. The worked example uses hypothetical results.

When you're ready to build your evidence, create a free Unlimited Verifier account, verify your list and reply to SendGrid with real numbers.

Signal-to-action map for a SendGrid review

Signal in notice What to do What to include in reply
Hard bounce spike Find the send and list source, remove invalid addresses Campaign name, bounce counts, source of list
High complaint activity Remove complainers, review opt-in and content Complaint counts removed, changes to sign-up flow
Unverified imported list Verify remaining contacts before any resend Verification method, results, and removed totals
Repeat issue after warning Pause all sending and audit the process Root cause, controls added, staged re-entry plan

Frequently asked questions

What bounce rate triggers a SendGrid account review?

SendGrid does not publish an exact bounce rate that triggers a review. The decision is a judgment call that weighs your bounce spike alongside complaint rate, sending history, and where your contacts came from. Read the notice closely, since it names the signal under review, and treat that signal as the thing to fix.

How long does a SendGrid bounce rate review take?

The timeline varies because each review depends on the account's history and how quickly the sender responds. There is no published fixed duration. Reply promptly with complete evidence, stop all sending during the review, and keep your records so you can answer follow-up requests without delay.

Can I keep sending while my SendGrid account is under review?

It is safest to stop sending entirely until the review closes. Each additional bounce during the review weakens your case and can extend the hold. Pause scheduled campaigns and automations, and only resume after you have removed and verified problem addresses and received guidance on re-entry.

Does SendGrid remove hard bounces automatically?

SendGrid adds hard bounces to its suppression list so it stops mailing those addresses. This prevents new damage but does not erase bounces already recorded, which still count in your sending history. Keep these suppressions in place and do not remove them to resend to those addresses.

What is the difference between a hard bounce and a block?

A hard bounce means the address is permanently invalid, usually signaled by an SMTP code such as 5.1.1. A block means the recipient's server rejected your message, often because of reputation or authentication problems. Cleaning your list fixes hard bounces but will not fix blocks, so check authentication and reputation separately.

Should I verify my whole list before replying to SendGrid?

Yes, verifying the remaining list is a strong step because it shows you have addressed the source. Remove unsubscribes, complaints, and known invalid addresses first, then run the rest through a reputable email verification service. Include the verification results and counts in your reply so the reviewer can see the evidence.

What should a SendGrid bounce review reply include?

A useful reply states the cause, such as one send to an imported or revived list, and gives exact counts of addresses removed and verified. Describe the verification method and results, and explain the controls you added. Commit to a specific bounce ceiling for future sending and outline a staged re-entry plan rather than a general promise to do better.

Can a SendGrid account be terminated over bounce rate?

Escalation can go from a notice and information request to a sending restriction, and to suspension or termination if the problem persists. Termination is more likely when the issue is ignored or repeats after review. Responding quickly, fixing the named signal, and following the re-entry plan reduces that risk considerably.

How should I re-enter sending after a SendGrid review?

Restart with your most engaged, recently active verified contacts rather than your full list. Increase volume gradually over several weeks while watching bounces and complaints after each send. If bounces rise again, pause and investigate before continuing, since a repeat spike can reopen the review.

Do unsubscribes and spam complaints affect a bounce rate review?

Unsubscribes and complaints are separate signals from bounces, but reviewers consider them together with bounce data. Remove unsubscribed and complained-about contacts from your sending lists and keep them suppressed. Show that you honor opt-outs quickly, since high complaint activity can make a bounce review harder to close.

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 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.