> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/getting-started/key-concepts-and-terminology.md). # Key Concepts and Terminology Before you can get the most out of CERTInext, it helps to have a solid grounding in the terminology the platform uses - not just the obvious terms like "certificate" and "CA," but the operational concepts that shape how things actually work day to day. This section covers the foundational vocabulary: digital certificates, Certificate Authorities (CAs), private and public PKI, Certificate Signing Requests (CSRs), domain validation, discovery, provisioning, renewal, revocation, and automation workflows. It also walks through the operational components you'll encounter in the platform - Bots, scan targets, CA connectors, key stores, and trust chains - and explains the distinction between discovery and provisioning, which trips up a lot of new users. Getting this vocabulary straight matters because it affects how you configure integrations, read dashboard metrics, apply lifecycle controls, and troubleshoot when something goes wrong. It also gives technical, operational, and compliance teams a shared language, which is often the first thing that breaks down when certificate incidents occur. Whether you're connecting to public CAs like emSign and DigiCert, working with private CAs such as emCA or AD CS, or managing cloud and container environments, consistent terminology is what keeps policy enforcement coherent across the board. --- # 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://docs.certinext.io/documentation/getting-started/key-concepts-and-terminology.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.