Why a Website May Be Marked Not Secure

A browser may label a page “Not secure” when it is served over HTTP or when HTTPS has a certificate or content problem. The exact warning depends on the browser and situation.

Checks for site owners

1. Make sure the domain has a valid TLS certificate.
2. Confirm both the root domain and any required subdomains are covered.
3. Redirect HTTP traffic to the matching HTTPS URL using a permanent redirect where appropriate.
4. Update internal links, canonical URLs, images, scripts, stylesheets, and form actions to use HTTPS.
5. Look for mixed content where an HTTPS page loads resources over HTTP.
6. Test the site after changes and check that redirects do not create loops.

HTTPS is important, but it does not by itself prove that a site is free of malware, vulnerabilities, or deceptive content. Keep software updated and review security configuration separately.