Website Uptime Monitoring with SSL and Domain Alerts

What it does

Alerts that mean something

Fewer false alarms, earlier warnings, and a reason with every incident.

🌐

Six monitor types

HTTP(S), HTTP(S) with the status code you choose, a keyword on the page, JSON health checks, TCP port and ping.

⏳

Timeout-tolerant down detection

A busy healthy site can time out once, so a timeout needs two in a row before the monitor goes down. An HTTP error, a DNS failure or a refused connection is called down at once.

🔒

SSL expiry warnings

An alert at 7, 3 and 1 days before a certificate expires, in the colour of the urgency, naming the days left, the expiry date and the issuer.

🏷️

Domain expiry and registry hold

Alerts at 60, 30, 14, 7, 3 and 1 days before a domain expires, and when the registry puts it on hold. If a site stops answering because its domain lapsed, the incident says so.

📊

Availability history

Uptime percentage, downtime, incidents and the longest outage for the last 24 hours, 7 days, 30 days or any month, with a tag on every failure: Timeout, DNS, Connection, HTTP error, TLS, Keyword, Degraded or Domain.

📣

Status pages and PDF reports

Public or private status pages for your clients, and landscape PDF reports for the whole fleet or one host, with incidents and the certificates and domains closest to expiry.

Alerts that reach people

One hub for who hears about what

The Uptime Notification Hub routes Monitor Down with its recovery notice, SSL Expiry and Domain Expiry to the monitor email addresses, the built-in Telegram, WhatsApp and email list, and the channels you own. Already running Uptime Kuma? Import your monitors.

Every client's monitors in one list, filterable by status, type and client
A Domains page lists every domain behind your monitors with registrar, expiry and status
Uptime over the last 30 days on the dashboard and the Control Room wall
Import your existing monitors from Uptime Kuma

AVAILABILITY · LAST 30 DAYSIllustrative data

Uptime99.96%

Incidents2 · longest 11 minutes

What it checks

Sites, APIs, services and the paperwork behind them

HTTP(S)

HTTP status code

Keyword

JSON health check

TCP port

Ping

SSL certificates

Domain registration

Public and private status pages

FAQ

Questions teams
ask us first

Anything else? Ask on the demo.

How often are websites checked?

Every 60 seconds by default, with a timeout you can set for each monitor.

Why did my monitor not go down on the first timeout?

A timeout is weak evidence, because a busy healthy site produces one now and then, so monytr.ai needs two in a row before it calls a site down. Anything stronger, such as an HTTP error, a DNS failure, a refused connection or a missing keyword, is called down immediately.

Can it monitor an API or an internal service?

Yes. Use a JSON health check to read the status fields an API returns, a TCP port check for a service, or ping for a device. JSON checks grade a response as up, degraded or down.

Does it warn me before a domain expires?

Yes. Domain Registration shows the registrar, expiry date, registry status and name servers, with alerts at 60, 30, 14, 7, 3 and 1 days and when the registry puts the domain on hold.

Can my clients see a status page?

Yes. A status page shows the monitors you choose, and it can be public or private to chosen email addresses or domains.

Keep going