Article

Is It Safe to Email a Two-Year-Old List? A Practical Answer

By Unlimited Verifier Team ·

Flowchart showing a two-year-old email list being verified, then sending first to recent clickers while keeping bounces under 2%.

Summary

Yes, a two-year-old email list is safe to email once every address is verified and you start with contacts who clicked, replied or bought in the last 90 days. List age matters less than verification results and recent engagement. Keep bounces under 2% per send and spam complaints under 0.1%.

Yes, a two-year-old list is safe to email once you verify it and send first to contacts who clicked in the last 90 days, keeping bounces under 2% of each send. Age alone isn't the risk. Unverified addresses and stale consent are.

Mailing the whole list unchecked is where most teams get hurt. Two years of job changes, closed mailboxes and fading consent can push one campaign past the 2% ceiling this guide recommends, and it can generate spam complaints from people who no longer recognise your brand. If your ESP has already acted on bounces, our full guide to high bounce rate account suspension covers the platform side.

Quick answer

Is a two-year-old email list safe to email?

A two-year-old list is safe to email only for contacts you can show are still reachable and still expect your mail. The list's age tells you little on its own. Two years is long enough for real change, though. People switch employers, which closes work addresses, and providers close or recycle free accounts. Consent drifts too: someone who signed up for a webinar in 2023 may not expect a promotional campaign in 2025.

Our working rule is simple. A contact is ready for a marketing send when it verifies as Valid and has shown a click, reply or purchase within the last 365 days. Anything else waits for a permission email or gets suppressed. That rule turns the vague question "is this list too old?" into a count you can act on.

Bottom line: Judge each contact by its verification result and recent behaviour, not by how old the list is.

Why does a two-year-old list become risky?

A two-year-old list becomes risky through four mechanisms, and each one shows up in a different metric. Invalid addresses produce hard bounces. Recycled traps and stale consent produce complaints and reputation damage. Misleading engagement data hides all of it.

If the old list came from a recent import rather than years of signups, why bounce rates jump after importing a list explains the usual pattern.

Bottom line: Bounces, complaints and traps each signal a different problem, and open rates can hide all three.

How much of a two-year-old list is likely dead?

There is no reliable universal percentage, so measure your own list instead of trusting an industry average. Decay depends heavily on the audience. Most teams running email verification for ecommerce and SaaS programs find that B2B lists decay faster than consumer lists, because job changes close work addresses. Some vendors publish decay estimates. Treat those as their own claims, drawn from their customer data, not as a forecast for your list.

To measure your own decay:

  1. Pull bounce history from your last several campaigns, grouped by contact.
  2. Split the list by last click, reply or purchase date, not by the date the contact was created. Creation date tells you when someone joined. Engagement date tells you whether they still care.
  3. Verify a sample from each cohort. The gap between cohorts' invalid rates shows where the decay sits.

In the worked example later in this guide, the invalid rate climbs from about 3% in the most recently engaged cohort to over 20% in the dormant one. Your numbers will differ, but the shape of the curve is common.

Bottom line: Your own bounce history and a verification run tell you more about decay than any published average.

Which contacts should you email, and which should you stop?

Split the list into four cohorts by last engagement, then give each cohort a different action. This table is the core of the approach.

Cohort (last click, reply or purchase) What it usually means Action
Core: 0–90 days Recent, real engagement Verify, then send first
Warm: 91–365 days Engaged within the past year Verify, then send in the second wave
Cold: 366–730 days Interest is fading, and opens are unreliable Verify, send one permission email, suppress non-responders
Dormant: no click, reply or purchase in 730+ days, or never Little evidence they want your mail Suppress from marketing; permission email only if your legal basis allows it

Why these cutoffs? Ninety days captures people who are still mid-relationship. Three hundred sixty-five days captures people who still engage at least once a year. These are practical defaults, not industry standards. A monthly newsletter might justify a shorter warm window, and a quarterly catalogue might need a longer one.

The point of the cohorts is to protect your sender reputation. Your first sends should go to the people most likely to engage and least likely to complain.

Bottom line: Clicks, replies and purchases build the cohorts, and open-only contacts count as unproven.

What are your options for emailing an old list?

Five approaches are common. Verification-first is the one that protects deliverability and produces evidence you can show a compliance team.

