A badge on a page proves nothing. Anyone can copy a picture onto a page that steals from you. This checks something a copy cannot fake: whether the page you are actually looking at is byte for byte the page that was published, and whether its fingerprint was recorded before now.
You do not have to trust us to use this. Every step below is one you can run yourself, and the registry it checks against is public and free to query.
Read this first, it is the limit of what a seal can do. A seal proves a page served from this site has not changed since it was published. It can tell you nothing about a page on any other domain, because whoever runs that domain controls everything you see there, including a copy of this badge. So check the address bar before you check anything else. If you were sent a page and want to be certain, save the file and drop it in below: that checks what you actually have, rather than what a link claims.
shasum -a 256 thatfile
curl "https://vealth.net/anchor/verify?sha256=<your hash>"
If the fingerprints differ, the page was changed after publication. That is the whole point: a copied badge stays identical, a copied page does not.
A mesh where only one party can vouch for itself is not a mesh. The format is one file and one rule, so any party can publish their own list, anchor it on the same free registry, and be checked by this same page. Nobody needs our permission and nobody pays us.
What a seal claims is narrow and worth saying plainly: this page has not changed since it was published, and its fingerprint was on record at a known time. It does not claim the contents are true, or that the publisher is trustworthy. It closes the one hole a copied badge leaves open.
Registry: vealth.net/anchor, free to submit and free to verify. Browser verifier for any file: proof-ledger. Anchoring happens in weekly batches, so a very recently published page may be recorded but not yet anchored, and this page will say so rather than imply proof it does not have.