The product

Independent validation.
One neutral infrastructure.

Tindom verifies what was signed — the signature format, the certificate chain, the qualification level — independent of the platform that created it, and independent of any single trust list. Built on infrastructure no platform controls.

Document validation

Independent verification. No platform dependency.

Tindom validates PAdES, XAdES, CAdES, and JAdES signed documents — the four formats that cover virtually every electronically signed document in active use today, from signed PDFs to XML-based government filings, CMS-signed enterprise documents, and JSON-based signatures — against the EU trusted lists, third-country lists recognised under eIDAS, the Swiss and UK trusted lists, and the Adobe Approved Trust List, using a self-hosted engine independent of the platform that created the signature. The result is structured evidence: the qualification level, the signer, the trust chain, and when it was verified, all without relying on a vendor's assurance.

The Document Trust Grade

The result, expressed as one letter.

A validation result is a technical object: an ETSI indication, a baseline level, a trust regime, a revocation status. Tindom reports all of it — and then grades it, A+ to F, against a rubric published in full. The grade answers the question an organisation actually has to answer about every incoming document: how strongly does this file prove, on its own, who signed it and that it has not changed — and how long will it keep proving it, without the signing platform?

Integrations

Built to fit into how you already work

Every validation on this site runs through a structured JSON API under the hood: submit a document, get back the signature format, qualification level, trust chain, and verification time. Organizations that want to call that directly from their own systems, rather than through the web widget, can talk to us about API access.

It's already live in a simpler form, too: send a signed document to validate@tindom.se and get a structured validation report back by email — no integration work required.

The next step is making that capability callable from wherever documents already flow: a document-management system checking authenticity before filing, a case-management platform verifying a submission, or an AI agent validating a signature before acting on a contract. We're exploring MCP support specifically so agentic workflows can call Tindom's validation as a tool, not just a website.