EpochLab

Unix Time Validator

Is this a valid Unix timestamp?

Check a value before you trust it: which precision it plausibly is, what date it lands on, and whether it trips any of the usual overflow and sentinel traps.

Questions people ask

The things that come up about unix time validators, answered plainly.

What makes a timestamp invalid?

Nothing about the number itself — any integer is a valid instant. What the page checks is whether it is plausible: a value that lands in 1970 or the year 33,000 is almost always a unit error, and 2147483647 is the 32-bit ceiling rather than a real date.

What is 2147483647?

The largest signed 32-bit integer, which as a Unix timestamp is 03:14:07 UTC on 19 January 2038. It is also a common sentinel for 'never expires', so seeing it usually means a placeholder rather than a date.

Related tools

Seconds, milliseconds, microseconds and nanoseconds, in both directions.

Timestamp ValidatorChecks a numeric timestamp for the mistakes that actually happen: the wrong unit, a 32-bit overflow, a sentinel value, or a date nowhere near where it should be.
Unix Timestamp ConverterPaste a timestamp and get the date; paste a date and get the timestamp. Seconds, milliseconds, microseconds and nanoseconds are detected from the digit count, and the guess is shown so you can override it.
Date ValidatorChecks that a date exists as well as parses — 31 February and 29 February in a common year both parse fine in most languages, and neither is a date.
Epoch Difference CalculatorSubtract one timestamp from another and get the answer in seconds and in human units — plus the same difference expressed in each of the four common precisions.

All 160 tools · More in unix time & epochs