Knowledge Base

Overview 

This article explains Organization Validation (OV) SSL/TLS certificate validation and what customers can expect during the process. OV validation confirms that a website is operated by a verified organization or individual and that the certificate request was properly authorized. 

OV SSL/TLS certificates provide a higher level of trust than Domain Validation (DV) certificates by verifying identity information in addition to domain control. 

Common Questions This Article Answers 

• What is an Organization Validation (OV) SSL/TLS certificate? 

• How is OV validation different from DV and EV? 

• What information is verified during OV validation? 

• What actions are required from me during OV validation? 

• How does OV SSL/TLS help build trust for my website? 

 

What is Organization Validated (OV) SSL/TLS Validation? 

Organization Validation (OV) SSL/TLS certificate validation verifies both control of the domain name and the identity of the certificate holder defined by global industry standards (CA/Browser Forum Baseline Requirements). 

OV SSL/TLS certificates may be issued to: 

• Individuals 

• Private organizations 

• Registered business entities 

• Government entities 

• International entities 

OV SSL/TLS certificates are commonly used by individuals and organizations that want to secure their websites while also providing visitors with visible assurance of verified identity. Typical use cases include: 

• Business and organizational websites that want to show verified ownership and legitimacy 

• Professional or individual websites where identity verification is important for trust 

• Public‑facing services that collect user information or credentials 

• Non‑commercial and community organizations that want to demonstrate transparency and authenticity 

• Government or public sector websites that require encrypted connections and verified identity 

• Small to medium‑sized organizations that want stronger trust indicators than DV certificates without the additional requirements of EV. 

OV SSL/TLS certificates provide a balance between security, identity verification, and ease of issuance, making them suitable for a wide range of websites. 

 

How OV SSL/TLS Validation Works 

OV SSL/TLS validation follows industry‑standard verification practices to confirm that a certificate request was submitted by a legitimate and authorized individual or organization. 

Unlike DV SSL/TLS certificates, which only verify domain ownership, OV SSL/TLS certificates require additional validation: 

1. Verification of identity information 

2. Confirmation of contact details 

3. Confirmation that the certificate request was authorized 

Trusted public data sources such as reliable third-party business data sources, government registries, and public records are used to complete these checks. The validation process also includes confirming domain control and contacting the organization to ensure the request is authorized. 

 

What Is Verified During OV SSL/TLS Validation 

OV SSL/TLS validation includes the following required checks, depending on whether the certificate is issued to an organization or an individual: 

Identity Verification 

• Organization: Confirms the organization’s name using reliable third‑party data sources or government registries 

• Acceptable organization name format in the certificate: Legal name or DBA or DBA (Legal Name) 

• Individual: Confirms the individual’s legal name using a valid, government‑issued photo identification document 

Address Verification 

• Organization: Verifies the organization’s address and confirms that it is the applicant’s operational or physical business address using reliable third-party public data sources and/or government sources. If discrepancies are found, additional documentation may be required 

• Individual: Verifies physical presence using reliable information associated with the individual’s government‑issued identification 

Contact Information (Method of Communication) 

• Confirms a working business phone number or email address listed in reliable third‑party data sources or government registries 

Domain Control Verification (DCV) 

• Confirms that the applicant controls the domain name(s) included in the certificate using a supported method 

Subscriber Agreement and Request Authenticity (Callback) 

• Verification that the Subscriber Agreement was signed 

• Confirms that the certificate request was legitimately authorized by the individual applicant or by an authorized representative of the organization 

 

What to Expect During OV SSL Validation 

While validation is in progress, customers are expected to: 

• Complete Domain Control Verification (DCV) using one of the supported methods. 

• Review and accept the Subscriber Agreement. 

• Respond to a verification call or email confirming certificate authorization (see more details below). 

• Provide additional documentation if requested by the validation team. 

Prompt responses help prevent delays. 

If any organization's details cannot be verified, a Validation Specialist will reach out with guidance on how to resolve the issue. 

Customers can track validation progress and required actions through the Validation Manager link included in the order confirmation email. 

 

Certificate Request Authentication (Callback) 

Callback authentication is a critical part of secure and compliant OV SSL/TLS certificate issuance. This step helps prevent fraud, ensures regulatory compliance, and protects the trust that end users place in digital certificates. 

For OV SSL/TLS certificates issued to organizations, a reliable method of communication must be used to confirm that the certificate request is authentic and properly authorized. This verification may be completed with an authorized representative of the organization or through an authoritative source associated with the organization. 

How Callback Authentication Works 

Callback authentication confirms that the certificate request was intentionally submitted and approved. The following callback methods may be used, depending on the situation: 

• Automated telephone callback 
  An email is sent to the applicant’s administrative contact containing a link to initiate an automated call to a verified business phone number. During the call, a verification code is provided. Entering this code completes the authentication process. 

• Automated email callback 
  A verification link is sent to a verified business email address. Clicking the link confirms authorization using a secure and traceable communication method. 

• Manual callback (phone or email) 
  Manual callbacks are used when automated methods are unavailable or when additional verification is required. These callbacks are performed by a validation specialist using verified contact details. 

All callback methods are designed to ensure secure, reliable, and efficient authentication based on the applicant’s circumstances. 

If You Have Trouble Completing the Callback 

• If the automated callback fails but the phone number or email address is correct, contact support via chat to request a manual callback. 

• If the phone number or email address is incorrect or cannot be verified, upload documentation showing a valid business phone number or email address for your organization. 
  This documentation must come from a reliable third‑party data source or government registry and list the contact details under the same organization name. 

Important Notes About Callback Verification 

• Callback authentication can only be completed using phone numbers or email addresses that are independently verified through reliable third‑party data sources or government registries. 

• Callback attempts are not made using unverified or self‑provided contact details. 

• Completing this step promptly helps prevent delays in certificate issuance. 

 

Frequently Asked Questions (FAQs) 

Why does OV validation take longer than DV? 

OV SSL/TLS certificates require verification of identity and contact information in addition to domain control. These extra checks may require customer interaction, which can extend the validation timeline compared to DV certificates. 

Why do I need to complete a callback (verification call or email)? 

The callback confirms that the certificate request was intentionally submitted and approved by the correct individual or organization. This step helps prevent unauthorized or fraudulent certificate issuance and is required for OV certificates. 

How does the callback process work? 

Callback authentication is completed using a verified business phone number or email address. Depending on the situation, this may be done through an automated call, an automated email verification link, or a manual callback. All methods use secure and traceable communication channels. 

Why can’t the callback be completed using my provided phone number or email? 

Callback verification can only be completed using contact details that are independently verified through reliable third‑party data sources or government registries. Self‑provided or unverified contact information cannot be used for this step. 

What should I do if the automated callback fails? 

If the automated callback does not work but the phone number or email address is correct, you can contact support via chat to request a manual callback. Manual callbacks are performed using the same verified contact details. 

What if the phone number or email address on file is incorrect? 

If the contact information cannot be verified, you may be asked to provide documentation showing a valid business phone number or email address. This documentation must come from a reliable third‑party data source or government registry and list the contact details under the same organization name. 

Why was I asked for documentation or clarification? 

Additional information may be requested if identity, address, or contact details cannot be independently confirmed, or if submitted information does not match trusted public records. 

What should I do if my OV order seems stuck? 

Track validation progress and required actions through the Validation Manager link included in the order confirmation email. Review pending items in your Validation Manager portal and in any communication email, complete DCV, ensure the Subscriber Agreement is signed correctly, and respond to any verification requests.