Talk to us →
Home / Verify a document
Document registry - live

Verify a document against the LENS registry.

Scan a LENS verification QR, enter the printed reference, or upload the exact electronic file. The live registry reports whether it has a matching record and whether that record is current, superseded, revoked, or expired.

Coverage: the registry can answer only for documents formally registered by LENS. A missing result is inconclusive, especially for material issued before 21 August 2026. Email solutions@lenscorp.ai when a result needs human confirmation.

Registry
Live
Account required
No
Lookup methods
3
File limit
25 MB
Step 1 - present the document
No account needed
Camera off

Camera starts only after you tap. Video stays on this device; only the decoded LENS code is checked.

Where to look
Illustration only. A document-specific block may appear on an issued file.

No camera? Use or the form.

Step 2 - registry answer
Nothing checked yet

Results come from the live registry. The page does not infer authenticity from branding, filenames, text or appearance.

Document type
Reference
Issuing entity
Issue date
Validity
Revision
Lookup scope
Registry status
Live registry·File bytes stay on your device·Answers are not cached
How verification works

One registry, three lookup paths with clear limits.

The verifier separates QR possession, public-reference status and exact-file matching so the answer never claims more than the evidence supports.

01 - At issue

The record is registered

LENS records the reference, permitted metadata, authoritative-file digest and a one-way digest of the document QR token.

02 - By QR

Possession is checked

The scanned capability can resolve its attached record, including protected classes, while the database still applies that class's field redactions.

03 - By reference

Public status is checked

A typed or scanned reference returns only the public fields allowed for that document class. Protected references remain non-enumerable.

04 - By exact file

The bytes and status are matched

The browser calculates SHA-256 locally. A match identifies the exact registered bytes, while an uncached answer reports current status.

LENSCORP AI PRIVATE LIMITED
Active issuing entity - CIN U72900UP2021FTC143729
LENSCORP PRIVATE LIMITED
Active issuing entity in the LENS registry
The live verifier uses practical privacy and integrity controls
On-device hashing
The selected file bytes remain in your browser
One-way QR storage
The registry stores only a digest of each random token
Disclosure rules
Sensitive classes are not enumerable by public reference
Fresh status
Verification responses use no-store caching controls
Designed for the document in front of you

A clear answer, with its limits visible.

The mobile flow keeps the verdict, record and evidence scope together. The camera opens only after a deliberate tap, and reference entry remains available when a code will not scan.

01Camera permission is requested only after you choose to scan
02Every verdict states whether it came from a QR, reference or exact-file digest
03Unknown, unavailable and sensitive-document cases fail without a false authenticity claim
Before you rely on a result

What the verifier does and does not prove.

What happens to a file I select?
Your browser reads the file and calculates its SHA-256 digest locally. The file bytes are not uploaded. Only the digest is sent to the registry for matching, and a verification event is recorded under the privacy and retention policy.
What is the difference between a QR, reference and file check?
A QR check proves possession of an active capability attached to a registry record, but a code can be photographed or forwarded. A reference check resolves only document classes that permit public reference lookup. Neither checks the content of the copy in front of you. A file check compares the exact SHA-256 digest of the electronic file against an authoritative registered file.
Why can a genuine-looking file fail to match?
Any byte change creates a different digest. Re-saving, flattening, compressing, converting, digitally signing again, scanning or photographing a document can all change its bytes. A digest miss is inconclusive; it is not proof of tampering or fraud.
Does "no matching public record" mean the document is fake?
No. It means only that this lookup returned no public match. The document may predate the registry, may not yet be backfilled, may belong to a class that requires an exact-file lookup, or may be unregistered. Ask LENS for manual confirmation before making a fraud allegation or a high-impact decision.
Why do some document references return no details?
Some commercial and personal-subject documents are deliberately not enumerable by reference. Scan the document-specific QR or, if you hold the exact electronic file, use the upload tab. Both paths can answer without exposing the document through a guessable identifier, and protected fields remain redacted.
What should I do before paying or changing bank details?
Do not rely on branding or email appearance alone. Verify the exact registered file where possible and confirm any banking change through a known LENS contact using independently sourced contact details. For manual review, send the document and source email to solutions@lenscorp.ai.

Need a human confirmation?

Send the document, the address it arrived from and the printed reference to solutions@lenscorp.ai. The team can confirm records that are older, restricted or not yet backfilled.

solutions@lenscorp.ai → +91 99907 36796