The service, in detail

This page is the plain description of what WebTime Viewer does for every monitor you create, and what it does not do. The numbers are how the service is built. The limits of each plan are on the pricing page.

Every monitor is checked at the interval you chose, around the clock. The scheduler runs every minute of every day on our server and checks each monitor that is due. The fastest interval you can choose is the one your plan allows (one, three or five minutes); you may always choose a slower one. Checks run from a single location.

A website or API check is one HTTP or HTTPS request to your URL, following up to five redirects, with a timeout of up to 30 seconds. We record the status code, the response time, whether the keyword you asked for was found (or absent, if that is what you asked), and a short description of any error. We do not store the page itself.

A certificate monitor makes one TLS handshake a day and reads the certificate's expiry date. A domain monitor makes one RDAP lookup a day to the public registry for the domain's expiry date. Both warn you 30, 14, 7, 3 and 1 days before expiry, once per threshold.

A heartbeat monitor is the reverse: we give you a URL, your scheduled job calls it when it finishes, and if the call does not arrive within the period you set plus a grace period, an incident opens. Heartbeats are available on every plan and count towards your monitor limit.

Two consecutive failed checks open an incident; one successful check closes it. A single failed check never alerts anyone. On a one-minute plan that means roughly two minutes from the first failure to the email.

Alerts are email only. They go to the addresses you add, each of which must confirm itself by clicking a link we send before it receives anything, up to the number of addresses your plan allows. Until you add one, alerts go to your account address. Every alert names the monitor, what failed, when it started and what the response was.

Cadence: one message when an incident opens, at most one an hour while it continues, never more than six for one incident, and one message when it resolves with the total downtime. Alerts depend on this site's email service being configured; if delivery is interrupted the dashboard says so.

Detailed check results are kept for the number of days your plan includes and are then deleted. Daily uptime — one summary per monitor per day — is kept for as long as your account exists, regardless of plan, so a status page keeps its record after the detailed checks are gone. On an unlimited plan detailed results are kept for 365 days.

A public status page, on the plans that include one, lives at an address you choose and needs no login to view. It shows the display name you give each monitor, its current state, its uptime over the last 30 days, a 90-day bar per monitor and the incident history with any notes you write. It never shows the URL or hostname being checked. Unpublishing removes it immediately.

You may only monitor sites, APIs and services you own, operate or are authorised to monitor, and the service is built so it cannot be turned into a scanning tool:

The full rules, including fair use on unlimited plans and how to ask us to stop checking a site you operate, are in our Acceptable Use Policy.

Everything is managed from your dashboard after you log in: add, pause, edit and delete monitors; add and confirm alert addresses; publish or unpublish your status page; and see your plan, card on file and receipts on the account page. Every plan is a recurring monthly subscription except the Day Pass, a single charge for 24 hours. We email you 5 to 7 days before each renewal and a receipt after every successful charge. To cancel, open Easy to Cancel from the footer of any page — no login needed, just the email on your account and the last four digits of your card: it stops all future charges immediately, you keep access until the end of the paid period, and we confirm by email. Refund requests within 30 days of any charge are honoured in full under our Refund & Cancellation Policy.