VERIFY
Confirm a message or file was really signed by who it claims. Everything happens on your device — the signature, text, and keys never reach our server.
Verification runs in your browser
The signature, text, and keys are never sent to our server and nothing is logged. You can disconnect from the internet and it still works.
The most trustworthy way, and the only way without JavaScript: verify on your own device with GnuPG. Nothing depends on this page being honest.
# import the signer's key once gpg --import signer.asc # verify a signed (cleartext) message gpg --verify message.txt.asc # verify a file by its detached signature gpg --verify wallet.tar.gz.sig wallet.tar.gz
A good signature prints “Good signature from …” with the signer's name and key fingerprint. Cross-check that fingerprint against several independent sources before trusting it.
SIGNED MESSAGE (CLEARTEXT)
SIGNER'S PUBLIC KEY
FILE (E.G. A DOWNLOADED WALLET OR RELEASE)
This file is read in your browser, never uploaded.
SIGNATURE FILE (.asc / .sig)
SIGNER'S PUBLIC KEY
Valid means the content matches this key. It does not by itself prove who controls the key — confirm the fingerprint through an independent channel.
Monero lets an address owner sign a message with their wallet. A checker for those signatures is planned here as a separate tool. For now, verify address signatures in your own wallet.