Chaindoc
Verify ASiC

ASiC container signature verification

Validate the digital signatures bundled inside your .asice and .asics containers. Drop in a signed ASiC file and Chaindoc unpacks it, then checks each inner XAdES or CAdES signature, the certificate chain, container timestamps, and eIDAS compliance with the EU DSS library.

VERIFY .asice

Verify ASiC Container

Upload a signed .asice or .asics container to validate the ASiC-S / ASiC-E signatures packed inside it using EU DSS verification standards.

  • Free ASiC & eIDAS container validation
  • Every inner signature checked, one by one
  • Detailed report ready in seconds
  • Your file is never stored

We'll send a verification code to confirm your identity.

EU DSS compliant

What ASiC verification checks

An ASiC container is a ZIP package defined by ETSI EN 319 162 that carries your signed files together with their signatures. Chaindoc runs the whole container through the EU Digital Signature Service (DSS) library and checks it against these rules.

Container and manifest integrity

Unzips the ASiC package and reads the META-INF manifest that ties each signature to the file it covers. Swap a file or tamper with the manifest and the check catches it.

A verdict per signature

One container can hold several signatures over several files. Chaindoc re-hashes each signed data object and compares it to what the signature claims, so you get a pass or fail for every signature, not just the package as a whole.

Certificate chain and revocation

Traces each signer's certificate back to a trusted root and checks whether it was revoked, using CRL and OCSP responders.

Timestamps and eIDAS compliance

Reads container and signature timestamps, then confirms whether the signature meets eIDAS rules and the ETSI EN 319 162 profile for ASiC containers.

Container types

ASiC-S and ASiC-E containers

ASiC (Associated Signature Containers) is defined by ETSI EN 319 162. It's a ZIP-based package that carries the signed files together with their signatures, so everything you need to validate travels in one file.

ASiC-S (Simple)

One data file plus one signature or timestamp token. Extensions are .asics and .scs. Handy when you're timestamping or signing a single document and want a tidy, self-contained package.

ASiC-E (Extended)

Several data files, several signatures, and a META-INF manifest. Extensions are .asice and .sce. This is the eIDAS e-delivery container and the format behind most national ID-card signing.

XAdES or CAdES inside

ASiC is only the wrapper. The signatures within are either XAdES over XML or CAdES over binary CMS, and Chaindoc validates whichever it finds.

BDOC and DigiDoc files

Estonia's .bdoc is an ASiC-E container under the hood. Upload it and the DSS engine validates it the same way, along with the DigiDoc4 packages used across the Baltic eID ecosystem.

FAQ

Common questions about ASiC container verification

What ASiC is, how the check runs, and what the result means. More on our support page.

Guides and resources

ASiC containers and digital signature guides

How ASiC-E, ASiC-S, and the XAdES and CAdES signatures inside them keep signed files verifiable and eIDAS-ready.

View all articles