Web Attestation
Generate cryptographic TLSNotary proofs that websites served specific content at a specific time. Free and powered by Bittensor Subnet 103.
How it works
- 1Enter a URL. Paste any public HTTPS URL you want to prove.
- 2Wait for the proof. A miner on Bittensor Subnet 103 generates a TLSNotary proof. Simple pages take 30 seconds; large pages can take up to 3 minutes.
- 3Download your proof. The cryptographic proof file is tamper-proof and verifiable by anyone.
Web Attestation Suite
This free tool demonstrates decentralized web attestation. For production use with storage, notifications, and advanced features, see our specialized products.
Debust
Trustless cryptographic receipts for the internet. Paste a URL, get a tamper-proof proof. Decentralized, shareable, and independently verified.
FirmRecord
Cryptographic web evidence for legal and enterprise. Chrome extension captures verified screenshots, HTML, and timestamps. Case tracking and Arweave storage.
ProveAudit
AI-powered code audits with cryptographic proof of every finding. Three independent analyses, results in under an hour, verifiable forever.
The difference is in access constraints, not content. This free tool attests any URL but doesn't store results. Debust adds persistent storage, accounts, and shareable proof links. FirmRecord adds a Chrome extension, case tracking, and enterprise features for legal and compliance teams. ProveAudit applies the same cryptographic verification to AI-generated code audits, with three independent runs and permanent records. All three are built on the same decentralized TLSNotary infrastructure powered by Bittensor Subnet 103 miners.
What is a TLSNotary proof?
TLSNotary uses multi-party computation during the TLS handshake to produce a cryptographic proof that a specific web server sent specific content. Unlike screenshots or web archives, this proof is tamper-proof and cryptographically verifiable by anyone.
Use cases include legal evidence, journalism verification, governance transparency, and academic citations with permanent, cryptographic provenance.
Why Djinn attestations are different
Most TLSNotary services are centralized, so you have to trust the operator's notary server not to collude or fabricate proofs. Djinn aims to reduce that trust assumption. Bittensor Subnet 103 validators randomly select two miners on different IP addresses for each attestation: one acts as the prover, the other as the notary. Neither knows in advance they'll be paired, and neither can influence the assignment. The result is a cryptographic proof with no single point of trust.