- Open New monitorGo to Monitors and choose "New monitor".
- Choose HTTP(S)Under Check type, select HTTP(S).
- Enter name and URLType a Name and the full public URL, including https://.
- Add an expected keyword (optional)With the GET method, enter text in "Expected keyword (optional)". The check fails unless the response body contains it.
- Set interval and timeoutUnder Schedule, set the Check interval (seconds) and Timeout (seconds) within your plan limits.
- Create the monitorChoose "Create monitor". The first result usually arrives within one interval.
An HTTP(S) monitor requests a URL on a schedule and checks the status code, an optional keyword and the TLS certificate. It is available on every plan, including Free.
Fill in the basics
- Name: how the monitor appears in lists, alerts and status pages.
- URL: a public
http://orhttps://URL. If the URL has a query string that may contain a token, the field is masked; tick Show the full URL to see it. Lists and alerts show only the host. - HTTP method: GET by default. HEAD is also available on Free. Other methods (POST, PUT, PATCH, DELETE, OPTIONS) need Starter; see advanced HTTP checks.
- Tags (optional): comma-separated, lowercase letters, digits,
-or_, up to 10. Tags are used for alert routing and filters.
Check for a keyword
A keyword check catches pages that return 200 but show an error. With the GET method, enter text in Expected keyword (optional). The check fails unless the response body contains that text, as a plain substring. Pick something that only appears when the page works, such as a product name in the footer or "status":"ok" in an API response.
To fail when text is present (for example "Maintenance mode"), use a "Body does not contain text" assertion, which is part of advanced HTTP checks on Starter.
Set the schedule
Check interval (seconds) accepts 15 to 3,600 seconds, but not faster than your plan allows: 300 seconds on Free, 60 on Starter, 30 on Team. Timeout (seconds) accepts 1 to 30 seconds and must be at least 2 seconds shorter than the interval.
What every HTTP check measures
- Status code: 2xx and 3xx count as up by default. Custom ranges such as 200–299 only are a Starter feature.
- Redirects: followed automatically, up to 5 hops. Each redirect target is re-validated.
- Response time: recorded with a DNS, connect, TLS and time-to-first-byte breakdown.
- TLS certificate: an invalid, expired, untrusted or wrong-hostname certificate fails the check, so you get alerted. The certificate expiry date is visible on every HTTPS monitor under TLS certificate expires.
Separate advance warning emails before a certificate expires are not available yet. Check the expiry date on the monitor page, and rely on the alert if a certificate does expire.
After you create it
The confirmation screen links to View monitor. On the monitor page you can Pause, Pin, edit or delete it. Editing cannot change the check type; create a new monitor instead. Saving an edit starts a new configuration version, so older results no longer affect the state.
Frequently asked questions
Is the keyword check case-sensitive?
The keyword is matched as a plain substring of the response body, so enter it exactly as it appears on the page.
Does Uptime Tracker warn me before my SSL certificate expires?
The certificate expiry date is shown on every HTTPS monitor, and an expired or invalid certificate triggers an alert. Separate advance warning emails are not built yet.
Can I monitor a page behind a login?
On Starter you can send custom headers, such as an Authorization header from a stored secret. On Team, API workflows can log in first and reuse the token.
