Free Forever

Verify Any Document.
Free. Forever.

Anyone can verify a Sealayer-anchored document instantly. Scan a QR code, upload a file, or paste a hash. No account required. No fees. No limits.

Three Ways to Verify

Choose the method that works best for your situation. All three produce the same cryptographic verification.

METHOD 01

QR Code Scan

Every Sealayer-issued document contains a unique QR code. Scan it with your smartphone camera and you are taken directly to the verification result -- no app download required.

  • Works with any smartphone camera
  • No app installation needed
  • Instant redirect to verification page
  • Shows full issuer and blockchain details
QR Code

Point your camera at the QR code on the document

METHOD 02

File Upload

Upload the document file directly to our verification portal. We compute the SHA-256 hash locally in your browser and check it against the blockchain -- your file never leaves your device.

  • Hash computed locally in browser
  • File never uploaded to our servers
  • Supports PDF, images, and Office formats
  • Compares against blockchain record

Drop your file here

PDF, PNG, JPG, DOCX

Hash is computed locally -- your file never leaves your device

METHOD 03

Hash Lookup

If you already have the document hash (SHA-256), paste it directly into the verification portal. We check the hash against every blockchain anchor in our system and return the result instantly.

  • Paste any SHA-256 hash
  • Checks all blockchain anchors
  • Shows full issuance history
  • API available for integrations
a3f8e2b1c4d5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1

Paste any SHA-256 hash to check against blockchain records

Tamper Detection

When verification fails, you know exactly why. Sealayer detects every form of document tampering.

Hash Mismatch

If even one byte of the document has been modified, the SHA-256 hash will not match the blockchain record.

Missing Anchor

If a document claims to be Sealayer-verified but has no blockchain anchor, the verification fails immediately.

Timestamp Mismatch

If the RFC 3161 timestamp does not match the blockchain record, the document has been tampered with after issuance.

Revoked Document

If an issuer has revoked the document, the verification will show the revocation date and reason.

Crystal-Clear Results

Verification results are designed for clarity. Whether the document is verified, tampered, or unknown, the result is unambiguous and includes full provenance details.

  • Green/red status indicator -- no ambiguity
  • Issuer name, date, and organisation details
  • Blockchain transaction link (Polygonscan)
  • RFC 3161 timestamp verification
  • Document hash and Merkle proof
Document Verified

Issuer: Bright Bytes Technology LLC

Blockchain: 0x3f1a...8b2e

Verification Failed

Reason: Hash mismatch -- document has been modified

Expected: a3f8...c92d

Try It Right Now

Verify any Sealayer-anchored document. It takes 5 seconds. No account. No payment. No limits.