Discover your perfect domain name with our Domain Availability API. Get personalized suggestions and find the ideal match for your website. By default, we provide 5 domain suggestions, but by signing in and setting 'suggestion' to true, you can fetch up to 100 domain suggestions.
Check the availability of multiple domains effortlessly with our user-friendly API. Ideal for businesses, it saves time and effort by quickly checking domain availability in bulk, streamlining your domain management process.
Stay updated with the latest domain information through real-time data synchronization, ensuring your queries are accurate and relevant. This feature guarantees that you always have the most current domain data at your fingertips.
We support data retrieval in JSON and XML formats, providing flexibility and compatibility with various applications and systems. This ensures seamless data integration and processing for your needs.
{ "domainNames":[ "jfreaks.pk", "whoisfreaks.com" ] }
{ "tld":[ "com", "pk" ] }
Our Domain Availability API checks if a domain is available for registration or not. It also suggests other domains and their availability for registration.
Domains are suggested based on a GTLDs that are more popular in terms of higher number of domains registered with that particular TLD.
Bulk Domain Availability API allows you to check domain availability of multiple domains in a single request. A maximum of 100 domains can be sent in a single request. Moreover, it generates suggestions based on custom TLDs.
Bulk Domain Availability API response takes from 16 seconds to 1 minute for 100 domains.
We will provide 500 API credits to new users and yes, those credits have a rate-limiting of 10 requests per minute for Live APIs, 5 requests per minute for Bulk Domain Lookup, and 1 request per minute for Reverse/Historical Endpoints.
Yes, we have rate limiting on requests being made on all of our paid plans. The requests limit is shown in the following table.
The Table is divided into three types of plans:
Credits | Live-rpm | Bulk-rpm | Historical/Reverse-rpm |
---|---|---|---|
5000 | 20 | 8 | 3 |
15000 | 35 | 12 | 5 |
50000 | 80 | 20 | 10 |
150000 | 120 | 25 | 15 |
450000 | 150 | 35 | 20 |
1000000 | 200 | 50 | 25 |
3000000 | 300 | 70 | 35 |
Credits | Live-rpm | Bulk-rpm | Historical/Reverse-rpm |
---|---|---|---|
5000 | 20 | 8 | 3 |
15000 | 35 | 12 | 5 |
50000 | 80 | 20 | 10 |
150000 | 120 | 25 | 15 |
450000 | 150 | 35 | 20 |
1000000 | 200 | 50 | 25 |
3000000 | 300 | 70 | 35 |
In case, the request per minute exceeds, it'll throw an error with HTTP error code of 429.
Yes, there are following three header parameters in the response: