Server Clock Timestamps: What They Prove and What Not
Published: June 11, 2026 · sello-temporal · server-clock · evidencia-digital · Leer este artículo en español
A server_clock timestamp proves that a specific server registered the SHA-256 fingerprint of a file at a given moment, according to its own clock. It demonstrates the file existed on that date and has kept its integrity since; it does not demonstrate when the content was created or who made it.
What the seal records exactly
When a file reaches Veritas UGC, the server computes its SHA-256 fingerprint and binds it to the time of its internal clock: that is the server_clock seal. The record is linked to a signed certificate, a public identifier searchable at /verify, and the 7-link traceability chain. The resulting claim is narrow and verifiable: this exact content existed, at the latest, at this instant. Everything a third party needs to check it is the file and the public link.
What it does not prove, said plainly
The seal does not prove the creation date of the content: a photo from 2020 can be sealed in 2026, and the seal only certifies 2026. It does not certify authorship either, because the attached identity is declared, not verified. And it is not a qualified TSA or a blockchain anchor: Veritas UGC uses neither and says so without hedging, because an honest seal is worth more than an inflated technical promise. Anyone needing a qualified timestamp with reinforced legal effects should go to a qualified provider.
When a server_clock is enough
In most everyday disputes, the key question is who can show they had what, and since when, and there a well-documented server seal delivers: it fixes a certain date of existence with readable traceability that an expert can examine. It works as one piece of evidence weighed alongside other signals, never as an automatic verdict. Sealing takes seconds, with no account and a limit of 10 per hour at /certificar, so the cost-benefit rarely fails: seal first, argue later. And if the controversy escalates, the signed certificate and the legal receipt issued by Veritas Nexus Legal LLC give the expert a documented starting point, with every link of the chain ready to be examined on its own merits.
Frequently asked questions
How does a server_clock differ from a TSA?
A qualified TSA signs timestamps under strict regulatory requirements and enjoys reinforced legal presumptions in several jurisdictions. A server_clock seal records the time of the platform's own server, declared as such. Veritas UGC uses server_clock and does not present itself as a TSA: it is honest technical evidence with a defined, publicly verifiable scope.
Does the seal prove when my content was created?
No. It proves the file existed at the moment of sealing and has not changed since. The real creation date may be much earlier. That is why the recommended practice is to seal as soon as possible after capturing or finishing the content: the shorter the gap between creation and seal, the more useful the evidence becomes.
Could a wrong server clock affect the seal?
Server clocks are routinely synchronized, but the seal is declared as server_clock precisely to be transparent about its origin. The date is part of the 7-link traceability chain and the legal receipt, so any later review knows exactly what kind of time source it is evaluating.
Seal your content now
Free, no account required, with a public verification link.
Veritas UGC generates technical evidence (hash, timestamp and traceability). It is not legal advice nor a government IP registry.