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 / Troubleshooting

Allowing our checks through a firewall

If your server sits behind a firewall, a security service or bot protection, it may block our checks. The monitor then says down while the site works for real visitors. This guide explains where checks come from and how to let them through.

Where checks come from

Checks run from our probe servers in the cities listed on the locations page.

A monitor is not checked from one fixed place. A few cities check it each round, taking turns, and more cities check as soon as one sees a problem. So every city on that list can reach your server at some point. If you allow only some of them, the others will report failures.

If you ticked cities under Check from in the monitor's More settings, only those cities check it.

The list of cities changes over time. The locations page shows the current one.

Getting the addresses for an allow-list

The server addresses are not listed in the app. To allow our checks by IP address, email [email protected] and ask for the current list of check addresses. Tell us which monitor types you use.

Because servers are added over time, an IP allow-list needs updating now and then. Where your firewall allows it, the user agent rule below needs less upkeep.

Allowing checks by user agent

Website, keyword, API and page load checks send this user agent with every request:

HonkWatch/1.0 (+https://honkwatch.com/bot)

Many security services and web application firewalls can skip their bot checks for a user agent. Add a rule that allows requests with this user agent to the addresses you monitor.

If you add your own User-Agent line under Request headers, one per line on a monitor, that one is sent instead.

A user agent can be copied by anyone, so allow it only for the pages you monitor, not your whole site, if your tool lets you.

Allowing checks with a header of your own

Website, keyword and API monitors can send extra request headers. You can make up a header with a secret value and tell your firewall to allow requests that carry it.

  1. Open the monitor from your dashboard, press Edit and open More settings.
  2. In Request headers, one per line, add a line such as X-Monitor-Key: a-long-random-value.
  3. Press Save changes.
  4. In your firewall or security service, add a rule that allows requests with that header and value.

Treat the value like a password. Anyone who knows it can get past the rule.

What each monitor type sends

Website, keyword, APIAn HTTP or HTTPS request to the address you entered, with the method you chose (GET unless you changed it).
Page loadThe page itself, then the stylesheets, scripts, images and icons it links to, up to a set number of files. Allow the hosts those files come from too.
Ping3 ping (ICMP echo) packets. Allow ICMP echo requests and replies.
Port (TCP)A connection to the port you entered.
Port (UDP)The packet you entered, to the port you entered.
SSL certificateA secure connection to the host and port, to read the certificate.
DNS recordA DNS query for the name, to the DNS server you entered or, if you left it empty, to the probe's own resolver.
Domain expiryNothing reaches your server. We look the domain up in the registry's public records (RDAP).
Third-party serviceNothing reaches your server. We read the other company's status page.
HeartbeatNothing is sent to you. Your job calls us at https://honkwatch.com/hb/..., so your server needs to be allowed to make outgoing HTTPS requests to that address.

Check that it works

  1. Add the rule in your firewall or security service.
  2. Open the monitor from your dashboard.
  3. Wait for a few rounds of checks, then look at By location. Each city that checked recently should show a response time, not an error. Cities that have not had a turn yet show “Unknown, no recent report”.
  4. If some cities still fail, look at Latest checks for the error and compare those cities with your rule.

When it does not work

  • 403 or 429 status codes. Something is still blocking or rate-limiting the checks. Check your security service's event log for blocked requests at the times shown in Latest checks.
  • Timeouts from some cities only. A firewall that drops traffic often shows as a timeout, not an error. Also check whether your site blocks some countries. See A monitor says down but my site works.
  • “That address can't be monitored”. Only public internet addresses can be checked. Private network addresses, such as 10.x.x.x or 192.168.x.x, are refused.
← I did not get an alert Questions and answers →

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