How often should you clean your email list?
How often to clean your email list depends on how fast cold data goes stale. Here is a sensible re-verification cadence to protect your sender reputation.
Most senders think about list cleaning once, right before a campaign, and then forget about it for months. That is backwards. The real question is not whether to clean, but how often to clean an email list so that dead addresses never pile up faster than you remove them. For cold outreach, where the data was bought or scraped rather than opted in, the answer is more often than you would guess.
How fast a cold outreach list goes stale
Every email list decays from the day it is built. People change jobs, companies rebrand or fold, inboxes fill up, and providers retire old addresses. A rough industry rule of thumb is that something like 2% of a B2B list goes stale each month, which means a list you verified in January is already a few percent wrong by spring and can be well over 20% wrong a year later. Cold lists decay faster than opted-in ones, because the data is often months old before it reaches you and was never confirmed by the person themselves.
The decay is not spread evenly, either. A list heavy on startups and fast-growing companies churns faster than one of established enterprises, because job changes are the single biggest driver of a dead address. For the full picture on what drives this, see why email lists decay. The practical takeaway for a sender is simple: a verification result that is more than a month or two old is a guess, not a fact, and you should treat it that way.
How often to clean an email list: a sensible cadence
There is no single number that fits every list, because cadence depends on how actively you send and how old the data is. The table below is a good default for a cold-outreach operation. The guiding idea is to re-verify often enough that the share of dead addresses never gets ahead of the roughly 2% a month that nature adds.
| Situation | Re-verify when | Why |
|---|---|---|
| Active cold list you send to weekly | Every 30 days | Matches the monthly decay rate before it compounds |
| List that sat idle for 1 to 3 months | Right before the next send | Decay kept accruing while the list was parked |
| List older than 6 months | Full re-verify, treat as new | Likely 10% or more dead by now |
| Any list before a large or high-stakes send | Always, no exceptions | One bad batch can damage a whole domain |
| Freshly imported data | On import | Catch dead addresses at the door |
The thirty-day rhythm matters most for lists in active rotation. If you are mailing the same list every week, a monthly re-verification keeps the newly departed from accumulating into a bounce problem you only notice when your reply rate drops. For a list you touch rarely, cadence by the calendar is less useful than cadence by event: verify it the moment you decide to send to it again.
Why cleaning before a big send protects your reputation
Bounces are not just wasted sends. Every hard bounce and every spam-trap hit tells Gmail, Outlook and Yahoo that you did not check who you were writing to, and that judgment attaches to your sending domain, not only to the one bad address. A bounce rate that creeps over 2% is the point where most teams should stop and look. MailFleet flags any campaign bounce rate above 2% in dark red for exactly that reason, and its Deliverability page raises a Watch status at 4% bounced and a Critical status at 8%, so you find out before a filter decides for you.
The danger with a big send is that the damage is front-loaded and hard to undo. If a quarter of a 10,000-address batch is dead, that is 2,500 bounces landing in a day or two, which reads to a receiving server like a list you never cleaned. Cleaning before you send keeps the bounce rate low enough that your genuine messages keep reaching the inbox. It also works hand in hand with sensible volume. There is no point verifying carefully and then blasting the list on day one, so pace yourself with a realistic view of how many cold emails per day a warming domain can carry.
How to clean an email list without burning credits
Cleaning does not have to mean re-paying to check every address every month. MailFleet verifies addresses before they enter a campaign, and an address your workspace checked in the last 30 days is free to check again, so a monthly re-verification cadence costs you nothing for the addresses that have not aged out. A malformed address is marked invalid for free, too. Verification is included on Pro, with 300 checks a day, and Scale, with 1,000 checks a day; Basic and the free trial do not include it.
A few things happen automatically, so you do not have to police them by hand:
- On every import, duplicates, unsubscribes and previously bounced addresses are stripped out before anything is added to your workspace.
- You can tick Verify emails before importing and choose which statuses to let in. Verified is allowed by default, and you can also allow Catch-all, Role email and Unknown. Invalid, disabled, disposable, full and spam-trap addresses are never imported, whatever you pick.
- A suppressed lead keeps its bounced or unsubscribed status on re-import, so a stale CSV can never resurrect someone who already dropped out.
Those checks run on the way in. Verification tells you more than valid versus invalid: a result can come back as Verified, Catch-all, Role email, Unknown, Inbox full, Invalid, Disabled, Disposable or Spam trap, which lets you decide how aggressive to be. A tight sender might send only to Verified addresses, while a looser one might include Catch-all and accept a slightly higher risk.
A practical cleaning workflow
Put together, a sender's cleaning routine is short and mostly automatic:
- Verify on import, and let the tool drop the invalid, disposable and spam-trap addresses before they ever reach a list.
- Re-verify any list older than 30 days before its next campaign. Open the list on the Leads page and run Verify emails, which is free for anything checked in the last month.
- Always re-verify before a large or high-stakes send, no matter how recently the list was built, because the cost of one bad batch is a bruised domain.
- Watch the bounce rate per campaign and per domain. Treat 2% as a yellow flag and anything higher as a reason to pause and clean rather than keep sending. A clean list is one half of the story, so pair it with the rest of a cold email deliverability checklist.
- Keep a blocklist for domains and addresses you never want to touch again, so a cleaned list stays clean the next time you import.
None of this is heavy. The whole point of a cadence is that you decide the rules once and then let them run, instead of scrambling to scrub a list the night before a launch.
FAQ
How often should I clean a cold email list?
For an active cold list you send to regularly, re-verify about every 30 days, which roughly matches how fast a B2B list decays. Always re-verify before a large send and before mailing a list that has been sitting idle for a month or more. A list older than six months is best treated as new and verified in full.
Does cleaning my list really protect my sender reputation?
Yes. Bounces and spam-trap hits attach to your sending domain, not just to the bad address, and a bounce rate drifting over 2% is where deliverability starts to suffer. Removing dead addresses before a send keeps that rate low, so your genuine messages keep reaching the inbox rather than the spam folder.
How much does regular re-verification cost in MailFleet?
Verification is included on Pro, at 300 checks a day, and Scale, at 1,000 checks a day; Basic and the free trial do not include it. An address your workspace checked in the last 30 days is free to check again, so a monthly cadence costs nothing for addresses that have not aged out, and a malformed address is marked invalid for free.
Can I just rely on my sending tool to drop bad addresses?
Partly. MailFleet strips duplicates, unsubscribes and previously bounced addresses on every import automatically, and a true hard bounce halts that lead's sequence on its own. But those steps catch problems at the door or after the fact, while proactive re-verification is what stops a batch of newly dead addresses from bouncing in the first place.