Skip to content

Verify a report or an attestation

Every CrashMire crash test report (PDF) and every attestation is signed with an Ed25519 key. Drop the file, paste the signature block, or open the verification link: the page says whether the signature is valid, not valid or unknown, and what was signed.

Verify a document

Nothing is stored: the file is read in memory to compute its fingerprint, then forgotten. 20 MB at most.

What the signature proves

That the document comes from CrashMire and has not been changed since it was signed: for a report, the exact PDF file (every PDF sent or downloaded carries its own number); for an attestation, its content (agent, test date, fingerprint of the tested state, results). The signed text holds the SHA-256 fingerprint of the content, the signing date and the version of the crash test method.

It says nothing more than the document does, and nothing about the tested agent beyond the report: a signed report is still a measurement, on these scenarios, these models, at that date.

The public key

With this key, anyone can verify a signature without this page (any Ed25519 tool). The exact format of the signed text is described at this stable address:

algorithm: Ed25519
key_id: 4816f5a378a86628
public_key_base64: RNwtof+M92j+HIlA0wL4wRSA1QjnDIo2OJ1BnAxAge4=

https://crashmire.com/signing-key.txt

The trust center →