Organization Validation (OV) SSL Certificate Requirements

An Organization Validation (OV) SSL Certificate sits between Domain Validation (DV) and Extended Validation (EV). Alongside checking control of the domain, the Certificate Authority (CA) confirms that the organization behind the request is a real, registered business.

That extra step means a little paperwork and a short wait, so it helps to know what is required before you start. Learn About SSL Certificate Validation 🔗

What the Validation Covers

An Organization Validation (OV) SSL Certificate involves two checks. The first proves control of the domain, and the second confirms the organization exists and operates legally.

The organization details that are verified are recorded in the SSL Certificate, which is what separates an Organization Validation (OV) SSL Certificate from a domain-only one. The check usually takes one to three business days once the paperwork is in order.

Proving Control of the Domain

Domain control is proven through Domain Control Validation (DCV), using the same methods as any other SSL Certificate. You can place a Domain Name System (DNS) TXT record, upload a supplied file to the web server, or reply to an e-mail sent to a fixed role address.

This part no longer relies on WHOIS. Following an industry rule change during 2025, contact details drawn from WHOIS are not accepted, so the Domain Name System (DNS), file, or role-address routes are what prove control now. Learn About Domain Control Validation (DCV) 🔗

Documents the Organization Provides

To confirm the business, the Certificate Authority (CA) asks for official evidence that it exists. This usually means government-issued registration documents or articles of incorporation, suited to the jurisdiction.

Proof of the physical address may also be requested, such as a recent utility bill or bank statement. Where the business trades under a Doing Business As (DBA) name, documents linking that name to the legal entity are needed too.

Confirming the Requester

The Certificate Authority (CA) also checks that the person ordering the SSL Certificate is authorized to do so for the organization. This is often a brief call to a published business number, or contact with someone named in official records.

The requester should be ready to confirm details of both the order and the organization. Having the right person available keeps this step short.

Preparing the Certificate Signing Request (CSR)

An Organization Validation (OV) SSL Certificate needs a Certificate Signing Request (CSR) whose details match the verification documents, including the organization name and location. A mismatch here is a common cause of delay.

Generate the Certificate Signing Request (CSR) on your server and keep the matching Private Key safe, since it cannot be recovered if lost. Learn About Certificate Signing Requests (CSR) 🔗

Avoiding Common Delays

Most hold-ups come from small mismatches between the documents, the Certificate Signing Request (CSR), and the domain registration. Exact, consistent names and addresses across all of them keep the check moving.

Out-of-date public business listings are another frequent cause. Checking and updating those before you start saves a back-and-forth later. Read the Trustico® Organization Validation (OV) Guide 🔗

After Issuance

Once issued, the Organization Validation (OV) SSL Certificate is installed on the web server with its Private Key and the intermediate files that complete the chain. Keep your organization and contact details current with the Certificate Authority (CA) for future checks.

The SSL Certificate is validated again for each new term, and a reissue stays free during its life for a Private Key change or a server move. Learn About SSL Certificate Installation 🔗