Every certificate inventory I've inherited has had a few OV certs nobody could explain. Usually there were three or four, imported from a commercial CA and renewed by hand once a year by whoever happened to catch the expiry email. Ask why they're OV and you get "I think security wanted that" or "the bank needed it." Ask for the document that says so and the conversation usually ends there.
Once a year, that was tolerable. CA/B Forum ballot SC-081v3 puts an end to it. Maximum leaf lifetime is already down to 200 days. It drops to 100 in March 2027 and to 47 in March 2029. The same ballot also cut how long a CA can reuse your organization's validated identity. A manual OV workflow that used to take one afternoon a year is headed for eight or more, so now is a good time to ask what the extra validation actually buys you.
What OV and EV change in 2026, and what they don't
Start with what users see. They see nothing. Chrome 77 moved the EV organization name out of the address bar in September 2019, and Firefox 70 followed a month later. Safari had already dropped it in 2018. Google had data behind the decision (Thompson et al., "The Web's Identity Crisis," USENIX Security 2019): when the EV indicator disappeared, users didn't notice, so it wasn't protecting anyone. Today the organization name in an OV or EV cert only shows up if someone opens the certificate viewer. Your customers don't.
The connection doesn't gain anything either. Put an OV cert and a DV cert on the same hostname with the same key type and you get the same handshake and the same encryption, and clients validate both the same way. Validation level describes what the CA checked before issuing. It says nothing about how your traffic is protected.
The real difference is in the Subject field. A DV cert asserts control of a domain. OV adds a verified legal entity name, locality and country. EV adds stricter vetting under the separate EV Guidelines, plus jurisdiction of incorporation and a registration number. That identity data is real, but it's weaker than it looks. In 2017 Ian Carroll registered a company called "Stripe, Inc" in Kentucky and got an EV certificate for it. Nothing was forged. Legal names are only unique within a jurisdiction.
So why do teams keep buying them? I've almost never seen the threat model come into it. It's usually one of these:
- A vendor security questionnaire asks "Does your site use an EV certificate?" because the template was last updated in 2015.
- A partner contract says so. B2B integration agreements sometimes specify OV or EV for the endpoints a partner connects to. Occasionally the partner checks at onboarding. Usually it's boilerplate nobody enforces.
- A bank or payment processor lists OV or EV in its technical onboarding docs. PCI DSS itself doesn't require any validation level. It asks for strong cryptography and valid certificates.
- An auditor treats validation level as a security control, sees DV, reads it as "lower assurance" and writes a finding. You can argue, or you can buy an OV cert. Most teams buy the cert.
Is an EV certificate worth it for a public website in 2026? No. You pay more and wait longer for vetting, and you get a field nobody reads. OV is a closer call, and only because a real contract sometimes requires it.
There's a related problem. If a partner uses your publicly trusted cert as a client certificate for mutual TLS, that setup is going away no matter what the validation level is. The Chrome Root Program is pushing CAs onto hierarchies dedicated to server authentication, and the major CAs have spent 2026 removing the clientAuth EKU from public TLS certs. Find those integrations now, while it's still a planned migration and not an outage.
What SC-081v3 does to OV and EV beyond lifetimes
Most SC-081v3 coverage sticks to the lifetime schedule and the domain control validation reuse limits (200 days, then 100, then 10 days in 2029). Those affect everyone. The change that only affects OV and EV is the limit on reusing subject identity information. Until March 15, 2026, a CA could reuse your validated organization details for up to 825 days. Now the limit is 398. EV was already on a roughly 13-month cycle under the EV Guidelines, so OV now revalidates about as often as EV.
What org revalidation involves depends on the CA. Typically it means:
- re-confirming the legal entity against a government registry or a qualified information source like Dun & Bradstreet
- verifying a phone number through a reliable source
- a callback or email confirmation with someone authorized to approve requests
If nothing has changed, it's quick. If something has, it stalls:
- The company rebranded, and the legal name in the registry no longer matches the organization on the CA account.
- An acquisition closed, the subsidiary was merged into the parent, and the old legal entity now shows as inactive.
- The D-U-N-S record still lists an old address, or the phone number of an office you left years ago.
- The callback lands on a main switchboard where nobody knows what a "certificate approver" is.
This matters more than it used to. At most commercial CAs, organization validation is tracked per organization in your account, not per certificate. When it lapses, every OV order under that organization is blocked until someone fixes it. Revalidation now comes around every 398 days and you're issuing far more often, so eventually a revalidation will land in the middle of a busy renewal period. If revalidation fails in a week with twenty renewals due, none of them issue. The DV certs keep renewing and the OV ones sit in pending.
I've watched this happen after an acquisition. Legal updated the entity name and nobody told whoever owned the CA account. The first sign of trouble was a renewal stuck in "pending validation" with nine days left on the cert. Fixing a D&B record can take weeks.
The cloud-provider trap
AWS Certificate Manager only issues DV public certificates. Google-managed certificates in GCP Certificate Manager are DV only too. So any OV or EV cert on an ALB, a CloudFront distribution or a Google Cloud load balancer is imported (AWS) or self-managed (GCP), and neither platform will renew it for you. ACM does at least send daily expiration events to EventBridge for imported certs. Everything else is up to you: generating a CSR, pushing it through the CA's portal and re-importing the result. The managed renewal the rest of your ACM inventory gets doesn't apply.
Azure is the exception. Key Vault has integrated issuers for DigiCert and GlobalSign and can request and auto-renew OV and EV certificates through them. That's the closest you'll get to managed OV renewal in the big three clouds, but there are two caveats. First, org validation still lives in your DigiCert or GlobalSign account, so a lapsed revalidation breaks Key Vault renewal just as it breaks everything else. Second, every consumer of the cert (App Gateway, App Service, your own workloads) still has to pick up the new version.
Now the math. A 47-day maximum lifetime means at least eight issuances per cert per year, and closer to twelve if you renew with a sensible buffer. For an imported OV cert going through a vendor portal, each renewal looks like this:
- Generate a key and CSR.
- Submit it and wait on the CA.
- Download the result.
- Re-import it into ACM or upload it to GCP.
- Confirm the listener picked it up.
Ten imported OV certs means more than a hundred manual renewals a year. Each one is another chance to paste the wrong chain or forget the intermediate.
The pain starts long before 2029. At 200 days you renew about twice a year, and from March 2027 it's four times. Long before the limit hits 47 days, nobody will still be renewing these through the portal.
How to find out what you actually have
The validation type is recorded in the certificate itself. Certs issued under the Baseline Requirements carry a reserved CA/B Forum policy OID in the Certificate Policies extension:
| Validation type | OID |
|---|---|
| DV | 2.23.140.1.2.1 |
| OV | 2.23.140.1.2.2 |
| Individual validation | 2.23.140.1.2.3 |
| EV | 2.23.140.1.1 |
Running openssl x509 -in cert.pem -noout -text | grep -A3 "Certificate Policies" will show it, and so will any certificate viewer. Go by the OID, not the product name on the invoice.
For the inventory, pull from everywhere certs live:
- ACM in every account and region (imported certs are flagged as imported)
- Key Vault
- GCP Certificate Manager, plus the older Compute Engine SSL certificate resources
- your external endpoints
- whatever is running on VMs or appliances
Certificate Transparency catches what the rest misses. A crt.sh search on your domains returns every publicly trusted cert issued for them, including the OV cert another team bought on a corporate card.
Then, for each OV or EV cert, answer three questions:
- Who asked for it? You need a named person, team or external party. "Security" doesn't count.
- Is the requirement in writing? That means a contract clause, a partner's onboarding spec, or an audit finding with a reference number.
- When was it last confirmed? A 2019 contract with a partner who has since replaced their whole integration stack is history, not a requirement.
Most OV certs I've traced fail the second question. The requirement was verbal, or it came from a questionnaire someone filled in once, or it was just "we've always bought OV for production." That isn't a requirement. It's a habit, and it's about to get expensive.
Deciding what moves to DV
There are only three cases.
No written requirement: move it to DV. If nobody can produce a document, switch the cert to DV through your cloud provider's managed issuance or through ACME. On AWS and GCP there's a bonus: the cert stops being imported and starts renewing itself. If someone objects later, good. Now you're discussing an actual requirement.
Written down, but only as a questionnaire checkbox or an auditor's preference: push back once. Point to the protocol: the handshake and encryption are identical, and browsers show no difference. Point out that PCI DSS doesn't specify a validation level. A lot of reviewers drop the demand once they have to justify it. If they don't, keep OV and record why.
A contractual requirement that holds up: keep OV and automate it. DigiCert, Sectigo and GlobalSign all support ACME with External Account Binding (RFC 8555, section 7.3.4). EAB ties your ACME client to your CA account. Once your organization is pre-validated there, the client can get OV certs without anyone logging into a portal. certbot, cert-manager, lego, acme.sh and win-acme all support EAB. On Azure, Key Vault's integrated issuers do the same job. On AWS you also need something that re-imports into ACM after each renewal. It's extra plumbing, but you only build it once.
For every OV cert you keep, treat org validation expiry as a hard deadline. Most teams skip this step. Your CA account shows when each organization's validation expires. Track that date wherever you already track cert expiry, alert at 60 and 30 days, and give it an owner who can actually answer a callback. Start revalidation early. Most CAs let you renew it before it lapses without blocking issuance. Finally, add one line to your M&A and rebrand checklists: tell whoever owns the CA account. That line alone would have saved several renewals I've watched go wrong.
Imported certs are the dangerous ones, because they look fine until a renewal is stuck nine days before expiry. CertPulse pulls ACM, Key Vault and GCP Certificate Manager into one inventory next to your external endpoints, so the imported OV cert on a forgotten CloudFront distribution gets the same expiry alerts as everything else. Whatever tool you use, put the certs that won't renew on their own at the top of the list. You don't want to discover them in a crt.sh search after an outage.
This is why we built CertPulse
CertPulse connects to your AWS, Azure, and GCP accounts, enumerates every certificate, monitors your external endpoints, and watches Certificate Transparency logs. One dashboard for every cert. Alerts when auto-renewal fails. Alerts when certs approach expiry. Alerts when someone issues a cert for your domain that you didn't request.
If you're looking for complete certificate visibility without maintaining scripts, we can get you there in about 5 minutes.