> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/legal-evidence/verifying-digitally-signed-documents.md).
# Verifying Digitally Signed Documents
The emSigner application has the ability to validate a Digitally Signed document. Please follow the below steps to validate the Digital Signed document.
**Step 1:** Login to emSigner Super Admin account. Click on ‘Settings’ tab to open the Admin Settings. Click on ‘***Co Branding***’ below Admin Settings.
Validate Signed File under Settings
**Step 2:** Click on the Validate Signed File to upload the Digitally signed document. Upload any PDF, XML or PKCS7 and click on validate
Upload file to validate
**Step 3:** The application will provide the status of the verification along with the certificate details.
Document verification result
The details of the Digital Signature verification, Expiry check, Trust Chain Verification check and the Revocation check details are also provided in this Document Verification Result page.
Document Signature Verification
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://support.emsigner.com/legal-evidence/verifying-digitally-signed-documents.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.