Skip to content

Features

A status page for your clients

A public status page shows clients whether their websites are up, without logging in or calling support. You choose which websites appear on it, and you can add a public note to an outage explaining what is going on.

Updated 4 Nov 2026

What clients see

The page shows only the websites you select; for visitors, the others don’t exist. Each one has a 90-day uptime bar, uptime for the last 24 hours and the last thirty days, outage history, and optionally the response time. The status refreshes every minute, and the page shows how much of the time the checks covered.

An unconfirmed issue never reaches the status page: until repeated checks confirm an outage, the client sees the last confirmed status (more on the website monitoring page). When the host blocks the checks, the page says uptime isn’t verified rather than claiming the site is down. During a scheduled maintenance window it shows a Maintenance label.

Public notes on outages

The team writes notes on each incident. Notes marked as public appear right on the status page (“We’re looking into the cause with the host and will update you within an hour.”); internal ones stay behind the login.

How to set it up

The Owner manages status pages under Tools → Status pages. You pick the websites and enter a title, and the address is derived from the title, for example /status/client-websites. Before you publish, open the address and check the visible websites and public notes.

The number of status pages depends on the plan: Free 1, Start 5, Profi 100, and Agency 100. Each client can have their own. The steps are in the manual chapter on clients and reports.

Custom domain

A status page can run on the client’s or the agency’s domain, such as status.example.com. In the page settings you save the domain and add a verification TXT record _hlidac.<domain> to DNS. You point an A/AAAA or CNAME record to the address the digiWatcher operator gives you.

Once ownership is verified, the operator connects the domain on the server, certificate included; it isn’t switched on instantly with one button. Ownership is then rechecked regularly: if a recheck fails or there is no fresh proof for 24 hours, the domain is no longer treated as verified. The custom domain serves only the status page and its public data—there is no admin login there.

Uptime badge for the client’s website

Each website on a status page without a password has an image showing its uptime percentage and check coverage, which you can embed on the client’s website or in its footer. The image URL looks like /api/public/badge/<page-address>/<website-number>; the website number is in the address of its details page in the app. The dny parameter sets a different period (up to 90 days) and label sets your own label. The badge currently shows its values in Czech, so set a label in your client’s language.

The badge only shows a website that is really on the public page. For any other, it returns the same “unavailable” answer as for one that doesn’t exist, so nobody can use it to find out what else you monitor.

Password: weak protection, not security

You can lock a status page with a password. The password is sent in the request body, never in the URL, and unlock attempts are rate limited. Even so, it is weak protection: it stops people from stumbling on the page, not a targeted attack. Don’t put anything sensitive on a status page, even a locked one.

If a client needs more than a public overview, give them access to the client portal with their own password. It shows only the websites you select, shared care records, and reports (more on the monthly client reports page).

Email updates for subscribers

Visitors to a public page can enter their email to get a message about an outage and the recovery. The subscription starts only after they confirm their email; the confirmation link is valid for 24 hours and works once. Every message includes an unsubscribe link and reveals neither the internal cause nor the URL of the monitored website.

  • Subscriptions are only available on a page without a password. A locked or disabled page sends no messages.
  • A short outage that ended before the message went out may be skipped. A recovery message only follows an outage message.
  • An account without a paid plan has a daily cap on messages to subscribers.

What it costs

Status pages are part of every plan; only the number differs. Start is €12 a month for 10 websites, Profi €32 for 30 websites, and Agency €66 for 100 websites.

Frequently asked questions

Can each client have their own status page?

Yes. You select different websites for each page, and the plan sets how many pages you can have. The pricing page shows the number for each plan.

Is a password-protected status page safe for sensitive information?

No. The password is weak protection that stops people from stumbling on the page, not a targeted attack. Don’t put anything sensitive on a status page; use the client portal for a more private overview.

Will clients see internal notes on outages?

No. The status page only shows notes marked as public. Internal notes and the technical cause of an outage stay in the admin area.

How quickly can I set up a custom domain?

You save the domain and verify it with a DNS TXT record yourself. The service operator connects it on the server and sets up the certificate after ownership is verified, so expect it not to be instant.

Why can’t visitors subscribe on a locked page?

Subscriptions are only available on public pages without a password. When you lock or disable a page, messages to its subscribers stop.

Try digiWatcher on your own websites

For the first 30 days, you get the Start plan free, with no credit card. Your first payment unlocks email invitations for clients, scheduled email reports, and more than 3 client logins.

Public status page for agency clients | digiWatcher