Email Verifier and Email Validator, Bulk Email Verification
Pricing
$2.00 / 1,000 checked email addresses
Email Verifier and Email Validator, Bulk Email Verification
Input a list of email addresses, get back a validation row per address: practical RFC 5322 syntax, live MX/A domain checks over DNS-over-HTTPS, disposable-domain and role-account flags. It checks the address and domain, not the mailbox. Billed only per address checked.
Pricing
$2.00 / 1,000 checked email addresses
Rating
0.0
(0)
Developer
Pono Data
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
11 days ago
Last modified
Categories
Share
Email Validator
Clean a list of email addresses you already have. For each address the actor
checks practical RFC 5322 syntax, whether the domain can actually receive mail
(MX records, with an A/AAAA fallback per RFC 5321) over DNS-over-HTTPS, whether
the domain is a known disposable/temporary-mail provider, and whether the local
part is a role mailbox (info@, support@, ...) rather than a person.
This actor validates addresses you supply. It does not find, guess, or harvest addresses.
Honest scope
It verifies the address and its domain, not the individual mailbox. It does not open an SMTP session or probe whether a specific inbox exists, so it will not claim a precise deliverability percentage. What it returns is exact: the syntax verdict and the domain's live mail records.
Input
- Email addresses: one per line.
- DNS resolver: Cloudflare or Google (the other is the fallback).
- Max checked addresses: cap on billed rows (0 = no cap).
Output
email, normalized, localPart, domain, syntaxValid, hasMx, mxHost,
domainResolves, disposable, roleAccount, status, freeProvider,
didYouMean, plus provenance (sourceUrl is the DoH MX query, retrievedAt,
confidence, dataSource).
freeProvider: true when the lowercased domain is on a fixed built-in list of free consumer mailbox providers such as gmail.com, outlook.com and yahoo.com.didYouMean: a corrected address, built by fixing a mistyped top-level label (.conto.com,.neto.net,.ogrto.org, and similar) and then matching a known provider exactly one edit away, only when exactly one provider matches; otherwise null.
didYouMean is a suggestion for a likely typo, not a verdict. It never changes
status, confidence or billing, and it is given whether or not the typed
domain has MX records.
Billing
Pay per address actually checked. Addresses that fail the syntax check before any
DNS work are written to the free rejected dataset and are not billed.
Sample output
A real run checking a mixed list (deliverable, disposable, and bad addresses):
| syntax | MX | role | disposable | status | |
|---|---|---|---|---|---|
| info@cloudflare.com | True | True | True | False | deliverable_domain |
| support@github.com | True | True | True | False | deliverable_domain |
| test@mailinator.com | True | True | False | True | disposable |
| x@guerrillamail.com | True | True | False | True | disposable |
Malformed addresses route to the free reject dataset. Each checked row carries a sourceUrl (the live MX lookup), for example https://cloudflare-dns.com/dns-query?name=cloudflare.com&type=MX.
See also
More clean, pay-only-for-results data tools from Pono Data:
- Verified B2B Email Finder - business emails proven deliverable
- Bulk DNS Lookup - DNS records plus SPF, DMARC, and CAA
- Domain WHOIS via RDAP - registration data, structured from RDAP
Full catalog: https://apify.com/thoob