Distributed Monitoring
Distributed Monitoring Distributed monitoring is a method of website monitoring when the checking is performed from several locations.

Distributed monitoring is a method of website monitoring when the checking is performed from several locations. The main purpose for this is to exclude errors of checking server (which is always possible) from the site statistic and provide more precise result. Usually it is realized through the network of independent servers which check the sites one-by-one or simultaneously. The advangtages of such checks are listed below:

Checks are happening from different locations, just like the real users do.

If a single check fails - others may prove or decline the failure. So, probability of false downtimes is really low.

It is possible to overview the access and download speed from different countries and cities.

Possibility to catch network-related or DNS problems: site might be visible from your computer, but are you sure it works for everyone?

  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.Availability
more glossary
"

Seems like a great service when you are having problems with your host.

"
- jay
Blacklisted again? Why does this keep happening to me?!

We’re happy to announce that this tool has just got even more awesome! Now you can use our DNSBL check tool as a one-time job or on a regular basis. It means you can keep your IP address in a continuous check against dozens of the most popular blacklists. 

Previously, we have introduced one of the “Check site instantly ” board functions -  DNSBL - which helps you find out whether your server is blacklisted before it gets out of control.

We’re happy to announce that this tool has just got even more awesome! Now you can use our DNSBL check tool as a one-time job or on a regular basis. It means you can keep your IP address in a continuous check against dozens of popular blacklists. 

This can significantly ease your website’s life online, moreover, bring balance into it.

New options

With the new extension of the DNSBL check tool, it's become easier to test your website accessibility, as well as, server message deliverability.

For example, suppose your IP address is currently on the DNSBL monitoring. The moment your website is found blacklisted, our system will report back to you all the detailed information on the check results - the name of the blacklist (which one of the DNS-based anti-spam lists recognize you as a source of spam activity) and the reason for listing (this information is public and provided directly by DNSBL databases).

All this will allow you to quickly clean up “the mess”, speed up the process of domain removal (delisting), protect your business reputation and, by extension, prevent recurrence of such a problem in the future.

HostTracker, as a website monitoring service, always keeps moving forward - our list of DNSBL servers is constantly updated.

The whole setup process will take you only a few minutes to complete:

Some Secrets of Activating Blacklist Monitoring

The good news is that you’re opted to activate the DNSBL check for already existing monitoring tasks. All you need to do is to put a tick mark in the box next to “DNSBL check” field when editing or adding a check task.

Once enabled, HostTracker starts gathering information about your website availability and checking whether your IP is currently listed. A Contact Group for notifications will be automatically added to the current test task. If our system finds your server blacklisted, you’ll immediately receive a message with the relevant information.

We hope that with such a tool you’ll enjoy the convenience, simplicity and quality of our all-in-one monitoring service. If you have any questions or suggestions, feel free to contact us - we’re always looking for ways to improve! 

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
Blogs:
HostTracker blog HostTracker page on Facebook