--- title: "Why a Signed Carrier Vetting Record Still Needs an Independent Timestamp" description: "A signed, sealed vetting record proves nothing was altered. It does not prove when the record existed, unless the clock behind it is independent too. How RFC 3161 timestamps close that gap, and why it is the evidence question underwriters and defense counsel ask next." author: John Nowlan published: 2026-07-31 updated: 2026-07-31 category: Compliance canonical: https://www.cipherandrow.com/blog/independent-timestamp-carrier-vetting-record --- # Why a Signed Carrier Vetting Record Still Needs an Independent Timestamp By John Nowlan · Published 2026-07-31 · Cipher & Row Blog Ask a freight broker in 2026 whether they can prove they checked a carrier before booking, and most will say yes. Ask whether they can prove *when* they checked it, independent of their own word for it, and the room usually goes quiet. That is the gap this article is about. ### Key takeaways - A tamper-evident signature proves a record has not been altered since it was created. It does not, by itself, prove when it was created, because the clock behind that claim is usually the vendor's own server. - RFC 3161 is the internet standard for closing that gap: an independent third party timestamps a fingerprint of the record and signs it, so the time claim no longer depends on the party who has an interest in the outcome. - It is the same mechanism used to timestamp signed contracts under electronic-signature practice and to establish priority on patent filings. It is not blockchain, and Cipher & Row does not use blockchain anywhere in this system. - Cipher & Row now stamps every sealed Compliance Vault record with an independent RFC 3161 timestamp, alongside the existing Ed25519 signature and immutable event log, automatically, on every plan that includes the vault. - We think this becomes the next expected layer of a carrier vetting record, the same way a signed audit trail went from differentiator to shipped feature at the largest onboarding platform in the industry in under two months. > A signature proves nothing changed. An independent timestamp proves when it was true to begin with, without asking anyone to take the record-keeper's word for it. ## What a signature actually proves, and what it does not We wrote [earlier this month](https://www.cipherandrow.com/blog/carrier-vetting-audit-trails-2026-tms-highway-descartes-cipher-row) about the shift underway across the industry: carrier vetting used to be a private check a broker ran and forgot. Now shippers ask for evidence of it in RFPs, insurers ask at renewal, and plaintiff's attorneys ask after a bad load. Every sealed record on Cipher & Row, and increasingly on competing platforms, answers that with a cryptographic signature: a mathematical proof that the record you are looking at is identical to the one that was sealed, and that nobody, including us, has quietly edited it since. That is a real, valuable property. It is also narrower than it sounds. A signature proves integrity: this record has not changed. It says nothing on its own about *when* the record came into existence, because the timestamp attached to a signed record is, by default, whatever the signing system's own clock said at the time. If that system belongs to the party whose diligence is being questioned, and it usually does, the timestamp is a claim, not independent evidence. A careful reader on the other side of a dispute knows that. ## Who is holding the clock This is not a hypothetical concern. It is the standard first move against any self-reported timestamp: who controls the server, and could they have backdated it? For most vetting platforms, including the version of Cipher & Row's own Compliance Vault before this month, the honest answer was the same one every vendor gives: our system clock, secured the same way the rest of our infrastructure is secured. That is a reasonable answer. It is not the strongest one available. The strongest available answer is to remove your own clock from the claim entirely. Hand a cryptographic fingerprint of the sealed record, and nothing else, to a party who has no stake in the outcome, and let them attach the time and sign it themselves. Now the timestamp does not depend on trusting Cipher & Row's clock, our security practices, or our incentives. It depends on the math, and on a third party who was never a participant in the transaction being timestamped. ## What an RFC 3161 timestamp actually does RFC 3161 is the internet standard for exactly this. A Time Stamping Authority receives a hash, a short cryptographic fingerprint, of a document. It never sees the document itself, only the fingerprint, which reveals nothing about the content. The authority attaches the current time, signs the whole thing with its own certificate, and hands back a token. Anyone holding that token and the original document can independently recompute the fingerprint and confirm the token matches, without asking the authority anything and without asking us anything. What that token proves is precise, and worth stating exactly: the record existed no later than the time in the token. Not that it was created at that exact moment, and not that anyone reviewed or acted on it correctly. An upper bound, cryptographically attested by an independent third party. It is the same mechanism that underpins timestamping in electronic-signature workflows and that inventors use to establish priority on a patent filing. It has been boring, reliable internet infrastructure for two decades. It is also worth saying plainly what it is not, because the word "cryptographic" invites the comparison: this is not blockchain. There is no distributed ledger, no chain of blocks, no network of validators reaching consensus. It is one signed assertion from one identifiable, trusted third party, closer to a notary's stamp than to a cryptocurrency. We wrote about [why that distinction matters](https://www.cipherandrow.com/blog/blockchain-freight-beyond-hype) when we shipped the underlying record-sealing technology; the timestamp layer follows the same principle. Boring and standard beats novel every time the question is whether a court or an underwriter will trust it. ## Why this is the evidence question underwriters and defense counsel ask Step back from the cryptography and ask what a coverage attorney or an underwriter reviewing a claim actually wants to see. Not a promise that a company runs a careful process. Contemporaneous, specific evidence: this exact carrier, checked against these exact records, on this exact date, by a process nobody can quietly rewrite after the fact. That is the standard diligence defense in a negligent-selection claim, and it is the same standard underwriters look for when they price a broker's risk or review a file after a loss. A self-timestamped log gets most of the way there and stops one step short: it proves the check happened, but the "when" still rests on the broker's own system. An independently witnessed timestamp removes that last objection. It turns "we say we checked this on the 12th" into a claim a third party who was never involved in the transaction will independently confirm. We are not aware of another carrier vetting platform, including the ones we compared in detail in our audit trail article, that timestamps its records this way as of this writing; most vetting logs, where they exist at all, are timestamped only by the vendor's own system. Not advertised does not prove a capability is absent, and we would be glad to be wrong about that. But it is the distinction we think an underwriter reviewing a broker's E&O file, or defense counsel building a diligence record for a claim, should be asking every vendor about. ## Is this the next standard? We think so, and we will say why rather than just assert it. Twelve months ago, a signed, exportable audit trail for carrier vetting barely existed as a product category. Then Descartes shipped one inside MyCarrierPortal, the largest onboarding platform in the industry, and the conversation moved from "do you keep a record" to "can you produce it." Independent timestamping has followed the same arc in every other field that eventually needed it: e-signatures, financial audit trails, patent filings. First it is a differentiator only the most careful player bothers with. Then it is the obvious follow-up question once the first generation of the technology becomes ordinary. We built this now because we think that second question is closer than most of the industry expects, and because a timestamp obtained today cannot be obtained retroactively. There is no version of this where waiting made the record stronger. ## Where this fits in the Compliance Vault Every sealed record in your Cipher & Row [Compliance Vault](https://www.cipherandrow.com/blog/cipher-row-packet-scanner-how-it-works) now carries an independent RFC 3161 timestamp alongside its existing Ed25519 signature and immutable event log, on every plan that includes the vault, no separate toggle or add-on required. The public verify link works the same way it always has: hand it to a shipper, an underwriter, or opposing counsel, and they confirm the record for themselves, no account needed. That confirmation now includes an independently witnessed answer to when the record existed, not just whether it changed since. If you underwrite freight broker risk, review E&O claims, or advise brokers on what a defensible diligence record looks like, the fastest way to see the format is to look at one directly. A free lookup at [cipherandrow.com/verify](https://www.cipherandrow.com/verify) needs no signup, and the [pricing page](https://www.cipherandrow.com/pricing) lays out what ships on each plan, including the Compliance Vault. We built the record to be checked, not taken on faith, and that includes by you. ## Quick answers **What does an independent timestamp actually prove?** That a specific record, identified by its cryptographic fingerprint, existed no later than a specific time, attested by a third party that was not a participant in creating the record. It does not prove the exact moment of creation, and it does not certify anything about the record's content. **Is this blockchain?** No. There is no distributed ledger and no network of validators. It is one signed assertion from an identifiable, independent time-stamping authority, functionally closer to a notary than to a cryptocurrency. **Why does a signature alone fall short of this?** A signature proves a record has not been altered since it was signed. The timestamp on a signed record is normally set by the signing system's own clock, which belongs to the party whose diligence is in question. An independent timestamp removes that party from the timing claim entirely. **Do I have to do anything to get this on my Cipher & Row records?** No. It applies automatically to sealed Compliance Vault records on plans that include the vault. There is no separate signup, integration, or toggle. **Does this replace legal advice or guarantee a claim outcome?** No. It is a verifiable record of the verification you performed, not a certification that a carrier decision was correct or a substitute for legal counsel. What it settles is the factual question of what was checked and when, independently of anyone's word. ## Frequently asked questions **What does an independent timestamp actually prove?** That a specific record, identified by its cryptographic fingerprint, existed no later than a specific time, attested by a third party that was not a participant in creating the record. It does not prove the exact moment of creation, and it does not certify anything about the record's content. **Is an RFC 3161 timestamp the same thing as blockchain?** No. There is no distributed ledger and no network of validators reaching consensus. It is one signed assertion from a single identifiable, independent time-stamping authority, closer to a notary's stamp than to a cryptocurrency. **Why isn't a tamper-evident signature enough on its own?** A signature proves a record has not been altered since it was signed. The timestamp attached to a signed record is normally set by the signing system's own clock, which belongs to the party whose diligence is being evaluated. An independent third-party timestamp removes that party from the timing claim. **Do underwriters or defense counsel actually ask about this?** The standard questions in a diligence defense are whether a check happened, on what date, and whether the record could have been altered afterward. An independently witnessed timestamp answers the date question without asking anyone to trust the vendor's own clock, which is the distinction we think becomes a routine question in E&O file review and claims defense. **Do I need to set anything up to get this on my records?** No signup or integration is required. It applies automatically to sealed Compliance Vault records on Cipher & Row plans that include the vault. --- Read this article in your browser: https://www.cipherandrow.com/blog/independent-timestamp-carrier-vetting-record Cipher & Row verifies US and Canadian carriers and brokers, monitors them for changes, and seals every vetting decision into a verifiable record. Try a free lookup, no signup: https://www.cipherandrow.com/verify