SecureMail Validation API delivers a reliable and efficient way to detect and block disposable and public email addresses, improving data quality and enhancing security. This API validates emails in real time, checking for domains associated with temporary or high-risk providers, and utilizes MX record validation to confirm domain legitimacy. By filtering out risky emails, this API helps prevent low-quality user registrations and fosters trustworthy user interactions.
In addition to detection, it also corrects common typing errors, streamlining the registration process by promoting valid email submissions. Designed for secure applications, SaaS platforms, and digital services, the SecureMail Validation API is easy to integrate and provides accurate results in JSON format, making it a vital tool for companies aiming to maintain clean and authentic email databases. It’s a powerful resource for businesses looking to reduce spam, enhance data integrity, and boost user verification security.
Sends the email parameter to the endpoint to verify if it belongs to a temporary or public domain.Receives a JSON with the status and details of the email.
Check Disposable Email - Endpoint Features
| Object | Description |
|---|---|
email |
[Required] |
{
"did_you_mean": null,
"domain": "gianes.com",
"is_disposable_domain": true,
"is_public_domain": false,
"mx": true,
"status": true
}
curl --location --request GET 'https://zylalabs.com/api/5479/secure+mail+validation+api/7102/[email protected]' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Send an email to the endpoint to receive information about its legitimacy and possible public domain or temporary status.
Validates whether an email belongs to a public or temporary domain, helping to filter out low-value records.
The API receives an email and responds with data about its validity, type (temporary/public), and other details useful for evaluation.
User verification: Allows to accept only emails from reliable providers, blocking disposable accounts. Campaign optimization: Ensures that emails in marketing campaigns are valid and of high quality. Security protection: Prevents users from registering with temporary or spam emails, improving security.
Beside the number of API calls per month allowed, there are no other limitations.
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
The API uses API keys for authentication. To access the API, include your API key in the request header. The API key is provided upon registration and should be kept secure.
The API returns detailed information about the age and history of a domain, including years, months and days since its creation, as well as expiration and update dates.
The endpoint returns a JSON object containing information about the email's legitimacy, including whether it belongs to a disposable or public domain, MX record validation status, and suggestions for correcting common typing errors.
Key fields in the response include "is_disposable_domain," "is_public_domain," "mx," "status," and "did_you_mean." These fields indicate the email's validity and provide suggestions for corrections.
The response data is structured in a JSON format, with key-value pairs that provide specific details about the email's status and characteristics, making it easy to parse and utilize in applications.
The endpoint provides information on whether an email is from a disposable or public domain, its MX record status, and suggestions for correcting potential typos, enhancing user registration quality.
The endpoint accepts a single parameter: the email address to be validated. Ensure the email is formatted correctly to receive accurate validation results.
Data accuracy is maintained through continuous updates and checks against known disposable and public email domains, as well as MX record validation to confirm domain legitimacy.
Typical use cases include validating user registrations, filtering email lists for marketing campaigns, and enhancing security by preventing the use of temporary or spam email addresses.
Users can utilize the returned data to filter out low-quality email submissions, improve user verification processes, and enhance the overall integrity of their email databases by acting on the "is_disposable_domain" and "did_you_mean" fields.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
1,417ms
Service Level:
100%
Response Time:
258ms
Service Level:
100%
Response Time:
2,741ms
Service Level:
100%
Response Time:
1,865ms
Service Level:
100%
Response Time:
1,891ms
Service Level:
100%
Response Time:
309ms
Service Level:
100%
Response Time:
187ms
Service Level:
100%
Response Time:
287ms
Service Level:
100%
Response Time:
59ms
Service Level:
100%
Response Time:
315ms
Service Level:
100%
Response Time:
9,164ms
Service Level:
100%
Response Time:
242ms
Service Level:
100%
Response Time:
1,291ms
Service Level:
100%
Response Time:
414ms
Service Level:
100%
Response Time:
1,274ms
Service Level:
100%
Response Time:
1,430ms
Service Level:
100%
Response Time:
659ms
Service Level:
100%
Response Time:
1,227ms
Service Level:
100%
Response Time:
1,249ms
Service Level:
100%
Response Time:
1,351ms