Ping (ICMP)
Ping (ICMP) Ping is request message for protocol ICMP.

Ping is request message for ICMP (stands for Internet Control Message Protocol). This protocol is used by different network devices to check if a service or a device is available. Usually it is used for network diagnostics.

Ping monitoring allows you to keep an eye on your network infrastructure. Ping failure means broken connection to a network entity. It is handy to use Ping together with HTTP monitoring. In this case, you get additional information - for example, you know if the error is site-related, or the whole server has gone down. However, sometimes ICMP could be blocked for incoming requests, in order to prevent ddos attacks.

  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.Downtime
  • CM.Glossary.DistributedMonitoring
  • CM.Glossary.HTTP
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
 
Become partner
Sign In
Sign Up
Prices & packages
Our monitoring network
Home > Our monitoring network > Become partner
Datacenter info
Deployment info
Your company info
Share:
Send to Twitter Send to Facebook Send to LinkedIn Share on Google+
Blogs:
HostTracker blog HostTracker page on Facebook