What do you actually need to find out?
Each of these pages answers one question in full, with the file in the engine that does the work. This page only exists to point you at the right one.
The symptom, and the page that answers it
| What happened to you | What is actually going on | Where it is answered |
|---|---|---|
| A client called to tell you their site was down. | You found out last, which is a reporting problem before it is a monitoring problem. The fix is that the client sees the same thing you do, without an account. | Client access |
| The site answers 200 and looks wrong anyway. | Something changed in the page: a string that vanished, an error printed inside a valid response, a layout that lost its stylesheet. A status code cannot see any of it. | Page changes |
| It works on your laptop and fails on a phone. | Almost always a certificate whose intermediate the server never sends. Desktop browsers repair it silently, which is why it reaches production. | Certificate monitoring |
| You just want a date, right now, on one name. | Then you do not need any of the above. The free tools answer in one second, no account, and they say what the answer hides. | SSL certificate checker |
These are not three products
Every reading above happens on the same pass, on the same check, at the same interval. There is no certificate add-on and no reporting tier: a site you monitor is read once, and everything on this page is part of that one reading. It is also why the price does not depend on how many of these you use.
What separates monitoring tools, and how to test one goes through the whole pass in order, and the pricing page says what you pay for and what you do not.
Coming from a tool you already pay for? The seven usual suspects in one table, including the rows where they win.
One check, read properly
Unlimited monitors, one price, and the same engine whether we run it or you install it yourself.