SSL Certificate Types: DV, OV, EV, Wildcard, SAN
By MinniHost Guides Editorial Team Review by MinniHost Guides Editorial Team Last checked Posted Topic: SSL & HTTPS
SSL certificates vary on two separate axes. Validation says how much the certificate authority checked: domain only (DV), plus the organization (OV), or an extended identity check (EV). Coverage says which names are included: one name, a wildcard such as *.example.com, or several names in one multi-domain (SAN) certificate. Encryption strength does not change with the type.
Part of our guide: What Is an SSL Certificate? How HTTPS Works
General information, not professional security or financial advice. Check your host’s and certificate authority’s current documentation; steps differ by provider.
SSL certificates come in types along two separate lines: how much the certificate authority checked about you, and how many names the certificate covers. Mixing the two up is the most common confusion. This guide, part of our explanation of what an SSL certificate is, sets out each type, a comparison table and a plain recommendation for a small site.
What are the two axes?
Validation is who vouches for you; coverage is which names are included. A certificate has one setting on each axis. For example, you can have a domain-validated wildcard certificate or an organization-validated multi-domain certificate. Neither axis changes how strongly the traffic is encrypted.
How do DV, OV and EV compare?
DV proves domain control, OV adds a verified organization, and EV adds the strictest identity checks. The CA/Browser Forum Baseline Requirements define a separate certificate profile for each of the first levels, and each carries a reserved policy identifier in the certificate. The identifiers are 2.23.140.1.2.1 for domain validated and 2.23.140.1.2.2 for organization validated. EV certificates must follow the Baseline Requirements profile plus the separate EV Guidelines.
The Baseline Requirements also define an individual validated profile, for a person rather than an organization. It is uncommon on small business sites and we do not cover it further.
Domain validation is what automated authorities such as Let’s Encrypt provide. Let’s Encrypt says it offers only domain validation and has no plans for OV or EV.
How does coverage work: single, wildcard and SAN?
A certificate lists the names it covers in its subject alternative name (SAN) extension, and clients check that list. RFC 9525 says the Common Name must not be used to identify a service.
- Single name: one name, such as
www.example.com. Often a second name for the bare domain is included too. - Multi-domain (SAN): several named hostnames in one certificate, which can belong to different domains.
- Wildcard: a name starting
*., such as*.example.com. RFC 9525 allows only one wildcard character, and only as the complete left-most label. The Baseline Requirements allow a CA to issue*.example.combut not a name under a public suffix such as*.co.ukunless the applicant controls the whole namespace.
One private key protects every name in a certificate. If you share one wildcard key across many servers, a leak affects all of them. Wildcard issuance at Let’s Encrypt must use the DNS-01 challenge, so it needs control of your DNS.
Which type suits which site?
A single-site blog or business site normally needs a DV certificate that lists the main name and the www name. A site with many subdomains may prefer a wildcard or a SAN list. Pick OV or EV only if someone requires the verified organization name; for who is likely to need that, ask your client or compliance contact. Many hosts already issue a DV certificate on every domain, so check your control panel before buying (see installing and verifying the certificate).
Do lifetime and renewal rules differ by type?
No. The Baseline Requirements cap the validity of every public subscriber certificate, whatever its type. For certificates issued from 15 March 2026 the maximum is 200 days, dropping to 100 days from 15 March 2027 and 47 days from 15 March 2029. Read more in renewing an SSL certificate.
How does cost vary, without prices?
Cost depends on the validation level, the coverage and the vendor, which set their own prices. Domain validation can be free, as Let’s Encrypt shows. We quote no prices because they change and need a dated vendor source; get a current written quote and compare it with what your host already includes. The hosting cost calculator can take your own quote.
What not to do
- Do not buy a higher validation level because a seller says it is “more secure”. The encryption is the same.
- Do not share a wildcard private key widely or send it by email.
- Do not paste a private key into any website, including our checker.
You can confirm what a live site’s certificate covers with the certificate checker tool, and see how a request is made in what a CSR is.
Sources re-opened and compared with this text by the MinniHost Guides team on 2026-11-17. The team holds no engineering licence or vendor certification.
| Feature | Domain validated (DV) | Organization validated (OV) | Extended validation (EV) |
|---|---|---|---|
| What the CA checks | That the applicant controls the domain name | Domain control plus the organization's identity | Domain control plus the stricter checks in the EV Guidelines |
| Organization in the certificate | Not required | Verified organization name required | Verified organization details, per the EV Guidelines |
| Typical use | Blogs, small business sites, personal sites | Businesses that want their verified name recorded | Organizations that want the strictest identity checks |
| Reserved policy identifier | 2.23.140.1.2.1 | 2.23.140.1.2.2 | Defined by the EV Guidelines |
| Encryption strength | Same as the others | Same as the others | Same as the others |
A small site almost always needs only DV. Choose OV or EV only when a business or contract requires the organization's verified name in the certificate, and check what your visitors will actually see in current browsers.
Your questions answered
What are the types of SSL certificates?
They fall into two groups. By validation there are domain validated (DV), organization validated (OV) and extended validation (EV) certificates. By coverage there are single-name, wildcard and multi-domain (SAN) certificates. You pick one from each group, for example a DV wildcard or an OV multi-domain certificate. The encryption itself works the same way in all of them.
Is EV worth it for a small site?
Usually not. EV requires the strictest identity checks, but the connection is encrypted exactly as with DV. Browser interfaces change, so do not assume visitors will see the organization name without opening the certificate. Choose EV only if a client, contract or compliance rule asks for it, and check the vendor's current documentation.
What is a wildcard certificate?
A wildcard certificate has a name that starts with an asterisk, such as *.example.com, and covers names that fit that pattern. RFC 9525 allows one wildcard character, as the whole left-most label. It is convenient for many subdomains under one domain, but a leaked private key then exposes all of them. Let's Encrypt issues wildcards through DNS-01.
Does a SAN certificate cover subdomains?
Only the names listed in it. A SAN, or subject alternative name, certificate carries a list of names, and clients check that list. If you list www.example.com and shop.example.com, those are covered; blog.example.com is not unless it is listed or a wildcard is included. Many certificates combine a few listed names with a wildcard.
Is DV secure enough for a business site?
For encryption, yes. A DV certificate gives the same protection for data in transit as OV or EV. What it does not do is record who runs the site. If your business needs the organization's name verified and written into the certificate, choose OV. Security of the server, passwords and software matters far more than the validation level.
Where this comes from
- CA/Browser Forum: Baseline Requirements for TLS Server Certificates, version 2.3.1 (4 October 2026) (cabforum.org)
- RFC 5280: Internet X.509 Public Key Infrastructure Certificate and CRL Profile (rfc-editor.org)
- RFC 9525: Service Identity in TLS (rfc-editor.org)
- Let's Encrypt: Frequently Asked Questions (letsencrypt.org)
- Let's Encrypt: Challenge Types (letsencrypt.org)
- MDN: Transport Layer Security (TLS) (developer.mozilla.org)
- What Is an SSL Certificate? How HTTPS Works
An SSL certificate links a website's public key to its domain name so browsers can encrypt traffic and check who they reach. How it works, what it proves
- How to Get an SSL Certificate for Your Website
Get an SSL certificate: check your host, use automatic issuance or buy one, install it, force HTTPS and fix mixed content, with WordPress notes.
- Let's Encrypt: Free SSL Certificates Explained
Let's Encrypt issues free, automated, domain-validated SSL certificates. How ACME issuance and renewal work, the limits, and how free compares with paid.
- How to Renew an SSL Certificate Before It Expires
Renew an SSL certificate before it expires: check the end date, fix failed automatic renewals, renew a purchased one and plan for shorter lifetimes.
- What Is an SSL Certificate Chain? Root and Intermediate
An SSL certificate chain links your site's certificate through intermediates to a trusted root. What to send, common errors and how to fix them.
- Fix: "Unable to Get Local Issuer Certificate"
The error "unable to get local issuer certificate" means a client cannot find a certificate's signer. Learn which side is at fault and fix it safely.