Sign any document with ML-DSA (NIST FIPS-204) and receive a verifiable cryptographic certificate. Anyone can independently verify the signature — no need to trust PQCServer. Your document never leaves your browser.
Upload any file — PDF, DOCX, image, ZIP. Or type text directly. The document stays in your browser.
Your browser computes a SHA-256 fingerprint of the document. This hash uniquely identifies the document content.
The hash is signed with your ML-DSA private key — locally, in your browser. Only the signature is sent to PQCServer.
PQCServer records the hash, signature and UTC timestamp. You receive a shareable link and a JSON certificate to download.
Two parties agree to use ML-DSA signatures in their contract. Both sign and exchange certificates. Cryptographically binding if both parties accept the standard.
Sign binary releases, firmware, or code packages. Users verify the signature matches the published public key — proving authenticity and integrity.
Journalists sign documents and whistleblower material at collection time. The timestamp proves the document existed before a certain date, regardless of when it is published.
Sign research papers, datasets, or invention disclosures to establish priority. The cryptographic timestamp proves who had what knowledge at what time.
Companies can use ML-DSA for internal document workflows — sign invoices, purchase orders, or HR documents without needing a qualified certificate authority.
Sign log files, configuration snapshots, or database exports at regular intervals. Creates a tamper-evident record that can be verified years later.
PQCServer certificates are cryptographically strong but are not yet qualified electronic signatures under eIDAS. Here is a transparent breakdown:
Generate your ML-DSA keypair, sign your first document, and get a verifiable cryptographic certificate — free, no account required.