Article

How Long Do Email Verification Results Stay Accurate? A Practical Guide

By Unlimited Verifier Team ·

Timeline diagram showing an email verification result going stale over 30 to 90 days and prompting re-verification before sending.

Summary

Most email verification results stay reliable for roughly 30 to 90 days, though no industry standard sets that window. Valid results decay fastest, so treat any Valid result older than 90 days as stale and re-check dormant or event-sourced contacts after 30 days.

Most email verification results stay reliable for 30 to 90 days, but no industry standard sets that window. As a planning rule, treat any Valid result older than 90 days as stale, and re-check dormant or event-sourced contacts after 30.

A verification result is a snapshot of what a receiving mail server said about an address at one moment. Since then, people change jobs, companies retire domains, mailboxes close, and providers change how they respond. The useful question is not "is this result accurate?" but "how old is this result, and what am I about to use it for?"

Quick answer

What does an email verification result actually measure?

A verification result records a few checks run at one point in time. Syntax and domain checks are static, but the mailbox check is live. It opens an SMTP conversation with the domain's mail server and asks whether that server would accept mail for the address, without delivering a message. The protocol is defined in RFC 5321, and the answer depends on how the receiving server chooses to respond.

That creates two limits on what the result can tell you:

Accuracy and shelf life are different properties. Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark, and it describes how often a check was correct when it ran. It says nothing about how long the answer stays true. Read what the 99% accuracy claims really mean before you rely on any headline figure. Most confusion about result age comes from treating accuracy and shelf life as one property.

Bottom line: A result is a live answer given at one time, so its accuracy has a clock attached.

Why do verification results go stale?

Results go stale for four reasons, and each affects a different part of a list.

  1. People leave. Employees change jobs, and consumers close accounts or move to new providers. For B2B lists, job turnover is usually the largest driver.
  2. Domains change. A company switches email providers, rebrands, or lets its domain lapse. A lapsed domain can be re-registered by someone else, and old addresses on it can start accepting mail, sometimes as spam traps.
  3. Providers change behaviour. A server can start accepting every address, begin rate-limiting probes, or tighten its policies. The mailbox has not changed, but the answer has.
  4. Your list changes. Recycled consumer addresses, newly imported contacts and old records from a previous platform all carry different risk levels.

The most useful practical point is that the age of a result matters more than the age of the list. A contact added yesterday through a validated sign-up form may need no re-check for months. A contact imported two years ago and verified last spring may already be stale. Teams that store one last-verified date for an entire file either re-check fresh records unnecessarily or trust old ones.

Bottom line: Decay comes from people, domains, providers and the list's own history, and you need to track it per contact.

How fast do different kinds of lists decay?

No public standard measures decay precisely. We could not find an independently verified decay rate for B2B or consumer lists that we would cite as reliable, so the table below gives recommended maximum ages before re-verification instead. The next section shows how to measure your own rate, which is more useful than any published average.

List type Main decay driver Recommended max age before re-verifying Why
B2B prospect or CRM list Job changes, domain and email-provider switches 90 days Job titles and employers change, and a company switching providers changes its MX records, so a Valid domain check can stop holding
Trade-show, event or scraped list Unconfirmed sign-ups, mistyped and shared addresses Verify before first send, re-check at 30 days Quality problems exist from the start, and decay compounds them
Ecommerce customer list Account closures, provider switches 6 months Customers keep addresses for years, but churn is steady
Engaged consumer newsletter Gradual mailbox abandonment 6 months Recent opens and clicks are evidence the mailbox is live
Dormant list (no engagement for 12+ months) Abandoned mailboxes, recycled addresses Re-verify immediately before any send Highest decay and spam-trap exposure

Teams working on email verification for ecommerce and SaaS usually find that B2B and dormant segments need the shortest cycles, while active customer lists can run on longer ones. Our independent verifier benchmark covers how verifiers compare on accuracy, which is a separate question from how fast a list ages.

Bottom line: Use 90 days as the default maximum for B2B lists and 30 days for event or dormant segments before any send.

How can you measure your own decay rate?

Compare two verification runs on the same addresses. The change in the Valid count, divided by the months between runs, gives you a decay rate for your own list. That number is more reliable than any industry average, because it reflects your sources, region and sending history.

Use this formula:

Monthly decay ≈ 1 − (Still Valid ÷ Previously Valid)^(1 ÷ months between runs)

Example (illustrative numbers): In January you verify a segment and get 10,400 Valid addresses. In April you re-verify those same 10,400 addresses, and 10,050 are still Valid. The loss is 350 addresses, or 3.4% over three months. Converting to a monthly rate gives 1 − (10,050 ÷ 10,400)^(1/3) ≈ 1.1% per month.

Three caveats apply:

