Public verify
Check a kill receipt signature
HMAC verify checks receipt integrity. It is not the token-liveness check. Paste the JSON. We recompute the canonical payload and check the signature against a published public key (Ed25519) or this host's HMAC secret — not a screenshot, not a vendor revoked=true flag.
Independent verify — not the vendor API
Paste a kill receipt. LingerCut recomputes the canonical JSON and checks the signature against a published public key (Ed25519) or the host HMAC secret. This page does not call Google, Microsoft, GitHub, or Okta. HMAC verify checks receipt integrity. It is not the token-liveness check. Replay bounce vs still-live is the liveness proof — and only if that probe was recorded on the receipt.
What a valid signature proves: the receipt bytes were not altered after LingerCut signed them.
What it does not prove: that leftover access is gone, or that a vendor revoke API told the truth. Only an independent replay bounce recorded on the receipt proves liveness failure.
Published verifying keys
No Ed25519 public key is published on this host. HMAC receipts are checked only on the signing host. See /security.