Website monitoring
Website monitoring Website monitoring is an automated process of checking availability of a site.

Website monitoring is an automated process of checking availability of a site. The main goal of it is evaluation of possibility to access the site by clients. It is clear, that a site is efficient when an interested person can load the page and make a purchase or look for some information. If this action fails for some reason - the site does not execute its mission, and a client will find what he needs somewhere else.

There are many solutions of this problems, and all of them could be divided into passive and active ways. The result of monitoring is the value of uptime, measured with some accuracy. Having it, one can conclude how long is the site broken during some period of time (usually, for a year). Low uptime usually means that the server where the site is hosted, or internet connection to it, is unreliable and is required to be changed.

  • CM.Glossary.Uptime
  • CM.Glossary.Downtime
  • CM.Glossary.ActiveMonitoring
  • CM.Glossary.PassiveMonitoring
  • CM.Glossary.Availability
more glossary
"I have been using your service to monitor my site and it's a very good tool."
- Fatima
Shellshock vulnerability online 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 blog
 
Terms and Conditions
Sign In
Sign Up
Prices & packages
Our monitoring network
Home > Terms and Conditions

Limitation on Liability

  • The Company makes every effort to provide accurate and uninterrupted Service and solve all contingency problems with the Service, if these should occur. However, the Company is not responsible for incidental or consequential damages, loss of profit or any other negative consequences connected with the use of the Service

Service Suspension

  • The Company reserves the right to suspend service to a User with no explanation of the reason.

Refund

  • In case the User is not satisfied with the quality of the service provided by the Service in the current or previous month, the Company will pay back all amounts received from the User for the period in question, at his/her first request sent to the Company via e-mail.

Confidentiality of Registration Information

  • The Company does not disclose personal information provided by the User upon registration to any third parties.

Cookies

  • Cookies are employed by the Service for user identification and authentication.

Session Log

  • When a User is working with the Service Site, information about the Site pages visited by the User is being logged. This information is used to improve the functionality of the Service.
Share:
Send to Twitter Send to Facebook Send to LinkedIn Share on Google+
Blogs:
HostTracker blog HostTracker page on Facebook