This page is a content-addressed public artifact: it is published on IPFS, anyone may copy or re-host it, and any copy with the same fingerprint is the authentic verifier. Every cryptographic check runs on your device. The public records it reads come from providers you can replace below β public Algorand indexers, public IPNS routers, public IPFS gateways, public DNS β so no single company, including FreeholdIP, has to exist for a record to verify.
.json (or a downloaded self-verifying copy) here,
or One per line; first that answers wins. Edits are saved in this browser only.
Algorand indexers β public, keyless read of the chain.
IPNS routers β hand over the name's SIGNED record. A courier, not an authority: the signature is checked in this page against the key carried inside the name itself, so a router cannot move a name β only fail to answer.
IPFS gateways β serve content by its fingerprint; a wrong body is detected locally and the next gateway is tried.
DNS-over-HTTPS β for the issuer domain-vouch check.
FreeholdIP mirrors (optional) β only used to fetch a credential record by its ID and for the curated-directory badge; never trusted for the math.
What this page checks, and where the trust comes from. A FreeholdIP credential is a signed document. This page recomputes the issuer's signature locally; reads the issuer's identity from the public Algorand record (a name asset whose holder address must be derivable from the declared signing key β a forger can neither hold that name nor produce that signature); re-checks the issuer's own signed revocation registry through a public IPFS gateway; and, where the issuer publishes one, checks the DNS record on the issuer's own domain. FreeholdIP's servers are not part of any of those checks.
Build source: serverless-verify.mjs in the FreeholdIP credentials repository.