Article

How to Fix an Email List Where 30% of Addresses Are Invalid

By Unlimited Verifier Team ·

Flow diagram showing a mailing list with 30 percent invalid addresses being paused, diagnosed by import batch, then split into suppress, hold and send groups du

Summary

If 30% of your email list is invalid, stop mailing the full list, suppress the invalid addresses, hold risky ones, and send only to verified contacts. A share this high usually signals a faulty collection or import process rather than normal decay, so diagnose the cause before deleting anything.

The fastest fix for a list where 30% of addresses are invalid is to stop mailing the whole list, suppress the invalid addresses, hold back the risky ones, and send only to verified contacts until you know why the list broke. A 30% rate usually points to a faulty collection or import process rather than normal decay, so the order of your fixes matters.

This page covers the full recovery path, from diagnosis to re-entry, and sits within our wider bulk email list verification workflow.

Quick answer

Why is a 30% invalid rate a different problem from a few bad addresses?

A 30% invalid rate means the list failed at collection or import, not that it simply aged. Ordinary decay, such as job changes and closed mailboxes, raises the invalid share gradually. A share of 30% in one list almost always traces back to an intake process that let bad data in.

The arithmetic explains why you must act first. A hard bounce is a permanent delivery failure. The classic example is SMTP enhanced status code 5.1.1, meaning the destination mailbox does not exist, as defined in RFC 3463. Every invalid address you mail is likely to produce one.

Invalid share Hard bounces per 10,000 sends (if unfiltered) Compared with Amazon SES's published levels
3% 300 Under the 5% review level
10% 1,000 Twice the 5% review level, at the 10% pause level
30% 3,000 Six times the 5% review level and three times the 10% pause level

Sources disagree on where the line sits. Amazon SES's documentation describes 5% as the point where accounts are reviewed and 10% as a level where sending may be paused. Google's sender guidelines ask bulk senders to keep spam reports below 0.1% and never let them reach 0.3%. Bounces and complaints are tracked separately, and a list that never opted in tends to produce both. We recommend one number: a total bounce ceiling of 2%, with under 1% for your first re-entry sends. That leaves headroom before any platform's automated trigger.

Bottom line: A 30% invalid share breaches typical bounce thresholds on the first full send. Stop sending before you start cleaning.

What causes a 30% invalid rate?

Most cases fall into one of five patterns, and each leaves a recognisable signature in the data. Identify the pattern first, because it decides whether you need a one-off cleanup or an intake fix.

Pattern What the invalid addresses look like Likely cause Check first
Import or mapping error Invalid results cluster in one batch; some entries contain names, spaces or stray commas A column shifted during a CRM migration, or a delimiter mismatch Sort by import date and source column
Typo domains Concentrated on near-misses such as gmial.com or yaho.com Sign-up forms that accept any text without a syntax or domain check Top 20 domains by invalid count
Bought or rented lists Many role accounts, dead corporate domains, mixed countries Third-party data with no opt-in history Source field or list name
Bot or fake sign-ups Disposable domains, placeholders like test@test.com, sudden spikes An unprotected form, or automated traffic Sign-up timestamps and domains
Natural decay Spread evenly across join dates, mostly corporate domains Job changes and closed mailboxes in old B2B lists Invalid rate by join year

Ask the people who run your forms and imports what changed in the last six months. The cause is usually a change someone made, such as a new form field, a migration or a purchased file, rather than a slow leak. In many lists, one bad batch explains a large share of the invalid addresses while the rest of the database is healthy. That is good news, because you can fix one batch without discarding everything.

Bottom line: Find the pattern before you delete anything. A spike in one batch means a process fault. A smooth curve means a maintenance problem.

What should you do with each invalid, risky and valid address?

Each category needs a specific action, and the choice affects deliverability and your compliance position. Here is how to handle each one.

