NET::ERR_CERT_REVOKED

NET::ERR_CERT_REVOKED Explained

Shoppers and owners
The short answer

NET::ERR_CERT_REVOKED means the certificate authority that issued the site's certificate has cancelled it, before its normal expiry date. Chrome treats this as final: it removes the option to continue and tells you outright that you cannot visit the site. Certificates are usually revoked because the private key was compromised or the certificate was issued incorrectly, so this deserves more caution than an expired certificate.

Seeing this on a site? Check it now.

Paste the address and we will tell you exactly which check is failing, and why. Free, and you do not have to open the site yourself.

If you were just trying to buy something

Do not try to get past this one. Chrome has removed the option on purpose, and there is no setting that brings it back.

A revoked certificate means the authority that issued it withdrew its approval. The most common reasons are that the site's private key was stolen, or the certificate should never have been issued in the first place. Either way, you cannot verify who is really answering.

If you have an account on the site, or you have bought from it recently, change that password now, and use a different password from the one you use elsewhere. Keep an eye on the card you used. Contact the business through a phone number or an app, not through the site.

If this is your site

Treat this as a security incident until you can prove otherwise, not as a certificate chore.

Contact your certificate authority first and ask why it was revoked. They will tell you the reason. If it was key compromise, replacing the certificate is not enough on its own. You need a brand new private key, and you need to work out how the old one got out.

Do not reuse the old key or the old certificate signing request. Generate a fresh key, request a new certificate, install it, and reload every server and CDN edge that terminates connections. Then run the free check to confirm visitors are getting the new one.

Chrome does not let you continue

This is what makes revocation different from every other certificate error. There is no "Advanced" route through. Chrome states it plainly:

You cannot visit <SITE> right now because its certificate has been revoked.

Only three certificate situations remove the proceed option. The other two are certificate pinning and HSTS. Everything else, including expired, self signed and wrong hostname, still offers "Proceed to <SITE> (unsafe)".

What revocation actually is

A certificate has a fixed expiry date, but the authority that issued it can also cancel it early. That is revocation.

It is a deliberate act by the authority, not something that happens through neglect. Somebody, usually the site owner or the authority itself, decided that this specific certificate must stop being trusted immediately.

Browsers learn about it in two ways: lists of revoked certificates that ship with or are pushed to the browser, and live queries to the authority. Chrome leans on its own pushed list, which is why a revoked certificate can be blocked in Chrome while another browser still lets it through. That difference confuses people, but it does not make the revocation less real.

Why a certificate gets revoked

The reasons that matter to a visitor:

  • The private key was compromised. The secret half of the certificate leaked, was stolen, or was exposed in a breach or a public code repository. Anyone holding it could impersonate the site, which is exactly why revocation exists.
  • The certificate was mis-issued. The authority discovered it should never have been granted, for example because the domain ownership check was flawed or the details were wrong.
  • The server itself was compromised. If attackers got into the server, they may have got the key with it, so the certificate is revoked as a precaution.
  • The domain changed hands or the details are no longer accurate. The organisation named on the certificate no longer controls the domain.
  • Routine replacement done properly. Owners sometimes revoke an old certificate after replacing it. This is the harmless case, but you have no way to tell it apart from the others as a visitor.

Revoked is not the same as expired

People lump these together and they should not.

An expired certificate is a missed deadline. It is usually an administrative slip and the browser still lets you make your own decision about it.

A revoked certificate is an authority actively withdrawing trust in that specific certificate while it would otherwise still be valid. Somebody decided it was unsafe. Chrome takes the decision out of your hands, which tells you how the browser rates it.

If you want the background on who issues certificates and what withdrawing one means, see our guides to certificate authorities and SSL certificates.

If it is your site: what to do, in order

The order matters, because replacing the certificate without finding the cause can leave you in the same position within days.

  1. 1.Ask your certificate authority why. They know the revocation reason and it decides everything that follows. Key compromise and a routine replacement need very different responses.
  2. 2.Assume the private key is exposed until the authority tells you otherwise. Generate a completely new key pair. Never reuse the old key or an old certificate signing request.
  3. 3.Look for how it leaked. Check whether a key file ended up in a code repository, a backup, a shared drive, or an email. Check server access logs and administrator accounts for anything you do not recognise.
  4. 4.Install the new certificate everywhere. Every web server, load balancer and CDN that terminates connections, then reload each one so the change takes effect.
  5. 5.Rotate everything else the server holds. If the machine was compromised, database passwords, API keys and admin logins are all suspect too.
  6. 6.Verify from outside. Use the checker at the top of this page. It reports what a visitor actually receives, which is the only test that counts.

What our check can tell you

Our engine inspects the certificate a site presents and reports the precise reason it is not trusted, including whether it has expired, is self signed, is not issued by a trusted authority, or does not match this website address. That is the same information the checker box on this page shows you.

It means you can diagnose a site without opening it, which matters more here than on any other certificate error, because with revocation you genuinely should not be loading the page.

Frequently asked questions

Can I bypass NET::ERR_CERT_REVOKED?

No. Chrome removes the proceed option entirely and shows the message "You cannot visit <SITE> right now because its certificate has been revoked." Revocation is one of only three certificate situations with no override, alongside HSTS and certificate pinning. Any guide offering a workaround is telling you to disable a protection that exists for a good reason.

Is a revoked certificate worse than an expired one?

Yes, and it is worth understanding why. Expiry is a deadline passing, usually through neglect. Revocation is the issuing authority deciding this specific certificate must stop being trusted right now, most often because a private key was compromised or the certificate was issued incorrectly. Chrome reflects that difference by removing your ability to continue.

The site works in another browser. Does that mean it is fine?

No. Browsers check revocation differently, and Chrome relies heavily on lists pushed directly to it, so it often blocks a revoked certificate that another browser still accepts. The certificate has still been withdrawn. Do not use that as permission to enter your details.

I had an account on that site. What should I do?

Change that password, and change it anywhere else you reused it. If you entered payment details recently, watch the card and report anything unexpected to your bank. Contact the business by phone or through an app rather than through the site, and be wary of any email that arrives claiming to help you with the problem.

It is my certificate and I did not revoke it. Who did?

Either your certificate authority did, or someone with access to your account there. Contact the authority immediately and ask for the revocation reason, then check who else can reach that account. Authorities revoke on their own initiative when they learn a key is exposed or a certificate was mis-issued, and they will tell you which applies.

Related errors

See all errors explained →

Stop guessing what is wrong.

Run a free check on any site and see every trust and security signal at once, in plain English.

Run a free check Browse the fixes