Websites and APIs
Besides scripts that ping, TaskBeacon can check a website or an API itself: our server requests the address on a schedule and alerts you when it is down, answers with the wrong status, misses a word that should be on the page, gets much slower, or when its SSL certificate or domain is about to expire. Nothing to install or paste.
Add a check
On Jobs, open the arrow next to + New job and choose Website or API check. Enter the address
(https://example.com/health), how often to check, and optionally a word the page must contain.
Under More are the method (GET or HEAD), the expected status codes, the timeout and the warning days.
A check counts as one job against your plan, like a script.
How often
Every 1, 5, 15 or 60 minutes. On Free the shortest interval is 5 minutes; 1 minute is for paid plans (see Pricing). Each address is requested at most once per interval; when several checks watch the same address, one request serves them all.
When you get an alert
- Failed: no answer within the timeout, a connection or certificate error, a status outside the expected
ones (by default anything other than 2xx or 3xx after redirects), or the page lacks the word you asked for.
We check from one place only, so a failure is checked once more about a minute later; only a second failure turns the check Failed.
The alert says what went wrong, e.g.
HTTP 503 Service Unavailable. - Odd data: the site works, but the certificate or domain expires within the days you chose, or it answered far slower than usual twice in a row (at least three times the usual time and one second more).
- Back to OK: the next good answer.
- Missed: only if our checks stopped running for longer than the interval plus 10 minutes.
Mark as checked on an expiry warning keeps quiet about that certificate or domain date; a renewed certificate or domain starts over.
SSL certificate and domain expiry
For an https:// address, every check reads the certificate's expiry date; the job page shows
“expires in N days”. A certificate that is already invalid or expired makes the check Failed, as browsers refuse it too.
The domain's expiry date comes from its registry through RDAP, the successor of WHOIS, once a day. Not every registry publishes it: many country domains have no RDAP service listed by IANA, and some leave the date out. Then the job page says unknown and you never get a domain warning for it.
What our requests look like
- User agent:
TaskBeacon-Uptime/1.0 (+https://taskbeacon.io/docs/uptime/), from the server that taskbeacon.io points to. Allow it if a firewall or bot protection blocks unknown visitors. - Up to 5 redirects are followed; at most 256 KB of the page is read; nothing is stored except the status code, the response time, the expiry dates and, on a failure, the error.
- The response time is the time until the answer starts (including DNS, connection and TLS).
- Response time and status are kept like a job's runs: the last 100 checks on Free.
Addresses we don't check
Only public addresses on ports 80, 443 and 1024 or higher. Addresses that lead to private, local or reserved networks
(e.g. 192.168.x.x, 10.x.x.x, localhost) are refused, on every check and every redirect,
so a check can't be used to look inside a network. Addresses with a user name or password in them are not supported.
For an internal service, run a small script on your side that pings TaskBeacon instead
(see Getting started).
Use cases: Get an alert before an SSL certificate or domain expires · Get an alert when a website is down or slow. More questions: FAQ.