Article
How to Verify Only New Contacts Each Month: A Recurring Workflow
By Unlimited Verifier Team ·

Summary
To verify only new contacts each month, export contacts captured since your last run, remove addresses already in a master results ledger, verify the rest, and merge results back. Re-check Valid contacts every 90 days and never re-run Invalid ones unless the person re-subscribes.To verify only new contacts each month, export the contacts whose first-captured date falls since your last run, remove any address already in a master results ledger, verify what remains, and merge the results back, re-checking Valid contacts every 90 days. For a 90,000-contact database that adds about 6,800 contacts a month, the monthly new-only run covers roughly 7.6% of the list.
The method is simple, but the details decide whether it holds up. Monthly routines tend to break on three things: how you define "new," where you store results, and when you re-check contacts you have already cleared. The verification itself is rarely the problem. For the full pipeline, see the bulk email list verification workflow. This page covers the recurring, incremental version.
Quick answer
- Define "new" by an immutable first-captured date, not by last-modified date, which resets every time a contact is edited.
- Keep your own master ledger of every address and its result. Unlimited Verifier keeps results 30 days on Pro and 24 hours on Free, so it cannot serve as your storage.
- Verify new contacts every cycle, re-check Valid contacts every 90 days, and never re-run Invalid ones unless the person re-subscribes.
- Run routine batches on standard verification, which is unlimited on every plan, and reserve the 25,000 monthly deep verifications on Pro for imports and disputed addresses.
- Respect the list cap. Pro lists hold up to 25,000 emails each, so split larger batches before upload.
What does "verify only new contacts" actually mean?
It means every address in your database has a verification status with a date attached, and each cycle you send the verifier only the addresses that lack a current status. Those fall into three groups: new (never verified), current (verified within your re-check window), and due (verified, but past the window).
Your monthly job is to process new and due contacts and leave current ones alone. The catch is that "new" is a property of your records, not of the address. An address imported into a fresh ESP account this month may have been verified two years ago in your own ledger. The ledger, not the ESP's created date, is the source of truth.
Bottom line: A monthly run is new plus due, and the ledger tells you which is which.
Why not just verify the whole list every month?
You can, but it is rarely the right default. On a 90,000-contact list, a full monthly run means 90,000 checks each cycle. Standard verification is unlimited on every Unlimited Verifier plan, so per-email cost is not the main issue. The real problems are time, repeated confirmation of addresses that have not changed, and the fact that deep verifications draw from a 25,000-per-month quota on Pro.
The opposite mistake is worse. Verifying nothing after the first clean-up lets stale addresses accumulate. That matters most for SaaS and ecommerce teams, where email verification for ecommerce and SaaS problems usually come from aged B2B and checkout data. Google's sender guidelines say bulk senders should keep user-reported spam below 0.10% and never let it reach 0.30%. Dead or recycled addresses are a common route to complaints and spam-trap hits, so a periodic re-check is part of email verification compliance and hygiene, not an optional extra.
Bottom line: Full-list runs waste capacity, but never re-checking lets decay build up. Verify new contacts monthly and re-check the rest on a cycle.
How do you define "new" without missing or double-counting contacts?
Filter on a field that never changes. Store a first_captured_at timestamp when a contact enters your system, and build every monthly export from it. If you filter on last-modified instead, any edit (a name fix, a tag, a field update) pulls an old contact into the "new" batch. That costs verifications and blurs your monthly numbers.
Normalise before you compare
Trim whitespace and lowercase every address before matching it against the ledger. Do not collapse plus-addressing (name+tag@) or dot variants (n.ame@gmail.com). Gmail ignores dots, but many other providers do not, so merging them can match two different mailboxes. Accepting a little duplicate verification is cheaper than a false match.
Treat imports as their own source
A 5,000-row import added this month is "new" to your ESP, but many of its addresses may be years old. Tag each row with a source (signup_form, trade_show_import, crm_migration) and verify imports as their own batch. Imports usually produce most of your invalid addresses, so keep their failure rate visible rather than blending it into organic signups.
A changed address is a new contact
When someone replaces an old address, the new one has no history and should be verified immediately. Link it to the same person record, but give it its own ledger row.
Bottom line: Filter on an immutable capture date, normalise lightly, and track imports separately so their failure rate stays visible.
Which method finds your new contacts?
The ledger diff is the most dependable method, and the date filter is the simplest. Four approaches work, and they differ mainly in reliability and setup effort.
| Method | How it works | Main risk | Best fit |
|---|---|---|---|
| Export by first-captured date | Filter a CSV export from your ESP or CRM on the creation date | Old imports often lack a reliable created date | Teams whose capture dates are clean and consistent |
| ESP segment or tag | Saved segment such as "new this month," reset each cycle | Tags get reused or edited, so the segment drifts | Small lists already managed with tags |
| Ledger diff | Full export minus every key already in the ledger, with due contacts added back | Needs a ledger and a consistent key column | Large databases where accuracy matters most |
| API at capture | Verify each address as it arrives through the email verification API | Needs developer time; API access is a Pro feature | High-volume forms where bad addresses should never enter the system |
For most teams above 50,000 contacts, the ledger diff is the safest choice because it does not depend on the quality of your dates or tags. Use the date filter if you already trust your created-date field. Use the API if signup volume is high enough that a monthly batch feels too late.
Bottom line: Choose the ledger diff for accuracy, the date filter for simplicity, and the API when you want to remove the monthly batch entirely.
How do you build a master results ledger?
A ledger is one table with one row per normalised address. A spreadsheet works for small lists. A database table or a custom field set in your CRM works better above 50,000 rows.
Use these columns:
- email_key: the normalised address, used as the unique key.
- first_captured_at: when the address entered your system.
- last_verified_at: date of the most recent check.
- result: Valid, Risky or Invalid, as returned by the verifier.
- check_type: standard or deep.
- source: signup form, import or migration.
- next_check_due:
last_verified_atplus your re-check interval.
Save every results file the moment you export it. Results remain available for 24 hours on Free and 30 days on Pro, so waiting a week to merge can mean the file is gone. Your ledger is the only permanent record, and it doubles as an audit trail if a compliance team asks when an address was last verified.
Bottom line: The ledger is what makes a monthly routine repeatable. Without it, you are re-checking from memory.
How often should you re-verify contacts you have already checked?
Guidance varies. Some sources suggest monthly re-checks for high-churn B2B lists, while others suggest every six to twelve months. We recommend 90 days as the default window for Valid contacts. In our view, shorter windows cost more than the decay they catch, and longer windows let job changes and abandoned mailboxes pile up. Adjust the figure against your own bounce data, and see email list maintenance best practices for schedules by list type.
| Status | Re-check interval | Why |
|---|---|---|
| Valid | Every 90 days | Catches job changes and abandoned mailboxes before they bounce |
| Risky (catch-all, role, disposable) | Only when engagement changes, or quarterly at most | A catch-all domain's answer usually reflects its mail server's configuration, so it rarely changes between runs |
| Invalid | Never; suppress permanently | A dead mailbox stays dead unless the person re-subscribes |
| Re-subscribed or changed address | Verify immediately | A new event creates a new trust question |
The catch-all row deserves attention. Spending deep verifications on the same catch-all domain every month buys little, because the domain's accept-all behaviour is a server setting, not a per-address fact. The catch-all email verification page explains how these results are categorised. Keep those contacts in Risky, send to them only when engagement suggests they want the mail, and keep them out of your monthly deep budget.
Bottom line: Re-check Valid contacts every 90 days, leave Risky contacts alone unless engagement changes, and never re-verify Invalid ones.
What is the monthly routine, step by step?
Run the cycle the same way each month so your counts stay comparable. If you are starting from scratch, a step-by-step guide to cleaning a bulk email list covers the one-off clean-up that comes first.
- Record the window. Note this run's date and the previous run's date. Your export covers contacts first captured between them.
- Pull new organic contacts. Export everyone whose
first_captured_atfalls in the window, excluding imports. - Pull imports separately. Export the month's imports as their own file so their failure rate stays visible.
- Pull due contacts. Export Valid contacts where
next_check_dueis on or before today. - Normalise and deduplicate. Lowercase and trim each address, and drop any key already current in the ledger.
- Verify each batch. Run organic new contacts and due contacts on standard verification. Run imports on deep verification, within your monthly quota.
- Export and reconcile. Export results as CSV, Excel or JSON, and check that the row count matches what you submitted.
- Merge, push and log. Update the ledger, re-import Valid contacts into your ESP, suppress Invalid ones, and log the month's counts: submitted, Valid, Risky, Invalid and deep checks used. For the suppression step, see what to do with invalid emails after list cleaning.
Bottom line: A fixed eight-step routine turns verification into a repeatable process you can audit.
How do you run a monthly batch? A beginner's tutorial
This walkthrough covers one monthly batch. You need a CSV or Excel export from your ESP or CRM with an email column and a created-date column. If you do not have an account yet, you can sign up and test with a small export first.
- Export the month's new contacts. Filter on your first-captured date and export a CSV that includes the email column. Check the file formats email verifiers accept before uploading.
- Check the row count. On Pro, each list holds up to 25,000 emails. If the file is larger, split the CSV first. On Free, each list holds 150 emails, and you get 25 lists a month.
- Open the upload page. Upload and verify a list accepts CSV and Excel files up to 10MB and detects the email column automatically. The how to upload a CSV guide walks through the form.
- Separate by source. Keep organic new contacts and due Valid contacts in one file, and imports in another. Run imports on deep verification, as your plan allows, and run the rest on standard.
- Read the three buckets. Valid contacts are safe to send to. Invalid contacts are suppressed. Risky contacts, which include catch-all, disposable and role addresses, are held back. The results file guide explains each column.
- Download and save the file the same day. Results remain for 24 hours on Free and 30 days on Pro. Keep a copy in your own storage.
- Merge the results into your ledger, using the normalised address as the match key. The CRM merge guide covers this step in more detail.
- Re-import Valid contacts into your ESP as a segment, and suppress the Invalid list. Unlimited Verifier has no native ESP integrations, so this is a manual re-import or an API workflow. See how to re-import a cleaned list.
To spot-check a single disputed address, such as a VIP contact that came back Risky, use the free email checker rather than spending a batch on it.
Bottom line: One batch takes eight actions, and each one has an output you can check.
What does a 90,000-contact example look like on Pro?
The numbers below are hypothetical, but the plan limits and arithmetic are real.
Setup: The database holds 90,000 contacts. Each month it gains 5,000 addresses from signup forms and 1,800 from a trade-show import. Assume 81,000 contacts are currently Valid (90% of the database), with re-checks on a 90-day cycle.
Step 1: Compare Free and Pro capacity.
- On Free, 6,800 new contacts would need 46 lists of 150 (6,800 ÷ 150 = 45.3, rounded up). Free allows 25 lists a month, or 3,750 emails, so Free cannot cover this volume.
- On Pro, the same 6,800 fit in a handful of lists, none near the 25,000 cap.
Step 2: Verify the new contacts.
- Organic signups: 5,000 addresses on standard verification. Standard checks are unlimited, so they do not draw from the deep quota.
- Trade-show import: 1,800 addresses on deep verification. That uses 1,800 of 25,000 monthly deep verifications, leaving 23,200. Timing for batches like this is covered in how long it takes to verify 100k emails.
Step 3: Add the due re-checks.
- Under a 90-day cycle, about 81,000 ÷ 3 = 27,000 Valid contacts fall due each month on average.
- A single list cannot exceed 25,000 on Pro, so split the 27,000 into two lists of 13,500.
- Run both on standard verification. This does not reduce the 23,200 deep verifications left.
Step 4: Total the month.
- New-only mode: 5,000 + 1,800 = 6,800 checks, or 6,800 ÷ 90,000 = 7.6% of the database.
- Hybrid mode with re-checks: 6,800 + 27,000 = 33,800 checks, or 33,800 ÷ 90,000 = 37.6% of the database.
- Plan cost: one Pro month at $29, or $25 a month on annual billing, per the published plan facts. For how to compare costs across vendors, see email verification pricing.
The hybrid figure surprises many teams. "Verify only new contacts" sounds cheap, but a list that never re-checks its Valid contacts slowly fills with bad data. The 90-day cycle is what keeps the database honest, and standard verification keeps the extra volume affordable.
Step 5: Move signups to the API. If the 5,000 organic signups were verified at capture through the email verification API, the monthly batch shrinks to imports and re-checks. Pro includes 100,000 API emails a month, so 5,000 signups use 5% of that allowance (5,000 ÷ 100,000). Bulk requests accept up to 10,000 emails each, so the monthly import of 1,800 fits in one request. For the workflow, see real-time email validation and the email verification API and automation guide.
Bottom line: New-only mode costs 6,800 checks a month. Adding a 90-day re-check cycle raises it to 33,800, and standard verification keeps that extra volume inside the same $29 plan.
What mistakes do teams make with monthly verification?
These pitfalls recur in public guidance and in the failure modes that vendor documentation describes. Each one is avoidable with the steps above.
- Filtering on last-modified date. Every edit makes an old contact look new, which inflates monthly counts and wastes checks.
- Blending imports with organic signups. Imports usually carry the highest failure rates, and blending them hides that.
- Not saving the results file. Results last 24 hours on Free and 30 days on Pro, so an unsaved file is gone.
- Re-running Risky contacts every month. Catch-all results rarely change, so the spend buys little.
- Re-importing Invalid contacts after a fresh export, which undoes the suppression.
- Ignoring opt-outs. The FTC's CAN-SPAM compliance guide requires honouring opt-out requests within 10 business days, and your suppression list has to survive every re-import.
- Confusing verification with consent. A Valid address is deliverable, not necessarily opted in. Keep consent records separate.
- Uploading files over the list cap. Split large exports before upload rather than after a failed attempt.
Bottom line: Most errors come from an unstable definition of "new" or from results that were never saved.
How we compared (and limitations)
This article is based on public documentation: Unlimited Verifier's published plan facts, Google's sender guidelines, Yahoo's sender requirements, the SMTP specification in RFC 5321, and the FTC's CAN-SPAM guide. We have not run controlled tests against any ESP or verification vendor. If you are still choosing a verifier, compare options in our guide to the best email verification tools and the how to choose an email verifier checklist.
Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. The 90-day re-check window is our recommendation, not a published standard, and guidance on the right interval disagrees. The 90,000-contact example and its volumes are hypothetical, but the plan limits and arithmetic are real. Platform rules, plan limits and retention windows can change, so check current plan details before you build a routine around them.
Bottom line: The method is sound, but the intervals and volumes are a starting point to adjust against your own churn and bounce data.
Worked monthly volume example
| Item | Count |
|---|---|
| Total contacts | 90,000 |
| New contacts captured this month | 6,800 |
| Share of list verified in monthly run | about 7.6% |
| Due Valid re-checks (90-day window, illustrative) | depends on last run history |
| Invalid contacts re-run | 0 unless re-subscribed |
Frequently asked questions
What counts as a new contact for monthly verification?
A new contact is any address with a first-captured date after your last run that has no entry in your master results ledger. Use the immutable capture date, not last-modified date, because edits reset the latter and would cause unnecessary re-verification.
Why should I keep my own results ledger?
Your own ledger is the only reliable record of when each address was last verified. Unlimited Verifier keeps results for a limited period (30 days on Pro, 24 hours on Free), so it cannot serve as long-term storage for incremental runs.
How often should I re-check Valid contacts?
A 90-day re-check window is a practical default for most lists. It catches addresses that have gone dead or changed without forcing a full verification every month. Adjust based on your list's churn and bounce history.
Should Invalid addresses be verified again each month?
No, not by default. Invalid addresses should stay suppressed. Re-verify one only if the person re-subscribes or submits a new form, since that is a signal the address may have been corrected.
Which verification mode should I use for monthly runs?
Standard verification is suitable for routine batches and is unlimited on every plan. Reserve deep verifications, which have a monthly quota on Pro, for imports and disputed addresses.
What if my new-contact batch is larger than the upload limit?
Pro lists hold up to 25,000 emails each, so split larger batches into multiple lists before upload. Keep track of which chunk each address belongs to so results merge back correctly into your ledger.
How do I handle contacts who changed status between runs?
Write each new result to the ledger with a verification date and status. When a later run returns a different status, overwrite the older entry and suppress any address that has moved to Invalid or risky so it is not mailed.
Is monthly incremental verification enough to protect sender reputation?
It helps maintain list hygiene, but it works best alongside good sending practices, engagement-based suppression, and monitoring of complaint and bounce rates. Verification reduces risk but does not replace those controls.
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 standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
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.