NET ERR CERT REVOKED Error in Chrome: Fixes

The “NET::ERR_CERT_REVOKED” error in Chrome means the website’s security certificate has been officially revoked by its issuer, so Chrome blocks the connection to protect you. This guide explains why it happens and walks you through the practical fixes, from checking your system clock to clearing cached certificates.

What Does NET::ERR_CERT_REVOKED Mean?

When you visit a secure site (HTTPS), Chrome checks the site’s digital certificate to verify it’s legitimate. A certificate can be revoked if the private key was compromised, the domain changed hands, or the issuer made an error. Chrome receives a list of revoked certificates (via OCSP or CRL) and refuses to load the page if the certificate appears on that list. This is different from other certificate errors like NET::ERR_CERT_DATE_INVALID (expired or wrong date) or NET::ERR_CERT_AUTHORITY_INVALID (untrusted issuer). Revocation is a permanent or semi-permanent state—the certificate is no longer valid for any use.

Why You See This Error (Common Causes)

Website owner revoked the certificate – most common, often due to a security breach or domain transfer.
Your system clock is wrong – a date far in the past or future can make a valid certificate appear revoked.
Outdated cached certificate information – Chrome stores old revocation data that may be stale.
Corporate or antivirus SSL inspection – some security software replaces certificates with its own, which may trigger revocation checks.
Malware or a compromised network – in rare cases, a malicious proxy injects a revoked certificate.

How to Fix NET::ERR_CERT_REVOKED (Step-by-Step)

Check your system clock. Right-click the time in your taskbar (Windows) or System Settings (macOS) and ensure the date, time, and time zone are correct. Enable automatic time sync if possible.
Clear Chrome’s cached certificates. Go to chrome://settings/security, scroll to “Advanced,” and click “Manage certificates.” Under the “Trusted Root Certification Authorities” tab, remove any entries related to the site or its issuer, then restart Chrome. (Note: this is a general cleanup, not a fix for a specific revoked cert.)
Disable antivirus SSL scanning temporarily. Many AV suites have a “HTTPS scanning” or “SSL inspection” feature. Turn it off, then try the site again. Re-enable it after testing.
Try a different network. If you’re on a corporate or public Wi-Fi, switch to a mobile hotspot. If the error disappears, the network’s proxy is the cause.
Reset Chrome flags or profile. Type chrome://flags, click “Reset all” to restore defaults. Also try creating a new Chrome profile to rule out extension interference.
Use the site’s HTTP version (not recommended). If the site offers plain HTTP, you can access it, but you lose encryption. Only do this for non-sensitive pages and only if you trust the site.

If none of these work, the site genuinely has a revoked certificate. You can verify using an online SSL checker (search “SSL checker” and enter the domain). If it shows revoked, the site owner must obtain a new certificate—there’s nothing you can do on your end.

What NOT to Do (Important Safety Warning)

Never click “Advanced” and then “Proceed to site” when you see this error. Unlike some other certificate warnings, Chrome does not even offer a bypass for revoked certificates in normal browsing—and for good reason. A revoked certificate means the site’s identity cannot be trusted. Proceeding could expose you to phishing or man-in-the-middle attacks. If you absolutely must access the site (e.g., it’s your own server), fix the certificate server-side instead.

NET::ERR_CERT_REVOKED vs. Other Chrome Certificate Errors

Chrome shows several similar errors. Here’s how they differ:

NET::ERR_CERT_REVOKED – certificate is on the revocation list.
NET::ERR_CERT_DATE_INVALID – certificate is expired or the system date is wrong.
NET::ERR_CERT_AUTHORITY_INVALID – the issuer isn’t trusted (e.g., self-signed).
NET::ERR_CERT_COMMON_NAME_INVALID – the certificate’s domain doesn’t match the site.

Revocation is the most serious because it’s an active decision by the issuer to invalidate the certificate, not just a technical mismatch.

How to Check if a Certificate Is Really Revoked

You can manually check revocation using the certificate’s serial number. In Chrome, click the padlock icon in the address bar, then “Connection is secure” → “Certificate is valid.” Look for the “Serial number” and “Issuer” fields. Then visit the issuer’s OCSP responder URL (often found in the certificate details) or use a third-party SSL checker that displays revocation status. If the issuer says “revoked,” the site owner must fix it.

Frequently Asked Questions

Can I bypass NET::ERR_CERT_REVOKED?

Chrome does not offer a standard bypass for revoked certificates, and you shouldn’t try to force one. The only safe path is to fix the underlying cause—either on your system (clock, cache, AV) or on the server (new certificate).

Why does this error appear on my own website?

If you’re the site owner, your certificate was revoked. Check your email from the certificate authority (CA) for a revocation notice. You’ll need to purchase or issue a new certificate and reinstall it on your server. Also ensure your server’s OCSP stapling is configured correctly.

Does clearing cookies or cache fix this error?

Clearing cookies alone won’t help, but clearing the cached certificate store (as shown above) can. In Chrome, you can also go to chrome://net-internals/#hsts to delete domain security policies, but that’s rarely needed for revocation errors.

Is this error a sign of malware?

Not usually, but if you see it on many sites at once, especially with a wrong system clock, malware or a rogue proxy could be interfering. Run a full antivirus scan and check your network’s DNS settings (look for suspicious entries).

How long does a certificate revocation take to propagate?

Revocation lists are usually updated within minutes to hours, but browsers may cache the old status for up to 48 hours. If you just revoked a certificate, wait a day and test again.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →