How to Verify an Email List Before Cold Outreach
Before you start an outreach campaign, check the email addresses you plan to use. An email verification tool can identify invalid addresses and flag other categories that need review, including disposable emails, shared inboxes, catch-all domains, and inconclusive results.
A useful verification workflow goes beyond running a check. You also need to interpret the results, connect them to the right contact records, and keep your campaign rules intact.
The Email Verifier & Deliverability Checker on Apify provides a Console interface and an API for this process. You submit addresses and receive verification statuses, scores, and individual flags.
Start with the list you actually intend to contact
Prepare the email addresses for the specific campaign. Keep a copy of the original contact records, including the identifiers you will need when updating a spreadsheet or CRM.
The Actor accepts an email list, rather than a whole contact database. If your source is a spreadsheet, extract the email column first. If another tool collected the contacts, pass the resulting addresses into the verifier.
Prepare spelling and formatting before submission. The Actor forwards the supplied strings without a separate trimming, deduplication, or typo-correction step.
Submit a small batch first
Open the Actor, paste a small selection of addresses, review the applicable pricing, and start the run. This gives you an opportunity to understand the output before processing the rest of the list.
The input accepts up to 1,000 entries per run. Larger lists should be split into separate runs. Account rules and spending limits can affect how much of a batch is processed, so keep a record of each run and the addresses submitted.
If you already use Apify, the cold outreach example task is a convenient starting point. Replace the demonstration addresses with your campaign list.
Read the verification status before choosing contacts
The main result category is in the status field. Other fields provide context, including the overall score, syntax result, disposable flag, role-account flag, and deliverability signals.
A practical review separates the results into three working groups:
| Working group | Examples | What to do next |
|---|---|---|
| Candidates for your normal selection rules | safe |
Apply your existing campaign and contact requirements |
| Results needing separate review |
catch_all, unknown, role_account, inbox_full
|
Decide whether to hold, recheck, or handle them separately |
| Results generally unsuitable for the active outreach list |
invalid, disabled, spamtrap
|
Exclude them until there is a justified correction or reassessment |
Disposable addresses should be handled according to the purpose of your list. Their temporary nature may make them unsuitable for a lasting business relationship, even if they can receive a message at the time of checking.
A role account may belong to a legitimate shared inbox. A catch-all result describes domain behavior and does not confirm a particular person's mailbox. Avoid turning these distinct results into a single "valid" category.
Use the score as supporting information
The Actor returns overall_score on a scale from 0 to 100. Use it alongside the status and flags.
Do not interpret a score of 90 as a 90% probability of inbox placement. A missing score can also fall back to zero. Your selection rule needs to consider the available evidence rather than a score alone.
Some flags can contain an inconclusive value such as "None". If you use an automated filter, make sure that it understands those values instead of treating every nonempty string as true.
Export and join the results carefully
Export CSV or Excel for manual review, or retrieve JSON through the API. Apify datasets support these export formats.
Keep the verification fields alongside the correct contact record when updating your source system. Do not join rows only by their position: the response may contain fewer rows than the submitted list, and its ordering should not be assumed to match your original contact table.
Preserve unsubscribes and existing suppression rules when preparing the final campaign audience. A technical verification result does not tell you whether someone has asked to stop receiving messages.
Check whether the batch completed
Before calling a list "verified," review the run's status, saved results, and summary. A spending limit or interruption can leave a partial result set.
Avoid immediately submitting the full list again when you see fewer results. First determine what was saved and which contacts still need attention. A new run can create new charges.
Keep verification close to the decision
An email assessment reflects the time it was performed. Addresses and mailbox conditions can change, particularly when you are working with an older contact list.
When the list has been sitting for a while, reassess the contacts you actually plan to use. Choose the timing based on how quickly your data changes and how soon the campaign will run.
Address verification can help you identify avoidable address problems. Sending quality still depends on the wider campaign, including your relationship with recipients and how the sending system is operated.
Top comments (0)