Questions.

Websites and APIs over HTTP, TCP ports for VPNs and gateways, DNS records, TLS certificates, domain registrations, heartbeats for scheduled jobs, mail health, an office or ISP link, certificate transparency logs, and certificates or statuses reported from places hostnag can't reach on its own. Eleven monitor types in all, covering anything with an address.

Pick from six presets: 1, 5, 15, 60, 360 or 1440 minutes. Free floors at 5 minutes for uptime-style monitors and 1440 for expiry ones; Pro drops that to 1 and 60, Business to 1 and 15. Certificate transparency stays at 1440 minutes, once a day, on every plan, because crt.sh is rate limited.

Four locations: US East, US West, Frankfurt and Tokyo. Free watches from one of them, Pro from up to three, Business from all four.

No. hostnag runs from the cloud with nothing installed on your side, so "ping" means TCP reachability on a port you name, not an ICMP echo.

Not directly. Private and loopback addresses are refused as both targets and resolvers, on purpose. A host the cloud can't reach can report its own status through a status report URL or the Beacon script, both fed from the inside.

15 seconds for uptime-style monitors like HTTP, TCP, DNS and links. Expiry monitors, certificates and domain registrations, get 30 seconds, since RDAP and TLS handshakes can run slower.

Yes, from UptimeRobot, Better Stack, Pingdom, Uptime Kuma or a CSV file. hostnag previews every candidate first and creates monitors up to your plan's limit; an API key or token is used once to fetch the list and is never stored.

No. A failure needs to be confirmed, either a second location seeing it or a second consecutive run, before hostnag opens an alert. One flaky result from one place is never enough to nag anyone.

30, 14, 7, 3 and 1 days out by default, and you can change them per group. The final window repeats daily, so a certificate or domain close to lapsing never falls out of view.

Nine kinds: email on every plan, plus Slack, Discord, Teams, Telegram and webhook on Pro, plus SMS, PagerDuty and Opsgenie on Business. Set them up once for the org and route them per group.

Yes, both for a whole group and for a single monitor, and you can also set quiet hours on your own timezone. Alerts that go unacknowledged escalate through up to three tiers, each after its own number of minutes, until someone acknowledges from inside the alert.

Yes. A recovery notice goes out the moment a monitor clears, carrying how long it was down for, so the story is complete without opening the app.

JSON at version 3, with the group and the details of what happened, signed with x-hostnag-* headers so you can verify it came from hostnag. Any breaking change bumps the version number.

Uptime and expiry for the monitors you choose, updated at most a minute behind live, never the actual targets or error strings. Visitors can subscribe by email, and every page and monitor gets its own SVG badge.

Yes, one per group, emailed to owners and admins on the 1st. You can set an SLA target for it; Pro keeps 3 months of reports, Business keeps 12.

Five monitors in one group, one seat, checks every 5 minutes from one location, email alerts, and 30 days of history. It costs nothing and needs no card to start.

From inside the app, any time. hostnag hands you off to Stripe Checkout and the new plan applies as soon as it completes.

Monitors over the new plan's limit are paused, not deleted. Turn them back on, or upgrade again, and nothing about them was lost.

Yes, from the Stripe Customer Portal, whenever you like. There's no minimum term and no call required.

No. The Free plan needs no card at all; you only reach Stripe Checkout when you choose to upgrade.

One seat on Free, five on Pro, twenty five on Business. Every seat can be an owner, admin, member or viewer.

Yes, an authenticator app plus one-time recovery codes. An org can require it for every owner and admin, so the policy isn't left to individual habit.

Yes, a list of every active session. Sign one out on its own, or end everything else at once from a single device.

In Supabase Vault; hostnag's own database only ever holds a reference to them, never the value. Custom HTTP headers on a monitor are the one exception, stored in plaintext, and the form tells you so before you type one in.

The data lives on Supabase in us-east-1; the watching itself runs on Vercel, dialing out from whichever locations you've picked.

30 days on Free, 90 on Pro, 365 on Business. Older results roll off; nothing pages you for data that's already aged out.

Two plain scripts, beacon.sh and beacon.ps1, plus one config file you write yourself. Nothing is installed as a service, nothing signs itself, and nothing updates on its own; you can read every line before you run it.

Download the script to a path you choose, add one config line per door you want it to knock on, a ping, a status, or a certificate, and schedule it yourself with cron or Task Scheduler. The Beacon dialog on the group page writes the config for you.

Delete the two files, the script and its config. There's no uninstaller and nothing left behind.

Yes, pass --verbose (-Verbose on Windows) and it prints one line per config line that reached a door, then a final count of how many succeeded and how many failed. Left off, a working run stays silent, the way a scheduled job should.