List hygiene7 min read
Email list cleaning checklist before your next campaign
Short answer
Clean your list in eight steps before you send: keep a copy, remove duplicates and typos, drop people you may not mail, verify every address, decide what to do with risky results, check your sending setup, send a small first batch and remove the bounces. Mailbox providers judge you by bounces and complaints, so a clean list protects your sending domain.
Key takeaways
- Remove duplicates, typos, unsubscribes and old hard bounces before you pay to verify anything.
- Send to ok addresses, remove invalid and disposable ones, and hold back catch_all and unknown.
- Treat the small first batch as a test, and pause if its hard bounce rate climbs above about 2%.
- Verify an older list again before every big send.
Why clean your email list before you send?
Mailbox providers judge you by your bounces and complaints, and a dirty list raises both on the very first send. Amazon SES's documentation says to keep your hard bounce rate below 5%. SES puts an account under review at 5% and may pause sending at 10%. Brevo's help center lists a hard bounce rate above 2% among the triggers that can suspend a campaign or account.
Complaints count too. Google's sender guidelines and Yahoo's best practices both ask you to keep the spam rate below 0.3%, and Google recommends staying under 0.10%. Old and mistyped addresses push your bounces up. People who do not know you push your complaints up.
Cleaning removes dead addresses. It cannot give you permission. Consent and the legal basis for cold or marketing email differ by country, so check the rules where your recipients live. Our post on why buying email lists burns your domain covers the details. This checklist assumes you have permission or a lawful reason to write to every person on your list. This is a general summary. Ask a lawyer about your own case.
What should you clean in your list before a campaign?
Work through eight steps, in this order. You remove the people you must not mail before you pay to check anyone, and you test the rest on a small batch before the full send.
- Keep a copy of the original file. If a later step removes too much, you can start over.
- Remove duplicates and fix obvious typos such as gmial.com or hotmial.com. A typo loses you a real contact, and a duplicate sends one person the same mail twice.
- Drop every address you have no lawful basis to mail, everyone who unsubscribed, and every address that hard bounced before.
- Check syntax, domain and mailbox with an email verifier. It asks the receiving server over SMTP whether the mailbox exists, without sending a message (see how email verification works).
- Decide what to do with risky results: catch_all, unknown, role and disposable. The table below gives a default for each.
- Check your sending domain: SPF, DKIM, DMARC, one-click unsubscribe and a visible unsubscribe link.
- Send a small first batch and watch the bounces for a day or two before you send the rest.
- After the send, remove every address that bounced, from this list and from your next campaign.
On step 6: Google's sender guidelines ask every sender to set up SPF or DKIM. A sender above 5,000 messages a day to Gmail needs SPF, DKIM and DMARC, plus one-click unsubscribe for marketing mail. Yahoo asks bulk senders for the same and expects unsubscribes to be honored within 2 days. One-click unsubscribe uses two message headers, List-Unsubscribe and List-Unsubscribe-Post, as RFC 8058 describes. Both providers also want a visible unsubscribe link in the body.
On step 8: Mailchimp's help center says it cleans hard-bounced addresses automatically in most cases. Other tools differ, and the same address may sit in your CRM or a second list, so remove it everywhere.
What should you do with each verification result?
Send to ok, remove invalid and disposable, and handle role, catch_all and unknown with care. The table gives a default action for each result.
| Result | What it means | What to do |
|---|---|---|
| ok | The server accepted the mailbox and the check found no warning sign. | Send. These addresses form your main batch. |
| invalid | The address is malformed, the domain has no mail server, or the mailbox does not exist. | Remove it. It would hard bounce. |
| disposable | A throwaway inbox from a temporary-mail service. | Remove it. The inbox may be gone soon. |
| role | A shared inbox such as info@ or sales@. | Send only if your offer fits the role. Several people read it, so watch complaints. |
| catch_all | The domain accepts every address, so one mailbox is not proven. | Send only to people who know you, in a small batch, or hold back. |
| unknown | The server gave no clear answer, for example it blocked the check or timed out. | Treat it like catch_all. Check again later if the contact matters. |
Our post on catch-all addresses explains why a domain that accepts everything proves nothing about one mailbox. An unknown result is honest uncertainty, so do not count it as valid.
How big should the first batch be, and when should you stop?
Start with a few hundred addresses, or a few percent of a large list. This is our own rule of thumb. A small batch shows whether the list is clean and limits the damage if it is not. Wait a day or two, then divide the hard bounces by the messages sent. In a batch of 200, four bounces already make 2%, so a single address moves the rate.
Treat these numbers as guidance. HubSpot's guide (in German) advises staying under 2%, and Amazon SES puts accounts under review at 5%. If your first batch bounces above 2%, pause. Find out which step missed those addresses before you send the rest. Providers count bounces differently, so compare like with like. Our post on what a good bounce rate is shows how to read the number.
How often should you repeat the cleaning?
Verify an older list again before every big send. Published estimates of how fast a list goes bad run from roughly 15% to 30% a year, and most come from verification vendors, so treat any single figure as a planning number. People change jobs and drop old addresses, which is why a list that was clean last year holds dead addresses today. Our post on how fast email lists decay goes through the numbers.
Between big sends, remove bounces and unsubscribes after every campaign (steps 3 and 8). That keeps the next cleaning short.
How can you check a whole list at once?
An email verifier runs step 4 on the whole file in one go. CleanBounceList accepts CSV, TXT and XLSX files, checks each mailbox over SMTP without sending mail, and labels every address ok, invalid, catch_all, disposable, role or unknown. Each unique address costs one credit, unknown results included. Duplicates are free. New accounts get 100 free credits, so you can test a small file first. The list cleaning page has the details. A check shows which addresses can receive mail. It does not make a list without permission acceptable.
Frequently asked questions
How often should I clean my email list?
Clean an older list again before every big send, and remove bounces and unsubscribes after each campaign. Lists decay as people change jobs and addresses, with published estimates of roughly 15% to 30% a year. A list that is a year old needs a fresh check before you rely on it.
What bounce rate means I should stop sending?
Pause if the hard bounce rate of your first batch goes above about 2%. This is guidance: HubSpot's guide advises staying under 2%, Brevo's help center lists above 2% as a suspension trigger, and Amazon SES puts accounts under review at 5%. Find the cause before you send more.
Should I send to catch_all and unknown addresses?
Only to people who know you, in a small batch, or hold them back. These results are not proven: the domain accepts every address, or the server gave no clear answer. A bounce here hurts your reputation. A contact you hold back can be tried again later.
Does verifying a list make it legal to email?
No. Verification shows which addresses can receive mail. It says nothing about consent or your legal basis, which differ by country. Check the rules for your recipients first and keep a record of where each address came from. A verified list without permission still draws complaints.
Should I remove role addresses like info@ from my list?
It depends on your offer. Keep them if the offer fits the role, for example a sales inbox for a business service. Several people read these inboxes, so watch complaints and unsubscribes closely. Remove them if the message is personal or aimed at one named contact.