CRM
Clean imports before creating contacts and automations.
Bulk verify emails before CRM import or outreach
Classify addresses as good, risky or bad and detect disposable domains, role accounts and catch-all behavior to reduce bounces and isolate records needing review.
The first button is an affiliate link. We may receive a commission if you purchase an eligible plan, at no extra cost to you.
Direct answer
How do you clean an email list before a campaign?
Submit a list and use status, score and technical reasons to separate valid, risky and invalid addresses. Export the result and retain the reason behind each decision instead of deleting records blindly.
A positive verification does not guarantee delivery or permission to contact. Apply consent, legitimate-interest and anti-spam rules for your jurisdiction.
- Actor
michael.g/email-verifier-validator- Published pricing
- from $0.60 per 1,000 results
- Total Users
- 1,5K
- Check
- August 20, 2026
Actor used
Email Verifier Validator
Built by Michael G. It was selected for adoption, practical utility and a use case not previously covered by FlujoDato.
Check the official listing5.0 / 511 reviews
1,5Ktotal users
435monthly users
55bookmarks
Public listing signals checked August 20, 2026; they can change.
Copy-ready setup
Validate a three-email sample
{
"emails": [
"ventas@empresa.com",
"contacto@proveedor.com",
"hola@gmail.com"
]
}- 01
Deduplicate first
Do not pay twice for the same normalized address.
- 02
Validate a sample
Check how corporate, free and catch-all domains behave.
- 03
Separate risk from invalidity
Do not automatically delete everything that is not
good. - 04
Retain the reason
Store score and technical code for audit.
Output and controls
Fields you should review
| Field | Use | Check |
|---|---|---|
status | Classify good, risky or bad | Define policy by segment |
score | Sort by confidence | Do not treat as contact permission |
technical_status | Understand the check | Can change with the server |
disposable / role | Detect special accounts | Review before exclusion |
catch_all | Flag ambiguous domains | Does not confirm an individual inbox |
Cost
Pay per verified email
The listing showed pricing from $0.60 per 1,000 results. Deduplication and a sample run prevent spending on repeated records or a poorly defined policy.
| Component | Published pricing | Check |
|---|---|---|
| michael.g/email-verifier-validator | from $0.60 per 1,000 results | Confirm current Apify pricing before running at volume. |
| Recommended pilot | Minimum input | Review quality before scaling |
Added value
Problems it helps solve
Reputation
Reduce avoidable bounces and protect sending quality.
Prioritization
Separate valid, risky and review-required records.
FAQ
Before you automate
Will a good email always receive the message?
No. Mailboxes, filters and policies can change after verification.
Should I delete catch-all addresses?
Not automatically. Mark them uncertain and decide based on value, source and risk.
Does verification equal consent?
No. Technical validation does not replace a lawful basis for contact.
Lead quality
Validate a sample before cleaning everything
Define how to handle good, risky, bad and catch-all using 20 real records.