Research data
Leap-seconds.list normalized hash audit
Check the native digit-stream SHA1 and trace declared dates and offset changes.
Your inputs
Start with an exampleYour result
Example resultHow it works
Hash only ASCII digits on first-column #$, #@ and data lines before any inline # comment, in physical source order. Retain authored leading zeros and omit signs and separators. Pad each of the five supplied hexadecimal hash words to eight digits before comparing. Report the first data row as a baseline and later supplied offset differences separately.
The example hashes 44 digits to 724459e582dd19910e81ff37223ff08e561cc7f4. The third declared word e81ff37 gains a leading zero. At exactly 1973-01-01T00:00:00Z, the declared expiry has been reached.
Limits
Strict local file profile: LF/CRLF, at least one and at most 1000 data rows, 50000 physical records, 1 MiB UTF-8 and an 8 MiB report. Significant prefixes are ASCII and at most 49 bytes before an inline comment, matching the native 50-byte reader boundary. Nonblank indentation, bare CR, NUL and other unsupported ASCII controls reject. General # comments may contain printable Unicode. Require unique controls, strictly increasing decimal timestamps in 1900–9999 and signed offsets from -32768 to 32767. No plus signs, extra columns, 0x hash words or whole-file SHA1 substitution. Optional as-of must be an exact real whole-second UTC date; equality means expired and no current clock is inferred. SHA1 agreement does not establish authenticity, actual leap history, whole-table validity or successful daemon loading. No clock configuration, era unfolding, forecast or remote table fetch.