Syntax
Address format verification
MailChecker checks address format, domains and mail server responses to help your application identify contacts with potential problems.
Check syntax, DNS/MX, disposable domains and SMTP in a single API request.
decisionResults from each validation stepThis demonstration does not send a real request.
The API returns the checks in a JSON response with a recommendation and its reason. Use the results to accept a signup, ask for a correction or block an address.
Explore the integrationAddress format verification
Mail server lookup for the domain
Known disposable domain detection
Recipient mail server response
An email that bounces because of an invalid address can still count against your sending plan. Validation helps you find these contacts before a campaign and avoid some of those attempts.
Ask users to correct an invalid address format before completing signup.
Review contacts with missing domains or other signs of trouble before sending a campaign.
Use the reason returned by the API to decide how your application handles each result.
No. It checks syntax, domain and SMTP signals. Recipient filters, policies and other conditions may still prevent delivery.
No. Every validation requires a valid API key. The public documentation covers authentication and integration examples.
Each completed request will count, including cached results, invalid addresses and inconclusive outcomes. Internal failures will not be charged. The allowance will be shared across your keys and will not roll over.
New validations will be blocked with an error explaining that the allowance is exhausted. Wait for renewal or confirm an upgrade. There will be no automatic overage charges.
The documentation includes request examples and response fields to help you build your integration.