Whois History Tracker API

"Access historical domain WHOIS data seamlessly with the API, aiding cybersecurity, brand protection, legal investigations, and domain management."

About the API:  

The Whois History Tracker API is an invaluable tool that allows users to access comprehensive historical WHOIS data related to domain names. This API serves as a repository of historical records, offering a wealth of data and insights to individuals and organizations interested in delving into historical information associated with domain name registrations and ownership details.

In essence, the API is designed to facilitate the retrieval of historical WHOIS data, a critical component of Internet governance and domain management. WHOIS data contains vital information about domain registrations, including details about the domain owner's contact information, registration and expiration dates, and details about the domain's host and registrar. This historical data has significant value in a variety of applications, ranging from legal investigations and cybersecurity research to brand protection and domain portfolio management.

One of the most prominent features of Whois History Tracker API is its ability to obtain historical WHOIS records for a specific domain name. This functionality allows users to track changes in domain ownership and contact information over time. This feature is especially beneficial for trademark owners and legal professionals who wish to effectively monitor and protect their intellectual property rights.

The API is designed for seamless integration, making it highly adaptable to a wide variety of applications and systems. Users can easily incorporate it into their existing domain management tools, cybersecurity platforms or legal databases, enhancing their ability to efficiently access and analyze historical WHOIS data.

In summary, the Whois History Tracker API is a versatile and indispensable tool for accessing extensive historical WHOIS data associated with domain names. Its wide range of applications, seamless integration options and the wealth of data it provides make it an invaluable resource for cybersecurity professionals, brand owners, legal experts, domain investors and researchers alike. Whether you're investigating cyber threats, protecting your brand or conducting in-depth market research, this API provides the historical WHOIS insights needed to make informed decisions and proactively address various challenges in the digital landscape.

What this API receives and what your API provides (input/output)?

It will receive parameters and provide you with a JSON.

 

What are the most common uses cases of this API?

  1. Cybersecurity analysis: Investigate domain ownership changes to track malicious activity and cyber threats.

  2. Brand protection: Monitor domain ownership history to safeguard trademarks and brand identity.

  3. Legal investigations: Gather evidence for legal cases related to domain and intellectual property disputes.

  4. Domain portfolio management: Analyze historical data for informed domain asset management.

  5. Market research: Study domain registration trends and industry-specific ownership patterns.

Are there any limitations to your plans?

Besides the number of API calls available for the plan, there are no other limitations.

API Documentation

Endpoints


To use this endpoint you must indicate the URL of a domain and the word historical in the parameters.



                                                                            
GET https://zylalabs.com/api/2623/whois+history+tracker+api/2637/get+historical
                                                                            
                                                                        

Get Historical - Endpoint Features

