pAulse Performance the recordthe work

Check The record

Check this page without trusting me

Two independent timestamp authorities signed the record of this page. You can measure the page in this tab, or verify both tokens offline with one command.

Every other claim on this site is mine. These two are not: an authority holds the private key, it signed a hash and a time, and the token it returned verifies against a certificate you already have. My clock is not involved, and neither is my signature.

Sealed
reading
Clocks
reading
Page
reading

Measure this page

The button fetches this site's front page in your browser and hashes it with the browser's own SHA-256. Nothing is sent anywhere: the comparison happens on your machine, against the hash recorded when the page was sealed.

not measured yet

The hash covers the HTML bytes served at /. If the page changed after the seal, this says so.

The record

The tokens are over proof.json, the file that records the page's hash, its size and the commit it came from. Seal the record and the page is sealed with it.

proof.json sha256reading
page sha256reading
page sizereading
page commitreading
sealed atreading

The two clocks

One is a community authority that signs under its own root, which is shipped beside the token. The other is a commercial authority whose chain ends in a root every operating system already trusts. They fail for unrelated reasons, which is the point of carrying both.

AuthoritySerialIssuedTokenChecked against
reading

Verify offline

Download the record and the two tokens, then run these. No network, no account, no tool of mine:

shasum -a 256 proof.json
# compare that with the proof.json sha256 above

curl -O https://pAulseperformance.com/proof.json
curl -O https://pAulseperformance.com/seal/proof-freetsa.tsr
curl -O https://pAulseperformance.com/seal/ca-freetsa.pem
openssl ts -verify -in proof-freetsa.tsr -data proof.json -CAfile ca-freetsa.pem

curl -O https://pAulseperformance.com/seal/proof-sectigo.tsr
openssl ts -verify -in proof-sectigo.tsr -data proof.json -CAfile /etc/ssl/cert.pem

The second one uses your system trust store, because that authority's root is already in it. Both print Verification: OK.

Every seal

A single token says these bytes existed then. The series says the record has been kept, and re-sealed whenever it moved, which is the part a reader can watch over time.

SealedPage sha256Clocks
reading

What this does not prove

A token fixes a time, never a truth. It says these bytes existed by that date. It does not say the page is correct, that I am who I say, or that the record is complete. Neither authority is a qualified trust service, and a compromised authority could sign a false time; that is why there are two, and why the hashes are recomputable by hand.

Compare this with the other direction: the site's own proof is a claim I make about myself and can rewrite. These tokens are the part I cannot.