emailverifier.dev

Overview

emailverifier.dev checks addresses and domains through a web interface, REST API and remote MCP tools. It suits product teams validating signups, lead forms and imports; its strongest fit is workflows that need distinct risky and uncertain outcomes rather than a simple pass-or-fail.

Its per-check credit model and bulk jobs make it useful for both application integrations and list cleanup, though teams handling sensitive lists should weigh the temporary storage required for bulk processing.

Key features

Address checks assess structure, likely typos, mail-routing DNS, provider type, disposable and role-based signals, and mailbox acceptance or catch-all behavior when available. Results are grouped as deliverable, risky, undeliverable or unknown. That distinction helps avoid treating uncertainty as failure, while the range of signals can inform signup and import decisions.

Domain checks identify whether a provider is disposable, a known free mailbox service or neither. The MCP domain tool also returns risk and mail-routing data. Each email verification or domain check costs one project credit; REST and MCP tool calls follow the same one-credit rate. A public demo allows 10 checks per hour without using project credits.

Bulk verification accepts CSV and TXT uploads or pasted addresses, with up to 100 CSV columns and 5,000 unique addresses per job. Output retains the original rows and adds status, recommended action, flagged state, signals and any typo suggestion. Completed files expire after seven days. This is a practical route for CRM imports, but lists and working results are temporarily stored so jobs can continue after the user leaves.

Single-address checks are not stored in the application usage database. The service says it stores passwords, API keys, verification links and password-reset links as one-way hashes, and uses secure HTTP-only cookies for sessions. Stripe handles payment and billing; emailverifier.dev says it does not store full card numbers. Support is by email for account, billing, API, privacy and security questions.

Pricing

The free Start free plan costs nothing, requires no card, and includes 1,000 starter credits, one API key per project, REST and MCP access, and credits that do not expire. It is a meaningful evaluation and light-use option, but the one-key limit may constrain teams that need separate project credentials.

The Credit pack costs $10, paid once and provides 20,000 credits per pack. Buyers can purchase 1–100 packs in one checkout; credits do not expire. An optional $10 auto top-up triggers at 1,000 credits. Since each email or domain check uses one credit, this makes costs straightforward to track, though heavier ongoing use means buying more packs or enabling top-up rather than subscribing to a monthly allowance. There is no free trial.

Platforms

Access is through web and API tools, including a REST API and remote MCP server. The web tools cover individual, domain and bulk checks; the API and MCP options are suited to adding verification to product workflows.

Who it's for

Product teams adding checks to signups, free trials, lead forms, CRM imports or other application flows are the clearest fit. The service also suits teams that need occasional batch cleanup without a recurring subscription, especially when non-expiring credits match their usage pattern. It is less suited to workflows that require bulk files not to be temporarily stored, or teams that need more than one API key per free project.

Pros and cons

• Pros: Separate risky and unknown outcomes preserve uncertainty instead of forcing every address into a binary decision.
• Pros: Non-expiring free and paid credits suit irregular verification needs, and the free plan includes REST and MCP access.
• Pros: Bulk jobs accept up to 5,000 unique addresses and preserve source rows alongside actionable signals and typo suggestions.
• Cons: Each check consumes one credit, including domain checks, so repeated use draws down the same project balance.
• Cons: Bulk lists and working results are temporarily stored, with completed files expiring after seven days.
• Cons: The free plan permits one API key per project, limiting credential separation for teams on that tier.

Alternatives

For a broader shortlist, see Email Verification Services.

• VerifyAnyEmail is worth considering if iOS access or monthly free credits matter: its free tier includes 1,000 credits per month, but limits batches to 10 and one concurrent batch, with no webhooks or priority support. Its 1,000-credit pay-as-you-go option costs 4.00 USD.
• Bounceless may suit users who prefer 1,000 free credits each month and do not want unknown results billed. Its 5,000-credit pack costs $19, paid once.
• Email Verifier API offers a smaller no-card starting point of 100 one-time credits that never expire; its 1,000-credit option costs $9.95, paid once.
• Emailable is an option for buyers who want a monthly subscription: it offers 250 free credits for new accounts and a 5,000-credit monthly subscription at $32.30 a month.
• EmailOversight is another service to compare for verification needs.
• Mailbeam may fit teams looking for monthly free credits plus webhooks and community support; its free tier includes 1,000 verifications per month and bulk CSV upload.
• MyEmailVerifier offers 100 free credits daily and an extension alongside API and web access, making it a candidate for users who value daily replenishment or browser access.
• QuickEmailVerification is an alternative with a daily-reset free tier of 100 credits.

Verdict

Choose emailverifier.dev if you need email and domain checks in product flows, want web-based bulk cleanup, and prefer credits that never expire. Its layered outcomes and REST/MCP access are the main reasons to choose it. Look elsewhere if temporary bulk-data storage is unacceptable, you need multiple free-tier API keys per project, or a monthly free allowance better matches your workload.