Email Verifier — Syntax, MX & Disposable Check
Pricing
from $0.50 / 1,000 results
Email Verifier — Syntax, MX & Disposable Check
Verify email addresses from public DNS and public data: syntax, domain, MX records, disposable domains and role accounts. No SMTP probing of third-party mail servers, so no sender-reputation risk.
Pricing
from $0.50 / 1,000 results
Rating
0.0
(0)
Developer
Axery
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
15 hours ago
Last modified
Categories
Share
Email Verifier (Syntax + MX + Disposable)
Verifies email addresses using public DNS and public data only — no login, no paid API, no SMTP probing of other people's mail servers.
What it checks
| Check | How |
|---|---|
| Syntax | RFC 5321/5322-shaped rules, including the real length ceilings (64 local / 255 domain / 320 total) |
| Domain exists | DNS-over-HTTPS, NXDOMAIN detection |
| MX records | Full mail-exchanger list with priorities, sorted |
| A-record fallback | A domain with no MX can still receive mail via its A record (RFC 5321) — checked before calling an address dead |
| Disposable domains | Public disposable-email-domains blocklist, fetched once per run |
| Role accounts | info@, admin@, support@ and similar — valid, but usually not a person |
Two independent DoH resolvers (Google, Cloudflare) are tried in turn, so one provider being unreachable degrades to the other instead of failing the run.
What it deliberately does NOT do
It does not connect to the recipient's mail server and probe individual mailboxes with SMTP RCPT TO. That technique hammers third-party infrastructure without consent, many providers treat it as abuse, and modern catch-all configurations make its answer unreliable anyway.
The honest consequence, stated plainly rather than hidden: this Actor tells you whether an address can receive mail (domain resolves, MX exists), not whether that specific mailbox exists. That is why there is no valid status — only:
deliverable— domain resolves and accepts mail, no flagsrisky— deliverable but disposable, a role account, or relying on an A-record fallbackinvalid— provably cannot receive mailunknown— the DNS lookup itself failed
Every underlying signal (syntax_valid, domain_exists, has_mx, mx_records, is_disposable, is_role_account) is emitted alongside the verdict, so you can apply your own thresholds instead of trusting the summary.
checks_performed lists which checks actually ran for each row — useful when a DNS failure means fewer ran than usual. And when the disposable check is turned off, is_disposable reports null, not false, so an unchecked address is never mistaken for a clean one.
Input
| Field | Type | Notes |
|---|---|---|
emails | array | Addresses to verify — one row each. |
checkDisposable | boolean | Fetch and match the public disposable blocklist. |
proxyConfiguration | object | Not normally needed — public DoH resolvers only. |
Local development
sample_output.json is real output covering deliverable, role-account, disposable, NXDOMAIN and two syntax-failure cases.
