A properly signed PDF (PAdES format) carries its own proof: a cryptographic seal embedded in the file, checkable against public EU and Adobe trust lists without contacting the platform that created it. If the file has no embedded seal, its authenticity depends entirely on the platform’s own records instead.
When a signed agreement is disputed, or you simply need to hand proof of authenticity to someone else, logging into the original signing platform isn’t always possible. The counterparty may have used a platform you have no account with. The dispute may be adversarial, and you don’t want to rely on the other side’s vendor to confirm their own signature is genuine. Or the platform itself may no longer exist. In every one of these cases, what you actually need is a way to check the file, not the vendor.
Open the PDF in a viewer that shows signature panels (Adobe Acrobat does this natively). A properly built electronic signature under eIDAS uses the PAdES format, embedding the signature directly in the PDF’s own signature dictionary. If the viewer shows no signature panel at all, the document’s authenticity claim, whatever it is, lives outside the file, typically in the signing platform’s own database.
A found signature panel tells you a signature exists, not that it’s trustworthy. The certificate behind it needs to chain up to a recognized trust anchor: the EU List of Trusted Lists (LOTL) for EU-qualified signatures and seals, or Adobe’s AATL for signatures built for Acrobat trust without an EU qualification behind them. See Adobe AATL vs EU LOTL for what each actually proves.
The cryptographic seal covers the exact bytes of the file at the moment of signing. Any change afterward, even a single re-saved page, breaks the seal’s match and should show as invalid in a proper validator. This is the property that makes an embedded signature meaningful evidence: it’s not just "someone signed this at some point", it’s "this exact file, unchanged, was signed by this certificate."
Reading a signature panel is one thing; parsing the certificate chain, checking revocation status, and confirming trust-list membership by hand is not realistic for most people, and Adobe Acrobat’s own signature panel doesn’t independently re-verify against the EU list. That’s the actual gap an independent validator fills: running the check server-side against every trust list it carries and returning a plain answer, rather than asking you to interpret a certificate yourself.
Plenty of signed documents, especially from platforms built around a simple click-to-sign flow, carry no independently verifiable seal in the file itself. That’s not necessarily a legal problem, but it does mean the document’s authenticity can’t be checked independently of the platform’s own word. Worth knowing before a dispute, not during one.