> 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-5-certificate-information.md).

# Step 5 - Certificate Information

This step shows a summary of your organization's details (auto-filled, read-only) and collects the domain name(s) the certificate will protect. This is where the four products differ most significantly.

&#x20;

<figure><img src="/files/EPHvlkxyYhiGcXdzhcz3" alt=""><figcaption></figcaption></figure>

&#x20;

#### 5a. Organization Summary (Read-Only - All Products)

*The top portion of this screen displays the organization details you confirmed in Step 3. These fields are informational only and cannot be edited here. If you notice an error, click Back to return to Step 3.*

Organization Name - Your organization's legal name (e.g., ABC limited)

Organization Unit - Department name or blank if not specified

Street Address 1 - Registered street address

Street Address 2 - Additional address details or blank

Country - Country of registration (e.g., United States of America (USA))

State / Province - State or province (e.g., California)

Locality - City (e.g., California)

Postal Code / Post Office Box Number - ZIP/postal code (e.g., 8765678)

&#x20;

#### 5b. Domain Name Fields - Differences by Product

**Product Difference**&#x20;

The domain entry section below the organization summary is the key difference between the four OV products.

Read the sub-section for your chosen product carefully.

&#x20;

**OV SSL Certificate - Single Domain**

<figure><img src="/files/JVZ6mOTHUflFb9OSWgAC" alt=""><figcaption></figcaption></figure>

&#x20;

**Automatically secure 'www' variant of websites**: *A checkbox that, when ticked, instructs the system to also secure the [www.yourdomain.com](http://www.yourdomain.com) version of your domain automatically, at no extra cost. Tick this box if your website is accessed both with and without 'www' (which is the case for most websites). Leave unticked only if your domain is exclusively accessed without [www](http://www).*

**Domain Name (\*)**: *The single fully-qualified domain name (FQDN) the certificate will protect (e.g., shop.example.com). Type the domain name exactly as it should appear in the certificate. Do not include 'http\://' or 'https\://'. Example: example.com or portal.example.com*

**Note - OV SSL Domain**&#x20;

Enter only the base domain or subdomain you want to protect. A single OV SSL certificate covers exactly one domain.

The 'Automatically secure www variant' checkbox adds [www.yourdomain.com](http://www.yourdomain.com) as an additional SAN (Subject Alternative Name) at no extra cost - tick it unless you have a specific reason not to.

&#x20;

**OV Wildcard SSL Certificate - Single Wildcard Domain**

<figure><img src="/files/1E5xS53PHwV5KySs17oA" alt=""><figcaption></figcaption></figure>

&#x20;

**Domain Name (\*)**: The wildcard domain in \*.yourdomain.com format. The asterisk (\*) represents any single subdomain label. *Enter the wildcard domain using the \*.yourdomain.com format. Example: \*.example.com - this will cover mail.example.com, shop.example.com, portal.example.com, etc. Do NOT include the asterisk if you want the root domain only; use OV SSL for that.*

**Note - OV Wildcard SSL Domain**&#x20;

The 'www variant' checkbox is not available for Wildcard certificates because \*.domain.com already covers [www.domain.com](http://www.domain.com) (www is itself a subdomain).

**Note**: a Wildcard certificate covers only ONE level of subdomain depth. \*.example.com covers shop.example.com but does NOT cover deep.shop.example.com.

&#x20;

**OV UCC SSL Certificate - Multiple Domains**

<figure><img src="/files/i44IrZ2RdR4tjkztNWjt" alt=""><figcaption></figcaption></figure>

&#x20;

**Automatically secure 'www' variant of websites**: *Tick to also secure the [www.yourdomain.com](http://www.yourdomain.com) version of the primary domain automatically. Tick if applicable for your primary domain.*

**Domain Name (\*)**: The primary (main) domain name the certificate will protect. *Enter your primary domain name (e.g., example.com).*

**Additional Domain Names (\*)**: A multi-entry field where you add all extra domain names beyond the primary domain. *Each domain appears as a removable tag. The included base is up to 4 domains total (primary + additional).* Beyond 4, each domain is charged at $XXX USD. *Click inside the 'Select' dropdown/input box and type each additional domain, pressing Enter or clicking the '+' button after each one. You can also click 'Import additional domain' to paste or upload a list of domains in bulk. Click the X next to any domain to remove it.*

**Import additional domain (button)**: Allows bulk import of multiple domain names at once instead of adding them one by one. *Click to open an import dialog. Paste a list of domain names (one per line) and confirm.*

**Clear (button)**: Removes all entries from the Additional Domain Names list. Use only if you want to start the domain list from scratch.

**Note - OV UCC SSL Domains & Pricing**&#x20;

The base price covers up to 4 domains (1 primary + up to 3 additional).

Each domain beyond 4 costs extra.

*The Order Summary in Step 7 will display a separate line item: 'Additional SAN Cost' so you can verify the total before paying.*

Plan your domain list carefully - domains can be added/removed after issuance using the 'Add / Remove SANs' action, but each change may require additional domain verification.

&#x20;

**OV Wildcard UCC SSL Certificate - Multiple Wildcard Domains**

<figure><img src="/files/CNCCHEIY2taK0s4IXVbc" alt=""><figcaption></figcaption></figure>

**Domain Name (\*)**: The primary wildcard domain in \*.yourdomain.com format. *Enter the primary wildcard domain (e.g., \*.example.com).*

**Additional Domain Names (\*)**: Additional wildcard or regular domain names beyond the primary. Base price covers up to 4 entries total. Each additional domain beyond 4 costs extra. *Add each additional wildcard domain (e.g., \*.example.net, \*.another-domain.com) using the same method as OV UCC SSL described above.*

**Import additional domain (button)**: Bulk import of additional domains. *Same as OV UCC SSL - paste a list for bulk entry.*

**Note - OV Wildcard UCC SSL Domains & Pricing**&#x20;

The base price covers up to 4 wildcard domains.

Each additional wildcard domain beyond 4 costs extra.

This is significantly higher than the UCC SAN cost because each wildcard entry covers an entire subdomain namespace.

The 'www variant' option is not available here - wildcard domains already cover www as a subdomain.

&#x20;

**Action**&#x20;

*After entering all domain name(s), click Next to proceed to Step 6.*


---

# 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-5-certificate-information.md?ask=<question>&goal=<endgoal>
```

`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.
