Email Checker: Syntax, MX, Disposable and Typos (No SMTP)
Pricing
$0.50 / 1,000 e-mails
Email Checker: Syntax, MX, Disposable and Typos (No SMTP)
Check e-mail addresses without probing mailboxes. Validates syntax, looks up MX records, flags disposable domains and role addresses, and suggests typo fixes. Every address is returned.
Pricing
$0.50 / 1,000 e-mails
Rating
0.0
(0)
Developer
Open Data Desk
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Features
Share
Check a list of e-mail addresses without probing anyone's mailbox. The Actor validates syntax, looks up MX records in DNS, flags disposable domains and role addresses such as info@, and suggests a fix when the domain looks like a typo. Every address is returned, including the ones that fail.
This is cheaper and more honest than a "bounce" checker that pretends to know whether a mailbox exists. We never open an SMTP connection.
What does the Email Checker do?
Typical uses:
- Clean a list before you import it into a newsletter tool or a CRM.
- Catch typo domains such as
gmial.comorgmail.con. - Drop or flag disposable inboxes and role addresses.
- Run a bulk check from another Actor's dataset.
What data do you get?
Each input address becomes one row.
| Field | What it is |
|---|---|
inputIndex | Position in your input, starting at 0 |
email, emailNormalized | The original address and a lower-case trimmed copy |
localPart, domain | The two sides of the @ |
syntaxOk | Whether the address looks well formed |
hasMx, mxHosts | Whether the domain has MX records, and the hosts |
isDisposable | Whether the domain is a known disposable inbox |
isRoleAddress | Whether the local part is a role such as info, sales or admin |
typoSuggestion | A likely domain if a typo is suspected, otherwise null |
issues | A list of problems |
status | ok, invalid_syntax, disposable, typo_suspected, no_mx, mx_lookup_failed, or skipped_limit |
The original address is never rewritten. A typo suggestion is only a hint.
Example output
One address from a test run. The Actor also flags invalid syntax, disposable domains and likely typos.
{"inputIndex": 0,"email": "alex@example.com","emailNormalized": "alex@example.com","localPart": "alex","domain": "example.com","syntaxOk": true,"isRoleAddress": false,"isDisposable": false,"typoSuggestion": null,"issues": [],"status": "ok","hasMx": true,"mxHosts": [""],"mxError": null}
Nothing is silently dropped
Invalid, disposable and typo-suspect addresses stay in the results with a status. If you set Max addresses to check lower than the size of your list, the remaining addresses are still written with status skipped_limit.
How to use it
- Paste addresses in
E-mail addresses, or give records / a dataset ID. - Leave
Look up MX recordson unless you only want syntax and disposable checks. - Set
Max addresses to checkand click Start. - Download the result as JSON, CSV or Excel, or read it with the API.
What we do not do
- We do not connect to a mail server, send a probe, or try to find out whether a mailbox exists.
- We do not guarantee that an address with MX records can receive mail, or that a
no_mxdomain never can (some domains receive mail on an A record). - Catch-all domains can look fine and still bounce later.
Limits
- Disposable-domain detection uses a bundled public list (MIT licence, see
src/disposable-domains.LICENSE). The list is a snapshot, not a live feed. - Typo suggestions cover well-known providers. An unusual private domain will not get a suggestion.
How much does it cost?
You pay for each address that is written, including invalid and skipped ones. The price per 1,000 addresses is shown at the top of this page, and you can set a maximum cost per run.
Data and privacy
E-mail addresses are personal data. The Actor does not keep a copy after the run ends, beyond what Apify stores for your run in the usual way, and it does not log the addresses themselves. You are responsible for how you use the list.
Issues and requests
If a domain is wrongly flagged, or a typo is missed, please open an issue on the Issues tab. You can send the domain only, without the person's name.