Action Apply to Why Main risk if misapplied
Suppress permanently Invalid results Stops the address being mailed again, including after a re-import Deleting the record without keeping a suppression entry lets the address return on the next import
Hold back Risky results (catch-all, disposable, role accounts) Their mailbox can't be confirmed, so they stay out of early sends Treating them as Valid inflates your deliverable count
Correct obvious typos Clear domain typos such as gmial.com Recovers real people who mistyped A corrected address is still unverified and still lacks consent
Re-permission Valid addresses with long-term inactivity, or an unclear source Asks the person to reconfirm they want the mail Mailing them without confirmation risks complaints

Two points deserve more attention than a table allows. First, a typo correction is a guess. Fix the domain, re-verify the corrected address, and send a confirmation email before adding it to a campaign. Second, deleting contact records without keeping a suppression list is the most common way bad addresses return. When someone re-imports an old file, the suppression list is what stops them coming back.

For more on each category after the results arrive, see what to do with invalid emails after list cleaning.

Bottom line: Suppress Invalid, hold Risky, correct typos only with confirmation, and re-permission anyone whose consent you cannot show.

Can you trust the Invalid results before suppressing 30,000 contacts?

Usually yes, but check before you suppress at scale. Two quick checks catch most false alarms. First, see whether Invalid results concentrate on a single domain. Some mail servers throttle or reject repeated verification probes, so one corporate domain returning a large block of Invalid results may reflect that server's behaviour rather than dead mailboxes. Spot-check 20 to 50 of those addresses with the free email checker before you act on the whole group.

Second, look for obvious patterns that confirm a broken batch, such as placeholder strings, names in the email field or addresses with spaces. If a spot check contradicts the verdict, hold that domain back rather than suppressing it. This is a judgement call, but a few minutes of sampling is cheap insurance against suppressing a legitimate customer base.

Bottom line: Sample before you suppress at scale. A domain-level block can look like a list failure.

Why do catch-all addresses need special handling?

A catch-all domain accepts mail for any address, so a positive result from it doesn't confirm that the specific mailbox exists. On a list that is 30% invalid, catch-all addresses matter more because counting them as Valid overstates your deliverable count and hides risk. Unlimited Verifier detects catch-all domains, so you can see which results they affect. Treat any catch-all result as unconfirmed until engagement data or a small test send supports it. The catch-all email verification page explains how these results are handled.

Bottom line: A catch-all result is unconfirmed, not Valid, until engagement or a test send says otherwise.

What should you do in the next seven days?

Follow these steps in order, because each one depends on the data from the step before.

  1. Day 0: Freeze sending. Pause every campaign, automation and welcome series that pulls from the affected list. Each extra bounce makes recovery harder.
  2. Day 1: Pull failure data by source. Use your ESP's bounce report and your CRM's import history to group failures by batch, source and date.
  3. Day 1: Export and trim. Export the full list as CSV. Keep the email column and two or three segmentation fields, such as last engagement date.
  4. Day 2: Verify everything. Run the whole list, not just the addresses that bounced. An address that didn't bounce last time can still be dead.
  5. Day 2: Triage. Separate Valid, Risky and Invalid. Correct only obvious typos, and queue those for a confirmation email.
  6. Day 3: Suppress and document. Add Invalid addresses to your suppression list. Record the count for each bucket, the batch that caused the spike, and the date.
  7. Days 4–7: Send a first small batch. Send only to Valid contacts with recent engagement. Then ramp volume over one to three weeks, keeping bounces under 1%.
  8. Ongoing: Fix the intake. Add validation at the point of entry and verify every import before it reaches your ESP.

For the general version of this process, see our step-by-step guide to cleaning a bulk email list.

Bottom line: Freeze, diagnose, verify the whole list, suppress, then re-engage in small steps. Fixing intake is what stops the problem recurring.

How do you verify a 30%-invalid list in Unlimited Verifier?

