Scheduling, read out loud
Paste a crontab line. You get it in plain English and the next times it will actually fire, computed in your own timezone. Everything runs in this tab.
When day of month and day of week are both restricted, they are combined with OR, not AND. 0 0 1 * 1 does not mean "the 1st, if it is a Monday". It means every 1st of the month, and every Monday as well. The specification is explicit:
"if either the month or day of month is specified as an element or list, and the day of week is also specified as an element or list, then any day matching either the month and day of month, or the day of week, shall be matched."
If only one of the two is restricted, the fields behave the way you would expect. The surprise only appears when you constrain both, which is exactly when someone is trying to be precise.
In order: minute [0,59], hour [0,23], day of the month [1,31], month of the year [1,12], day of the week [0,6] with 0 = Sunday. Many implementations also accept 7 for Sunday and three-letter names such as mon or jan; both are handled here.
Within a field, * means every value, a-b a range, a,b,c a list, and */n every nth value. The shorthands @daily, @hourly, @weekly, @monthly and @yearly expand to ordinary lines; @reboot has no schedule at all and fires once at startup.
The next runs are computed in your browser's timezone. A server usually runs in UTC or in whatever the machine is set to, so the wall-clock times on that machine may differ. Daylight saving transitions are another edge: a job scheduled inside the hour that is skipped in spring does not run that day, and one inside the repeated autumn hour can run twice, depending on the cron implementation.
This reads the expression. It says nothing about whether the job itself works.