Feel free to read the latest blog post and try out the new version (only proof of concept, but functional):
https://tlsnotary.org/wp/?p=27Simple explanation: audit a page and get a .audit file. You can give it an auditor later - where 'auditor' means anyone

. It's transferrable (it's as if the server had signed the page with a digital signature).
You perform the audit with a remote 'notary server', which knows basically nothing: there is no login, no credentials, you don't give the notary server either your html or the encrypted version of your html. It sees nothing except the server pubkey. It just provides you with some preliminary random secrets and then signs that you received the completed version of the secrets after you committed to a hash of your encrypted data.
Well, a little more detail in the blog post above.
Note that although there isn't much going on at the main repo
https://github.com/tlsnotary/tlsnotary at the moment, there is a lot of work being done in other places.
In a little while I might throw up a couple of .audit files so others can look at them (you can just run the auditor script locally to verify a .audit file's validity).