Documentation forPingdom

TLS SSL and encryption protocols for Pingdom HTTP Uptime checks

This article applies to the HTTP(S) Uptime checks only

The way we try different protocols to use works like this:

  1. Start with TLS1.*
  2. If a TLS error is returned we then move on to...
  3. SSLv3 and if that fails
  4. An SSL/TLS error is logged if all these fail and a second opinion is conducted.

Our probes support most ciphers used:

  1. TLS1.1
  2. TLS1.2
  3. TLS 1.3
  4. TLS1.0
  5. SSLv3

We still use SSL version 3 to make requests at times because many servers out there still expect this and will break if another protocol is used.

What this means, in reality, is that if your site has any sort of error page when specific encryption is used, instead of asking to renegotiate, it might fail from our end.

Our Root cause analysis tool is running HTTP 1.0 at the moment and is thus somewhat outdated when it comes to certain pages. 

Navigation Notice: When the APM Integrated Experience is enabled, Pingdom shares a common navigation and enhanced feature set with other integrated experience products. How you navigate Pingdom and access its features may vary from these instructions.