How public verification works

Anyone. There is no account, no login and no fee on this surface. If a document carries a Rox Register QR code or reference, you can check it here, whether you are the counterparty, an auditor, a regulator or simply the person the document was handed to.

Scanning the QR code is the best way in: it opens the record page directly and carries the check key that unlocks the in-browser file comparison.

The issuer computes a salted SHA-256 fingerprint of the document and seals only that fingerprint. The document itself never reaches Rox Register, and a fingerprint reveals nothing about the content it seals. Anchors are signed by 3-of-5 MPC nodes, so no single machine, and no single operator, can produce one alone.

Genuine: the reference is sealed on the register, by the named issuer, at the shown time. If the record is anchored, the on-chain transaction is displayed as evidence.

Revoked: the issuer has withdrawn the record. The seal and its history remain on-chain, but the record should not be accepted as valid.

Superseded: a newer version of the record exists; ask for the current one.

No record found: the reference is not sealed here. Check for typos, then treat the document with caution and confirm with the issuer.

Match / Mismatch (file check): your copy of the file is, or is not, byte for byte the content the issuer sealed.

The verdict does not rest on Rox's word. Anchors live on RoxChain, a chain with independent validators that Rox does not control, and every anchored record shows its transaction, slot and block time, which anyone can confirm against the chain directly.

The file check runs in your browser: the file is fingerprinted locally and never uploaded. The check key that enables it travels only in the link's fragment, which browsers never send to any server, so it stays between the document and you.