Skip to content
HonkWatch
PricingLocationsHonk RadarHelpAPI Log inGet started
All help topics

Getting started

  • Getting started
  • How checks work

Monitors

  • Which monitor to use
  • Website monitor
  • API monitor
  • Keyword monitor
  • Ping monitor
  • Port monitors (TCP and UDP)
  • DNS monitor
  • SSL certificate monitor
  • Domain expiry monitor
  • Third-party services
  • Page load monitor
  • Heartbeat monitor (cron jobs)
  • Maintenance windows
  • Incidents

Alerts

  • Setting up alerts
  • Email alerts
  • Slack
  • Microsoft Teams
  • Discord
  • Telegram
  • PagerDuty
  • ntfy
  • Webhooks
  • Zapier

Phone and desktop app

  • The phone and desktop app
  • App alerts not arriving

Status pages

  • Status pages
  • Status page on your own domain

Team and account

  • Team members
  • Plans and limits
  • API keys and the API
  • Your account

Troubleshooting

  • A monitor says down but my site works
  • I did not get an alert
  • Allowing our checks through a firewall
  • Questions and answers

Help / Monitors

Website monitor

A website monitor requests a web address from our checking cities and checks that it answers with a good status code before the timeout. It also records how long the answer took and, for https:// addresses, how many days the certificate has left.

What you need first

  • The full address of the page, for example https://example.com/ or https://example.com/login.
  • The page must be reachable from the public internet without a VPN. If a firewall only lets known addresses in, see Allowing our checks through a firewall.
  • At least one alert channel with Down ticked. New accounts start with one, for their own email address. See Setting up alerts.

Set it up

  1. Open Monitors and press Add monitor.
  2. Pick Website (HTTP/HTTPS).
  3. Type the address into URL. If you leave out http:// or https://, we use https://.
  4. Give it a Friendly name. Alerts use this name.
  5. Choose Check every. The list shows only the intervals your plan allows.
  6. Press Start monitoring.

The defaults suit most sites. You only need More settings if the page needs something special.

More settings

SettingDefaultWhat it does
MethodGETThe request method: GET, HEAD, POST, PUT, PATCH, DELETE or OPTIONS. Until you confirm your email, only GET and HEAD work.
Good status codes200-399Any other code counts as a failure. Write single codes and ranges separated by commas, like 200-299,301.
Follow redirectsOnWhen on, we follow redirects and judge the final page. When off, the redirect itself is the answer, so its code (such as 301) must be in your good status codes.
Request headers, one per lineNoneFor example Authorization: Bearer .... Headers that would change where the request goes, such as Host or X-Forwarded-For, are left out. If a redirect sends us to another host, your headers are not passed on to it.
Request bodyNoneSent with POST, PUT and PATCH only.
Timeout (seconds)10How long to wait for an answer, 1 to 30.
Alert when slower than (ms, optional)OffSends a slow alert when the average time of the recent good checks goes over this. Tick Alert when any single location is slower to use the slowest city instead.
Warn before certificate expiry (days)14For https:// addresses: a certificate warning when fewer days are left.
Down when this many locations agree2How many cities must see the failure.
Each of them after this many failed checks in a row21, 2 or 3. Two ignores one-off blips.
Check fromAll cities, taking turnsTick cities to use only those. Your plan sets how many you can tick.
Repeat the down alert every (minutes, 0 = once)0Reminders during a long outage, at least 5 minutes apart. They stop when someone acknowledges the incident.

How checks work explains the down rule in detail.

Test it

  1. After saving, stay on the monitor's page. It says "Waiting for the first check", then "Working" once results come in.
  2. The response time chart fills in as checks arrive. It starts on All locations; pick Average or one city from that list to see other views.
  3. To test the alert itself, open Alerts and press Send test next to a channel. This sends a real message from a "Test monitor".

When it does not work

  • "That address can't be monitored". The address is private or internal, such as localhost or a 192.168. address. Only public internet addresses work.
  • Down with "HTTP 403" or "HTTP 429". The site, or a firewall or bot protection in front of it, is turning our checks away. Allow our checks through (see Allowing our checks through a firewall), or check a page that is not protected.
  • Down with "HTTP 301" or "HTTP 302". Follow redirects is off and the code is not in your good status codes. Turn redirects back on, or use the final address.
  • Down with "HTTP 401". The page needs a login. Add the header it needs under Request headers, or check a public page.
  • Down with a timeout. The page took longer than the timeout. Raise Timeout (seconds) if the page is slow but working.
  • Down from one part of the world only. Some sites block whole countries. Under Check from, tick only the cities your visitors use.
  • Down, but the site works for you. See A monitor says down but my site works.
  • No alert arrived. See I did not get an alert.
← Which monitor to use API monitor →

Still stuck? Email [email protected] and say which guide you were following.