RFC 3161 Trusted Timestamps for Audit Logs

    1

    Prove when a log, ledger or document existed with an independent RFC 3161 time-stamp authority; only a digest leaves your machine, and the token verifies offline with stock openssl years later.

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    RFC 3161 Trusted Timestamps for Audit Logs

    Example session with this skill installed

    Anchor today's head of our audit-log hash chain (SHA-512 of audit.log) to a trusted timestamp authority, store the token, and show me how to verify it offline next year.

    • Read your context and instructions
    • Compiled the rfc 3161 trusted

    Summary

    Anchored the chain head to FreeTSA. Only the 64-byte digest left the machine; the token verified against the pinned CA before it was stored.

    FieldValue
    Sourceaudit.log (chain head)
    Digest (SHA-512)9f3a…c41e
    Authorityhttps://freetsa.org/tsr
    Attested time2026-10-29T09:35:16Z
    Serial0x098969ED
    Tokenanchors/audit-20261029.tsr (4,674 bytes)
    Verificationopenssl ts -verify: OK
    
    # offline verification, any time later, with the pinned certificates
    openssl ts -verify -digest 9f3a…c41e -sha512 \
      -in anchors/audit-20261029.tsr -CAfile certs/cacert.pem -untrusted certs/tsa.crt
    

    What was recorded

    • Ledger row: source audit-log, label chain-head-2026-10-29, token path, attested time, serial. The token file was written before the row; re-anchoring the same digest never overwrites.
    • Certificates: certs/cacert.pem and certs/tsa.crt fetched once with fetch-certs.sh, SHA-256 recorded in certs/SHA256SUMS.

    Next steps

    • Enable reference/anchor-chain-head.timer so the head is anchored daily.
    • Back up anchors/ with the ledger; a token without its digest is useless, a digest without its token is unproven.
    • Verify with a wrong digest once to see the failure path (message imprint mismatch, exit 1).

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A hash-chained audit log proves nothing was edited after the fact. It does not prove when: someone with database access can rebuild the whole chain with different timestamps and it still verifies. This skill closes that gap with RFC 3161 trusted timestamps from an independent authority.

    What you get

    • scripts/tsa.mjs: build the request from a SHA-512 digest (openssl ts -query -digest, so content never leaves the machine), request the token, verify it against the authority's CA, read the attested time and serial.
    • scripts/anchor.mjs: a CLI to hash a file, anchor a digest to a .tsr file, verify offline, and print token info.
    • scripts/anchor-store.mjs and scripts/server.mjs: a loopback service with an append-only SQLite ledger. Tokens are files, the database is a pointer; the token is written before the row; verification re-runs openssl every time (no cached verdict); a token that fails verification is never stored; anchors with missing token files are reported, not hidden; re-anchoring never overwrites.
    • scripts/fetch-certs.sh: fetch and hash the authority's certificates once so verification stays offline.
    • A hardened systemd unit and a daily timer template for anchoring a chain head.
    • reference/design.md: the reasoning behind each rule and how to verify by hand years later.
    • Tests that run fully offline with a fake authority.

    Requirements

    Default authority is FreeTSA (free, public); any RFC 3161 authority works. Node 22.5+, openssl, no packages.

    Limitations

    Proves existence at a time, not authorship or accuracy. Engineering for admissibility, not legal advice.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.

    Does not prove content accuracy or authorship. Free TSA providers have no SLA. Requires outbound HTTPS to anchor; verification is offline. Node 22.5+ required.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 19 days ago

    Accounts
    Freetsa
    Software
    Node.js 22.5+OpenSSLRFC 3161 timestamp authority

    FreeTSA is the default timestamp authority.

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files

    Allowed Hosts

    freetsa.org

    Shell runs openssl ts for request and verification. Read/write files: the digest source, .tsr token files, certificate files and the SQLite ledger in directories you configure. Network: HTTPS POST of a timestamp request (digest only) to the authority URL you configure, plus the one-time certificate fetch.

    Listed19 days ago

    What's inside

    Frequently Asked Questions

    This skill allows you to obtain cryptographically signed proof from independent Time-Stamp Authorities (TSAs) that a document or log existed at a specific moment, preventing backdating and ensuring non-repudiation during audits.

    The skill uses a privacy-first approach by only sending SHA-512 hashes to the timestamp authority; your actual log content and sensitive document data never leave your local environment.

    You will need Node.js 22.5 or higher and a standard OpenSSL installation; the skill is designed to work as a standalone utility or can be integrated into AI agent workflows via its local HTTP service.

    Verification can be done completely offline using standard OpenSSL commands and the stored public certificates, ensuring your evidence remains valid even if the original service is unavailable.

    The package includes the core anchoring engine, a local SQLite-backed ledger for audit trails, a CLI for manual operations, and an HTTP service for seamless integration with other AI agents and automated pipelines.

    While the skill supports free public TSAs for testing and low-volume use, it is designed to work with any RFC 3161 compliant provider if your compliance needs require a paid SLA.

    New in APIs & Backend