Intelligence Hub/TLS Misconfigurations

Top TLS Misconfigurations

The most common TLS and SSL configuration errors found across the web — ranked by frequency, with prevalence data and actionable fixes.

5 critical issue types3 warning issue typesUpdated from real scan data
23%
of domains have at least one TLS issue
TLS 1.0/1.1
#1 most common misconfiguration
41%
missing HSTS header
#1

TLS 1.0 or 1.1 Still Enabled

CriticalCVE-2014-3566 (POODLE)

Legacy TLS versions with known vulnerabilities (POODLE, BEAST) remain enabled on server. Modern browsers now block these but internal tools may still use them.

34%
prevalence
How to Fix

Disable TLS 1.0 and 1.1 in your server config. For Nginx: `ssl_protocols TLSv1.2 TLSv1.3;` — for Apache: `SSLProtocol -all +TLSv1.2 +TLSv1.3`.

#2

Expired or Soon-Expiring Certificate

Critical

Certificate has expired or will expire within 7 days. Browsers display hard-stop warnings preventing users from proceeding. Causes immediate revenue loss.

28%
prevalence
How to Fix

Enable auto-renewal via Let's Encrypt Certbot, AWS ACM, or your CA's ACME integration. Set 30/14/7-day expiry alerts with CertNotify.

#3

Incomplete Certificate Chain

Critical

Intermediate certificate missing from server response. Desktop browsers often cache intermediates, but mobile and API clients frequently fail — causing intermittent errors.

22%
prevalence
How to Fix

Concatenate your domain cert + intermediate cert(s) in the correct order in your PEM file. Test with: `openssl s_client -connect domain.com:443 -showcerts`.

#4

Weak Cipher Suites Enabled

WarningCVE-2015-0204 (FREAK), CVE-2016-0701

Server supports export-grade, RC4, 3DES, or NULL cipher suites which are cryptographically broken. Attackers can downgrade connections to these weak ciphers.

19%
prevalence
How to Fix

Use Mozilla SSL Config Generator to get a recommended cipher list for your server. Remove any RC4, DES, EXPORT, and NULL ciphers explicitly.

#5

Missing HSTS Header

Warning

HTTP Strict Transport Security is not set. Without it, first-visit HTTP requests are vulnerable to SSL stripping attacks, where attackers intercept plaintext connections.

41%
prevalence
How to Fix

Add: `Strict-Transport-Security: max-age=31536000; includeSubDomains; preload` to your server response headers. Then submit to the HSTS preload list.

#6

Self-Signed Certificate in Production

Critical

Self-signed certificate is not trusted by browsers or operating systems. All users see certificate warnings. Legitimate services should never use self-signed certs.

11%
prevalence
How to Fix

Replace with a certificate from a trusted CA. Let's Encrypt provides free, auto-renewing certificates via Certbot or ACME protocol.

#7

Certificate Domain Mismatch

Critical

Certificate is valid but does not cover the requested hostname. The SAN (Subject Alternative Name) list does not include the accessed subdomain or domain variant.

8%
prevalence
How to Fix

Reissue certificate to include all required domains in the SAN list. Wildcard certs (*.domain.com) cover all direct subdomains but not sub-subdomains.

#8

No Forward Secrecy (PFS) Support

Warning

Server does not support cipher suites that provide Perfect Forward Secrecy (ECDHE, DHE). Recorded traffic could be decrypted if the server private key is later compromised.

15%
prevalence
How to Fix

Prioritise ECDHE cipher suites in your server configuration. Ensure DHE key size is at least 2048 bits if DHE is used.

Check Your Domain for These Issues

Run a free TLS and SSL audit against your domain in seconds. No signup required.