Once you have a rate, plug it into your re-check interval. A 1.1% monthly rate means a segment will still be mostly Valid after 90 days, but dormant segments often decay much faster and should not be assumed to match.

Bottom line: Two runs on the same fixed sample give you a decay rate you can defend, and it beats any published average.

Do Valid, Invalid and Risky results expire at the same rate?

No. Each bucket ages differently, and that changes how you should handle it.

If your list has many catch-all addresses, the catch-all email verification page explains how those results are flagged. For a common source of catch-all results, see verifier accuracy on Microsoft 365 addresses.

Bottom line: Valid results go stale, Invalid results should stay suppressed, and Risky results need re-checking before every send.

Why does result age matter for compliance and deliverability?

Result age matters for both deliverability and compliance. Under the GDPR, Article 5 requires personal data to be "accurate and, where necessary, kept up to date." The UK GDPR carries the same principle. A list you never re-check is hard to defend under that rule, because you cannot show the data is current. The ICO, the UK regulator, publishes guidance on this accuracy principle, and it is worth reading if your list includes UK contacts. Teams building a email verification compliance and hygiene process can use the age of each result as one of their audit fields.

For deliverability, the risk is practical. Google's sender guidelines set spam-rate expectations that bulk senders must stay well inside. Stale lists generate complaints from people who no longer recognise the sender, and dead addresses that become spam traps add a second risk.

Bottom line: An outdated list fails both the inbox test and the accuracy test, so freshness is a compliance task as well as a deliverability one.

How do you check whether a result is still fresh?

Before every send to a segment, check four things together: age, source, engagement and purpose. Any one of them alone can mislead you. A recent verification of a dormant import is not the same as a recent verification of an engaged customer.

  1. When was each contact last verified? Read the last-verified field. If there is no field, treat the contact as unverified.
  2. How did it enter your system? A validated sign-up, an import, a purchase and an event each carry a different baseline risk.
  3. When did it last engage? An open, click, reply or purchase is evidence the mailbox is active.
  4. What is it about to receive? A newsletter, a transactional message and a cold outreach email tolerate different levels of risk.

Then apply this rule:

Bottom line: Check age, source, engagement and purpose together, and treat any missing date as unverified.

How do you re-verify an aging list, step by step?

This tutorial walks through a re-verification run with Unlimited Verifier. It assumes you have no existing workflow.

  1. Export your contacts as a CSV. Include the email column and the fields that show age and engagement, such as signup date, last open and last-verified date if you have one.
  2. Sort the file by last-verified date. Put anything older than 90 days, plus dormant and imported contacts, into their own file. This shows how much actually needs re-checking.
  3. Create an account if you don't have one. The Free plan allows 25 lists a month of up to 150 emails each. The arithmetic is 25 × 150 = 3,750 emails a month at most. A 40,000-contact list would need 267 Free files, so this is a Pro-sized job.
  4. Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. On Pro, each list can hold up to 25,000 emails, so split larger files first.
  5. Read the three buckets. Valid goes to your next send, Invalid goes to suppression, and Risky is held back. Catch-all addresses are flagged so you can handle them separately.
  6. Export the results as CSV, Excel or JSON. Save the bucket and the verification date in your own system, because platform retention is limited.
  7. Update your CRM. Write the new bucket and a fresh last-verified date to each contact. Re-import only Valid contacts into your sending segment, and move Invalid ones to suppression.
  8. Spot-check edge cases. If a high-value contact returns Risky, use the free email checker to test that single address before deciding what to do with it.

Bottom line: Export, split to fit your plan, verify, write the bucket and date back to each record, then send only what is fresh.

What does six months of silence cost a 40,000-contact list?

This example is illustrative. The 2% monthly decay rate is an assumption, not a measured figure, and the arithmetic is what matters. Replace the 2% with the rate you measure using the method above.

Setup: A SaaS company has 40,000 contacts marked Valid on 1 January. It does not re-verify and assumes the list is still good. Assume 2% of the remaining Valid addresses lose their mailboxes each month.

Decay over time:

Bounce impact: If the whole list is mailed after six months, roughly 4,566 messages would bounce, an 11.4% bounce rate. That is far above the 2% total-bounce ceiling many teams work to. The model assumes every decayed address bounces. Some decayed addresses become catch-alls that accept mail silently, which can hide spam-trap exposure instead of showing up as bounces. Our guide to typical bounce rates after cleaning covers what to expect in practice.

Cost of re-verifying on Pro:

Compared with roughly 4,566 bounces, a one-month re-check at this cost is a small expense. If your measured decay rate is 1.1% a month instead, six months leaves about 6.6% decayed, which is still enough to justify a re-check before any large send.

Bottom line: At an illustrative 2% monthly decay, a list checked once and then left alone for six months is more than a tenth dead.

