Inset of Sheet 8 of the atlas
damage-analysis.com is a site that DAREAKT serves. This hallmark is a signed reading of only what DAREAKT controls for that host: the name resolves to our server, our nginx answers on it over TLS 1.3, and it serves our security.txt. Our machine reads those three things from outside, at a stated time, and signs what it read.
It is a reading. It is not a certification, an audit or a warranty of the site, and it says nothing about the site's business, its content or how it handles data. It says what was true as read at the time shown, not what is true now, and anyone can repeat each check.
Decided in your browser, never printed by us.
Nothing on this page has been checked until its script has run. The result is worked out in your browser, never printed by us. The files are public, and the ways to check them yourself are further down.
Add ?s=H-000001 to the address to read a particular serial. Without it, the newest hallmark in the register of damage-analysis.com is shown.
Three readings of what DAREAKT controls for damage-analysis.com, and the line you can run to repeat each.
damage-analysis.com resolves to the DAREAKT server by plain DNS lookup, which is not DNSSEC-validated.
Run dig A and dig AAAA on damage-analysis.com and compare each address with the list in the evidence note.damage-analysis.com accepts encrypted connections over TLS 1.3.
Run openssl s_client -connect damage-analysis.com:443 -tls1_3 and look for a completed handshake.damage-analysis.com publishes a security.txt saying how to report a vulnerability, with a future expiry date.
Open damage-analysis.com/.well-known/security.txt and read the Contact and Expires lines.Not a certification, an audit or a warranty. And the six states this page can show.
Three ways, from weakest to strongest.
The quickest way, and the weakest
It shows the file is whole and signed by the key it names. It cannot show the key is ours, because the page and the key come from the same place.
A second place for the key
The command dig does not check the signatures in DNS, so use delv.
The strongest: nothing comes from this page
If your own reading differs from ours, the hallmark is wrong.
One file per hallmark, one register, one head, kept for damage-analysis.com on dareakt.com. Every file is signed with an Ed25519 key over its payload text, byte for byte. The register is a hash chain, and the head records how long it was when it was signed, so a register cut short can be seen. The same files are also served on damage-analysis.com itself, at /.well-known/hallmark/.
A hallmark
https://dareakt.com/.well-known/hallmark/damage-analysis/H-NNNNNN.jsonThe claims record it points at, kept byte for byte
https://dareakt.com/.well-known/hallmark/damage-analysis/H-NNNNNN.claims.jsonThe register of every hallmark and every revoke
https://dareakt.com/.well-known/hallmark/damage-analysis/register.jsonThe signed head of the register
https://dareakt.com/.well-known/hallmark/damage-analysis/head.jsonThe public key
https://dareakt.com/keys/hallmark-ed25519-public.pemThis page cannot prove the key is ours, because the page and the key come from the same place. The DNS record is the second place.
Read the key's record with delv
delv @185.12.64.2 _hallmark.dareakt.com TXTThe answer must say "; fully validated", and a TXT line must carry spki-sha256= followed by the fingerprint below. If the answer is not validated, or the fingerprint differs, or there is no such record, do not trust the hallmark.
Five steps on any machine with curl, python3 and openssl 3. Replace the serial with the one you want to check; this page has filled in the one it read.
1. Fetch a hallmark and the key
curl -sO https://dareakt.com/.well-known/hallmark/damage-analysis/H-NNNNNN.json -O https://dareakt.com/keys/hallmark-ed25519-public.pem2. Hash the key and compare it with the SPKI SHA-256 below
openssl pkey -pubin -in hallmark-ed25519-public.pem -outform DER | openssl dgst -sha2563. Compare it with the hash in DNS, using the delv command above.
4. Split the file into the signed text and the signature
python3 -c 'import json,base64;d=json.load(open("H-NNNNNN.json",encoding="utf-8"));open("payload.txt","w",encoding="utf-8",newline="").write(d["payload"]);open("sig.bin","wb").write(base64.b64decode(d["signature"]["sig"]))'5. Verify the signature
openssl pkeyutl -verify -pubin -inkey hallmark-ed25519-public.pem -rawin -in payload.txt -sigfile sig.binA good file prints Signature Verified Successfully. The signed text is the payload field byte for byte, so do not reformat it.
Pinned key (hallmark-v1)SPKI SHA-256 88559d78b028ddaa6db16a8cad6e1fb1054f93c67438b72367332c8588c6d97b
Every check inside a hallmark is a reading our machine made from outside, and its method is written beside it. If your own reading differs from ours, the hallmark is wrong.