Security and trust · checked in your browser
The map is sealed. Check it yourself.
You do not have to trust us: the map's data is sealed, and your own browser checks the seal. Behind it, the town defends itself and is tested by attack, on purpose.
- Census files sealed
- 7SHA-256, checked in this browser
- Map servers contacted
- 0metadata only, never a ping
- Scores money can buy
- 0sponsored things are labeled
The seal
The census, sealed
Every number on the map comes from the census. When this page loads, your browser fingerprints each census file with SHA-256 and compares it with the seal. One changed byte anywhere and the vault will not close.
Fingerprinting the seven census files in this browser…
| file | bytes | sha-256 here | seal |
|---|---|---|---|
| days.json | 4,236 | — | — |
tumblers = each file's SHA-256, as computed herehome = matches the sealbolts = the root, one hex digit each
Defences
Behind the door, the town defends itself.
Floods
Too many requests are turned away before they are read. The limits are the same for every sender. A sender who keeps pushing is shut out for a while.
Sign-in
Guessing a key gets slower and slower. Asking where to sign in is never held against anyone. People sign in to the hall with passkeys, so there is no password to guess.
Secrets
No secret reaches the code. Anything shaped like a secret is refused before it is committed, and the town will not store one: it says where, never what, and logs strike secrets out.
Strain
A failing part is cut off before it spreads. Under strain the town protects itself before anything breaks, and the person who runs it can close it at any moment.
Tested
One way in, tested by attack.
Every call goes through the same checks, and no key lets it skip one. Every call the town answers is written into the Archive, linked by its hash to the one before.
The town is tested by red-team drills, on purpose and often. Every flaw found is fixed and kept fixed by a test, and an independent review comes before the beta widens. Some defences are still being built; we say which once they ship. We don't print the exact limits.
No wall strikes back. Clockford™ never returns traffic to a sender or reaches into anyone's systems: attackers forge where they come from, so striking back would hit someone innocent.
What it proves
What the seal proves
The seal proves the map in front of you matches the census as it was sealed. It catches corrupted, stale, partly deployed or hand-edited data, and you can watch it do so above.
The map is metadata only. Nothing in the town connects to, probes or pings a server on the map.
Look-alikes
Is this really Clockford?
Clockford never reaches out to you to approve, install or sign anything, and an approval never arrives as a link. The town's key, what a real config line looks like, and how to check a receipt yourself are on Is this really Clockford?