ToolsStatus page checker
Does your status page do its job?
A status page is only useful if customers can reach it, follow it and read it from their own tools. Enter any public status page to see what it offers.
Checker
We fetch the page and a short, fixed list of common feed and status paths on the same site. We do not store or log the address you enter; we keep only daily totals of how many checks ran and what they found. A result is reused for 5 minutes, held in memory under a one-way hash of the address.
Enter a status page address to check it for HTTPS, a feed, subscription options, a machine-readable status endpoint and how recently it was updated.
Method
What is checked, and how.
HTTPS
The page is served over HTTPS
Checked on the final address after redirects. An HSTS header is reported too.
Feed
An RSS or Atom feed
First a feed linked from the page (link rel="alternate"), then a fixed list of common paths on the same site: /feed, /history.atom, /history.rss, /feed.atom, /feed.rss and /rss.
Subscriptions
Ways to be told
Signals in the page's HTML for email, webhook, Slack, Microsoft Teams and SMS subscriptions. Options a page draws later with JavaScript are not seen, so a missing signal is a prompt to look, not proof.
Status API
A machine-readable status document
A JSON document at /api/v2/status.json, /status.json or /index.json with a status or a timestamp, so customers can poll your status from their own monitoring.
Freshness
When it last said something
The newest date in the feed, or the JSON document's timestamp when there is no feed. A JSON timestamp can be the time the document was generated.
Safety
Public addresses only, small and quick
Every request goes through the same guard Observer uses for outbound webhooks: private, local and cloud metadata addresses are refused, including after a redirect. At most 12 requests, the first 3 MB of the page, 256 KB per probe and 20 seconds in total. Checks are rate-limited per visitor.
Privacy
The address is not kept
The address you enter is used for the check and then discarded. It is not logged or stored. A shared link carries it after the # sign, which browsers never send to a server, and only fills in the field: nothing is checked until the person who opens the link presses Check the page. Observer keeps only daily totals: how many checks ran and how many found each feature.