Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My website shows a Not secure warning even though I have a certificate

Short answer

A Not secure warning has three usual causes: the site is still opened over plain http, the certificate expired or does not cover the address, or the page is https but loads some images or scripts over http, called mixed content. Browsers block or flag those. Identify which one it is before changing anything.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The address bar says Not secure, or shows a crossed padlock.
  • A full page warning says the connection is not private.
  • The padlock was fine and disappeared after a redesign or a plugin change.
  • Some images are missing or the page looks broken on https.
  • It only shows on some pages, such as the shop or the contact page.

Why does this happen?

  1. The site loads some things over plain http

    web.dev explains mixed content: a page is loaded over https while some images, scripts or stylesheets are requested over http. Browsers typically flag the address bar as not secure for passive content, and most now block active content such as scripts by default.

  2. Old http addresses are hard-coded

    web.dev says the fix is to find every http resource URL, including hard-coded ones, and change each to https after confirming an https version exists. In a CMS these live in pages, themes and settings.

  3. The certificate expired or is not renewing

    Let's Encrypt says its default certificates are valid for 90 days and recommends renewing every 60 days. If the renewal job stopped, the site goes from secure to a full-page warning.

  4. Visitors can still open the plain http address

    A site with a certificate can still answer on http unless it is set to redirect. For WordPress, the handbook explains that the https setup needs the server's SSL to be configured first, and that behind a proxy the wrong settings can cause an endless redirect loop.

  5. Chrome may upgrade or fail an http resource

    web.dev says Chrome can upgrade passive http resources to https if a secure version exists, and if none exists the resource fails to load. That is why images vanish rather than just warn.

What can I do about it today?

  1. Click the warning and read itIs it a full page warning about the certificate, or only a small Not secure label? The first is certificate trouble, the second is usually mixed content. Screenshot it.
  2. Look at the certificate datesIn the browser, open the certificate details from the padlock and note the expiry date and the names it covers.
  3. Try the https address by handType https:// in front of the domain, with and without www. If one works and one does not, tell the developer which.
  4. Do not click through warnings on a shop or login pageVisitors should not be taught to do it either. Fix the cause.
  5. Ask whoever built the site what changedA redesign, a new CDN, a moved host or an imported database often puts http addresses back in.
  6. Do not do a find-and-replace on the live databaseChanging addresses by text search can corrupt stored settings. Do it on a copy, or with a tool built for it.

When should I bring someone in?

  • The certificate has expired and you do not know how it is renewed.
  • The site loops or breaks after turning on https.
  • Checkout or login pages are affected.

How do I handle it?

  1. Identify which kind it isCertificate, redirect or mixed content, using the browser's own messages and a crawl of the pages.
  2. Fix the certificate pathCoverage of every name, expiry, and a renewal job that actually runs and alerts.
  3. Find every http referencePages, theme files, widgets, settings and third-party scripts are searched, then changed to https after confirming the secure version exists.
  4. Set one clean redirecthttp goes to https in one layer, with the www and non-www versions decided, so there is no loop.
  5. Verify in the browser consoleKey pages are opened with the console and issues panel and checked until no blocked resources remain.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

I paid for a certificate, why does it still warn?

A valid certificate only secures the connection. If a page still loads images or scripts over http, the browser can still flag it.

Is it dangerous for my customers?

web.dev says active mixed content can let an attacker control the page and steal credentials. Passive content is a smaller risk, but the browser still warns.

How often does the certificate renew?

Let's Encrypt certificates are valid for 90 days and the page recommends renewing every 60. Other providers set their own period.

Will fixing it help my Google ranking?

I cannot say how Google weighs it. It does stop visitors from leaving at a warning.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.