emailverifier.dev
emailverifier.dev
- Free plan
- Web
- API
What emailverifier.dev is
emailverifier.dev checks email addresses before they enter product workflows such as signups, trials, lead forms, or CRM imports. It examines address structure, likely typos, mail-routing DNS, provider type, disposable and role-based signals, and mailbox acceptance or catch-all behavior when available. Results separate deliverable, risky, undeliverable, and unknown outcomes. Domain checks identify disposable providers, known free mailbox services, or neither, and return risk and mail-routing information. Teams can use the REST API, a remote MCP server, or bulk uploads from CSV, TXT, or pasted addresses. Bulk jobs support up to 5,000 unique addresses and preserve original rows while adding status, recommended action, flags, signals, and typo suggestions; finished files expire after seven days. The free plan includes 1,000 starter credits and one API key. A Credit pack costs $10 per one-time purchase for 20,000 credits. Each verification or domain check uses one credit, while the public demo allows 10 checks per hour without project credits.
Who it suits
It is designed for product teams adding email checks to forms, imports, and account flows. API, MCP, and bulk options suit both integrated and file-based workflows.
Good to know, and what to watch
- Distinguishes deliverable, risky, undeliverable, and unknown results
- Provides REST API and remote MCP tools
- Supports bulk jobs up to 5,000 addresses
- Free plan includes 1,000 credits
- Credits do not expire
- No free trial
- Bulk working data is temporarily stored
- Completed bulk files expire after seven days
- Credit packs cost $10 per one-time purchase
Plans
Every plan and priceStart free
Credit pack
Free plan
The verdict
emailverifier.dev offers address and domain checks through APIs, MCP, a demo, and bulk processing. Its credit model and temporary bulk-file retention are key details for teams planning integrations.
What the maker publishes
- 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. source
- 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. source
- 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. source
- 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. source
- 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. source
- 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. source
- Intended users
- The product is designed for product teams adding checks to signups, free trials, lead forms, CRM imports, and other application workflows. source
- Payment processing
- Stripe processes payment and billing information, and emailverifier.dev says it does not store full card numbers. source
- Purpose
- The service checks email addresses for malformed, disposable, role-based, and unroutable addresses before they enter a product. source
- Results
- The verifier distinguishes deliverable, risky, undeliverable, and unknown outcomes so an uncertain result is not automatically treated as a failure. source
- 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. source
- Support
- Support is provided by email at [email protected] for account, billing, API, privacy, and security questions. source
- 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. source
Checked against the maker's pages on 4 Oct 2026.