Object Description
domainName [Required]
whois [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"status":true,"whois":"historical","total_records":"27","whois_domains_historical":[{"num":1,"status":true,"domain_name":"google.com","create_date":"2017-01-30","expiry_date":"2020-09-14","domain_registrar":{"iana_id":"292","registrar_name":"markmonitor inc."},"registrant_contact":{"name":"Dns Admin","company":"Google Inc.","city":"Mountain View","state":"CA","zip_code":"94043","country_name":"United States","country_code":"US","email_address":"dns-admin@google.com","phone":"+1.6502530000"}},{"num":2,"status":true,"domain_name":"google.com","create_date":"1997-09-15","expiry_date":"2020-09-14","domain_registrar":{"iana_id":"292","registrar_name":"markmonitor inc."},"registrant_contact":{"name":"Dns Admin","company":"Google Inc.","city":"Mountain View","state":"CA","zip_code":"94043","country_name":"United States","country_code":"US","email_address":"dns-admin@google.com","phone":"16502530000"}},{"num":3,"status":true,"domain_name":"google.com","query_time":"2023-01-13 19:12:28","whois_server":"whois.verisign-grs.com","create_date":"1997-09-15","update_date":"2019-09-09","expiry_date":"2028-09-13","domain_registrar":{"iana_id":"292","registrar_name":"markmonitor inc.","whois_server":"whois.markmonitor.com","website_url":"http://www.markmonitor.com","email_address":"abusecomplaints@markmonitor.com","phone_number":"+1.2086851750"},"registrant_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"administrative_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"technical_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"name_servers":["ns1.google.com","ns2.google.com","ns3.google.com","ns4.google.com"],"domain_status":["clientDeleteProhibited","clientTransferProhibited","serverDeleteProhibited","serverTransferProhibited","serverUpdateProhibited","clientUpdateProhibited"],"registry_data":{"domain_name":"google.com","query_time":"2023-01-13 19:12:28","whois_server":"whois.verisign-grs.com","domain_registrar":{"iana_id":"292","registrar_name":"MarkMonitor Inc.","whois_server":"whois.markmonitor.com","website_url":"http://www.markmonitor.com","email_address":"abusecomplaints@markmonitor.com","phone_number":"+1.2086851750"},"name_servers":["ns1.google.com","ns2.google.com","ns3.google.com","ns4.google.com"],"domain_status":["clientDeleteProhibited","clientTransferProhibited","serverDeleteProhibited","serverTransferProhibited","serverUpdateProhibited","clientUpdateProhibited"]}},{"num":4,"status":true,"domain_name":"google.com","query_time":"2023-01-16 10:52:20","whois_server":"whois.verisign-grs.com","create_date":"1997-09-15","update_date":"2019-09-09","expiry_date":"2028-09-13","domain_registrar":{"iana_id":"292","registrar_name":"markmonitor inc.","whois_server":"whois.markmonitor.com","website_url":"http://www.markmonitor.com","email_address":"abusecomplaints@markmonitor.com","phone_number":"+1.2083895770"},"registrant_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"administrative_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"technical_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"name_servers":["ns1.google.com","ns2.google.com","ns3.google.com","ns4.google.com"],"domain_status":["clientDeleteProhibited","clientTransferProhibited","serverDeleteProhibited","serverTransferProhibited","serverUpdateProhibited","clientUpdateProhibited"],"registry_data":{"domain_name":"google.com","query_time":"2023-01-16 10:52:12","whois_server":"whois.verisign-grs.com","domain_registrar":{"iana_id":"292","registrar_name":"MarkMonitor Inc.","whois_server":"whois.markmonitor.com","website_url":"http://www.markmonitor.com","email_address":"abusecomplaints@markmonitor.com","phone_number":"+1.2086851750"},"name_servers":["ns1.google.com","ns2.google.com","ns3.google.com","ns4.google.com"],"domain_status":["clientDeleteProhibited","clientTransferProhibited","serverDeleteProhibited","serverTransferProhibited","serverUpdateProhibited","clientUpdateProhibited"]}},{"num":5,"status":true,"domain_name":"google.com","query_time":"2023-01-18 09:19:05","whois_server":"whois.verisign-grs.com","create_date":"1997-09-15","update_date":"2019-09-09","expiry_date":"2028-09-13","domain_registrar":{"iana_id":"292","registrar_name":"markmonitor inc.","whois_server":"whois.markmonitor.com","website_url":"http://www.markmonitor.com","email_address":"abusecomplaints@markmonitor.com","phone_number":"+1.2086851750"},"registrant_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"administrative_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"technical_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"name_servers":["ns1.google.com","ns2.google.com","ns3.google.com","ns4.google.com"],"domain_status":["clientDeleteProhibited","clientTransferProhibited","serverDeleteProhibited","serverTransferProhibited","serverUpdateProhibited","clientUpdateProhibited"],"registry_data":{"domain_name":"google.com","query_time":"2023-01-18 09:19:05","whois_server":"whois.verisign-grs.com","domain_registrar":{"iana_id":"292","registrar_name":"MarkMonitor Inc.","whois_server":"whois.markmonitor.com","website_url":"http://www.markmonitor.com","email_address":"abusecomplaints@markmonitor.com","phone_number":"+1.2086851750"},"name_servers":["ns1.google.com","ns2.google.com","ns3.google.com","ns4.google.com"],"domain_status":["clientDeleteProhibited","clientTransferProhibited","serverDeleteProhibited","serverTransferProhibited","serverUpdateProhibited","clientUpdateProhibited"]}},{"num":6,"status":true,"domain_name":"google.com","query_time":"2023-01-18 12:37:25","whois_server":"whois.verisign-grs.com","create_date":"1997-09-15","update_date":"2019-09-09","expiry_date":"2028-09-13","domain_registrar":{"iana_id":"292","registrar_name":"markmonitor inc.","whois_server":"whois.markmonitor.com","website_url":"http://www.markmonitor.com","email_address":"abusecomplaints@markmonitor.com","phone_number":"+1.2083895770"},"registrant_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"administrative_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"technical_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"name_servers":["ns1.google.com","ns2.google.com","ns3.google.com","ns4.google.com"],"domain_status":["clientDeleteProhibited","clientTransferProhibited","serverDeleteProhibited","serverTransferProhibited","serverUpdateProhibited","clientUpdateProhibited"],"registry_data":{"domain_name":"google.com","query_time":"2023-01-18 12:37:22","whois_server":"whois.verisign-grs.com","domain_registrar":{"iana_id":"292","registrar_name":"MarkMonitor Inc.","whois_server":"whois.markmonitor.com","website_url":"http://www.markmonitor.com","email_address":"abusecomplaints@markmonitor.com","phone_number":"+1.2086851750"},"name_servers":["ns1.google.com","ns2.google.com","ns3.google.com","ns4.google.com"],"domain_status":["clientDeleteProhibited","clientTransferProhibited","serverDeleteProhibited","serverTransferProhibited","serverUpdateProhibited","clientUpdateProhibited"]}},{"num":7,"status":true,"domain_name":"google.com","query_time":"2023-01-25 07:52:06","whois_server":"whois.verisign-grs.com","create_date":"1997-09-15","update_date":"2019-09-09","expiry_date":"2028-09-13","domain_registrar":{"iana_id":"292","registrar_name":"markmonitor inc.","whois_server":"whois.markmonitor.com","website_url":"http://www.markmonitor.com","email_address":"abusecomplaints@markmonitor.com","phone_number":"+1.2086851750"},"registrant_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"administrative_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"technical_contact":{"company":"Google LLC","state":"CA","country_name":"United States","country_code":"US","email_address":"select request email form at https://domains.markmonitor.com/whois/google.com"},"name_servers":["ns1.google.com","ns2.google.com","ns3.google.com","ns4.google.com"],"domain_status":["clientDeleteProhibited","clientTransferProhibited","serverDeleteProhibited","serverTransferProhibited","serverUpdateProhibited","clientUpdateProhibited"],"registry_data":{"domain_name":"goo...
                                                                                                                                                                                                                    
                                                                                                    

Get Historical - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/2623/whois+history+tracker+api/2637/get+historical?domainName=google.com&whois=historical' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

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 Whois History Tracker API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

🚀 Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

Whois History Tracker API FAQs

To use this API you must enter a domain name and the historical keyword.

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.

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.

The Whois History Tracker API is a powerful tool that allows users to access comprehensive historical WHOIS data related to domain names.

The GET Historical endpoint returns historical WHOIS data for a specified domain, including details such as domain name, creation and expiration dates, registrar information, and registrant contact details.

Key fields in the response include "domain_name," "create_date," "expiry_date," "domain_registrar," and "registrant_contact," which provide essential information about the domain's ownership history.

The response data is structured in JSON format, with a main object containing a status, total records, and an array of historical WHOIS records, each detailing specific domain information.

The endpoint provides information on domain ownership changes, registration dates, expiration dates, registrar details, and registrant contact information, useful for various applications.

Users can customize requests by specifying the domain URL and including the keyword "historical" in the parameters to retrieve tailored historical WHOIS data.

The data is sourced from WHOIS databases maintained by registrars and domain authorities, ensuring a comprehensive and reliable repository of historical domain information.

Data accuracy is maintained through regular updates from authoritative WHOIS sources and validation checks to ensure the integrity of the historical records provided.

Typical use cases include cybersecurity analysis to track malicious activities, brand protection to monitor trademark ownership, and legal investigations to gather evidence for disputes.

General FAQs

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). 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 paying by card, just contact us at hello@zylalabs.com

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at hello@zylalabs.com

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

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.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, refer to the ‘X-Zyla-API-Calls-Monthly-Remaining’ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the ‘X-Zyla-RateLimit-Limit’ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.

The ‘X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at hello@zylalabs.com

To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.


Related APIs