Option Protects deliverability? Main risk Best use
Send the full list as-is No Bounce spike, complaints, possible account review Rarely justified
Remove only last send's bounces Partly Untested addresses remain on the list A first step, not a complete fix
Re-engagement email to the full list No, if unverified Sends to dead and trap addresses Only after verification, to a Valid cold segment
Verify, then send to recent engagers Yes Smaller first audience The default
Sunset dormant contacts Yes Lower reach on paper Policy for the dormant tier

A re-engagement email sounds like the fix, but it is still a send. Sent to an unverified list, its bounces land on your reputation at the moment it is most fragile. For the full sequence, see how to send to an old email list safely.

Bottom line: Verify first, mail engaged contacts first, and sunset what remains.

What does verification actually check?

Verification checks whether an address is likely to receive mail, then sorts results into categories you can act on. Each check answers a different question, and none of them proves consent.

Check What it finds What it can't tell you
Syntax Malformed addresses, such as a missing @ or illegal characters Whether the mailbox exists
Domain and MX records Domains that can't receive mail or have no mail servers Whether a specific person works at that domain
SMTP mailbox check Whether the receiving server accepts the address, without delivering a message Whether the person reads or wants the mail
Catch-all detection Domains that accept every address, so the mailbox can't be confirmed Whether the specific mailbox is active
Disposable and role flags Throwaway providers and role accounts such as info@ Whether a role mailbox is monitored

Two limits matter in practice. First, catch-all domains accept every address, so a clean result tells you less. Treat those contacts as uncertain and send them last. Second, mail servers can refuse, throttle or defer checks, so some results are inconclusive. That is why a Risky category exists instead of a simple pass or fail.

Bottom line: Verification removes invalid addresses and flags uncertainty, but it can't prove anyone agreed to receive your mail.

What bounce and complaint numbers should you target?

Sources disagree, so pick one conservative target and hold to it.

Our recommendation is a 2% bounce ceiling for any send, a 1% target for early re-entry sends, and a complaint rate under 0.1%. The 2% ceiling leaves headroom below the lower platform triggers. The 0.1% complaint goal matches Google's own target and is the stricter of the two published lines.

Bottom line: Use 2% as the hard ceiling, 1% for early sends, and 0.1% as the complaint goal.

Does the law allow you to email a two-year-old list?

Sometimes. The list's age isn't the test. What matters is the lawful basis for each cohort and whether you can show it. This is general information, not legal advice.

For dormant contacts, the lawful basis is hardest to defend. Keep records of how and when each address was collected, and treat email verification compliance and hygiene as a documented process, not a one-off clean-up.

Bottom line: Verification keeps the list clean, but each cohort's lawful basis has to be documented separately.

How do you verify and segment an old list step by step?

Work through these eight steps in order. Each one produces a number you'll need later.

  1. Define "active" by behaviour. Use last click, reply or purchase, not signup date or open rate. Clicks require intent, and opens are inflated.
  2. Cohort the list. Apply the table above and count each cohort. Decisions are made per cohort, so you need the counts.
  3. Verify everything. Include dormant contacts. Their verification results tell you what to suppress and give you an accurate invalid count for the whole database.
  4. Count the buckets per cohort. Valid, Risky and Invalid counts by cohort show where decay sits. That is the evidence you'd cite in an appeal.
  5. Suppress Invalid and hold Risky. Invalid addresses come out permanently. Risky addresses stay out of early waves.
  6. Send to core Valid contacts first, in a small wave. Keep the first audience small enough that 1% is a countable number. On 5,700 contacts, 1% is 57 bounces.
  7. Ramp only when each wave stays under target. Each wave tests your reputation. Mailbox providers remember a bad send for a while, so does one high-bounce campaign hurt deliverability for weeks? explains why the ramp needs patience.
  8. Schedule re-verification. Repeat monthly or quarterly. The email list maintenance best practices guide covers cadence.

Bottom line: Behaviour sets the cohorts, verification sets the safe addresses, and each wave tests your reputation before you scale.

How do you verify a two-year-old list in Unlimited Verifier?

