XAdES & XML signature verification
Validate XAdES digital signatures in your XML documents. Upload a signed .xml file and Chaindoc checks the XML canonicalization, signature integrity, certificate chain, timestamps, and eIDAS compliance with the EU DSS library.
Verify XAdES Signature
Upload a signed XML document to validate its XAdES digital signatures using EU DSS verification standards.
What the XAdES check includes
- Free XAdES & eIDAS signature validation
- Certificate chain and revocation checks
- Detailed report ready in seconds
- Your file is never stored
The XML you upload is never stored. Its verification report is kept privately for 7 days before being deleted, and what stays in your account afterwards is a minimal record: result, signature count, date.
What XAdES verification checks
XAdES (XML Advanced Electronic Signatures) is defined by ETSI EN 319 132 and builds on the W3C XMLDSig standard. Chaindoc runs your file through the EU Digital Signature Service (DSS) library to validate it against these rules.
Recomputes the signed hash after XML canonicalization (C14N) to confirm nothing in the document changed after it was signed. This same XAdES signature can also travel bundled inside an ASiC container.
Traces the signer's certificate back to a trusted root and checks its revocation status through CRL and OCSP responders.
Validates embedded XAdES timestamps, so the signature still holds up years later even if the signing certificate expires.
Checks whether the signature meets eIDAS rules and the ETSI EN 319 132 profile for advanced and qualified electronic signatures. The same trust model applies across all signature formats.
E-signatures that pass validation
Sign documents online and let anyone verify the result. Chaindoc pairs every signature with certificate checks, timestamps and a blockchain anchor — so your agreements survive the same scrutiny you just ran here.
Supported XAdES profiles
Chaindoc validates the four XAdES baseline profiles from ETSI EN 319 132. Each one stacks more assurance on top of the profile below it.
XAdES-BASELINE-B
The baseline. Covers the minimum an advanced electronic signature needs under eIDAS.
XAdES-BASELINE-T
Adds a trusted timestamp that proves the XML was signed before a given moment. Handy when a filing deadline is involved.
XAdES-BASELINE-LT
Bundles the certificates and revocation data into the file, so it stays verifiable even after the issuing CA goes offline.
XAdES-BASELINE-LTA
Adds an archive timestamp for long-term storage. The signature keeps validating for years, even as old algorithms get retired. See pricing for archival options.
Common questions about XAdES signature verification
What XAdES is, how the check works, and what the result means. More on our support page.
XAdES stands for XML Advanced Electronic Signatures, an ETSI standard (EN 319 132) for signing XML documents. It builds on W3C XMLDSig and adds the metadata eIDAS needs: signing time, certificates, revocation data, and timestamps. You'll see it in e-invoices, government filings, and signed data exchanges.
Same cryptography, different container. PAdES embeds the signature inside a PDF; XAdES wraps it around XML. If you're checking a signed PDF instead, use the PDF signature verification tool. For binary CMS signatures in .p7m or .p7s files, reach for CAdES verification; and when a XAdES signature is bundled with its data inside a zipped package, that package is an ASiC container. XAdES also comes in three forms (enveloped, enveloping, and detached) that PDF signatures don't have.
It's about where the signature and the data sit. Enveloped: the signature lives inside the XML it signs, which is the common case for e-invoices. Enveloping: the signature wraps the data. Detached: the signature is a separate file from the original document. This page validates enveloped and enveloping signatures because both are self-contained. Detached signatures need the original file uploaded alongside them. The form above accepts it: pick the signature file first, and a second field appears for the document it was signed over.
Yes. Italian FatturaPA, Spanish Facturae, and other national e-invoice formats sign the XML with XAdES, and this tool validates them. Drop the signed .xml in and you get the signer, the certificate chain, and whether the signature meets eIDAS.
Usually one of a few things: the XML was edited after signing, the certificate expired or was revoked, or the chain doesn't reach a trusted root. The report points to the exact step that failed, so you're not left guessing. Need custom trust anchors for an internal PKI? Check pricing.
XML signature and document verification guides
How XAdES, XML canonicalization, and certificate validation keep signed documents tamper-proof and eIDAS-ready.
