Cron expression tester

Paste a cron schedule and get it in plain English, plus the next times it fires. Then, if you want, arm a free dead-man’s-switch so you’re told the moment it stops. No signup.

minute  hour  day-of-month  month  day-of-week  (or a macro like @daily)
We interpret the cron fields in this zone and show the next runs in it. Fixed offset — DST transitions aren’t modeled.
This schedule means

At 00:00, on Sunday.

Times below are shown in UTC. Pick your box’s zone above — cron reads the fields in the server’s local time. (Fixed offset; DST shifts aren’t modeled.) The dead-man’s-switch itself is timezone-free: it watches the gap between pings, so a late run is late in any zone.

Next 5 runs

#1Sun 2026-08-30 00:00 UTCin 424043 sec
#2Sun 2026-09-06 00:00 UTCin 1028843 sec
#3Sun 2026-09-13 00:00 UTCin 1633643 sec
#4Sun 2026-09-20 00:00 UTCin 2238443 sec
#5Sun 2026-09-27 00:00 UTCin 2843243 sec

Will you know if it silently stops?

A cron line that stops firing — a broken crontab, a dead box, a paused container, a schedule someone commented out — throws no error. Nothing pages you. You find out when the thing it was supposed to do didn’t happen.

Cronping arms a dead-man’s-switch from this exact schedule: your job pings a URL each run; if a ping is late, we email (or Slack/Discord) you. Free, no account.

Arm a free monitor for this schedule →
Try a common one:
*/5 * * * *0 * * * *0 0 * * *30 4 * * *0 9,17 * * 1-50 0 * * 00 0 1 * **/15 9-17 * * 1-5@daily

Monitor a whole crontab at once → · how Cronping works · cron troubleshooting guides