The Spam Domain API is an essential tool for protecting enterprise databases from temporary or disposable emails. This API uses a constantly evolving database, which is fed by actively crawling the Internet to identify new domains associated with temporary email services. Unlike traditional solutions that rely on static block lists, this API offers real-time detection, ensuring that companies can stay ahead of abusive users attempting to sign up with disposable emails. Ideal for companies that need to ensure the quality of their databases, prevent fraud and maintain a reliable user experience. With this API, you can prevent fraudulent registrations, improve the accuracy of your data analysis and maintain the security of your platform.
Validate Disposable Domain - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"domain":"hotmail.com","score":8,"meta":{"block_list":false,"domain_age":28,"website_resolves":true,"accepts_all_addresses":false,"valid_email_security":true}}
curl --location --request POST 'https://zylalabs.com/api/5748/spam+domain+api/7477/validate+disposable+domain' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"domain": "[email protected]"
}'
| 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.
The Spam Domain API is a tool designed to detect and block temporary or disposable email addresses in real time. It helps protect enterprise databases from fraudulent registrations and abuse by identifying new domains associated with temporary email services.
The API utilizes a constantly evolving database that is updated by actively crawling the Internet. This allows it to provide real-time detection of disposable email domains, unlike traditional solutions that rely on static block lists.
The main benefits include preventing fraudulent registrations, improving the accuracy of data analysis, maintaining a reliable user experience, and enhancing the overall security of your platform.
Companies that need to ensure the quality of their databases, prevent fraud, and maintain a secure user experience can greatly benefit from using the Spam Domain API.
Yes, the Spam Domain API is designed for easy integration into existing systems, allowing businesses to quickly implement its features to enhance their registration processes and protect their databases.
The Validate Disposable Domain endpoint returns a JSON object containing information about the domain's status, including whether it is disposable, its score, and metadata such as domain age and whether it resolves to a website.
Key fields in the response include "domain" (the queried domain), "score" (a numerical value indicating the domain's risk level), and "meta" (which contains additional details like "block_list," "domain_age," and "website_resolves").
The response data is structured as a JSON object. It includes the main domain information at the top level, followed by a "score" field and a "meta" object that provides further details about the domain's characteristics.
The primary parameter for this endpoint is the domain name, which should be included in the body of the POST request. Users can customize their requests by specifying different domains to validate.
Typical use cases include validating user registrations to prevent fraud, filtering out disposable emails during sign-up processes, and enhancing data quality for marketing campaigns by ensuring valid email addresses.
Data accuracy is maintained through continuous updates from actively crawling the Internet to identify new disposable email domains. This dynamic approach ensures that the API reflects the latest information available.
The API employs various quality checks, including verifying domain age, whether the domain resolves to a website, and assessing if it accepts all email addresses, ensuring reliable and accurate results.
Users can utilize the returned data by interpreting the "score" to assess risk levels, using the "meta" information to understand domain characteristics, and implementing logic in their systems to block or flag disposable email registrations.
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:
209ms
Service Level:
100%
Response Time:
661ms
Service Level:
100%
Response Time:
1,130ms
Service Level:
100%
Response Time:
8,082ms
Service Level:
100%
Response Time:
1,171ms
Service Level:
100%
Response Time:
1,625ms
Service Level:
100%
Response Time:
374ms
Service Level:
100%
Response Time:
804ms
Service Level:
100%
Response Time:
4,394ms
Service Level:
100%
Response Time:
4,288ms