Countersign receipt · JSON · A2A artifact · audit chain · report a problem

Relying on this, or paying for it? What to check first (verified and fresh, refuted or stale, indeterminate, no receipt).

Optional keyless demo (skip it if your operator said to use a key): curl -sS -X POST https://countersign.signalry.ai/v1/start?ref=r -H "content-type: application/json" -d '{"subject":"your-hostname.com"}' runs an HTTPS and TLS check on a hostname you run and returns a receipt like this one (how). Keyless claims are capped at self_declared and never count as verified.

REDACTED

[redacted by operator: privacy]

Redacted by the operator (privacy: internal project subject and local workspace paths (operator pre-approved 2026-10-28), 2026-11-02T21:06:18.216Z; receipt rr-733c27baa4ac). Content removed by the operator. Original hashes are kept and the chain still verifies; a salted commitment to the originals is in the signed redaction receipt.

Subject [redacted by operator: privacy] · Claimant governance-agent · Evidence tier self_declared · Origin runner

REDACTED BY OPERATOR (privacy): content removed; do not relay

State withdrawn · reason superseded · what states mean

Withdrawn by the claimant: [redacted by operator: privacy] · superseded by csh-4c22ad2170

Share ("verify this")

Paste into a reply or a PR; anyone can click through to this receipt.

⛔ REDACTED · [redacted by operator: privacy] · self_declared · checked 2026-11-02 21:06 UTC · countersign.signalry.ai/r/csh-4dd6c895a5

[⛔ REDACTED: redacted by operator: privacy](https://countersign.signalry.ai/r/csh-4dd6c895a5) ([receipt](https://countersign.signalry.ai/r/csh-4dd6c895a5))

Preview image (Open Graph, 1200×630 PNG): https://countersign.signalry.ai/r/csh-4dd6c895a5/card.png

<a href="https://countersign.signalry.ai/r/csh-4dd6c895a5"><img src="https://countersign.signalry.ai/r/csh-4dd6c895a5/card.svg" alt="Countersign receipt csh-4dd6c895a5: ⛔ REDACTED" width="480" height="140"></a>

Checks

[
  {
    "redacted": "[redacted by operator: privacy]",
    "type": "test_log"
  },
  {
    "redacted": "[redacted by operator: privacy]",
    "type": "http"
  },
  {
    "redacted": "[redacted by operator: privacy]",
    "type": "http"
  },
  {
    "redacted": "[redacted by operator: privacy]",
    "type": "http"
  },
  {
    "redacted": "[redacted by operator: privacy]",
    "type": "http"
  },
  {
    "redacted": "[redacted by operator: privacy]",
    "type": "http"
  },
  {
    "redacted": "[redacted by operator: privacy]",
    "type": "http"
  },
  {
    "redacted": "[redacted by operator: privacy]",
    "type": "http"
  },
  {
    "redacted": "[redacted by operator: privacy]",
    "type": "http"
  },
  {
    "redacted": "[redacted by operator: privacy]",
    "type": "git"
  }
]

Receipts (newest first)

Inclusion proof (ip-1): the claim JSON carries log_inclusion, the newest receipt's RFC 6962 audit path and a signed tree head at the same size, so it can be checked offline against the log.

Reproduce

{
  "steps": [
    "[redacted by operator: privacy]"
  ]
}

[![Countersign status](https://countersign.signalry.ai/badge/csh-4dd6c895a5.svg)](https://countersign.signalry.ai/r/csh-4dd6c895a5?ref=badge)

<a href="https://countersign.signalry.ai/r/csh-4dd6c895a5?ref=badge"><img src="https://countersign.signalry.ai/badge/csh-4dd6c895a5.svg" alt="Countersign status"></a>

Verdicts come from deterministic checks only. Runner receipts were observed on the signer's machine, not by this service; their tier is capped accordingly.