The Web Domain Registration Verification API is meticulously crafted to furnish intricate details regarding domain names and their registrants. By interfacing with the WhoIS database, it retrieves extensive data concerning domain ownership, registration specifics, and administrative contacts. Boasting an intuitive interface and robust capabilities, this API empowers users to swiftly and efficiently procure vital insights into any domain name.
At its core, the Web Domain Registration Verification API offers a streamlined yet potent method of querying the WhoIS database. Users input their domain of interest, prompting the API to promptly extract pertinent registration details from the WhoIS repository.
A standout feature of the Web Domain Registration Verification API is its real-time data updates, ensuring users receive precise and dependable information for their inquiries. This enables informed decision-making regarding domain ownership and registration.
In essence, the Web Domain Registration Verification API emerges as a versatile and indispensable tool for individuals seeking comprehensive insights into domain names and their registrants. With its wealth of data, instantaneous access, and robust functionality, the API facilitates informed decision-making, risk mitigation, and effective safeguarding of online assets across diverse industries.
It will receive a parameter and provide you with a JSON.
1,500 requests per day and 20 requests per minute in all plans.
To use this endpoint you must indicate the name of a domain in the parameter.
Object | Description |
---|---|
domain |
[Required] Indicates a URL |
{"domain_name": ["twitter.com"], "registrar": "csc corporate domains, inc.", "whois_server": "whois.corporatedomains.com", "updated_date": [1705453805, 1705471805], "creation_date": [948472097, 948454097], "expiration_date": 1737476897, "name_servers": ["a.r06.twtrdns.net", "d.r06.twtrdns.net", "c.r06.twtrdns.net", "b.u06.twtrdns.net", "a.u06.twtrdns.net", "c.u06.twtrdns.net", "b.r06.twtrdns.net", "d.u06.twtrdns.net"], "emails": ["[email protected]", "[email protected]", "[email protected]"], "dnssec": "unsigned", "name": "twitter, inc.", "org": "twitter, inc.", "address": "1355 market street", "city": "san francisco", "state": "ca", "zipcode": "94103", "country": "us"}
curl --location --request GET 'https://zylalabs.com/api/3887/web+domain+registration+verification+api/4589/whois+information?domain=twitter.com' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Web Domain Registration Verification API REST API, simply include your bearer token in the Authorization header.
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
Users must enter the URL of a domain to obtain registration information.
The Web Domain Registration Verification API allows users to retrieve information from the Whois database for a given domain name.
There are different plans to suit all tastes, including a free trial for a small number of requests, but your rate is limited to avoid abuse of the service.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Service Level:
100%
Response Time:
1,070ms
Service Level:
100%
Response Time:
117ms
Service Level:
100%
Response Time:
520ms
Service Level:
100%
Response Time:
530ms
Service Level:
100%
Response Time:
1,568ms
Service Level:
100%
Response Time:
1,115ms
Service Level:
100%
Response Time:
431ms
Service Level:
100%
Response Time:
2,074ms
Service Level:
100%
Response Time:
477ms
Service Level:
47%
Response Time:
726ms
Service Level:
100%
Response Time:
3,780ms
Service Level:
100%
Response Time:
1,088ms
Service Level:
100%
Response Time:
1,342ms
Service Level:
100%
Response Time:
640ms
Service Level:
100%
Response Time:
1,077ms
Service Level:
100%
Response Time:
1,178ms
Service Level:
100%
Response Time:
731ms