> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/3.0/configuration/securing-stifler-operations-with-ssl/finding-the-certhash.md).
# Finding the certificate thumbprint
To find the certhash, you need to find the certificate's thumbprint which can be found using either of the following:
* The IIS Certificate Manager
* The Windows Certificate Storage Manager
## Using IIS to get the certificate thumbprint
If IIS is installed, then this is the easier option. From here you can easily see all installed certificates. The UI for IIS is also the easiest way to create local self-signed certificates.
To look up an existing certificate, simply bring up the IIS Management Console (InetMgr.exe), select the **Computer Name**, and select **Server Certificates**:
You can see the certificate hash (thumbprint) in the "Certificate Hash" column. Double-click to open the certificate and under the **Details** tab, look for the **Thumbprint** property which contains the hash. This can be copied using CTRL-C.
## Using the local certificate store to get the certificate thumbprint
1. Open the local machine certificate snap-in by entering the command: **certlm.msc**.
2. Expand the **Personal** - **Certificates** folder and locate the certificate.
3. Double-click to open the certificate and at the **Details** tab, look for the **Thumbprint** property which contains the hash.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.2pintsoftware.com/stifler/3.0/configuration/securing-stifler-operations-with-ssl/finding-the-certhash.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
