Active Monitoring
Active Monitoring Active Monitoring is the way to check the site performance by simulation of visiting by real users.

Active Monitoring is the way to check the site performance by simulation of visiting by real users. It is done by external service, usually with distribyted networks. The checking servers create the requests like the real clients, who are trying to download a web page. Doing it on regular schedule, allows to check if the page is available from the web. If not - there is a possibility to catch and report the error. The difference between the bot and a real person is visible only for bulky pages with lots of content - in order to save the traffic, monitoring systems usually download only a part of such pages, which is enough to make sure the site is Ok.

Active monitoring is an independent eye on your site. The checking is not connected to your company and web hosting, and so provides the clear third-party view of the situation. HostTracker service uses active monitoring to supervise web sites.

  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.Downtime
  • CM.Glossary.DistributedMonitoring
  • CM.Glossary.PassiveMonitoring
more glossary
"

Although i'm using the free offering, but it has given me the liberty of alerting system for my landscape

"
- Adam
SSL Certificate Monitoring

For those seeking a possibility to keep SSL certificates always up-to-date and have a constant watch over their expiry dates, there is a Certificate expiration function. Read more: How to activate a Certificate expiration function?

 

For those seeking a possibility to keep SSL certificates always up-to-date and have a constant watch over their expiry dates, there is a Certificate expiration function. Having an effective SSL certificates monitoring should always be one of your main priorities.

How to activate

Simply sign up, go to Add check, then scroll to the bottom of drop-down list, click on Certificate expiration and wait till the Check window pops up prompting you to fill in the form.

Enter the domain name or the list of domain names you want to monitor for certificate expiry and add the task name.

Once this is completed, go to Subscriptions and set the alerting frequency interval. Finally, click on Save. Note that, we’ll contact you on the following events:

  • UP - If a certificate expires in:

    • 30 days (1 month)

    • 7 days (1 week)

    • 1 day

  • DOWN - The day your certificate expires

  • REPEAT - Daily, after your certificates expired, and has not been replaced yet.

Don’t forget to specify the Contact group for notification!

Put tick marks next to the contacts of people, who should be informed in case of any problems.

Note: if you want to be notified not only by email, but also by other messengers (Skype, Viber, Hangouts, Telegram), add them in the "Add Contact" bar or in the "Notifications" menu on the main page screen.

If you have any questions about configuring SSL, please contact our Support: ht2support@host-tracker.com

 

 

more blog
Thank you for feedback!
 
Sign In
Sign Up
Prices & packages
Our monitoring network
Home > Blog > Shellshock

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.

Share:
Send to Twitter Send to Facebook Send to LinkedIn Share on Google+
Blogs:
HostTracker blog HostTracker page on Facebook