We respect your privacy. This site sets no cookies and uses no trackers. The only thing it keeps in your browser is an offline copy of its own pages. Privacy details
Notices, incident history and measured availability of the service at tsa.internetidentitycard.com
Last updated: 11 October 2026
The service publishes its state as JSON at https://tsa.internetidentitycard.com/tsa/status ↗: the clock state (SYNC or FAIL), the time since that state began, the active key generation, the policy OID, the time of the last token, whether public issuance is open, and the current notices. This page explains how to read it and keeps the history that the JSON does not.
tsa-2026-a, certificate valid to 9 January 2038, signs for at most 15 months (ceremony record R1)stateSYNC, after a live measurement against four time sources. The service keeps no instance running between requests, so an idle instance reports FAIL with last_token_time: null until the first request measures the clock: that is a cold start, not an outage. A FAIL that persists after a token request is an incident and is recorded below.Dated, newest first. Notices are also carried in the notices field of the status JSON while they are current.
403 issuance_closed.None recorded since the opening on 10 October 2026. An incident, for this page, is any of: a token issued outside the SYNC state or with a wrong time; a suspected or confirmed compromise of a key; a revocation; a FAIL state persisting after a token request; the public verification endpoints (root, CRL, status) unreachable for more than one hour; a missed or failed nightly journal batch not recovered the following night; any loss of issuance-log data. Each incident is recorded here with its time (UTC), its effect on tokens, what was done, and the serial numbers of any token concerned, within seven days of being known.
| Date (UTC) | Effect | Tokens concerned | Resolution |
|---|---|---|---|
| No incident recorded. | |||
IIC TSA is a free service with no availability commitment and no service-level agreement (terms of use). Availability is therefore measured and published, not promised. Since 11 October 2026 at 13:00 UTC, an external probe (Google Cloud Monitoring uptime check) requests GET /tsa/status every 5 minutes from three regions (Europe, USA Oregon, Asia Pacific) and counts the check as passed when the answer is HTTP 200 and contains a status JSON. A cold-start FAIL clock state is not a probe failure: the probe measures whether the endpoint answers, not the clock state. The measured monthly figure is listed here from the first full month; months without a complete measurement are shown as such, not estimated.
| Month | Measured availability of /tsa/status | Method |
|---|---|---|
| November 2026 | to be published early December 2026 | uptime check, 3 regions, every 5 min |
| October 2026 (from the 10th) | partial month, probe in place from the 11th: not reported | — |
Every day at 00:20 UTC, the previous day's issuance-log entries are written to a batch file whose SHA-256 is time-stamped by DigiCert's public RFC 3161 server and anchored in Bitcoin through OpenTimestamps, then copied to an archive bucket in another region (Practice Statement, section 8). The first batch, for 10 October 2026, ran on 11 October 2026 at 00:20 UTC (25 entries, DigiCert token granted, archive copy made). A failed batch is an incident only if it is not recovered the following night; the entries of a given day are provided to a relying party on request.
Nothing on this page needs to be taken on trust:
curl -s https://tsa.internetidentitycard.com/tsa/statuscurl -s https://tsa.internetidentitycard.com/tsa/root.pem | openssl x509 -noout -fingerprint -sha256 — expected 86:52:E3:D1:3E:72:5F:7C:75:7C:FA:05:3D:64:13:60:AC:A4:43:CF:6C:09:D7:D6:DD:D4:4B:EA:85:1E:D3:B9curl -s https://tsa.internetidentitycard.com/tsa/crl | openssl crl -inform DER -noout -lastupdate -nextupdatecurl -s -o /dev/null -w "%{http_code}" -X POST https://tsa.internetidentitycard.com/tsa — expected 403This page is updated by the operator when a notice, an incident or a monthly figure is added; its date is in the subtitle. IIC TSA is designed to RFC 3161 / RFC 5816; it is not a qualified trust service, and IIC TSA and VerifBox belong to the same company.