Email Validator & Domain Checker — MX, Disposable, Typos, RDAP

Clean a list of email addresses or check a list of domains in one fast run. For every address you get a clear status (valid, risky, invalid, disposable, unknown), the reason, and a "did you mean" fix for typos like john@gmial.com → john@gmail.com. For domains you also get SPF, DMARC, nameservers and registration facts (registrar, creation and expiry dates) from the official RDAP registries.

What it checks, in short: syntax, the domain's MX / DNS mail setup, disposable (temporary) inbox services, role accounts and common typos. What it does not do: it never connects to mail servers (no SMTP check), so it cannot tell whether a specific mailbox exists. No personal data lookups — only public DNS, public registry data and open-licensed lists.

What it checks

Check	Emails	Domains
Syntax (RFC 5321/5322 rules people actually hit, IDN / Unicode domains)	✅	✅
Domain exists, MX records, null MX (RFC 7505), mail servers that do not resolve	✅	✅
Disposable / temporary email services (≈10,000 domains, also matched on subdomains and on mail servers)	✅	✅
Role accounts (info@, sales@, no-reply@ …)	✅	—
Free consumer providers (Gmail, Outlook, Yahoo, GMX, Proton …) and the mail host (Google Workspace, Microsoft 365, Proofpoint …)	✅	✅
Typo suggestions (gmial.com, hotmail.co, yahoo.con, outlok.com …)	✅	—
SPF record, DMARC policy, nameservers, IPv4 / IPv6	optional	✅
Registration via RDAP: registrar, created / updated / expires, age in days, status, DNSSEC	—	✅ (can be turned off)

Input

• Emails — one per line, or paste a CSV column. Name <ann@example.com> and mailto: links are fine.
• Domains — bare domains, URLs (https://www.example.com/page) or even email addresses; the domain is taken from each.
• Registration data (RDAP) — on by default for domains.
• DNS details for emails — adds SPF / DMARC / nameservers to each email row.

Up to 100,000 unique records per run. Duplicates (case-insensitive) and blank lines are removed before checking and are not charged.

Output

One row per unique input. The Overview table view shows the key columns; the full row also has mxRecords, mailProvider, isValidSyntax, checkedAt and, for domains, spf, dmarc, dmarcPolicy, nameservers, ipv4, ipv6 and registration.

status	Meaning	Typical reasons
valid	Syntax is fine and the domain accepts mail	accepts_mail
risky	Deliverable domain, but think before mailing	role_account, possible_typo, no_mx_record (mail only via the A record), quoted_local_part
invalid	Mail to this address cannot be delivered	domain_not_found, null_mx, no_mail_server, mx_unresolvable, syntax reasons such as invalid_dots, unknown_tld
disposable	Temporary inbox service	disposable_domain, disposable_mx
unknown	DNS did not answer in time — not charged, re-run later	dns_timeout, dns_error

Domain rows use active, inactive, not_registered, invalid and unknown.

A summary (counts by status, charged / not charged, speed) is saved as OUTPUT in the run's key-value store.

Accuracy and speed

We tested the Actor on a small labeled set of 169 addresses that we built ourselves (good, broken, disposable, role and typo cases); it classified 166 of them as expected. This is an internal sanity check, not an independent benchmark, and it measures classification only — not whether mail actually gets delivered. The three misses were forwarding services (33mail, Burner Mail, Spamgourmet) that the open disposable list does not include. On Apify with the default 512 MB it checked 8,000 mixed addresses in 5.4 seconds (about 1,500 per second).

Limits — read before you buy

• No SMTP / mailbox check. We never connect to mail servers to ask whether a mailbox exists. That practice is unreliable (catch-all servers, greylisting), blocked on cloud networks, and gets IP addresses blocklisted. So valid means "the domain is set up to receive mail", not "this exact mailbox exists", and catch-all domains are not detected.
• RDAP fair use. Registration lookups go to the official registries, at most 4 parallel requests per registry with spacing, cached per domain and slowed down when a registry asks. Registries' terms forbid using their data to support unsolicited bulk email; use it for list hygiene, fraud checks and research only. Only registrar facts are returned, never registrant contact data.
• Some registries (many country-code TLDs) have no RDAP service yet; those rows show registration.errorCode: "NO_RDAP_SERVER".

Pricing

Pay per record checked. Only final verdicts are charged:

Event	Price
Email or domain check (valid, risky, invalid, disposable, or a domain verdict)	$0.001 ($1 per 1,000)
Actor start	Apify default ($0.00005)

Free: unknown rows (DNS did not answer), values that are not an email address at all, duplicates and blank lines.

Examples: 1,000 addresses cost $1, 10,000 cost $10. If you set a maximum cost per run, the Actor stops cleanly when it is reached and keeps every result it already delivered. If a run is restarted or migrated, records that were already charged are not charged again.

FAQ

Why is a Gmail address valid when the mailbox might not exist? Without SMTP probing nobody can know that reliably; we report what DNS proves. Combine with a double opt-in for signups.

Why risky for info@? Role addresses reach a team or nobody, and are a frequent spam-trap source. Keep them if you know the company.

Where do the lists come from? The disposable list is the CC0 disposable-email-domains project; provider and role lists are our own.

Can I call it from code? Yes — any Apify API client or the REST API; the dataset is ready as JSON, CSV or Excel.