OpenStampsfor industry

Status

Most of this cannot go down, because most of it has no server

Checking a stamp, reading a chain and assembling a due-diligence statement run entirely in your browser. They reach nothing of ours, so they do not stop when we do, and they will still work on a day this company does not exist.

What is left is small: a relay that carries a digest to two free timestamp authorities — and to a qualified third where a contract has been signed — a mailbox two phones use to meet, accounts and billing — and four outside anchors nobody here controls, a fifth where a qualified authority is contracted. That is what this page measures. We publish no availability commitment; the enterprise checklist prints a refusal against an uptime SLA, and this page is what is offered in its place.

What reaches no server of ours

These carry no glyph, and that is deliberate: nothing here was measured. They are statements about where code runs, and the way to test one is not to believe this page — turn your network off, or watch the network tab, and do the thing.

  • Checking a stamp

    A .cts file opened on the Verify task is checked in the page: the digest, the signature, the beacon round and each RFC 3161 token, against bytes already in the file. No upload, no account, no request. A stranger with the file and a browser reaches the same finding without asking us anything.

  • Reading a chain and drawing its map

    The chain is walked in the browser and the outline it is drawn on is served from this origin. Map tiles from OpenStreetMap load only after you switch that layer on, and the switch says so beside itself.

  • Assembling a due-diligence statement

    The desk builds the statement, the geometry and the risk narrative in your browser, and hands you the file. Filing it into the EU Information System is a separate, deliberate press, under your own credentials — and it is in the measured table below, because that part does reach a server.

  • Recording a plot at the plot

    The farmer's page reads corners from the device and seals the record there. Sending it back to a buyer uses the hand-off mailbox, which is measured below; keeping it, or sending it any other way, is not our business and needs nothing of ours.

  • Opening one of these files in ten years

    The format is published and the conformance pack is public. A reader nobody has written yet can be written against them without asking us, which is the only version of durability that does not depend on us being here.

The surface that can fail with us

Each row was asked, just now, through the same handler a visitor would reach, and reports the HTTP code and the configuration flag that route answered with. A part switched off on this deployment reads not checked, never as a failure: there is nothing there to be up or down.

  • Not read yet

    Asking /api/status on this origin.

The anchors, by name

A stamp is a bracket. The lower edge is a drand beacon round, fetched by your browser at the moment of stamping; the upper edge is an RFC 3161 token from two independent free authorities — and from a qualified third where this deployment has contracted one — reached through our relay so the browser never talks to them directly. Four anchors always, a fifth where a contract has been signed, and we operate none of them.

The free timestamp authorities are not eIDAS-qualified trust service providers
freetsa.org is a free service run by one person on donations. timestamp.digicert.com is a courtesy endpoint for DigiCert code-signing customers. No legal presumption under eIDAS Article 41 may be implied from a token either one signs — by us, or by anyone quoting us. A third, qualified leg is built into the relay and answers only where a contract has been signed; whether this deployment has one is read from its configuration and printed in the cards below, never assumed here, and even then the reader's own pin table decides per token. Where no contract exists this sentence is the whole position. A qualified token can be added to an existing record later without re-stamping it, because the bracket is a set of anchors rather than a single signature; so can a renewal timestamp, which the format carries beside the envelope so that a record's identity never changes when it is renewed (the specification, §8.6). A token whose authority certificate has run out leaves a stamp no longer independently checkable by an ordinary PKI verifier — not false, and never a fault in the record — and the desk (dds.html) can renew a sealed record before that day; a renewal is one closed-stamp draw and never changes the record's identity.

Not read yet

Asking /api/status on this origin.

Each probe is one GET, and the only thing it can show is that the host answered our server and how long it took. It is not a test that a timestamp would be issued — that needs a real timestamp request, and asking a free service for a token in order to colour a status page is not a use we will make of it. The result is cached for five minutes at the server, so this page cannot become a way to generate load against a volunteer however hard anybody reloads it.

This page, on your device

Measured by your own browser, for this load only, and not sent anywhere. There is no analytics endpoint on this site and there will not be one, so these numbers exist on your screen and nowhere else. That is also why there is no cookie banner asking you about them: nothing leaves, so there is nothing to consent to.

  • Not measured

    This needs the page timing API, which your browser has not offered.

These describe your device and your network at least as much as they describe this server, which is exactly why they are shown to you rather than collected from you. Everything this page fetches — the stylesheet, the fonts, the script and /api/status — is on this origin; there is no third party to check for.

What this page does not measure

A status page earns its place by what it refuses to draw. These are the gaps, named, and each of them is a thing you would ordinarily be shown.

  • Uptime history

    Nothing has recorded any. There is no store of past moments here, so a ninety-day strip would be drawn rather than measured, and a drawn one is worse than none.

The full list of what is measured, in machine-readable form, is at /api/status on this origin. What we do not offer at all — an uptime SLA, SOC 2, ISO 27001, single sign-on, customer references — is on the enterprise checklist, printed as refusals rather than as a roadmap. What the anchors cost, and what the meter is meant to buy, is on the plans page.