Check an Authorship record
Choose the .oauthor file you were given. This page checks that its record holds together, that its timestamps are genuine and cover it, and who signed it, then replays how the work was written. It is free, needs no account, and the file never leaves this browser.
Drop a .oauthor file here, or several
The example is a short essay written in Authorship over two sessions, with one quotation pasted in.
Your note on this record
Kept in this browser alone, under the record’s fingerprint, so it comes back when the same record is opened here again. It is never uploaded and never put in the file. With several records, it goes into the table’s CSV.
Compare it with a brief you issued
If you issued the assignment brief this work was begun from, choose your copy of it. The page compares its fingerprint and code with those in the record’s first block.
What this page checks
- The chain. Every block of the record holds the SHA-256 of the block before it. Each is hashed again here; an event changed, moved or taken out breaks every block after it.
- The document. Every event is replayed from an empty page, and at the end of each block the result must have the fingerprint the block recorded. The last must be the document in the bundle.
- The timestamps. Each RFC 3161 token is checked: the authority’s signature, its certificate and the certificates above it up to a root this page holds (DigiCert’s and Sectigo’s, the two authorities Authorship asks), that each was valid when the token was made, and that the token is over this record as it stood at that block.
- The clock. A block dated by the author’s device after the timestamp over it is reported, since it cannot have been written after it was stamped.
- The signature. If the bundle is signed, the device key’s signature over the list of every file’s SHA-256, and the key’s fingerprint.
The record shows how and when a work came to exist, and that it was not altered after each timestamp. It cannot prove that no AI was used: someone could retype text by hand, and a determined forger could script keystrokes. What each part means, and what it cannot show, is set out on the Authorship page; the format is written down at the top of oauthor.js, the code this page runs.
Several files chosen together are set out in one table: each one’s result, length, time at work, how much was typed here and the most any one paste put there. A column’s heading sorts it, figures past a line said beside the table are set out as facts to look at, and the table downloads as CSV, made in this browser. A note you keep on a record stays in this browser alone.
This page is free and always will be. It reads records; it cannot make one. It asks no server anything: certificates are checked against the roots it carries, so whether an authority later revoked one is not checked.