Amsterdam · New York · Kyiv
mon.red checks your websites, servers, certificates, domains and cron jobs from three locations, and opens an incident only when they agree something is wrong.
Every check runs from all three locations
Checks
Six kinds of checks cover what your users see, the servers behind it, and the quiet things that expire or stop running without telling anyone.
HTTP status and response time, split into DNS and redirects, connection, TLS handshake and server response. Set the codes you expect and your own warning and fail thresholds.
A text or a regular expression must be on the page, so an error page that still answers 200 OK is caught too.
Is the server alive, and are the ports you need open: mail, databases or anything else on TCP.
Alerts before a certificate or a domain registration runs out, not the morning after.
Know when a domain's name servers (NS) or its IP address change, whether you planned it or not.
Cron jobs, backups and servers call a link when they are done. No signal in time, or a reported failure, means an alert.
Three locations
Every check runs from Amsterdam, New York and Kyiv. An incident opens only when enough locations see the problem, so a bad route somewhere between two data centers does not wake you up.
How many locations must agree, how long to wait and how often to remind you are set per monitor.
Alerts
Decide how soon to hear about a problem, how often to be reminded and whether to be told when it is fixed. Write the messages yourself with templates and placeholders. Every message carries a short link to the incident page.
Planned work
Paused and silenced monitors are marked in the list and never counted as problems.
Stop checking it altogether until you switch it back on.
Checks and history continue during maintenance, incidents stay silent.
History and charts
Dashboard
Plans
Create an account and add your sites and servers. The limits of the plan are shown here.
Free
FAQ
Yes. Enter any address on the start page and test it over HTTP or Ping from all three locations. The result has its own link you can send to anyone; it is kept for 3 days.
From servers in Amsterdam, New York and Kyiv. Every check runs from all of them, as often as every minute.
An incident opens only when enough locations see the problem. For each monitor you choose how many locations must agree, how long to wait before telling you and how often to remind you.
By email, Matrix, Telegram, Slack or Jabber. You write the messages yourself with templates, and each one links to the incident page.
The result of every check from every location is kept for 90 days. Hourly summaries are kept for 2 years.
Pause the monitor, or keep it checked and silence its incidents. Either way it is marked in the list and not counted as a problem.