Extended Validated (EV): support all features of OV certificates. In addition, a strict check is carried out as to the legitimacy of the company. EV certificates will not be accepted if they are not recorded in multiple transparency logs.
With SSL API 2.0 integration:
- DV certificates will require a “Tech Contact”.
- OV certificates will require the above and an additional “Organization Contact”.
- EV certificates will require the above and an additional “EV Approver Contact”. This is the contact person allowed to approve EV certificates in an organization.
Complete EV validation process
- Complete Domain Control Verification (DCV) to verify the domain(s) are controlled by the organization. This can be completed using 1 of 3 methods: DCV email, CNAME or HTTP(S) challenge.
- The CA must validate your authority to order a certificate for the given organization on the order. To do this, there will be a telephone call through the main business phone number to speak with someone who represents the organization such as the technical contact.
- It is possible there will be an email requesting for additional information.
What Details are Validated?
Typically, EV Validation basics consist of verifying the following:
- Organization legal name and status is in good standing
- Organization tradename / DBA (Doing Business As) if applicable
- Currently operating the business
- Address where you conduct business operations
- Organization main telephone number
- Control the domain(s) listed on the certificate
- Authenticity of the subscriber agreement
All CAs are bound to guidelines, which makes the validation process almost identical. For further details, please visit Sectigo’s knowledge base or DigiCert's documentation.