Email & Domain Validator (DNS-only)
Pricing
from $0.20 / 1,000 validated emails
Email & Domain Validator (DNS-only)
Bulk-validate email syntax, DNS/MX, disposable domains, role accounts and typos. No SMTP probing, nothing stored — privacy-first list cleaning.
Pricing
from $0.20 / 1,000 validated emails
Rating
0.0
(0)
Developer
Hanxiao Yang
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
24 days ago
Last modified
Categories
Security
Limited permissionsShare
Email & Domain Validator (DNS-only, Privacy-first)
Keywords: email validator, MX record check, disposable email detection, role account filter, typo domain suggestion, bulk email cleaner, no SMTP verification.
Clean email lists without SMTP probing. For each address: syntax, DNS/MX, disposable domain, role account (info@…), and typo suggestions (gmial.com → gmail.com). Nothing stored beyond your run dataset.
Why this Actor
- No SMTP — never touches mail servers (safer for IP reputation)
- Fast DNS cache per domain; thousands of addresses in seconds
- Privacy-first: process in memory, write only to your Apify dataset
- Clear verdicts:
valid·risky·disposable·undeliverable·invalid·unknown
Example input
{"emails": ["hello@gmail.com","info@example.com","test@gmial.com","user@mailinator.com"],"resolver": "system","concurrency": 20}
You can also paste a list into emailsText (newline or comma separated). Use resolver: "doh" (Cloudflare DoH) if system DNS is unreliable.
Output fields
| Field | Meaning |
|---|---|
syntaxValid / syntaxError | RFC-style syntax |
domainExists, hasMx, nullMx, mxHosts, hasA | Live DNS |
acceptsMailLikely | MX or A-record fallback |
isDisposable / isRoleAccount | disposable list / role local-parts |
suggestedDomain | common-provider typo fix |
verdict | overall label |
Pricing (pay per event)
- Validated email — $0.0002 per result (~$0.20 / 1,000)
- Actor start ~$0.00005
Limitations
Cannot prove an individual mailbox exists (no SMTP). Disposable lists are never complete. Only process lists you are allowed to handle.
Use cases & scheduling
- Clean a list before a campaign — paste emails into
emailsText, export rows whereverdictisvalid. - Sign-up form hygiene — detect disposable/temporary email domains and typos (
gmial.com→gmail.com). - Filter role accounts — drop
info@,sales@,support@from outreach lists. - Recurring CRM hygiene — schedule weekly against a fresh export so new bad domains are flagged early.
- Bulk MX record check — see which domains have MX, null MX, or only an A record.
Tip: create an Apify Schedule for the Actor or one of the tasks below to turn it into a recurring monitor, and add a webhook/integration to get results in Slack, email or Google Sheets.
Ready-made example tasks
One-click, pre-filled inputs you can run or copy:
FAQ
Does it check if the mailbox really exists?
No. There is no SMTP probing, so it cannot confirm an individual inbox — it checks syntax, DNS/MX, disposable and role patterns.
Why no SMTP?
SMTP probing hurts IP reputation and is often blocked or inaccurate on catch-all servers. DNS-only is fast and safe.
system vs doh resolver?
system uses the platform DNS; doh uses Cloudflare DNS-over-HTTPS when system DNS is unreliable.
Is my list stored?
Only in your own run dataset. Process only lists you are allowed to handle.