This walkthrough takes a beginner from export to re-import. You need your list export and an account.

  1. Export your contacts as a CSV. Include the email column and up to three segmentation fields. Keep the original export untouched. If your file uses semicolons, which is common in some European spreadsheet settings, convert it to commas first. A mismatched delimiter can merge columns. The file formats guide lists what is accepted.
  2. Create an account. Sign up for the Free plan to test with a small batch. Free covers 25 lists a month of up to 150 emails each, which is 3,750 emails at most. A full list needs Pro.
  3. Work out how many files you need. Divide your row count by the per-list limit. On Pro, each list can hold up to 25,000 emails, so 100,000 rows need four files. Split the file in a spreadsheet or with a short script. Our guide to splitting a large CSV shows the method.
  4. Check the file size. Uploads accept CSV and Excel files up to 10MB. At 25,000 rows, 10MB works out to about 400 bytes per row, so drop columns you don't need before uploading.
  5. Upload the file. Go to Upload and verify a list. The email column is detected automatically, but confirm it matched the right column before you run the check. The upload walkthrough shows each screen.
  6. Run the verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged.
  7. Read the three buckets. Valid addresses are the best candidates for re-engagement. Invalid addresses go to suppression. Risky addresses stay out of the first sends. The results file guide explains each column.
  8. Export the results immediately. Results can be exported as CSV, Excel or JSON. Free keeps results for 24 hours and Pro for 30 days, so download the file the same day regardless of plan.
  9. Pivot the Invalid rows. Group them by your source column and by join date. This tells you whether the problem is one batch or the whole list.
  10. Re-import only Valid contacts. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so the re-import is manual. Upload a new segment to your ESP and add the Invalid addresses to its suppression list. See the re-import guide and the CRM merge guide.

Bottom line: Export, split, upload, verify, read the buckets, save the results the same day, and re-import only Valid contacts.

Worked example: 100,000 contacts, 30% invalid

The verification counts below are illustrative, but the per-list limits, quotas and plan prices are the real plan facts.

The situation: A B2B company has a 100,000-row list built from a trade-show scan and a legacy CRM import. The verification run returns:

Check: 64,000 + 6,000 + 30,000 = 100,000.

Step 1: Split for the Pro cap. 100,000 ÷ 25,000 = 4 lists. Four uploads cover the file.

Step 2: Confirm Free won't do it. Free allows 25 lists of 150 emails, or 3,750 emails a month. 100,000 ÷ 3,750 ≈ 26.7 months of Free allowance, so Pro is the practical choice.

Step 3: Plan the deep checks. Pro includes 25,000 deep verifications a month. Spend 6,000 on the Risky group, the hardest decisions, which leaves 25,000 − 6,000 = 19,000 for spot-checks of Invalid results you want to confirm. Standard verification of the full list is unlimited, so it doesn't draw on that quota.

Step 4: Project the bounce rate.

Step 5: Compare the cost. Assume an illustrative ESP rate of $1.00 per 1,000 emails. Sending to all 100,000 costs $100 per send, and sending to 64,000 costs $64. The saving is $36 per send, or $360 over ten sends. A single Pro month costs $29 ($25 a month billed annually), so on these assumptions the verification pays for itself on the first campaign. ESP pricing varies widely, so substitute your own rate. For how verification pricing is structured across vendors, see email verification pricing.

Step 6: Plan re-engagement. Send to the 64,000 Valid contacts in order of recent engagement, starting with those who opened in the last 30 days. Hold the Risky group until the main list shows stable results.

Bottom line: Four Pro uploads, 6,000 deep checks and a Valid-only send bring a projected 30% bounce rate down to about 1%.

Can you verify this list through an API instead of a CSV?

Yes, and the API suits lists that keep changing. The email verification API and automation approach checks addresses as they arrive, rather than in a one-off batch. Unlimited Verifier's REST API uses API keys, supports single-email checks, and accepts bulk batches of up to 10,000 emails per request. Pro includes API access with 100,000 emails a month. Free has no API access.

For the 100,000-row example, 100,000 ÷ 10,000 = 10 batch requests, which uses the full monthly API allowance in one pass. You can create keys on the Email verification API page. For a one-off cleanup, the CSV route is simpler. Use the API when the list is continuously fed.

Bottom line: Use the CSV route for a one-off cleanup and the API for continuously fed lists.

How do you stop a 30% problem from coming back?

Prevention costs far less than cleanup, and it is where most teams underinvest. Three controls cover most of the risk.

