🟢
blog.cat.ssl

EV SSL: Why Browsers Dropped the Green Company Name

20.11.2026
← All articles

A few years ago, some websites showed the company's legal name in green next to the padlock in the address bar. That was the mark of an EV (Extended Validation) certificate, common on banks, large shops and payment services. Today Chrome, Firefox and Safari no longer display it. EV certificates still exist; browser makers deliberately stopped highlighting them.

What EV actually verifies

All SSL certificates encrypt the same way. The difference is what the certificate authority checks before issuing. DV (Domain Validation) only confirms control of the domain. OV (Organization Validation) also confirms the organization exists. EV is the strictest: legal registration, operational existence, address, phone verification and the authority of the person requesting it. The green name was meant to let users tell a real bank from a phishing look-alike.

Why browsers removed the green name

It did not work as hoped. Browser teams' research found most users did not notice whether the EV indicator was present and did not change behaviour when it vanished; people look at the page, not the address bar. Names were also not unique. In 2017 a security researcher registered a company in another US state with the same name as a well-known payment firm, obtained an EV certificate and showed the browser displaying a name indistinguishable from the original. On mobile, long names crowded out the domain, which matters more. Safari dropped the EV name in 2018, and Chrome 77 and Firefox 70 followed in 2019. Chrome later replaced the padlock itself with a neutral settings icon, because many people read the lock as "this site is trustworthy" when it only means the connection is encrypted.

Where to find EV details now

Click the icon left of the address, open the connection details and view the certificate: the Subject field shows the organization, country and registration number. From a terminal you can read the subject and policy identifier:

echo | openssl s_client -connect example.uz:443 -servername example.uz 2>/dev/null \
  | openssl x509 -noout -subject -ext certificatePolicies

Under CA/Browser Forum identifiers, 2.23.140.1.1 means EV, 2.23.140.1.2.2 OV and 2.23.140.1.2.1 DV. A Let's Encrypt certificate shows a plain DV result:

subject=CN=example.uz
X509v3 Certificate Policies:
    Policy: 2.23.140.1.2.1

Example: should a Tashkent electronics shop buy EV?

Suppose an online appliance store at misol.uz wants EV so the site "looks more trustworthy". Visitors would see no difference at all compared to a free Let's Encrypt certificate. The money works harder elsewhere: clearly listed legal name, tax ID, address and a working phone number, a clear returns policy, genuine reviews and a short, recognizable domain. Proper SPF, DKIM and DMARC on the shop's mail make spoofed emails harder, which does more against phishing than EV ever did.

A padlock does not mean a safe site

The key lesson is that the padlock and HTTPS only say the connection is encrypted. Free certificates take minutes to obtain, so a large share of phishing sites use HTTPS too. Teaching people that "a lock means safe" is therefore misleading; it is better to teach them to read the domain name carefully and to be wary of payment pages reached through links from strangers. For a business, a short, recognizable domain and registering obvious look-alike names in advance protect trust far better than any certificate badge.

When EV still makes sense

Some banking or government partners may require an organization-validated certificate in a contract or policy, and then OV or EV is simply mandatory. Base the decision on such a concrete requirement, not on marketing. For most sites an automatically renewed DV certificate is enough; on sayt.uz hosting Let's Encrypt is installed free and renews itself. If a partner explicitly requires OV or EV, check the options through the sayt.uz cabinet or support.

Related articles

📧 SSL for mail.domain.uz: Fixing the Outlook Certificate Warning ⏳ Let's Encrypt Rate Limits: Fixing "too many certificates" 📜 Certificate Transparency: How Public Logs of SSL Certificates Work 🏢 SSL for internal (intranet) sites: how to secure office systems
🌐 Language
🇺🇿 O⁠'zbek 🇺🇿 Özbek (yangi) 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