ERR_CERT_SYMANTEC_LEGACY — Old Symantec Cert 2026

Enterno.io Editorial Team

ERR_CERT_SYMANTEC_LEGACY: Legacy Certificate

By Anatoly Oshmanovsky · Updated Apr 17, 2026

Key idea:

NET::ERR_CERT_SYMANTEC_LEGACY — Chrome 70+ (October 2018) automatically distrusts certificates from Symantec, VeriSign, Thawte, GeoTrust and RapidSSL issued before December 1, 2017. Cause: Symantec violated Baseline Requirements and the CA was distrusted. Fix: reissue via DigiCert (which acquired Symantec's business) or any other CA such as Let's Encrypt.

This error blocks HTTPS access. Below: causes, fixes, working config, FAQ.

Try it now — free →

Common Causes

Certificate issued by Symantec/VeriSign/Thawte/GeoTrust before 2017-12-01
RapidSSL/SSL.com cert bought before 2018
Legacy corporate cert not rotated in 5+ years
Equifax Secure Certificate Authority (outdated sub-CA)
Old EV certs from Symantec brands

Step-by-Step Fix

Reissue via DigiCert (Symantec's successor) — free replacement for legacy customers
Or move to Let's Encrypt: certbot --nginx -d example.com
Check the CA: openssl x509 -in cert.pem -issuer — look for "Symantec"/"VeriSign"
Update fullchain on the server after the new cert is issued
Verify with SSL Checker — see CA and issue date

Check SSL Certificate →

Example: Proper nginx TLS config

server {
    listen 443 ssl http2;
    server_name example.com;

    ssl_certificate     /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;

    ssl_protocols       TLSv1.2 TLSv1.3;
    ssl_ciphers         ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256;
    ssl_prefer_server_ciphers off;

    ssl_stapling        on;
    ssl_stapling_verify on;
}

Related SSL Errors

CertificateExpiry, issuer, domains (SAN)

ChainIntermediate and root CA validation

TLS ProtocolTLS version and cipher suite

VulnerabilitiesHeartbleed, POODLE, weak ciphers

Why teams trust us

TLS 1.3

supported

Full

CA chain check

<2s

result

30/14/7

days-to-expiry alerts

How it works

Enter domain

TLS chain verified

Expiry date & vulnerabilities

What Does the SSL Check Cover?

SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.

Certificate Details

Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).

Chain of Trust

Full chain verification: from leaf certificate through intermediates to root CA.

TLS Analysis

Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.

Expiry Alerts

Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.

DV vs OV vs EV Certificates

DV (Domain Validation)

Confirms domain ownership only
Issued in minutes automatically
Free via Let's Encrypt
Suitable for most websites
Most common certificate type

OV / EV

Organization (OV) or Extended Validation (EV)
Issued in 1-5 business days
Costs $50 to $500/year
For finance, e-commerce, government sites
Increases user trust

Who uses this

DevOps

SSL certificate monitoring

Security

TLS config audit

SEO

HTTPS as ranking factor

E-commerce

customer trust

Common Mistakes

❌

Expired certificateBrowsers block sites with expired SSL. Set up auto-renewal or monitoring.

❌

Incomplete certificate chainWithout intermediate CA, some browsers and bots cannot verify the certificate.

❌

Mixed content on HTTPS siteHTTP resources on an HTTPS page — the browser lock icon disappears, reducing trust.

❌

Using TLS 1.0/1.1Legacy TLS versions have known vulnerabilities. Use TLS 1.2+ or 1.3.

❌

Domain mismatch in certificateThe certificate must cover all site domains, including www and subdomains.

Best Practices

✓

Set up auto-renewalLet's Encrypt + certbot with cron — certificate renews automatically every 60-90 days.

✓

Enable HSTSStrict-Transport-Security header forces browsers to always use HTTPS.

✓

Use TLS 1.3TLS 1.3 is faster (1-RTT handshake) and safer — legacy ciphers removed.

✓

Monitor expiration datesCreate a monitor on Enterno.io — get notified well before expiration.

✓

Verify chain after renewalAfter certificate renewal, confirm that intermediate certificates are installed.

Get more with a free account

SSL certificate monitoring, check history and alerts 30 days before expiry.

Learn more

How-to

Glossary

Research

TLS Cipher Suites 2026: Distribution Report

Errors

Alternatives

Frequently Asked Questions

Why did Google punish Symantec?

Symantec issued thousands of mis-issued certs in 2015–2017 (including for google.com without permission). Chrome announced the distrust in 2017 and enforced it in Chrome 70 (October 2018).

DigiCert acquired Symantec — does a reissue work?

Yes. DigiCert acquired Symantec's website security business in August 2017. New certs from the DigiCert CA are valid in Chrome.

Can I bypass the error?

No Chrome flags to bypass. The only path is a cert reissue.

Does Firefox/Safari still trust the old cert?

Mozilla and Apple applied similar distrust. In 2026 it basically does not work anywhere.