Your country & currency

Make yourself at home. Choose your preferred shopping currency.

Your selected country opens its KickHost website. Your shopping currency is saved. Visit country website .

KICKHOST SSL CHECKER

SSL CheckerCheck the connection.
Understand the next step.

Review the certificate your website serves, including its hostname coverage, expiry and certificate chain. A certificate check is one part of a wider website security review.

Check an existing HTTPS website.

For a detailed public TLS assessment, open Qualys SSL Labs and enter your public website hostname. This external service may connect to your server and publish assessment results. Do not enter private or internal hostnames.

Open SSL Labs checker ↗

What should you review?

  • Does the certificate cover the hostname visitors use?
  • Is the certificate current, and is the full chain served correctly?
  • Does the site redirect to HTTPS without mixed-content issues?
Need a different certificate?

READ A TLS REPORT

What a public certificate check can tell you.

A TLS scan reviews the certificate and connection presented by a public hostname. Use the results to spot certificate problems, then review the website and its software separately.

01

Hostname and dates

Confirm that the certificate names match the address visitors use and that it is within its validity period.

02

Certificate chain

Check that the server presents the required intermediate certificates and that the chain can be validated.

03

HTTPS is not a full security audit

A certificate scan does not assess passwords, application vulnerabilities, backups, malware or privacy compliance.

How a browser checks a website certificateA browser requests a secure connection, checks the hostname and certificate chain, and then establishes HTTPS if the checks pass.A PUBLIC TLS CHECKBrowserrequests HTTPSHostnamedatescertificate chainSecureconnectionA certificate scan does not test the whole website.
Simplified connection flow. A passing certificate check is not a complete website security assessment.

COMMON WARNINGS

What the browser message usually means.

Most certificate warnings come from a small number of causes. Browsers word them differently, so match the message to the likely cause before you order a replacement.

Typical browser warnings and the first thing to check
What you seeLikely causeFirst check
“Not secure” or no padlockThe page loads over HTTP, or some assets still use HTTP.Open the exact URL with https:// and confirm it redirects. Then look for mixed content.
Certificate is not valid for this nameThe certificate does not include the hostname in the address bar.Compare the hostname with the certificate names. Add the www or subdomain name, or choose wider coverage.
Certificate has expiredRenewal did not run, or the replacement was never installed.Check the expiry date in the certificate details, then confirm the new certificate is live on every server.
Certificate chain is incompleteThe server is not sending the intermediate certificate.Install the full chain supplied by the certificate authority, not only the leaf certificate.
Certificate is self-signedA temporary or internal certificate is being served publicly.Replace it with a certificate issued by a publicly trusted authority.
Warning on one page onlyAn image, script, font or form on that page points at another hostname.Inspect the page requests and fix the odd URL rather than reissuing the certificate.

Wording varies by browser and version. Use this table to find a starting point, then confirm with a TLS report for the exact hostname.

BEFORE YOU REISSUE

Confirm the cause before you buy another certificate.

A new certificate only fixes a certificate problem. If the warning comes from mixed content, a redirect loop or a proxy, replacing the certificate will not change what visitors see.

01

Test the exact hostname

Use the address visitors type, including www or a subdomain. A certificate can be valid for one name and invalid for another.

02

Check every server

If a CDN, load balancer or second web server terminates TLS, each one needs the current certificate and the full chain.

03

Fix HTTP references

Search the page source for http:// links to images, scripts, fonts and forms, then change them to HTTPS or relative URLs.

SSL CHECKER QUESTIONS

What to do with the result.

Questions, answered
Is it safe to check a website with an SSL checker?+
A public checker only reads the certificate the server presents, so it does not need access to your account. Use it on sites you own or have permission to test, avoid internal hostnames, and remember that external scanners connect from the public internet and some publish their results.
Why does the padlock disappear on some pages?+
That is usually mixed content. The page is served over HTTPS but still requests an image, script, font or form over HTTP, so the browser blocks the insecure request and downgrades the connection indicator. Fix the reference at its source rather than replacing the certificate.
The certificate is valid but the browser still warns. Why?+
Check the hostname first: a certificate for example.com may not cover www.example.com. Other common causes are an incomplete chain, an outdated TLS version, a device clock set to the wrong year, or security software intercepting the connection.
Does a passing check mean the website is secure?+
No. A certificate check covers transport encryption and the identity of the hostname. It says nothing about weak passwords, outdated plugins, malware, backup quality or how personal data is handled.
How often should I check a certificate?+
Check after any DNS, hosting or certificate change, before the expiry date, and on a routine schedule if you take payments or run a store. Automated renewal can fail quietly, so a monthly check is a reasonable habit.
Can I check a certificate before switching DNS?+
Not reliably through the public hostname, because the check follows live DNS. Test on a staging hostname or temporary address, then repeat the check after the DNS change has propagated.