How to Check SSL Certificate Status in Enhance

If a website shows "not secure", redirects strangely, or refuses to load over HTTPS, start by checking the SSL certificate inside Enhance. TekLan shared hosting uses Enhance for SSL management, so you do not need cPanel instructions or a separate certificate manager for normal Let's Encrypt certificates.

Check SSL Status in Enhance

1. Log in to web.teklanhosting.co.uk.
2. Click the affected website.
3. Open Security.
4. Find SSL certificates.
5. Check the status, certificate type, Force HTTPS toggle, and expiry date for the domain.

An active certificate means Enhance has issued and installed SSL for that hostname. If the certificate is pending or failed, the domain usually is not resolving to the right server yet, or a DNS record is blocking validation.

Check the Exact Hostname

SSL is hostname-specific. Check both the root domain and the www version if you use both:

https://example.co.uk
https://www.example.co.uk

If one works and the other does not, the failing hostname may be missing from the website, DNS, or certificate request.

Confirm Force HTTPS

Once SSL is active, go to Security → SSL certificates and check whether Force HTTPS is enabled. This redirects visitors from http:// to https://.

If Force HTTPS is off, the HTTPS version can still work, but visitors who type the HTTP version may not be redirected automatically.

Check the Public Response

From a terminal, check the headers:

curl -I https://example.co.uk

You want a sensible HTTP status such as 200 or a clean redirect to the canonical URL. If the command shows a certificate error, check DNS first, then reissue the certificate from Enhance.

Check DNS Before Reissuing

Let's Encrypt can only issue the certificate if the domain resolves to the correct TekLan hosting server. Check the A record:

dig example.co.uk A
dig www.example.co.uk A

If an old IP address still appears, fix DNS and wait for the previous TTL to expire before requesting the certificate again.

Check for Mixed Content

If the padlock appears but the browser still warns about insecure content, the page may load images, scripts, stylesheets, or fonts over http://. In WordPress, this often happens after a migration from an old HTTP site.

Open browser developer tools, check the console, and look for mixed content warnings. Fix the old URLs in the site content, theme settings, or database.

Common Causes

• The domain still points to the old host.
• The www record is missing or points somewhere different.
• An AAAA record points IPv6 visitors at an old server.
• A CAA DNS record does not allow Let's Encrypt.
• The website has old hard-coded http:// asset URLs.

Related TekLan Guides

Use SSL Certificates in Enhance for the full control panel walkthrough, and How to Check DNS Propagation Properly if the certificate is waiting on DNS.