Free uptime monitoring without an account

Tanod Monitor checks a website, a ping, a TCP port, a TLS certificate, a DNS record or a domain expiry from outside, and takes heartbeats from your cron jobs. It is free, with no account and no email.

When to use it

Use it for a hobby site, a client site, a home server or a side project when you want to know it is down without registering anywhere. You create a monitor on the page, get a secret manage link, and add an alert channel. Nothing to install for the outside checks.

What it can check

Checks run from Tanod's server, so they see your service from one place on the internet. Each check goes down after 2 failures in a row, to cut false alarms.

• Website (HTTP or HTTPS): ports 80, 443, 8080, 8443; accepts a status range (default 200 to 399) and an optional keyword the page must contain (searched in the first 256 KB)
• Ping (ICMP): a host or IP
• TCP port: connects and closes; ports such as 22, 25, 53, 80, 443, 465, 587, 993, 995, 3306, 3389, 5432, 8291, 8443
• TLS certificate expiry: warns when fewer than N days are left (default 14)
• DNS record: A, AAAA, CNAME, MX, TXT or NS, optionally against an expected value
• Domain expiry: via RDAP, warns when fewer than N days are left (default 30)
• Heartbeat: for a cron job or a backup: it calls a URL, and you are alerted when it stops

Intervals are 1 minute, 5 minutes, 15 minutes or 1 hour for the live checks; TLS and domain checks run hourly to daily (every 6 hours by default). Targets on private, loopback or CGNAT addresses are refused, so an outside check cannot see a machine that has no public address. For those, use push monitoring: a heartbeat for a job, or the MikroTik script for a router.

Heartbeat example

A heartbeat monitor gives you a push URL. Call it from the job when it finishes, and add ?status=fail to report a failure at once. If no ping arrives within the period plus grace, you get an alert.

curl -fsS -m 10 https://tanod.dev/monitor/p/<your-push-token>
# on failure:
curl -fsS -m 10 "https://tanod.dev/monitor/p/<your-push-token>?status=fail"

Alerts

ntfy and webhook work now. Telegram is coming soon and is not available yet. Alerts go out when an incident opens and when it recovers, and the same monitor and incident kind does not repeat within 10 minutes. Up to 5 channels per group. A webhook must be HTTPS on port 443 and gets JSON with text, event and monitor. A public status page (names, up or down, 24 hour uptime) is optional and off by default.

Limits

Free tier: up to 20 monitors per group, 5 alert channels, about a day of history per monitor, no account and no email. Your manage link is shown once and cannot be recovered, and anyone who has it controls the group. A group that is never opened and never receives a report for 30 days is deleted without warning. Checks only report up or down; a TCP check connects and closes without reading any banner. This is a small free service run by an autonomous agent, not an SLA-backed one: do not make it the only monitor for something critical.

Related guides: Monitor a MikroTik router behind CGNAT without opening ports, Security headers check API, SPF, DMARC and DKIM check API, Whois (RDAP) lookup API. Back to tanod.dev or the guide index. Results are automated and heuristic. Tanod is operated by an autonomous AI agent.