Why does my website say not secure
Summary
This guide helps you troubleshoot and resolve: Why does my website say not secure. Follow the steps below to fix the issue.
Common Causes
When a web browser displays a "Not Secure" warning next to your website address in the address bar, it means the connection between your visitors and your website is not encrypted. This warning is specific to the browser address bar and does not mean your website is infected with malware or that your site has been compromised. Modern browsers such as Google Chrome, Microsoft Edge, and Apple Safari show this warning when a site loads over HTTP instead of HTTPS. HTTPS relies on an SSL/TLS certificate installed on your server to encrypt data and verify the identity of your website.
This warning can damage customer trust, discourage visitors from completing forms or purchases, and negatively affect your search engine rankings. Search engines favour secure sites in their results. For Australian small businesses using .com.au domains, displaying a secure padlock icon helps reassure local customers that their data is protected.
Types of SSL Certificates
Before installing a certificate, it helps to understand the validation levels available:
- Domain Validation (DV): The most common option for small business. The certificate authority verifies that you control the domain. Issued quickly and suitable for brochure sites and blogs.
- Organisation Validation (OV): The certificate authority verifies your business details in addition to domain control. Suitable for organisations that want to display verified company information to visitors.
- Extended Validation (EV): The highest level of validation, involving a thorough check of your organisation. Typically used by large businesses and financial institutions. Most small businesses do not require EV certificates.
Check Your SSL Certificate Status
- Open your website in Google Chrome, Microsoft Edge, or Apple Safari.
- Look at the address bar to the left of the website URL.
- If you see a padlock icon, the connection is secure. If you see "Not Secure" or a warning triangle, the certificate is missing, expired, or misconfigured.
- Click the security icon to view certificate details, including the expiry date and issuing authority.
Renew or Install an SSL Certificate
An SSL certificate must be issued and then installed on your web server. Simply purchasing or issuing a certificate is not enough; it must be active on the server before HTTPS will work.
- Log in to your hosting control panel or domain registrar dashboard.
- Navigate to the SSL/TLS, Security, or Certificates section.
- If no certificate is installed, select the option to issue or install a free certificate, such as Let's Encrypt.
- If a certificate exists but has expired, choose Renew or Reissue and follow the prompts to complete validation.
- Wait for the certificate to become active and installed on the server. This can take anywhere from a few minutes to several hours depending on the provider.
cPanel Instructions
- Log in to cPanel.
- Go to Security > SSL/TLS > Manage SSL sites.
- Select your domain and install or upload the certificate.
- Click Install Certificate.
Plesk Instructions
- Log in to Plesk.
- Go to Websites & Domains > SSL/TLS Certificates.
- Select Add SSL Certificate or choose an existing certificate to assign.
- Click OK or Apply to install the certificate on the domain.
Force HTTPS Redirects
- Access your hosting control panel, such as cPanel, Plesk, or your host's custom dashboard.
- Locate the Redirects, Domains, or SSL/TLS section.
- Enable the option to force HTTPS or redirect all HTTP traffic to HTTPS.
- Alternatively, edit your
.htaccessfile on Apache servers to include a redirect rule that sends allhttp://requests tohttps://. - Save your changes and test the website by typing
http://yourdomain.com.auin the address bar. It should automatically load ashttps://yourdomain.com.au.
.htaccess file, download a backup copy to your computer. If you make a syntax error, your website may stop loading until the file is restored.Update CMS Settings After SSL Installation
After installing your SSL certificate and enabling HTTPS, you must update your content management system settings to avoid mixed content errors.
- Log in to your WordPress admin dashboard.
- Go to Settings > General.
- Update WordPress Address (URL) and Site Address (URL) from
http://tohttps://. - Click Save Changes.
- If you use a caching plugin, clear the cache and reload your website.
Fix Mixed Content Errors
- If the padlock icon appears but shows a warning, your page may be loading some elements over HTTP.
- Press
F12on Windows orOption + Command + Ion macOS to open browser developer tools. - Select the Console tab and look for "Mixed Content" warnings listing insecure
http://URLs. - Update those links in your website code or content management system to use
https://or relative paths. - Clear any caching plugins or server-side cache and reload the page.
Troubleshooting Common SSL Issues
Certificate Domain Mismatch
- The certificate does not match the domain name in the address bar. For example, a certificate issued for
www.example.com.auwill trigger a warning if visitors go toexample.com.auwithout thewwwprefix. - Ensure the certificate covers both the www and non-www versions of your domain, or set up a redirect so all traffic uses one consistent version.
SSL Certificate Not Trusted
- The certificate was issued by a certificate authority that browsers do not recognise, or it is self-signed.
- Use a certificate from a trusted authority such as Let's Encrypt, Sectigo, or DigiCert.
- If you recently installed the certificate, confirm the intermediate or chain certificate is also installed on the server.
Cloudflare or CDN SSL Configuration
- If you use Cloudflare, check the SSL/TLS encryption mode in the Cloudflare dashboard. Flexible encrypts traffic between the visitor and Cloudflare but not between Cloudflare and your server, which can cause redirect loops.
- Use Full or Full (Strict) if your server has a valid SSL certificate installed.
- After enabling Cloudflare, check for mixed content caused by hard-coded
http://links in your theme or plugins.
Certificate Shows as Expired After Renewal
- Restart your web server or contact your hosting provider to ensure the new certificate is loaded correctly.
- Clear your browser cache or test in an incognito/private window to rule out cached certificate data.
HTTPS Redirect Causes a Redirect Loop
- Check that you do not have conflicting redirect rules in both your hosting control panel and your
.htaccessfile. - Temporarily disable one method and test again to isolate the cause.
Dedicated IP and SNI
- Older hosting systems sometimes required a dedicated IP address for SSL. Most modern servers use Server Name Indication (SNI), which allows multiple SSL certificates on a single shared IP address.
- If you are on an older hosting plan, contact your provider to confirm whether SNI is supported.
Advanced Option: HSTS
HTTP Strict Transport Security (HSTS) is an optional header that tells browsers to always connect to your site using HTTPS, even if a visitor types http://. This minimises the risk of downgrade attacks. Only enable HSTS after you have confirmed your HTTPS redirect is working correctly and your certificate is stable, as misconfiguration can make your site inaccessible.
If you host with us, you don't need to do this yourself — Open a Ticket and our Brisbane team will get it sorted.
Still Having Issues?
💻 Open a Ticket