Platform how-to

SendGrid Bounce List: How to View, Export and Remove Addresses

A tall stack of envelopes on a desk, rendered in blue halftone dots

SendGrid keeps a list of every address that has hard-bounced on your account, and it never mentions it. There is no alert, no monthly summary, no count on the dashboard. Your application calls the API, SendGrid checks the address against the bounce list, drops the message without trying, and returns a success response for having accepted it.

That silence is the design. The bounce list is a safety mechanism, not a report, and it does its job without asking you to look. The trouble starts when you do not: the list grows, your contact database never hears about it, and the same dead addresses re-enter through your sign-up form, your CRM sync, or a re-import a year later. This guide shows where the bounce list lives, how to view and export it, when deleting an address from it is the right call and when it is a mistake, and how to stop bounced addresses from coming back through your own app.

Key takeaways

  • The bounce list is under Suppressions, with blocks, spam reports, invalid emails, and unsubscribes beside it. Only bounces and the hard-failure lists are permanent.
  • A message to a bounced address is dropped, not sent. The API still returns success, and the drop shows up as an event, not an error.
  • Export the list from the interface or the API, and use it as a suppression file against your contact database and every list you import.
  • Delete an address from the bounce list only with proof it works again. Never schedule a purge.

Where the bounce list lives and why it is silent

In the SendGrid interface, the left navigation has a Suppressions section. Inside it are separate lists: Bounces, Blocks, Spam Reports, Invalid Emails, Global Unsubscribes, and Group Unsubscribes. Bounces is the one this guide is about. Each entry shows the address, the date it was added, and the status message the receiving server returned, often specific: user unknown, domain not found, mailbox disabled.

The list is per account. If your account uses subusers, each subuser has its own Bounces list, and a bounce recorded under the transactional subuser is unknown to the marketing one. Teams discover this when the newsletter bounces at 4% on addresses the receipts stopped reaching months ago.

Silent is the right word for how it operates. When your application sends to an address on the list, SendGrid accepts the request, checks the suppression, and drops the message. The API response is a success, because the request was valid. The drop appears in the activity feed and in the Event Webhook as a dropped event with the reason attached, and nowhere else. Nothing on the sending side fails, so nothing on the sending side gets fixed. Your database still thinks the address is fine. What your ESP won't tell you about bounces is the longer version of that complaint.

What lands on the bounce list and what does not

SendGrid sorts failures into several lists, and only one of them is called Bounces. Knowing which is which decides what to export and what to leave alone.

Suppression listWhat put the address therePermanentTreat as dead
BouncesA permanent rejection: the mailbox or domain does not existYes, until removedYes
BlocksA temporary or policy rejection: rate limit, content filter, full mailboxNo, retried on each sendOnly after repeats
Invalid EmailsFailed syntax checks before any server was contactedYesYes
Spam ReportsThe recipient reported the messageYesYes, and never re-import
UnsubscribesThe recipient opted out, globally or from a groupYesNot dead, but not yours to mail

The Bounces list is SendGrid's version of a classic hard bounce. Blocks are its soft bounces: SendGrid does not suppress a blocked address, so it is tried again next time. A single block is noise. An address in Blocks on four consecutive sends is an abandoned inbox, and SendGrid will keep trying it until you decide otherwise. Hard bounce vs. soft bounce covers the reasoning for treating repeats as final. For a cleanup, export Bounces, Invalid Emails, and Spam Reports as the suppression side, and read Blocks for repeaters rather than suppressing it wholesale.

Dropped is not delivered, and success is not sent. A 202 from the API means SendGrid accepted the request, not that the message went anywhere. Addresses on the bounce list produce a dropped event, visible in the activity feed and the Event Webhook. If your app treats the API response as proof of delivery, it will never notice a single bounce.

How to view and export the list

There are two routes, and large accounts will prefer the second.

  1. Interface. Open Suppressions, choose Bounces, and use the search and date controls to narrow the view. The export control on that page produces a CSV of the addresses with their dates and reasons. Repeat for Invalid Emails and Spam Reports.
  2. API. GET /v3/suppression/bounces returns the same data as JSON, with optional start and end time parameters so you can pull only what changed since the last export. Flatten the result to a CSV with an email column.
  3. Subusers. Repeat either route for each subuser. A single account-level export does not include them.

Name the files plainly: sendgrid-bounces-2026-10.csv rather than export.csv. The suppression exports and your contact export have different column layouts; the cleaning step only needs the email column in each. Then export the list you want to check against them, whether that is Marketing Campaigns contacts from the Marketing area or a dump of the users table from your own database. Both are covered in how to remove bounced emails from SendGrid.

  1. Open Suppressions and view Bounces

    In the SendGrid interface, go to Suppressions and choose Bounces. Read the reasons; they tell you what kind of failure each address represents.

  2. Export the list

    Use the export control for a CSV, or call the bounces endpoint of the API with a start time to pull only recent entries. Repeat for each subuser.

  3. Export Invalid Emails and Spam Reports too

    These are permanent failures and belong in the same suppression folder.

  4. Clean your contacts and imports against the folder

    Upload the contact export or incoming list as the original and each suppression CSV as a suppression file. Download the cleaned CSV.

  5. Remove only with evidence

    Delete a single bounce entry when the owner has proven the address works. Leave the purge setting off.

  6. Feed the webhook into your database

    Store bounce and dropped events on the user record so the app stops re-adding addresses SendGrid has already refused.

When removing an address is the right call

Removing an address from the Bounces list tells SendGrid to try it again. That is the whole effect. It does not verify anything, repair anything, or improve any metric except the length of the list.

