Every email list you build starts going out of date the moment it is finished. Email list decay is the slow process by which good addresses stop working, as people change jobs, abandon inboxes, and move to new domains. Left unchecked, it quietly turns a clean list into a pile of bounces that can bruise your sender reputation long before you notice the drop in replies.
Why email list decay happens
An address is only a snapshot of where a person could be reached on the day the data was collected. Everything that makes that snapshot accurate is temporary. People leave companies, and when they do, their work mailbox is usually one of the first things the provider switches off. Teams rebrand or get acquired, and the old domain stops accepting mail. A personal inbox fills up and starts refusing new messages. A provider retires an address that has sat unused for years.
Job changes are the single biggest driver. In a normal year a meaningful share of any professional audience moves roles, and every move leaves a dead address behind. This is why a B2B list heavy on startups and fast-growing companies decays faster than one built from established, slow-moving organisations. The faster the people move, the faster the list rots.
Decay is not only about people leaving. Some addresses were never reachable to begin with. A typo at the point of capture, a throwaway inbox used to grab a lead magnet, or a role address that was later closed all look fine in a spreadsheet and fail the moment you send. Decay and bad capture compound, so a list that was never verified can carry a surprising amount of dead weight on day one.
A rough monthly decay rate
There is no universal figure, because decay depends on who is on the list and how it was built. As a rough rule of thumb, something like 2% of a typical B2B list goes stale each month. That sounds small until it compounds. A list you verified in January is a few percent wrong by spring and can be well past 20% wrong a year later, even if you never add a single new contact.
| Time since last verified | Rough share likely dead | What it means for a send |
|---|---|---|
| 1 month | around 2% | Fine for most sends |
| 3 months | roughly 5% to 6% | Re-verify before a large send |
| 6 months | around 10% or more | Treat the list as stale |
| 12 months | often 20% or more | Verify in full before using |
Treat these as orders of magnitude, not promises. A tightly maintained opt-in list decays slower than the table suggests, while a bought or scraped cold list can be worse, because the data was often months old before it ever reached you.
What decay costs you
A dead address is not a neutral miss. Every hard bounce and every spam-trap hit is a signal to Gmail, Outlook and Yahoo that you did not check who you were writing to, and that judgment attaches to your sending domain, not just to the one bad address. Let enough of them through at once and your genuine mail starts landing in spam. If your bounce rate has been creeping up, the cause is usually a list that has aged past its last verification. For the mechanics of keeping that number down, see how to reduce your email bounce rate.
The danger with decay is that it is invisible until a send exposes it. The list looks the same in your tool whether it is 2% dead or 25% dead. The only way to know is to check it against the mail servers that actually hold those mailboxes.
How verification catches a decayed list
Verification is how you measure decay without paying for it in bounces. Sends Verified checks each address without sending any mail. It looks up the domain's mail servers, opens an SMTP conversation with the right one, asks whether it would accept mail for that address, and hangs up before anything is delivered. Nobody on your list is emailed, so you can check a list as often as you like without touching your sending reputation. The full walk-through is in how email verification works.
Each address is scored on eight signals, including syntax, the domain, the mail server, the mailbox itself, whether the domain is a catch-all, and whether the address is disposable or a role account. The result is a category, and a few of those categories map directly onto the ways a list decays:
- Invalid means the address is not registered, has no mail server, or is malformed. It will bounce, and it should come off the list.
- Disabled means the provider has switched the account off. This is the classic fingerprint of someone who has left a company.
- Inbox full means the mailbox is over quota and refusing mail for now. The person may return, so it is worth re-checking rather than deleting outright.
One honest limit is worth knowing. When a domain accepts every address you throw at it, an individual mailbox cannot be confirmed by SMTP alone, so it comes back as Catch-all rather than Safe. Sends Verified tests these domains with a made-up address first, so a catch-all is flagged instead of waved through, and for Microsoft 365 catch-all domains it goes a step further and confirms the specific mailbox against the provider's directory. If you are not sure why a whole domain reads this way, what a catch-all email is explains it.
Results that the receiving server will not answer in time come back as Unknown, and Unknown is always free. The credit returns automatically when the task finishes, so a slow or greylisted server never costs you anything. Duplicates in the same upload are checked and charged once, which matters for a decayed list that has gathered repeats over the months.
A re-verification cadence that keeps up with decay
Because decay is continuous, a single clean-up has a short shelf life. The goal of a cadence is to re-verify often enough that dead addresses never pile up faster than roughly 2% a month adds them. For a list you mail regularly, a monthly check keeps pace. For one that has been sitting idle, the calendar matters less than the event: verify it the moment you decide to send to it again.
A verification result older than about three months should be treated as a guess rather than a fact, and re-checked before the next send. That is true even of addresses that came back Safe, because Safe only means the mailbox existed and accepted the check at that moment. An address can still bounce later for reasons on the sending side, such as SPF, DKIM or DMARC misalignment, a blocklisted sending IP, a server temporarily refusing, or the mailbox closing in the weeks after you checked. For the sending side of this same question, see how often to clean a sending list.
Uploading is not the bottleneck. A list can be a CSV or TXT file up to 50 MB or one million rows, the email column is detected for you, and every other column is kept in the download, so you can verify a full export and send it straight back into your tool without rebuilding it.
FAQ
How fast does an email list decay?
As a rough rule of thumb, around 2% of a B2B list goes stale each month, which compounds to roughly 20% or more over a year. The exact rate depends on your audience, so lists heavy on fast-moving startups decay faster than lists of established organisations, and cold data that was already months old on arrival is worse again. Treat any figure as an order of magnitude, not a guarantee.
Why do valid email addresses stop working over time?
The most common reason is that the person left the company, so the provider switched off their mailbox, which shows up as a Disabled result. Domains also change when companies rebrand, fold or get acquired, and busy inboxes fill up and start refusing mail. None of this is visible in your spreadsheet, which is why an address that worked last quarter can bounce today.
How often should I re-verify my list?
Re-verify an actively mailed list about every month to keep pace with normal decay, and always re-verify before a large or high-stakes send. Treat any result older than about three months as stale, and verify a list in full the moment you pull it back out of storage. Checking does not send mail, so frequent re-verification carries no risk to your reputation.
Does a clean verification mean the address will never bounce?
No. A Safe result means the mailbox existed and accepted the check at that moment, not that it will still be live weeks later. Mail can fail afterwards for sending-side reasons such as authentication misalignment, a blocklisted IP, or the mailbox being closed after the check, which is exactly why a re-verification cadence matters.