> 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/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-ov-public-trust-certificates/phase-1-steps/step-2-certificate-signing-request-csr.md).
# Step 2 - Certificate Signing Request (CSR)
A Certificate Signing Request (CSR) is a file you generate on your web server before applying for the certificate. It contains your public key and basic identity information. The CA uses the public key in your CSR to create your certificate - the corresponding private key remains securely on your server and is never sent to anyone.
**Important**
The public key and signature algorithm from your CSR are used for certificate generation.
Subject details such as Organization, Country, and State are pre-filled from your CSR for convenience but can be edited.
The values you submit in the form will be the final values in the issued certificate.
***Skip CSR**: An option to bypass CSR submission at this stage if you do not yet have one prepared. The CSR will then need to be provided before the certificate can be issued. Only use Skip CSR if specifically instructed by your administrator. In most cases, have your CSR ready before starting the application.*
***Upload CSR (Choose File button)**: Upload a CSR file (.csr or .txt) directly from your computer. Click Choose File, navigate to your saved CSR file, and select it. The CSR text will be loaded automatically.*
***Paste CSR (text area)**: An alternative to file upload - paste the raw CSR text directly into this box. Copy the full CSR text from your server (including the -----BEGIN CERTIFICATE REQUEST----- and -----END CERTIFICATE REQUEST----- lines) and paste it into this field.*
**CSR Format - What It Looks Like**
A valid CSR begins with: -----BEGIN CERTIFICATE REQUEST-----
Followed by several lines of base64-encoded text.
Ends with: -----END CERTIFICATE REQUEST-----
*Ensure you copy the entire block including the BEGIN and END lines.*
**Key Size Recommendation**
*When generating your CSR, use a minimum key size of 2048 bits (RSA) or 256 bits (ECC/ECDSA).*
CERTInext shows the key size and algorithm from your CSR on the final order view.
The screenshots in this guide show RSA 4096-bit keys.
**Action**
*After uploading or pasting your CSR, click Next to proceed.*
---
# 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/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-ov-public-trust-certificates/phase-1-steps/step-2-certificate-signing-request-csr.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.