Export each cohort as a CSV, upload it to Unlimited Verifier, and re-import only the Valid contacts. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so the workflow runs through files or the API.

  1. Export your contacts as CSV. Include the email column, last click date, last purchase date and signup date. Export your suppression file separately and keep a copy.
  2. Split by cohort in a spreadsheet. Filter by last click date and save each cohort as its own file.
  3. Create an account. You can sign up for free. The Free plan covers lists of up to 150 emails, 25 lists a month and 750 deep verifications a month, but it has no API access and keeps results for 24 hours. The Pro plan ($29 a month, or $25 a month billed annually) handles lists of up to 25,000 emails and includes API access.
  4. Upload the file on the upload page. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Check that the right column was picked. An email-only file of 40,000 rows is typically a few megabytes, but split any file that goes over the 10MB limit.
  5. Run verification. Each address gets syntax, domain, MX and SMTP mailbox checks. Catch-all, disposable and role-based addresses are flagged so you can hold them back.
  6. Read the three buckets. Valid goes to your first sends. Invalid goes to suppression. Risky is held back. For catch-all results, the catch-all email verification page explains how they're handled.
  7. Download results immediately. Export as CSV, Excel or JSON. Results are kept for 24 hours on the Free plan and 30 days on Pro, so archive your files.
  8. Re-import by bucket. Upload Valid contacts as a new segment, add Invalid contacts to suppression, and store Risky contacts in a hold segment. Before you import, read how to avoid ESP suspension when importing old lists.
  9. Spot-check edge cases. For a key account that comes back Risky, use the free email checker to test a single address before you decide.

Bottom line: Export by cohort, verify, download within the retention window, then re-import so your sends follow the buckets.

What does a 40,000-contact old-list cleanup look like in numbers?

This example is illustrative. The plan limits and arithmetic are real, and the results are hypothetical.

The situation: A B2B software company has 40,000 contacts collected over two years. It last mailed the full list 25 months ago.

Step 1: Check the plan fit.

Adding the core cohort to deep verification would total 27,000, which is over the monthly allowance. Core contacts have clicked in the last 90 days, so standard checks are enough for them. Dormant contacts are suppressed from marketing anyway, so deep checks there would be wasted.

Step 2: Cohort counts and hypothetical results.

Cohort Contacts Valid Risky Invalid Invalid rate
Core (0–90 days) 6,400 5,700 500 200 3.1%
Warm (91–365 days) 11,200 9,300 1,400 500 4.5%
Cold (366–730 days) 9,400 6,100 1,900 1,400 14.9%
Dormant (730+ days or never) 13,000 8,900 1,200 2,900 22.3%
Total 40,000 30,000 5,000 5,000 12.5%

Check: each row sums to its cohort count, and the totals reconcile. Overall, 30,000 Valid is 75%, Risky is 12.5% and Invalid is 12.5%. Dormant contacts make up 32.5% of the list but 58% of the invalid addresses (2,900 of 5,000).

Step 3: Turn the buckets into actions.

Action Who Count Check
Send wave 1 Core, Valid 5,700 1% = 57 bounces
Send wave 2, only if wave 1 stays under 1% Warm, Valid 9,300 1% = 93 bounces
Permission email Cold, Valid 6,100 1% = 61 bounces
Hold until core waves are clean Risky, core/warm/cold 3,800 Small test, last
Suppress from marketing Dormant, Valid and Risky 10,100 Permission email only if lawful basis allows
Remove permanently Invalid, all cohorts 5,000 Suppression list

Check: 5,700 + 9,300 + 6,100 + 3,800 + 10,100 + 5,000 = 40,000.

Step 4: Cost. One Pro month at $29 covers the whole clean-up. Spread across 40,000 contacts, that's about $0.73 per 1,000 contacts for the month. On the annual plan, $25 a month works out to $300 a year. If you want to compare email verification pricing across vendors, use cost per 1,000 contacts for your actual volume, not headline plan prices.

Bottom line: Cohorts turn a 40,000-row list into four uploads, a clear deep-verification budget and a send schedule where each wave can be checked against a countable bounce target.

What mistakes turn an old-list send into a bounce problem?

Bottom line: Most old-list problems come from sending too much, too early, based on the wrong signal.

How do you keep old-list checks automated going forward?

Verify addresses at the point of entry and re-verify on a schedule, so the list doesn't age into this problem again. Real-time email validation at signup stops most invalid addresses from entering the list in the first place.

