Allows you to check the availability of popular domain names using the “Beast Mode”. Sends a POST request with the body including the name in the “name” field. This endpoint is optimized to process popular domains in multiple TLDs, providing a quick way to identify available high-value names.
Check Name Beast Mode - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"favfood.ai":true,"favfood.app":true,"favfood.biz":true,"favfood.co":true,"favfood.dev":true,"favfood.info":true,"favfood.io":true,"favfood.net":true,"favfood.org":true,"favfood.tech":true,"favfood.us":true,"fav-food.ai":true,"fav-food.app":true,"fav-food.biz":true,"fav-food.co":true,"fav-food.dev":true,"fav-food.info":true,"fav-food.io":true,"fav-food.net":true,"fav-food.org":true,"fav-food.tech":true,"fav-food.us":true}
curl --location --request POST 'https://zylalabs.com/api/5366/domain+status+checker+api/6946/check+name+beast+mode' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"name": "fav food"
}'
This endpoint allows you to check the availability of one or more domains in different TLDs by means of a GET request. It includes the domains in the domains parameter. Ideal for quick and batch queries, it returns the availability status of each domain in JSON format for quick analysis and actions on domain records.
Domain Availability Check - Endpoint Features
| Object | Description |
|---|---|
domains |
[Required] |
domain |
Optional |
{"example.org":false,"foo.com":false,"somefoobardomain.io":true}
curl --location --request GET 'https://zylalabs.com/api/5366/domain+status+checker+api/6947/domain+availability+check?domains=Required' --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 a GET or POST request with the domain to check its availability in seconds.
The API checks the availability of domain names in all TLDs, with multiple query options.
It receives domain names and returns their availability in JSON formats.
Massive availability check for branding campaigns. Quick search for popular names with “Beast mode”. Real-time domain verification for users.
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 POST Check Name Beast Mode endpoint returns a JSON object indicating the availability status of popular domain names across multiple TLDs. The GET Domain Availability Check endpoint returns a JSON object with the availability status for one or more specified domains.
The key fields in the response data include the domain name as the key and a boolean value indicating availability (true for available, false for taken) for each domain checked.
The response data is organized as a JSON object where each domain name is a key, and its availability status (true or false) is the corresponding value, allowing for easy parsing and analysis.
The POST Check Name Beast Mode endpoint requires the "name" parameter in the request body, while the GET Domain Availability Check endpoint uses the "domains" parameter to specify one or more domain names for availability checks.
Users can customize their requests by specifying multiple domain names in the "domains" parameter for the GET endpoint or by selecting a specific popular name for the POST endpoint in Beast Mode, allowing tailored checks based on their needs.
Each endpoint provides information on domain availability across various TLDs. The POST endpoint focuses on popular names, while the GET endpoint allows for broader checks on user-specified domains.
Data accuracy is maintained through real-time checks against authoritative domain registries, ensuring that the availability status returned reflects the most current information available.
Typical use cases include rapid domain availability checks for branding, digital marketing campaigns, and web development projects, enabling users to make informed decisions on domain registration quickly.
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:
2,396ms
Service Level:
100%
Response Time:
2,477ms
Service Level:
100%
Response Time:
194ms
Service Level:
100%
Response Time:
1,579ms
Service Level:
100%
Response Time:
415ms
Service Level:
100%
Response Time:
95ms
Service Level:
100%
Response Time:
134ms
Service Level:
100%
Response Time:
219ms
Service Level:
100%
Response Time:
1,241ms
Service Level:
100%
Response Time:
316ms
Service Level:
100%
Response Time:
1,132ms
Service Level:
100%
Response Time:
891ms
Service Level:
100%
Response Time:
1,261ms
Service Level:
100%
Response Time:
1,461ms
Service Level:
100%
Response Time:
2,581ms
Service Level:
99%
Response Time:
14,190ms
Service Level:
100%
Response Time:
760ms
Service Level:
100%
Response Time:
424ms
Service Level:
100%
Response Time:
10,625ms
Service Level:
100%
Response Time:
7,480ms