> 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-smime-certificates/phase-1-steps/step-4-certificate-information.md).
# Step 4 - Certificate Information
This screen specifies the email address that will be secured by the S/MIME certificate. This is the most important field; it defines which email account the certificate will protect.
#### Field Reference
• Use Pre-Verified Domains: A checkbox that, when ticked, populates the Email ID field from a list of domains already verified by your organisation. Tick this if your IT administrator has already verified your email domain in CERTInext. Select your email from the resulting dropdown.
• Email ID (\*): The email address that this S/MIME certificate will be issued for. This becomes the 'Common Name' in the certificate. Enter the full email address of the mailbox this certificate is meant for (e.g., ).
**WARNING:** The Email ID entered here is permanently embedded in the certificate. If you enter the wrong email address, the certificate will be issued for the wrong mailbox and a new order will be required.
**NOTE**: If the Email ID is already populated from your CSR, review it carefully to make sure it matches the mailbox you intend to secure.
#### What to Do
• If your domain is pre-verified, tick 'Use Pre-Verified Domains' and select your email from the list.
• If not, type the full email address directly into the Email ID field.
• Double-check the email address - this cannot be changed after submission.
• Click Next.
---
# 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-smime-certificates/phase-1-steps/step-4-certificate-information.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.