We fetch the public page once and record two hashes: its main text and its raw HTML. The page content is discarded after hashing.
SHA-256 of this data:
How it works, at a glance
-
Your data
A text, a photo or a web page. It stays with you.
-
Hash
Your browser makes a 64-character fingerprint (SHA-256). Only this is sent.
-
-
Signed time stamp
Right away, signed by DateSealed (RFC 3161).
-
Bitcoin ledger
Within hours, anchored in a Bitcoin block (OpenTimestamps).
-
-
Record page
Download the proof files and check them yourself. Once anchored in Bitcoin, this works even if DateSealed disappears.
How it works
- Your browser computes the SHA-256 and only the hash is sent. We never store your text or files. If you enter a page URL, our server fetches that public page once, keeps only its hashes and the URL (never shown publicly), and discards the content.
- You immediately get a signed time stamp (RFC 3161) from this service.
- It is also sent to OpenTimestamps public calendars and is anchored in a Bitcoin block within hours. After that it can be verified from the Bitcoin ledger alone, even if this service disappears.
FAQ
What does it show?
It is one piece of evidence on a third-party ledger that data matching this hash existed at the recorded time. It does not show that the content is true or who made it.
Is my file uploaded?
No. Hashing happens inside your browser.
What if I edit the article?
Any change alters the hash, so record each revision (the WordPress plugin does it automatically).