Security & SSL · Practical guide

Why does my website say Not Secure?

A “Not Secure” warning usually means HTTPS is missing, the certificate is invalid, or the page loads insecure resources.

Quick answer

A “Not Secure” warning usually means HTTPS is missing, the certificate is invalid, or the page loads insecure resources.

Start with the checks below. Each step explains what to look for and what to try next.

Identify the browser warning

Open the exact https:// address. A certificate warning is different from a page that loads over plain HTTP. Read the certificate details and check the hostname, validity and trust chain.

Identify the warning first

Identify the warning first

Certificate missing, expired or name mismatch

Check certificate coverage, domain pointing and issuance status.

Padlock missing on only some pages

Inspect mixed HTTP images, scripts or styles on those pages.

Redirect loop after enabling HTTPS

Check the application, control-panel and proxy redirects for duplicate rules.

Certificate looks valid, browser still warns

Test in a fresh browser session and inspect the exact browser error.

Before you continue: Do not bypass certificate warnings or disable security checks to make a warning disappear.

Check the hosting setup

  1. Confirm the domain points to your hosting server.
  2. Find the SSL/TLS or certificate status in your control panel.
  3. Enable or renew the appropriate certificate if available.
  4. Only after a valid certificate is installed, configure an HTTP-to-HTTPS redirect.

Find mixed content

If HTTPS works but a padlock is missing, inspect the browser console for HTTP images, scripts or stylesheets. Update those links to HTTPS or relative URLs where safe.

What not to do

Do not ask visitors to ignore browser certificate warnings. Avoid redirect loops by checking existing WordPress site URLs and redirect rules before adding new ones.

How to confirm the issue is resolved

  1. Repeat the original action that produced the issue.
  2. Check the result in a second browser or network when relevant.
  3. Review logs or status messages for remaining errors.
  4. Keep a short record of what changed so it can be reversed if necessary.

If the issue persists, contact support with the exact error, time, affected domain and actions already tried—never include passwords or secret keys.

Guidance may vary by plan, control panel version and enabled features. Review the settings available to your account before changing live services.