Verification point
Record found and verified
A record's fingerprint is computed with SHA-256 over its host, its rubric version, and each check's id, status, rounded points, and counted flag. This page recomputes it from the stored record. It also recomputes the score, grade, and level from those check outcomes and compares them with the stored ones. The detail and evidence text of each check is not bound, so an edit there is not caught.
Verified — the fingerprint and the score both recompute from this record
The fingerprint recomputed from this host, this rubric version, and these check outcomes agrees with the one the record carries. The score, grade, and level recomputed from the same outcomes, for the site profile the record names, agree with the stored ones.
- Host
- github.com
- Score
- 32.7 · BB
- Level
- L1 Basic Web Presence
- Scanned
- Rubric
- v0.7
- Checks
- 51 of 61 scored
Score, grade, and level recomputed from the check outcomes. A check that is out of scope or not measured is not scored.
Fingerprint the record carries
2f401ac8f899489f4d7f230f490d80c24c4932a035b9e0d43895d17a90fdc867
What this proves, and what it does not
It proves the check outcomes are as they were written. A record cannot move to another host or another rubric version and still match its fingerprint. Neither can a check's status, points, or counted flag change. The score, grade, and level follow from them under the site profile and commercial signal the record names.
It does not bind the text. Each check's detail and evidence text is not part of the fingerprint, so an edit there is not caught. Neither is the out of scope or not measured label stored on a check that was not scored.
It does not bind the site profile. The site profile and the commercial signal are read from the record. They decide the category weights, the checks each level requires, and which checks are out of scope. When no check was scored, whether the scan was refused is read from the record too.
It does not prove the measurement is correct. It proves only that these check outcomes are the ones that were published. For correctness, re-run the scan.
Of the 61 checks, 2 are evaluated against a clock, so they can change with no change to the site:
- security-txt passes only while its Expires field is in the future.
- status-page reports a partial pass once the newest entry in a linked feed is more than 180 days old.
When one changes, the fingerprint changes with it. A difference there is not a finding.
Other things change a result with no change to the site. A request with no response within 12 s counts as no response, so the same bytes served slowly can change a check. A scan that reaches its 60 s deadline is not measured at all. dns-aid reads DNS. When the DNS-over-HTTPS resolver answers no question, it is not measured. A question that fails while others answer reads as no records. A difference that comes from one of these is not a finding either. A difference in any other check is a difference in what the site returned.
It is not a directory listing. Being listed is a separate claim that only exists while the site itself carries the verification token we issued. A fingerprint matches a record we hold; it does not mean the host endorses it, or that it is in the directory.
fingerprint = SHA-256( JSON( { v: 2, host, rubric, checks: [ [check_id, status, round(points, 3), counted ? 1 : 0], … ] } ) ), rows sorted by check id in code-point order
The bytes hashed for an example record with 3 checks: {"v":2,"host":"example.com","rubric":"0.7","checks":[["llms-txt","warn",0.667,1],["product-schema","na",0,0],["reachable","pass",1,1]]}
Its fingerprint: 1bc585b130c31d45172d5d6d39580f52ee56b73deaf00365e09863c599ac8f19
serialisation v2 · v 1 fingerprints are recomputed and reported as superseded, never as tamper evidence · rubric v 0.7 in force today