If the gate measures your server as conformant, you are welcome to display this. It costs nothing, it requires no account, and nobody pays to show it. It links back to a live verdict that anyone can recompute, so it is worth exactly as much as the measurement behind it, and not a cent more.
Plain SVG. No script, no tracking pixel, no phone-home. It is an image and a link.
The link points at your live verdict page, not at us. Two placeholders, two shapes. The link is /e/ followed by your endpoint with the https:// removed. The image is your endpoint, URL-encoded. A reader who clicks the badge lands on the current verdict, the date it was measured, the record_sha256, and one command to recompute it, not on a page about us. If the badge ever stops being accurate, the page it links to says so before we do.
An agent can ask the same question without a browser: call lookup_server on https://gate.horizonshield.dev/mcp with your endpoint. It reads stored measurements only, contacts nothing, and reports an absent endpoint as absent rather than as a failure.
The small badge above is drawn at request time, so it stops being green the moment your row does. That is the point of it. But it is twenty pixels tall, which is fine in a footer and useless on a business card.
So there is a larger one. Same source, same rule, drawn from the register when it is asked for.
We do not have a procedure for taking a badge away. If a server stops meeting the conditions, the next request simply does not draw green. That works for a live image and it does not work for a file you saved, because a saved file stays green forever.
So the file carries the date it was measured, and the address where the current row lives. A dated snapshot is not a lie. A green rectangle with no date would be.
Print it, put it in a deck, put it on a wall. Anyone who wants to know whether it is still true has the URL right there on the image.
There is no revocation committee. If the measurement changes, the verdict changes, and the badge is simply no longer accurate. We do not police it, and we do not need to: the link next to it is live.
The operator's own servers are listed in the directory under the same conditions, including the ones that took several tries to pass. On 2026-08-08 the first run against our own servers returned 0.0% on compensation disclosure. We publish that too.