Timestamp Signing
RFC 3161 timestamp signing simulation, adds trusted timestamps to data and verifies them.
Sign Data
Verify Timestamp
Instructions
Signing Principle
Timestamp signing binds data hashes with trusted timestamps and uses HMAC-SHA256 for signing, proving data existed at a specific point in time. This tool simulates the core RFC 3161 timestamp protocol: generate data digest → add current time → HMAC sign → encode as token. Production environments should use trusted third-party Timestamp Authorities (TSA).
Token Structure
Token is a Base64-encoded JSON object containing: dataHash (SHA-256 hash of data), timestamp (ISO 8601 timestamp), unixTimestamp (Unix seconds), signature (HMAC signature Base64), key (HMAC key Base64, for local verification).
Steps
1. Enter original data in the 'Sign Data' section; 2. Click 'Generate Timestamp Signature'; 3. View the generated timestamp, hash, and token; 4. For verification, enter original data and token in the verify section; 5. Click 'Verify' to check the result.
Notes
This tool is a simulation; the HMAC key is embedded in the token, suitable for educational purposes only; real timestamps must be issued by a TSA using asymmetric keys; the token must be fully preserved, missing any field makes verification impossible; inaccurate browser time affects timestamp trustworthiness.