Port Number Lookup
Find what runs on a port, with a note on whether it should be exposed.
Read a cron expression in plain English and see when it next runs.
The Cron Expression Parser reads an expression back in plain English, expands every field into the values it matches, and calculates the next run times — recognising six-field Quartz expressions and the shorthand forms.
Paste an expression from a crontab, a CI config or a Kubernetes CronJob and read what it actually does. Each field is expanded into the full set of values it matches, so a step or a range stops being something you have to work out in your head.
The next run times are calculated rather than estimated, by stepping forward minute by minute and testing the expression — which is exactly what cron does. Six-field expressions from Quartz and Spring are recognised and the seconds field called out, month and day names are understood, the shorthand forms expand, and the day-of-month against day-of-week OR behaviour is flagged whenever an expression is exposed to it.
A range with a step becomes the actual list of values, so you are not working it out in your head.
Quartz and Spring add a seconds field at the front, and pasting one into a crontab shifts everything by one. That is called out.
JAN and MON work as well as 1 and 1, including inside ranges.
By stepping forward and testing the expression, which is what cron itself does — so the answer is right rather than plausible.
Whenever both day fields are restricted, because that expression runs on either and almost nobody means it to.
Five fields, six fields, or a shorthand such as @daily.
What it does, in a sentence.
Every value each field matches, expanded from its ranges and steps.
The next several times it fires, calculated from now.
Because Quartz, Spring and a few other schedulers add a seconds field at the front. Standard Unix cron has five, so a six-field expression pasted into a crontab shifts everything by one.
Every 15th value from the start of the range — so in the minute field, at 0, 15, 30 and 45. It is a step, not "every 15 minutes from now", which matters if you expected it to drift.
Yes. The day-of-week field accepts 0 to 7 with both ends meaning Sunday, which exists purely so that nobody has to remember which convention their system uses.
They are calculated in your browser's time zone. Your server may well be on UTC, so compare before trusting them for a production schedule.
What people who use the Cron Expression Parser think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Cron Expression Parser. It takes half a minute and no account.
Write the first reviewFind what runs on a port, with a note on whether it should be exposed.
Produce SHA-1, SHA-256, SHA-384 and SHA-512 digests of any text.
Pretty-print XML with clean indentation, or collapse it back to one line.
Decode a JWT and read its header, claims and expiry in plain English.
Make every editor agree on indentation, line endings and charset.
Generate Java POJOs or records with Jackson annotations from JSON.
Break an emoji into its code points, modifiers and joiners.
Estimate how long a password would survive, and see exactly what weakens it.