For ongoing checks, the email verification API and automation approach means calling the API from your own scripts. Unlimited Verifier's API supports single-email checks and bulk batches of up to 10,000 emails per request. The Pro plan includes 100,000 API emails a month. API access isn't available on the Free plan. You can find keys on the email verification API page.

When you compare tools, look for four things: catch-all detection, a Risky category you can hold back, export formats that suit your workflow, and API volume that matches your batch sizes. Our guides to the best email verification tools and how to choose an email verifier go through those criteria. If a platform has already flagged your bounce rate, Mailgun's high bounce rate warning and our 5 steps after a bounce rate spike explain the immediate response.

Bottom line: Validate at entry, re-verify on a schedule, and automate the pieces you can, so clean-up becomes routine instead of an emergency.

How we compared (and limitations)

This article is based on public documentation: Google's and Yahoo's sender guidelines, Amazon SES's published thresholds, the FTC's CAN-SPAM guidance, UK ICO direct marketing guidance, RFC 3463 for SMTP status codes and M3AAWG's sender best practices. We have not tested any ESP's review process, and platform thresholds change without notice.

Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's own stated figure, not an independent benchmark. The worked example uses illustrative cohorts and hypothetical results, so it is not a forecast for any real list. This is general information, not legal advice. The lawful basis for any send depends on your jurisdiction and your records.

Bottom line: Treat thresholds, timelines and vendor figures as moving targets, and check every number against your own data.

Four-step safe-send framework

  1. Verify the full list. Keep only Valid addresses for the first campaign.
  2. Send to contacts with a click, reply or purchase in the last 90 days.
  3. Check bounces (target under 2%, under 1% early) and complaints (under 0.1%).
  4. If metrics hold, widen to the 365-day engaged group, then suppress or re-permission the rest.

Example: 10,000 contacts. Verification leaves 8,200 Valid. 1,900 clicked in 90 days. Send wave one to 1,900; if bounces stay under 1%, widen to the remaining engaged contacts next.

Frequently asked questions

How old is too old for an email list?

There is no fixed age limit. Age alone does not make a list unsafe. What matters is whether contacts still verify as valid and have engaged recently. Many teams treat contacts with no clicks, replies or purchases in 365 days as dormant and suppress or re-permission them before mailing at full volume.

Should I verify an email list before sending?

Yes. Verifying the full list before any campaign removes invalid and risky addresses that cause hard bounces and can expose you to spam traps. Keep only addresses marked Valid for the first send, then review the Unknown and Risky results separately before deciding whether to mail them.

What bounce rate is safe for an old list?

A common guideline is to keep bounces under 2% per send, and under 1% on early sends to an old list. Higher bounce rates signal poor list quality to mailbox providers and can trigger ESP account reviews or suspension.

Can spam traps hit a two-year-old list?

Yes. Abandoned addresses can be recycled into spam traps by mailbox providers and blocklist operators. Hitting one signals poor list hygiene and can damage sender reputation more than a simple bounce. Verification and suppressing long-dormant contacts reduce this risk.

Do I need consent to email an old list?

Consent rules depend on your jurisdiction and how contacts opted in. Under GDPR and similar laws, you need a lawful basis for marketing email, and consent must be specific and provable. If you cannot show a contact opted in and still expects mail, send a single permission email or suppress them.

Will emailing an old list hurt my sender reputation?

It can. Old lists generate bounces, complaints and spam trap hits, and these signals lower inbox placement. Starting with engaged contacts and widening in waves gives mailbox providers positive engagement data and limits the damage from any unhealthy segment.

Are open rates reliable for judging an old list?

Not reliably. Apple Mail Privacy Protection preloads tracking pixels for many recipients, which inflates open counts. Clicks, replies and purchases are stronger signals of real engagement, so base your recent-engagement segment on those actions.

How do I re-engage a dormant contact safely?

Send a short, clearly branded permission or re-engagement email asking the contact to confirm they want to hear from you. Contacts who do not respond within a set window should be suppressed from marketing sends rather than mailed at full volume.

Should I send to the whole old list at once?

No. Sending to the full list at once maximises bounces and complaints in one go. Begin with verified, recently engaged contacts, then expand in waves while monitoring bounce and complaint rates after each send.

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.