Outdated SSL certificate and TLS protocol
Vetora inspects your site's TLS connection directly (not just the HTTP headers) to check three things: the negotiated protocol version, the certificate's validity, and its expiration date.
Outdated TLS protocol (TLS 1.0 / 1.1 / SSLv3)
These versions are vulnerable to known attacks (POODLE, BEAST) and are progressively rejected by browsers. Most modern hosts (Vercel, Netlify, Cloudflare) already disable these versions by default — this finding mostly shows up on self-managed infrastructure (nginx, Apache, a homemade load balancer).
On nginx:
ssl_protocols TLSv1.2 TLSv1.3;Expired, self-signed, or mismatched certificate
In all three cases, your site's visitors see a blocking security warning in their browser before even reaching the page. A self-signed certificate also defeats the point of encryption against active interception, since nothing guarantees it's really your server.
The fix is the same in all three cases: get a certificate signed by a recognized authority, covering the right domain name, and renewed before it expires. Let's Encrypt is free and offers automatic renewal — just make sure that renewal actually works (a broken cron that no longer renews is a common cause of a surprise expiration).
Check whether your site is affected by this vulnerability.
Scan my app