Why Validate Emails?
Email validation helps you:- Reduce bounce rates by up to 98%
- Protect your sender reputation from hard bounces
- Save money by not sending to invalid addresses
- Improve deliverability by maintaining a clean list
Validating a Single Email
Use the validation API to check if an email address is valid before sending.Response
response.json
Validation Checks
Each validation performs multiple checks:| Check | Description |
|---|---|
| Syntax | RFC-compliant email format validation |
| MX Records | Verify domain has valid mail servers |
| Mailbox | SMTP-level check if mailbox exists |
| Disposable | Detect temporary email services |
| Role | Flag role-based addresses (info@, support@) |
| Free | Identify free email providers (gmail, yahoo) |
Confidence Levels
The API returns a confidence level for each validation:| Confidence | Description | Recommended Action |
|---|---|---|
high | Email is definitely valid | Safe to send |
medium | Email might be valid | Send with caution |
low | Email is likely invalid | Do not send |
Validate at Signup
The best time to validate is at the point of capture. Here’s an example signup form:Bulk Validation
Validate thousands of emails at once by uploading a CSV file in the dashboard, or use the bulk API:Bulk validation is available on Pro plan only. Free plan users should use the single email validation endpoint.
Pricing
| Plan | Credits | Price |
|---|---|---|
| Free | 1,000 credits | $0/forever |
| Pro | 100,000 credits/month | $29/month |
Best Practices
- Validate at signup - Catch invalid emails before they enter your database
- Use suggestions - Show typo corrections to users (e.g., “Did you mean gmail.com?”)
- Block disposable emails - Prevent abuse from temporary email services
- Handle role addresses - Consider whether to allow info@, support@, etc.
- Re-validate periodically - Email addresses can become invalid over time
Next Steps
Validation API Reference
Complete API documentation for email validation
Bulk Validation
Validate multiple emails at once