HTTPS scanning SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

Antivirus HTTPS/SSL scanning breaks certificates (Avast, Kaspersky, ESET, Bitdefender)

Security software intercepts HTTPS by re-signing certificates with its own root, which some apps and browsers reject.

Exact message you may see antivirus HTTPS scanning certificate errorAvast Web/Mail Shield certificate invalidKaspersky root certificate SSL errorESET SSL protocol scanning certificate issueIssuer: Avast trusted CA
Seen on: Windows Browser SSL

Meaning

Disable "HTTPS scanning"/"SSL filtering" or add exceptions for the affected sites/apps. Update the product (old versions use weak keys or break TLS 1.3), and import its root only where intended. The certificate issuer name shows the product's name.

Common causes

  • Antivirus replacing certificates
  • Its root not trusted by Firefox/Java/Node
  • Expired antivirus root certificate
  • TLS 1.3/pinning conflicts
  • Certificate issuer is the antivirus

⚡ Quick fix

  1. Disable HTTPS scanning or add exclusions
  2. Update the antivirus
  3. Check the issuer of the certificate in the browser

Detailed fix by platform

Shell

  1. openssl s_client -connect example.com:443 </dev/null 2>/dev/null | openssl x509 -noout -issuer

How to diagnose

  1. Issuer — Antivirus?
  2. Scanning — On?
  3. Software — Updated?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

cert mismatch — SMTP TLS certificate verification failed: hostname mismatch / unable to get local issuer (mail client or library) (Email / SMTP)cert mismatchclock — Certificate error caused by a wrong device clock (NET::ERR_CERT_DATE_INVALID, "your clock is ahead/behind") (SSL / TLS)clockDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)Djangoexpiry — Certificate expired unexpectedly — manual renewal missed or automation failing silently (SSL / TLS)expiryMITM — Firefox: MOZILLA_PKIX_ERROR_MITM_DETECTED — something on your computer or network is intercepting HTTPS (SSL / TLS)MITMNET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM — NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM — certificate signed with SHA-1 or MD5 (SSL / TLS)NET::ERR_CERT_WEAK_SI…pinning — NET::ERR_SSL_PINNED_KEY_NOT_IN_CERT_CHAIN — HPKP or built-in public key pinning mismatch (SSL / TLS)pinningSSL inspection — Corporate proxy TLS inspection (Zscaler, Netskope, Palo Alto): certificate issued by an untrusted corporate root (SSL / TLS)SSL inspectionHTTPS sca…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.