Cómo activar API para su cuenta Host-Tracker

HostTracker API utiliza formatos ampliados XML y JSON. Las interacciones con API se realizan mediante los métodos HTTP GET, POST, PUT, DELETE, PATCH.

Para activar API para su cuenta de HostTracker, debe escribir una solicitud a  ht2support@host-tracker.com, especificando su cuenta.

API significa "interfaz de programación de aplicaciones" (en Inglés - "application programming interface"). Es una de las características del servicio de monitoreo del sitio web de HostTracker, que se implementa en una lista preestablecida de solicitudes HTTP y respuestas HTTP para mantener y ajustar las características de HostTracker para su conveniencia. Proporciona la posibilidad de desarrollar aplicaciones que cooperarán automáticamente con el servicio HostTracker, en lugar de ajustes manuales a través de la interfaz de usuario.

HostTracker API utiliza formatos ampliados XML y JSON. Las interacciones con API se realizan mediante los métodos HTTP GET, POST, PUT, DELETE, PATCH.

Para activar API para su cuenta de HostTracker, debe escribir una solicitud a  ht2support@host-tracker.com, especificando su cuenta.

Descripción de ​REST API:

https://www.host-tracker.com/api/web/help.html

Descripción de SOAP API:

www.host-tracker.com/api/soap/v1/help.html

more blog
¡Gracias por su atención!
 
Iniciar sesión
Crear una cuenta
Precios y planes
Nuestra red
Home > Blog
Shellshock vulnerability online check (English)

Considering the recently discovered Shellshock vulnerability, HostTracker has created a tool for testing it.

Check your server for vulnerability

How does it work?

It is developed for a Linux server with a web server installed on it. The algorithm is very simple. We consequently generate 4 http requests:

  • 1. Ordinary request
  • 2. The request tries, using vulneratility, post a "harmful" cookie which causes 2-seconds delay in respond to our special http request.
  • 3. The request tries, using vulneratility, post a "harmful" cookie which causes 4-seconds delay in respond to our special http request.
  • 4. Same as #3

How to understand the result?

We compare response time for all 4 requests. Three situation are possible:

  • 1. Vulnerability found. We may affirm that if the difference in responses is about 2 seconds for requests without cookie and with 2-second-delay cookie, as well as for requests with 2 and 4-second delay cookie. It means that our request was able to use the vulnerability and set these cookies.
  • 2. Vulnerability not found. All the requests have about the same response time. The cookies, likely, were not installed because there is no vulnerability.
  • 3. Uncertain situation. If the response time differs widely, without coincidence with preset by cookies delay, we can not say for sure. It could be if the server is under high load. To check this, we use two requests with same cookies (#3 and #4). If the response time for two same checks varies, we make a conclusion that the response time is not affected by cookies. At least, not only by them. So in this case our method can not detect vulnerability

Safety of checks

Our test can not damage your server. The risk consists of appearance of one extra-cookie, which is used only for our requests and can not affect normal work-flow of your site.

more
Shellshock vulnerability check (Русский)

Considering the recently discovered Shellshock vulnerability, HostTracker has created a tool for testing it.

Check your server for vulnerability

How does it work?

It is developed for a Linux server with a web server installed on it. The algorithm is very simple. We consequently generate 4 http requests:

  • 1. Ordinary request
  • 2. The request tries, using vulneratility, post a "harmful" cookie which causes 2-seconds delay in respond to our special http request.
  • 3. The request tries, using vulneratility, post a "harmful" cookie which causes 4-seconds delay in respond to our special http request.
  • 4. Same as #3


Results of the test

How to understand the result?

We compare response time for all 4 requests. Three situation are possible:

  • 1. Vulnerability found. We may affirm that if the difference in responses is about 2 seconds for requests without cookie and with 2-second-delay cookie, as well as for requests with 2 and 4-second delay cookie. It means that our request was able to use the vulnerability and set these cookies.
  • 2. Vulnerability not found. All the requests have about the same response time. The cookies, likely, were not installed because there is no vulnerability.
  • 3. Uncertain situation. If the response time differs widely, without coincidence with preset by cookies delay, we can not say for sure. It could be if the server is under high load. To check this, we use two requests with same cookies (#3 and #4). If the response time for two same checks varies, we make a conclusion that the response time is not affected by cookies. At least, not only by them. So in this case our method can not detect vulnerability

 

Safety of checks

 

Our test can not damage your server. The risk consists of appearance of one extra-cookie, which is used only for our requests and can not affect normal work-flow of your site.

more
Compartir:
Enviar a Twitter Enviar a  Facebook Enviar a LinkedIn Compartir en Google+
Blogs:
HostTracker blog HostTracker page on Facebook