Should you re-verify on a schedule or at the point of sending?

Most teams combine two methods, because each covers a gap the other leaves.

Approach Freshness Effort Best for Trade-off
One-off bulk check before a campaign Snapshot at send time Low Small, infrequent sends Ages quickly if the campaign is delayed
Scheduled bulk re-verification (monthly or quarterly) Bounded by your cadence Medium (export, verify, re-import) Most B2B and ecommerce lists You must keep your own log of results
Real-time check at sign-up via API Fresh at entry Medium to high (development time) Sites with heavy sign-up traffic Does not refresh existing records
Pre-send check on the segment about to be mailed Freshest for that send Medium Dormant segments and high-stakes sends Adds time to every send

A calendar-only schedule has a blind spot. A segment re-verified on day 1 of a quarter can be 80 days old when a campaign goes out on day 80, so the freshest approach for rarely mailed segments is to verify on the send date.

The email verification API and automation route suits real-time checks at entry. Unlimited Verifier's REST API supports single-email checks and bulk batches of up to 10,000 emails per request, and Pro includes API access at 100,000 emails a month. API keys are managed on the email verification API page. Our guide to real-time validation at sign-up explains how to add checks to a form without slowing it down.

Bottom line: Validate at entry, re-verify on a schedule, and check dormant segments right before you send to them.

Does a results retention window affect how long results stay accurate?

No. Retention and accuracy are separate properties. Unlimited Verifier keeps results for 24 hours on Free and 30 days on Pro. That tells you how long results sit in your account, not how long they stay true. Retention windows also differ across email verification tools, so check them before you commit to a workflow.

The practical consequence: a 90-day re-verification cycle on Pro means the results from the first run are gone from the platform long before the next one. Unless you export and store the buckets and dates yourself, you have no record of what you verified or when. Store every export in your CRM or data warehouse with a last-verified date on every row. Our guide to list maintenance practices covers how to build that record into a regular routine.

Bottom line: Retention is storage, not shelf life, so keep your own dated record of every result.

What are the most common mistakes that make old results dangerous?

Bottom line: Most stale-list problems come from keeping results without dates, sending without re-checking, or treating snapshots as permanent.

How we compared (and limitations)

This article is based on public documentation and general industry practice. It is not based on a controlled re-verification test against any provider or list. Specifically:

For the broader accuracy picture, read our email verifier accuracy guide. To understand why different tools return different answers on the same list, see why different email verifiers give different results. For a checklist when comparing tools, read how to choose an email verifier.

Bottom line: Treat the numbers here as planning tools, and set your own cadence by measuring bounces and decay after each re-check.

Illustrative decay model

Illustrative model: a 40,000-contact list left unchecked for six months reaches an 11.4% decay rate. Step 1: Record the last-verified date per contact. Step 2: Flag Valid results older than 90 days. Step 3: Re-verify dormant contacts at 30 days. Step 4: Remove or segment addresses that fail on re-check before sending.

Frequently asked questions

Do email verification results expire?

Email verification results do not expire on a fixed date, but their reliability declines over time. Most teams plan on re-checking results within 30 to 90 days, because people change jobs, domains change, and mailboxes close. Older results should be re-verified before you send to them.

How often should I re-verify my email list?

Re-verify most lists every 30 to 90 days, and sooner for dormant or event-sourced contacts. Re-check any Valid result older than 90 days before a campaign. Lists that have not been mailed in months should be checked again before their first send.

Why do valid email addresses become invalid?

Valid addresses become invalid when mailboxes are closed, employees leave companies, or domains lapse or change email providers. Consumers also close accounts or switch providers. Any of these can turn a previously accepted address into a hard bounce.

Is a catch-all result still useful after 90 days?

A catch-all result confirms the domain accepts mail but not that a specific mailbox exists, so its age matters less than the domain's behaviour. Treat catch-all addresses separately and rely on engagement data or re-checks before high-stakes sends.

Can a verification result be wrong when it is first returned?

Yes. Verifiers check a live mail server, and servers can greylist, rate-limit, or accept every address. Some results are therefore uncertain at the moment they are returned, which is why unknown or catch-all results need careful handling.

Should I re-verify addresses before every campaign?

Re-verify before any campaign if the last check is older than your planning window, or if the list has been dormant. For routine sends to recently engaged contacts, a recent verification plus engagement data is usually sufficient.

How do I track when each email was last verified?

Store a last-verified date on every contact record rather than one date for the whole file. Export results to your CRM or database with the timestamp, so you can filter out stale records before each send.

What bounce rate signals a stale list?

Bounce rates rising above your normal baseline often indicate a stale list. Many senders aim to keep hard bounces low, and a sustained rise after a long gap without re-verification is a common warning sign to re-check the list.

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.