Email Verifier — Bulk Validator: Domain, Disposable & Typos
Pricing
from $0.001 / email verified
Email Verifier — Bulk Validator: Domain, Disposable & Typos
Clean email lists in bulk without sending mail: syntax, mail-server (MX) check, disposable and role detection, free-provider flag, typo suggestions, status and score. Verify any scraper dataset. Checks addresses and domains, not individual mailboxes.
Pricing
from $0.001 / email verified
Rating
0.0
(0)
Developer
Hipersoft
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
3 days ago
Last modified
Categories
Features
Share
Email Verifier — Bulk Email Validator: Syntax, Domain, Disposable & Typos
Email Verifier cleans email lists in bulk without sending any mail. It checks syntax, whether the domain can receive mail (MX), disposable and temporary addresses, role inboxes, free providers and domain typos such as gmial.com, then gives each address a clear status and score.

What does Email Verifier do?
Paste a list of addresses, or point it at a dataset from a lead scraper, and get one row per address that tells you whether to keep it, check it or drop it. Duplicates are skipped so you don't pay for them twice.
What it does not do: it doesn't confirm that a specific mailbox exists. It checks the address and its domain. likely_valid means the address looks right and the domain accepts mail; a mailbox on that domain can still bounce. If you need a per-mailbox check, use a dedicated mailbox verification tool as a second step, and use this one first to remove obvious bad addresses for less.
What does each email check tell you?
| Check | Field | Catches |
|---|---|---|
| Syntax | syntaxOk | Malformed addresses |
| Mail server | mxFound, mxHost, mxRecords | Domains that can't receive mail |
| Disposable | disposable | Temporary inboxes such as mailinator and yopmail |
| Role inbox | role | Shared addresses such as info@ and support@ |
| Free provider | isFreeProvider | gmail.com, outlook.com and similar, useful for B2B lists |
| Typos | didYouMean | gmial.com, hotnail.com and similar |
| Plus addressing | isPlusAddressed | name+tag@ variants |
| Domain mail setup | hasSpf, hasDmarc | Domains with sender policies published, a sign of a maintained mail setup |
Use cases
- Clean lead lists before importing them into a CRM or outreach tool.
- Lower your bounce rate by removing dead domains and typos before a campaign.
- Filter sign-ups for disposable addresses.
- Separate B2B from free-mail addresses in a lead list.
- Pre-filter before paid mailbox checks so you only pay for addresses worth checking.
How to verify an email list
- Open Email Verifier.
- Paste addresses under Emails, one per line, or enter a dataset ID under Verify a dataset.
- Click Start.
- Filter by
statusand export to JSON, CSV or Excel.
Input
{"emails": ["name+tag@gmail.com", "john@gmial.com", "sales@mailinator.com"],"dedupe": true}
| Field | Description |
|---|---|
emails | Addresses to verify. |
inputDatasetId | Optional dataset to read addresses from, such as a lead scraper's output. |
emailField | The column in that dataset holding the address (default email). |
dedupe | Check each address once (default on). |
concurrency | Addresses checked in parallel, 1 to 30 (default 10). |
Output
One row per address. These rows come from a real run.
{"email": "name+tag@gmail.com","valid": true,"syntaxOk": true,"domain": "gmail.com","mxFound": true,"mxHost": "gmail-smtp-in.l.google.com","disposable": false,"role": false,"smtpChecked": false,"deliverable": null,"reason": "Valid syntax and domain has a mail server (MX present).","ok": true,"status": "likely_valid","score": 80,"normalizedEmail": "name+tag@gmail.com","isFreeProvider": true,"isPlusAddressed": true,"didYouMean": null,"mxRecords": ["gmail-smtp-in.l.google.com","alt1.gmail-smtp-in.l.google.com","alt2.gmail-smtp-in.l.google.com","alt3.gmail-smtp-in.l.google.com","alt4.gmail-smtp-in.l.google.com"],"hasSpf": true,"hasDmarc": true,"checkedAt": "2026-11-04T12:54:02.510Z"}
A typo with no working domain:
{"email": "john@gmial.com","valid": false,"syntaxOk": true,"domain": "gmial.com","mxFound": false,"mxHost": null,"disposable": false,"role": false,"smtpChecked": false,"deliverable": null,"reason": "Domain has no mail server. Did you mean john@gmail.com?","ok": true,"status": "invalid","score": 0,"normalizedEmail": "john@gmial.com","isFreeProvider": false,"isPlusAddressed": false,"didYouMean": "john@gmail.com","mxRecords": [],"hasSpf": null,"hasDmarc": null,"checkedAt": "2026-11-04T12:54:02.510Z"}
What the status means
status | Meaning | Suggested action |
|---|---|---|
likely_valid | Good syntax, and the domain accepts mail. Mailbox not confirmed. | Keep |
risky | Disposable domain or likely typo. | Review or drop |
invalid | Bad syntax or no mail server. | Drop |
unknown | The lookup timed out. | Re-run |
score runs from 0 to 100. Good addresses start at 70, gain points for published SPF and DMARC records, and lose 15 for role inboxes. Filter on status first; the score is only a rough ranking.
Output schema
| Field | Type | Description |
|---|---|---|
email | string | The address as you supplied it. |
normalizedEmail | string | Trimmed and lowercased. |
status | string | likely_valid, risky, invalid or unknown. |
score | integer | Rough 0 to 100 ranking. |
valid | boolean | Good syntax, mail server found, not disposable. |
syntaxOk | boolean | Passes the syntax check. |
domain | string | Domain part of the address. |
mxFound | boolean | Domain has a mail server. |
mxHost / mxRecords | string / array | Primary mail server, and all of them. |
disposable | boolean | Temporary-email domain. |
role | boolean | Shared inbox such as info@. |
isFreeProvider | boolean | Free mail provider. |
isPlusAddressed | boolean | Uses +tag. |
didYouMean | string | Suggested fix for a likely typo. |
hasSpf / hasDmarc | boolean | Domain publishes these records. |
smtpChecked / deliverable | boolean | Optional check result; usually false and null. |
reason | string | Plain-language explanation. |
ok | boolean | The check itself completed. |
checkedAt | string (ISO date) | When the address was checked. |
Need email data too?
- Website Contact Scraper: find emails and phone numbers on company websites, then verify them here.
- Google Maps Email Extractor: business emails from Google Maps.
FAQ
Does it send emails? No. It never sends anything.
Does it confirm a mailbox exists?
No. It checks the address and the domain. Treat likely_valid as "worth keeping", not as a delivery guarantee.
How much does it cost? You pay per address checked, shown on the Pricing tab. Duplicates are skipped. Set a maximum cost per run and it stops cleanly at that limit, storing only what you paid for.
Can I verify the results of another scraper? Yes. Put that run's dataset ID in Verify a dataset and set the email column.
How big can my list be? Large lists are fine. Addresses on the same domain share one lookup, so big lists stay fast.
Can I connect this to other tools? Yes, through integrations on the Apify platform: Make, Zapier, Slack, Airbyte, GitHub, Google Drive and many more, plus the Apify API and webhooks.
Is it legal? Only verify addresses you have a right to process, and follow privacy and anti-spam law.
Feedback
How did it go? Good or bad, a review helps other users decide and tells us what to improve. Something broken or missing? Open an issue and we'll look at it.
Related Actors
Notes
Independent tool. Addresses are processed only to produce your results.