Verification supports compliance but does not replace consent. A valid address is not an opted-in address. The FTC's CAN-SPAM compliance guide sets the US rules on opt-out and sender identification. If you mail UK or EU contacts, the Information Commissioner's Office at ico.org.uk covers the rules on electronic marketing. Our overview of email verification compliance and hygiene explains where verification fits.

Bottom line: Validate at entry, verify every import, and re-verify on a schedule. Verification tells you an address is deliverable, not that the person agreed to hear from you.

Common mistakes that make a 30% problem worse

Bottom line: Most of these mistakes come from acting before you understand the list. Diagnose, suppress and verify first, then send.

How we compared (and limitations)

This article is based on public documentation: Amazon SES's published bounce guidance, Google's sender guidelines, RFC 3463, and FTC and ICO guidance on electronic marketing. We have not run controlled tests against any ESP's review process, and thresholds vary by platform and change over time.

The 99.5% accuracy figure for deep verification is Unlimited Verifier's own stated figure, not an independent benchmark. The worked-example counts, the 1% assumed bounce rate on Valid contacts and the $1.00 per 1,000 ESP rate are illustrative. Use your own bounce data and pricing for real decisions.

If you're comparing vendors for a list this size, use our buyer's checklist for choosing an email verifier alongside our roundup of the best email verification tools, which covers how the options differ.

Bottom line: Treat the figures here as a framework and substitute your own numbers before you act.

Four-step recovery framework

Step Action Outcome
1. Freeze Stop sends to the full list Prevents a bounce spike
2. Diagnose Group invalid results by batch, source and domain Identifies a faulty import or natural decay
3. Segment Suppress Invalid, hold Risky, send to Valid Protects reputation during recovery
4. Re-enter Re-permission contacts without provable consent, then resume at low volume Restores sending under a 1% bounce target

Frequently asked questions

Is a 30% invalid email rate normal?

No. A 30% invalid rate usually means the list failed at collection or import rather than aging naturally. Normal decay, such as job changes and closed mailboxes, raises the invalid share gradually. A sudden high share in one list almost always traces back to an intake process that let bad data in.

How do I find out why my list has so many invalid addresses?

Group the invalid results by import batch, signup source, and email domain. If invalid addresses cluster in one batch or source, the cause is likely a faulty import or form. If they spread evenly across join dates, the list is more likely decaying naturally.

Should I delete all invalid addresses from my list?

Suppress them rather than deleting them outright, so they are never mailed again. Keep the records until you have confirmed the cause, because the data can help you trace the faulty import or form that produced them.

What is a hard bounce?

A hard bounce is a permanent delivery failure. A common example is SMTP enhanced status code 5.1.1, meaning the destination mailbox does not exist, as defined in RFC 3463. Every invalid address you mail is likely to produce a hard bounce.

What bounce rate is safe for email campaigns?

This guide recommends a total bounce ceiling of 2%, with under 1% for your first re-entry sends. Platforms like Amazon SES describe 5% as a review level and 10% as a level where sending may be paused, so keeping well below those lines leaves headroom.

Should I email risky addresses after cleaning my list?

Hold them. Risky addresses may be valid or may bounce, so sending to them can raise your bounce rate. Re-verify them, or leave them out of campaigns until they resolve to Valid or are suppressed.

How do I re-permission contacts after a list cleanup?

Send only to Valid contacts whose consent you can show. For any Valid contact without provable consent, ask them to confirm they want to receive email before adding them back to regular campaigns.

How often should I verify my email list?

Verify before major sends, after large imports, and on a regular schedule for older lists. Verification catches invalid addresses before they generate bounces, which protects sender reputation with mailbox providers.

How do I stop a bad import from happening again?

Validate addresses at the point of entry, check imported files for formatting and domain errors before loading them, and tag each import batch so future invalid spikes are easy to trace. Fixing the intake process prevents the problem from recurring.

Can I verify a full list without paying per email?

Yes, according to the Unlimited Verifier plans described in this guide. Standard verification is unlimited on every plan, including Free, with no per-email fees. Free plan results are kept for 24 hours, so export them the same day.

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.