The right call looks like this: a customer writes to support from the bounced address, asking why the receipts stopped. The address demonstrably works. The bounce reason, when you look it up, was a server outage or a full mailbox that SendGrid classified as permanent. You remove the one address, send the next receipt, and watch the activity feed to confirm delivery. That is a correction, and it is what the remove control exists for.

The wrong call looks like this: the list has 11,000 entries, someone decides that is untidy, and the list is cleared so the count returns to zero. Every one of those 11,000 addresses is now eligible for delivery again. The next campaign bounces at a rate inbox providers notice immediately, and the account's sending reputation, which SendGrid shares across its IP pools, takes the hit. The bounce purge setting, which clears the list automatically on a schedule, is the same mistake with a timer attached. Leave it off. Sender reputation explained describes what a sudden bounce spike does to a domain and how long the recovery takes.

A bounce list with 11,000 entries is not a problem. It is 11,000 messages you did not pay to have rejected.

How to remove addresses safely

When removal is justified, do it narrowly.

  • One address in the interface. Find it on the Bounces page and use the remove control for that row. Confirm. Then send one message and check the activity feed before you trust the address with anything else.
  • One address by API. DELETE /v3/suppression/bounces/{email} removes a single entry. Wire it into your support tooling so each removal is logged against a ticket.
  • Never the whole list. The API also allows deleting every bounce at once. There is no honest reason to call it on a production account.
  • Record what you removed and why. A note with the date, the address, and the evidence. If the address bounces again, the note is what stops the next person from removing it a second time.

Removal is also irrelevant to billing. SendGrid's suppression lists do not count toward any contact tier; Marketing Campaigns pricing counts stored contacts, bounced or not. If the goal is a smaller bill, the fix is deleting the contact from Marketing Campaigns, not deleting the bounce. The FAQs cover the difference between the two in more detail.

Keep bounced addresses from re-entering through your app

The bounce list stops SendGrid from delivering to a dead address. It does not stop your application from adding it again. A user re-registers with the same typo, a CRM sync pushes last year's export back in, a marketing import brings 2,000 contacts from a partner, and a share of those addresses are already on the Bounces list. SendGrid will drop them silently and your database will go on counting them as reachable.

  1. Listen to the Event Webhook. SendGrid posts a bounce event and a dropped event to a URL you control. Store a flag on the user record when either arrives. Your own database then knows what SendGrid knows.
  2. Check before you insert. If your app accepts addresses in bulk, query the bounce flag, or the API, before saving them. An address on the list should not become a new active user.
  3. Clean imports before they reach Marketing Campaigns. Upload the incoming file to Email List Refresh as the original, with the Bounces, Invalid Emails, and Spam Reports exports as suppression files. Matching is case-insensitive and de-duplicated across files. The cleaned CSV keeps every column and loses only the addresses SendGrid has already refused.
  4. Repeat the export monthly. Pull the Bounces list with a start time of the last export and append it to your suppression folder. It takes a few minutes and keeps the folder current.

A 40,000-row import checked against two years of SendGrid suppressions will typically lose 1,000 to 1,500 rows. Those rows would have been dropped anyway. What you have saved is the contact fees and the quiet divergence between what your app believes and what SendGrid knows.

Free estimate

See what this costs your list

Pick your list size. We will show you the math, then send you a one-page cleanup plan for your platform.

Your estimatePick a list size and platform to see the numbers.
—addresses likely dead this year
—paid per year to store them
—contacts that can still be reached

No spam, no list rental. One email with your plan, then nothing unless you ask.

FAQ

Questions about sendgrid bounce list

Where is the bounce list in SendGrid?

Under Suppressions in the left navigation, on the Bounces page. It lists every address that returned a permanent rejection on your account, with the date and the status message from the receiving server. Blocks, Spam Reports, Invalid Emails, and Unsubscribes have their own pages in the same section. If your account uses subusers, each one has a separate Bounces list, so check them all.

How do I export the SendGrid bounce list?

From the Bounces page under Suppressions, use the export control to download a CSV of the addresses, dates, and reasons. For large accounts or regular pulls, call GET /v3/suppression/bounces with start and end time parameters and flatten the JSON to a CSV. Either file works as a suppression file against a contact export or an incoming list.

Should I delete addresses from the SendGrid bounce list?

Only one at a time, and only with proof the address works again, such as a message from its owner after the bounce date. Deleting an entry tells SendGrid to deliver to that address on the next send. Clearing the whole list, or enabling the bounce purge setting, re-enables every dead address at once, and the resulting bounce spike damages your sending reputation.

Why does SendGrid return success for an email that bounced?

Because the API response confirms that SendGrid accepted a valid request, not that the message was delivered. For an address on the bounce list, SendGrid accepts the request and then drops the message without attempting delivery. The drop appears as a dropped event in the activity feed and in the Event Webhook, with the bounce as the reason. Applications that rely on the API response alone never see it.

Do addresses on the SendGrid bounce list count toward my contact limit?

The bounce list itself does not count toward anything. Marketing Campaigns pricing counts stored contacts, and a bounced address that is still a contact keeps counting until you delete the contact. Removing the bounce entry does not help the bill and does re-enable delivery. To lower the count, export the bounce list, remove the matching contacts from Marketing Campaigns, and leave the suppression in place.

Clean your list before the next send.

Upload your contacts and every suppression file you have. Download a clean CSV with every column intact. Seven minutes, start to finish.

Envelopes drop into a funnel: good addresses stack up, bad ones are thrown out