Extended Validation Certificate
An Extended Validation Certificate is a certificate conforming to X.509 that proves the legal entity of the owner and is signed by a certificate authority key that can issue EV certificates. EV certificates can be used in the same manner as any other X.509 certificates, including securing web communications with HTTPS and signing software and documents. Unlike domain-validated certificates and organization-validation certificates, EV certificates can be issued only by a subset of certificate authorities and require verification of the requesting entity's legal identity before certificate issuance.
As of February 2021, all major web browsers have menus which show the EV status of the certificate and the verified legal identity of EV certificates. Mobile browsers typically display EV certificates the same way they do Domain Validation and Organization Validation certificates. Of the ten most popular websites online, none use EV certificates and the trend is away from their usage.
For software, the verified legal identity is displayed to the user by the operating system before proceeding with the installation.
Extended Validation certificates are stored in a file format specified by and typically use the same encryption as organization-validated certificates and domain-validated certificates, so they are compatible with most server and user agent software.
The criteria for issuing EV certificates are defined by the Guidelines for Extended Validation established by the CA/Browser Forum.
To issue an extended validation certificate, a CA requires verification of the requesting entity's identity and its operational status with its control over domain name and hosting server.
History
Introduction by CA/Browser Forum
In 2005 Melih Abdulhayoglu, CEO of the Comodo Group, convened the first meeting of the organization that became the CA/Browser Forum, hoping to improve standards for issuing SSL/TLS certificates. On June 12, 2007, the CA/Browser Forum officially ratified the first version of the Extended Validation SSL Guidelines, which took effect immediately. The formal approval successfully brought to a close more than two years of effort and provided the infrastructure for trusted website identity on the Internet. Then, in April 2008, the forum announced version 1.1 of the guidelines, building on the practical experience of its member CAs and relying-party application software suppliers gained in the months since the first version was approved for use.Creation of special UI indicators in browsers
Most major browsers created special user interface indicators for pages loaded via HTTPS secured by an EV certificate soon after the creation of the standard. This includes Google Chrome 1.0, Internet Explorer 7.0, Firefox 3, Safari 3.2, Opera 9.5. Furthermore, some mobile browsers, including Safari for iOS, Windows Phone, Firefox for Android, Chrome for Android, and iOS, added such UI indicators. Usually, browsers with EV support display the validated identity—usually a combination of organization name and jurisdiction—contained in the EV certificate's 'subject' field.In most implementations, the enhanced display includes:
- The name of the company or entity that owns the certificate;
- A lock symbol, also in the address bar, that varies in color depending on the security status of the website.
Removal of special UI indicators
In May 2018, Google announced plans to redesign user interfaces of Google Chrome to remove emphasis for EV certificates. Chrome 77, released in 2019, removed the EV certificate indication from the omnibox, but EV certificate status can be viewed by clicking on lock icon and then checking for legal entity name listed as "issued to" under "certificate". Firefox 70 removed the distinction in the omnibox or URL bar, but the details about certificate EV status are accessible in the more detailed view that opens after clicking on the lock icon.Apple Safari on iOS 12 and MacOS Mojave removed the visual distinction of EV status.
Issuing criteria
Only CAs who pass an independent qualified audit review may offer EV, and all CAs globally must follow the same detailed issuance requirements which aim to:- Establish the legal identity as well as the operational and physical presence of website owner;
- Establish that the applicant is the domain name owner or has exclusive control over the domain name;
- Confirm the identity and authority of the individuals acting for the website owner, and that documents pertaining to legal obligations are signed by an authorized officer;
- Limit the duration of certificate validity to ensure the certificate information is up to date. CA/B Forum is also limiting the maximum re-use of domain validation data and organization data to maximum of 397 days from March 2020 onward.
Extended Validation certificate identification
EV certificates are standard X.509 digital certificates. The primary way to identify an EV certificate is by referencing the Certificate Policies extension field. Each EV certificate's CP object identifier field identifies an EV certificate. The CA/Browser Forum's EV OID is 2.23.140.1.1. Other EV OIDs may be documented in the issuer's Certification Practice Statement. As with root certificate authorities in general, browsers may not recognize all issuers.EV HTTPS certificates contain a subject with X.509 OIDs for
jurisdictionOfIncorporationCountryName, jurisdictionOfIncorporationStateOrProvinceName ,jurisdictionLocalityName , businessCategory and serialNumber, with the serialNumber pointing to the ID at the relevant secretary of state or government business registrar.