SSL Certificate Scanner
Inspect the certificate chain, signature algorithm, issuer, and expiry, and catch the HTTPS mistakes that break the padlock: mixed content, Secure cookies set over HTTP, and non-standard ports.
Critical1High1Medium6Low4Info3
Medium6 checks
- Mixed-Protocol Content (HTTPS Page Loading HTTP Resources)Pages served over HTTPS include subresources (scripts, images, iframes, XHR) loaded over plain HTTP. Browsers block or warn on mixed content, and the HTTP subresources are vulnerable to MITM modification.
- Alt-Svc advertises cleartext HTTP/2 (h2c)An HTTPS response advertises an alternative service using the h2c protocol identifier. h2c is HTTP/2 over plain TCP, with no TLS at all.
- Link header preloads a cleartext subresourceAn HTTPS response carries a Link header pointing a subresource relation at an http URL. The relation is one of preload, modulepreload, preconnect, prefetch, dns-prefetch, prerender or stylesheet.
- Cleartext subresource loaded through srcset, poster or dataAn HTTPS page loads a cleartext subresource through an attribute other than src or a stylesheet href. The carrier is an img or source srcset candidate, a video poster, or an object data URL.
- Meta refresh sends visitors to a cleartext URLAn HTTPS page uses <meta http-equiv="refresh"> whose target URL is http://.
- Inline script calls a cleartext HTTP endpointAn inline script on an HTTPS page issues a request to a cleartext http endpoint. The call is a fetch, an XMLHttpRequest.open, or a library helper such as axios.get or jQuery ajax.
Low4 checks
- HTTPS Served on Non-Standard PortHTTPS is being served on a port other than 443. Non-standard ports confuse users, bypass browser HSTS expectations for port 443, and indicate the service may be intended as internal-only.
- HSTS declared in a meta tag, where browsers ignore itThe page carries a <meta http-equiv="Strict-Transport-Security"> tag, which browsers ignore. HSTS is only honoured as a real HTTP response header; the meta form has never been implemented by any browser.
- Resource hint on an HTTPS page targets a cleartext URLAn HTTPS page contains a link element resource hint whose href is a cleartext http URL. The relation is one of preload, modulepreload, preconnect, prefetch, dns-prefetch, prerender or manifest.
- Canonical URL declared as cleartext HTTPAn HTTPS page declares <link rel="canonical"> pointing at the http:// version of a URL.
Info3 checks
- Expect-CT Header Not PresentThe Expect-CT header is absent. This is informational, not something to fix: Chrome deprecated and removed Expect-CT support, and Certificate Transparency is now enforced unconditionally by browsers at certificate-validation time, independent of any response header. Essentially no site, including well-secured ones, sends this header anymore.
- X-HTTP-Method-Override / X-Forwarded-Method Header in ResponseThe response includes a header literally named X-HTTP-Method-Override or X-Forwarded-Method. These are conventionally request headers a client sends to ask the server to treat a request as a different HTTP verb, not headers a server sends back, so seeing one in a response is unusual and worth a look.
- HSTS Present on HTTP Response (SSL-Strip Indicator)A Strict-Transport-Security header was detected in a plain HTTP response. HSTS is only meaningful over HTTPS; its presence on HTTP indicates either a misconfigured server or an active SSL-strip interception where the attacker forwards HSTS headers to create a false sense of security.
About the SSL checks
- What does the SSL category check?
- Inspect the certificate chain, signature algorithm, issuer, and expiry, and catch the HTTPS mistakes that break the padlock: mixed content, Secure cookies set over HTTP, and non-standard ports. Certificate chain, signature algorithm, issuer, expiry date.
- How many ssl checks are there?
- VulnRadar runs 15 checks in this category, ranging across critical, high, medium, low, info severity.
- Do I need to install anything to run the ssl checks?
- No. Paste a URL in the browser or call the REST API, and the scan itself runs from our servers against that URL. There is no agent and no appliance to deploy alongside your application. A browser extension exists if you want to scan the page you are looking at, but nothing has to be installed to use this.
Run the ssl checks on your site
VulnRadar runs all 15 of these against a URL in seconds, with the evidence and fix for every finding. No agent to install, just paste a URL.