Shareable case links

Show what badges you have

Each badge on a case page is backed by a TLSNotary proof — cryptographic evidence generated from a real TLS session. Raw proof transcripts are never uploaded; only signed claim metadata is shared.

How to create and share a case

  1. Browse templates at /badges and note the IDs of badges you want to prove.
  2. Generate a TLSNotary proof for each badge using the browser extension. The extension opens the target URL (e.g. dashboard.stripe.com), captures the TLS session, applies the template's redaction rules, and returns a signed proof file.
  3. Choose a public handle, for example: sarah.
  4. Build your link by adding badge IDs as comma-separated values in the badges query parameter.
  5. Share the generated link — no cloud upload required.
/cases/sarah?badges=income%2Fstripe-monthly-volume%2Cdev%2Fgithub-account-age%2Ccredential%2Faws-certified-badge
Open example caseBrowse badge IDs

How TLSNotary proofs work

1. TLS Session
Extension intercepts your HTTPS connection to the target site using MPC-TLS.
2. Extract
Template selector and regex pull only the relevant value from the page.
3. Redact
All PII (emails, tokens, IDs) is stripped before the proof is finalised.
4. Notarise
A TLSNotary notary co-signs the session, proving it came from a real site.
5. Badge
You receive a compact signed proof file (~5 KB) — no server required.