Independent Document Validation

Most signed documents cannot be independently verified.

When trust lives with the platform that created the signature, not with you, legal certainty is fragile. Tindom validates a signed document independently — and grades what it finds, from A+ to F.

Talk to usValidate a document

The problem with signed documents

Platform dependency

Most electronic signatures can only be verified by the platform that created them. If the platform changes its API, gets acquired, or shuts down, you lose the ability to verify.

Legal exposure

In disputes, a signature that can't be independently validated is a liability, not an asset. The burden of proof shifts to you. Courts and regulators expect more.

Growing risk

As AI-driven identity fraud accelerates, the bar for trusted verification is rising. Most signing infrastructure was built before that bar moved. It hasn't caught up.

The Document Trust Grade

One letter, instead of a validation report nobody has time to read.

Tindom validates electronically signed documents against the EU trusted lists, third-country lists recognised under eIDAS, the Swiss and UK trusted lists, and the Adobe Approved Trust List, on infrastructure no signing platform controls. The full technical result is still there underneath — the certificate chain, the qualification level, the ETSI outcome. The grade is what makes it usable: a single letter your team can act on without knowing what PAdES B-LT means.

A+Beyond the standardAThe ETSI standard, met in fullBTrusted and time-anchoredCTrusted, but decayingDProvable file, unprovable signerEA claim, without proofFFails

What the grade asks

Has it changed?

Integrity comes first. If the signed content has been modified since signing, nothing else about the document matters.

Who signed it?

Does the identity chain to a recognised trust regime — an EU Trusted List, a national scheme, a commercial programme — or to nobody we can check?

Will it still prove it?

Does the file carry its own proof — timestamps and embedded validation material — so it still verifies years from now, offline, without the signing platform?

Why a grade, and not just a verdict

Every organisation that receives signed documents ends up doing the same work by hand: someone opens the file, decides whether the signature is good enough, and either passes it on or escalates it. A grade turns that into a rule you can write down — accept A and B, review C and D, stop at E and F — and applies it the same way to every document, every time.

The rubric is published in full: every rung, every trust regime we check against, and what the grade does not claim. It is at v0.1.0 and still in development — a low grade does not mean a document is not legally binding.

How a document is graded →See how it works →

Built for organizations where trust is non-negotiable

Legal & Compliance

Enterprise legal teams managing high-stakes contracts that need to remain verifiable long after they were signed, regardless of the platform used.

Government Agencies

Public sector bodies that require independent, auditable trails for administrative decisions and inter-agency document exchange under eIDAS.

Financial Institutions

Lenders, insurers, and asset managers whose regulatory obligations demand more than a vendor's assurance. They need verifiable, third-party proof.

Talk to us

Try the validator

Drop any electronically signed document — PDF, XML, or a CMS/JSON signature — to see its grade and validation status instantly. Free, no login required.

Validate a document