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.

Documentación de la API

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 - Características del Endpoint

Objeto Descripción
domainName [Requerido]
whois [Requerido]
Probar Endpoint

RESPUESTA DE EJEMPLO DE LA API

       
                                                                                                        
                                                                                                                                                                                                                            {"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":"[email protected]","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":"[email protected]","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":"[email protected]","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":"[email protected]","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":"[email protected]","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":"[email protected]","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":"[email protected]","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":"[email protected]","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":"[email protected]","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":"[email protected]","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":"[email protected]","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 - CÓDIGOS DE EJEMPLO


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' 


    

Clave de Acceso a la API y Autenticación

Después de registrarte, a cada desarrollador se le asigna una clave de acceso a la API personal, una combinación única de letras y dígitos proporcionada para acceder a nuestro endpoint de la API. Para autenticarte con el Whois History Tracker API simplemente incluye tu token de portador en el encabezado de Autorización.
Encabezados
Encabezado Descripción
Autorización [Requerido] Debería ser Bearer access_key. Consulta "Tu Clave de Acceso a la API" arriba cuando estés suscrito.

Precios Simples y Transparentes

Sin compromiso a largo plazo. Mejora, reduce o cancela en cualquier momento. La Prueba Gratuita incluye hasta 50 solicitudes.

🚀 PLAN CORPORATIVO A MEDIDA

Comienza en
$ 10.000/Año


  • Volumen Personalizado
  • Límite de solicitudes personalizado
  • Soporte al Cliente Especializado
  • Monitoreo de API en Tiempo Real

Funciones favoritas de los clientes

  • ✔︎ Paga Solo por Solicitudes Exitosas
  • ✔︎ Prueba Gratuita de 7 Días
  • ✔︎ Soporte Multilenguaje
  • ✔︎ Una Clave API, Todas las APIs.
  • ✔︎ Panel de Control Intuitivo
  • ✔︎ Manejo de Errores Integral
  • ✔︎ Documentación Amigable para Desarrolladores
  • ✔︎ Integración con Postman
  • ✔︎ Conexiones HTTPS Seguras
  • ✔︎ Tiempo de Actividad Fiable

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 es como una gran tienda de APIs, donde puedes encontrar miles de ellas en un solo lugar. También ofrecemos soporte dedicado y monitoreo en tiempo real de todas las APIs. Una vez que te registres, puedes elegir qué APIs quieres usar. Solo recuerda que cada API necesita su propia suscripción. Pero si te suscribes a varias, usarás la misma clave para todas, lo que hace todo más fácil para ti.

Los precios se muestran en USD (dólar estadounidense), EUR (euro), CAD (dólar canadiense), AUD (dólar australiano) y GBP (libra esterlina). Aceptamos todas las principales tarjetas de débito y crédito. Nuestro sistema de pago utiliza la última tecnología de seguridad y está respaldado por Stripe, una de las compañías de pago más confiables del mundo. Si tienes algún problema para pagar con tarjeta, contáctanos en [email protected]


Además, si ya tienes una suscripción activa en cualquiera de estas monedas (USD, EUR, CAD, AUD, GBP), esa moneda se mantendrá para suscripciones posteriores. Puedes cambiar la moneda en cualquier momento siempre que no tengas suscripciones activas.

La moneda local que aparece en la página de precios se basa en el país de tu dirección IP y se proporciona solo como referencia. Los precios reales están en USD (dólar estadounidense). Cuando realices un pago, el cargo aparecerá en tu estado de cuenta en USD, incluso si ves el monto equivalente en tu moneda local en nuestro sitio web. Esto significa que no puedes pagar directamente en tu moneda local.

Ocasionalmente, un banco puede rechazar el cargo debido a sus configuraciones de protección contra fraude. Te sugerimos comunicarte con tu banco primero para verificar si están bloqueando nuestros cargos. También puedes acceder al Portal de Facturación y cambiar la tarjeta asociada para realizar el pago. Si esto no funciona y necesitas más ayuda, por favor contacta a nuestro equipo en [email protected]

Los precios se determinan mediante una suscripción recurrente mensual o anual, dependiendo del plan elegido.

Las llamadas a la API se descuentan de tu plan en base a solicitudes exitosas. Cada plan incluye una cantidad específica de llamadas que puedes realizar por mes. Solo las llamadas exitosas, indicadas por una respuesta con estado 200, se contarán en tu total. Esto asegura que las solicitudes fallidas o incompletas no afecten tu cuota mensual.

Zyla API Hub funciona con un sistema de suscripción mensual recurrente. Tu ciclo de facturación comenzará el día en que compres uno de los planes de pago, y se renovará el mismo día del mes siguiente. Así que recuerda cancelar tu suscripción antes si quieres evitar futuros cargos.

Para actualizar tu plan de suscripción actual, simplemente ve a la página de precios de la API y selecciona el plan al que deseas actualizarte. La actualización será instantánea, permitiéndote disfrutar inmediatamente de las funciones del nuevo plan. Ten en cuenta que las llamadas restantes de tu plan anterior no se transferirán al nuevo plan, por lo que debes considerar esto al actualizar. Se te cobrará el monto total del nuevo plan.

Para verificar cuántas llamadas a la API te quedan en el mes actual, revisa el campo 'X-Zyla-API-Calls-Monthly-Remaining' en el encabezado de la respuesta. Por ejemplo, si tu plan permite 1,000 solicitudes por mes y has usado 100, este campo mostrará 900 llamadas restantes.

Para ver el número máximo de solicitudes a la API que permite tu plan, revisa el encabezado de la respuesta 'X-Zyla-RateLimit-Limit'. Por ejemplo, si tu plan incluye 1,000 solicitudes por mes, este encabezado mostrará 1,000.

El encabezado 'X-Zyla-RateLimit-Reset' muestra el número de segundos hasta que tu límite se restablezca. Esto te indica cuándo tu conteo de solicitudes se reiniciará. Por ejemplo, si muestra 3,600, significa que faltan 3,600 segundos para que el límite se restablezca.

Sí, puedes cancelar tu plan en cualquier momento desde tu cuenta, seleccionando la opción de cancelación en la página de Facturación. Ten en cuenta que las actualizaciones, degradaciones y cancelaciones tienen efecto inmediato. Además, al cancelar ya no tendrás acceso al servicio, incluso si te quedaban llamadas en tu cuota.

Puedes contactarnos a través de nuestro canal de chat para recibir asistencia inmediata. Siempre estamos en línea de 8 a. m. a 5 p. m. (EST). Si nos contactas fuera de ese horario, te responderemos lo antes posible. Además, puedes escribirnos por correo electrónico a [email protected]

Para darte la oportunidad de probar nuestras APIs sin compromiso, ofrecemos una prueba gratuita de 7 días que te permite realizar hasta 50 llamadas a la API sin costo. Esta prueba solo se puede usar una vez, por lo que recomendamos aplicarla a la API que más te interese. Aunque la mayoría de nuestras APIs ofrecen prueba gratuita, algunas pueden no hacerlo. La prueba finaliza después de 7 días o cuando realices 50 solicitudes, lo que ocurra primero. Si alcanzas el límite de 50 solicitudes durante la prueba, deberás "Iniciar tu Plan de Pago" para continuar haciendo solicitudes. Puedes encontrar el botón "Iniciar tu Plan de Pago" en tu perfil bajo Suscripción -> Elige la API a la que estás suscrito -> Pestaña de Precios. Alternativamente, si no cancelas tu suscripción antes del día 7, tu prueba gratuita finalizará y tu plan se cobrará automáticamente, otorgándote acceso a todas las llamadas a la API especificadas en tu plan. Ten esto en cuenta para evitar cargos no deseados.

Después de 7 días, se te cobrará el monto total del plan al que estabas suscrito durante la prueba. Por lo tanto, es importante cancelar antes de que finalice el periodo de prueba. No se aceptan solicitudes de reembolso por olvidar cancelar a tiempo.

Cuando te suscribes a una prueba gratuita de una API, puedes realizar hasta 50 llamadas. Si deseas realizar más llamadas después de este límite, la API te pedirá que "Inicies tu Plan de Pago". Puedes encontrar el botón "Iniciar tu Plan de Pago" en tu perfil bajo Suscripción -> Elige la API a la que estás suscrito -> Pestaña de Precios.

Las Órdenes de Pago se procesan entre el día 20 y el 30 de cada mes. Si envías tu solicitud antes del día 20, tu pago será procesado dentro de ese período.


APIs Relacionadas