- Home
- Email Verification APIs
- emailverifier.dev
emailverifier.dev
What it is
emailverifier.dev checks addresses before they enter product workflows, helping teams identify malformed, disposable, role-based, and unroutable emails. Its signals include address structure, likely typos, mail-routing DNS, provider type, and mailbox acceptance or catch-all behavior when available. Results distinguish deliverable, risky, undeliverable, and unknown outcomes, keeping uncertain checks separate from confirmed failures. Teams can use a REST API, remote MCP tools, or a public no-key demo; each project email or domain check uses one credit, while the demo allows 10 checks per hour without project credits. Bulk jobs accept CSV or TXT uploads or pasted addresses, handle up to 5,000 unique addresses, and retain original rows alongside results. The free plan includes 1,000 starter credits and one API key per project. A $10 one-time credit pack provides 20,000 credits. Completed bulk files expire after seven days; single checks are not stored in the application usage database, while bulk lists and working results are temporarily stored.
For and against
For
- Free plan includes 1,000 starter credits.
- REST API and remote MCP tools are available.
- Bulk jobs accept up to 5,000 unique addresses.
- Results distinguish risky and unknown outcomes.
Against
- Each project email or domain check uses one credit.
- Completed bulk files expire after seven days.
- Bulk lists and working results are temporarily stored.
The verdict
emailverifier.dev offers address and domain checks through web, API, MCP, and bulk workflows, with uncertain results labeled separately. Teams should account for credit use and temporary storage of bulk working data.
Who it suits
It is designed for product teams adding email checks to signups, free trials, lead forms, CRM imports, and other application workflows. It may suit teams that need API or bulk verification and can work with credit-based usage.
Plans and prices
Start free
1,000 starter credits · one API key per project · REST and MCP access · credits do not expire
Read 4 Oct 2026 · emailverifier.dev
Credit pack
20,000 credits per pack · buy 1–100 packs in one checkout · credits do not expire · optional $10 auto top-up at 1,000 credits
Read 4 Oct 2026 · emailverifier.dev
On the record
- API and AI tools
- The product offers a REST API and a remote MCP server with verify_email and check_domain tools; each tool call costs one project credit.emailverifier.dev · read 4 Oct 2026
- Bulk output and retention
- Bulk results preserve original rows and append status, recommended action, flagged state, signals, and any typo suggestion; completed files expire after seven days.emailverifier.dev · read 4 Oct 2026
- Bulk verification
- The bulk verifier accepts CSV or TXT uploads or pasted addresses, supports up to 100 CSV columns, and allows up to 5,000 unique addresses per job.emailverifier.dev · read 4 Oct 2026
- Credit usage
- Each email verification and domain check uses one project credit, while the public no-key demo allows 10 checks per hour without spending project credits.emailverifier.dev · read 4 Oct 2026
- Data handling
- Single-address checks are not stored in the application usage database, while bulk lists and working results are temporarily stored so jobs can finish after the user leaves.emailverifier.dev · read 4 Oct 2026
- Domain checks
- Domain reports classify a provider as disposable, a known free mailbox service, or neither, and the MCP domain tool returns classification, risk, and mail-routing data.emailverifier.dev · read 4 Oct 2026
- Intended users
- The product is designed for product teams adding checks to signups, free trials, lead forms, CRM imports, and other application workflows.emailverifier.dev · read 4 Oct 2026
- Payment processing
- Stripe processes payment and billing information, and emailverifier.dev says it does not store full card numbers.emailverifier.dev · read 4 Oct 2026
- Purpose
- The service checks email addresses for malformed, disposable, role-based, and unroutable addresses before they enter a product.emailverifier.dev · read 4 Oct 2026
- Results
- The verifier distinguishes deliverable, risky, undeliverable, and unknown outcomes so an uncertain result is not automatically treated as a failure.emailverifier.dev · read 4 Oct 2026
- Security practices
- The service says passwords, API keys, verification links, and password-reset links are stored as one-way hashes, and account sessions use secure HTTP-only cookies.emailverifier.dev · read 4 Oct 2026
- Support
- Support is provided by email at [email protected] for account, billing, API, privacy, and security questions.emailverifier.dev · read 4 Oct 2026
- Verification signals
- Checks include address structure, likely typos, mail-routing DNS, provider type, disposable and role signals, and mailbox acceptance or catch-all behavior when available.emailverifier.dev · read 4 Oct 2026
