Use the mixed-content finding to locate insecure resource references on an HTTPS home page. Correct those references in the website rather than suppressing the warning without checking them.

Read the example

1. Open PD Modules → Site Sentinel → Needs attention.
2. Find The page loads insecure resources for the intended site.
3. Review the example resource in What it means and the site’s last scan time.
4. Check Look for mixed content in Settings if the expected check is absent.

The released check examines selected resource attributes in the fetched home-page HTML. It reports up to ten distinct matches and includes one example. It does not render the page as a browser, crawl the whole site or enumerate every resource loaded later by scripts or stylesheets.

Correct the source reference

Use the website’s own content, theme or application controls to replace the insecure reference with the correct HTTPS resource where supported. Confirm that it loads correctly. A plain HTTP hyperlink is different from an embedded resource and is not what this check is looking for.

Verify both views

Review the affected page in your normal browser tools, then have Site Sentinel check the relevant site again. Confirm its timestamp advanced and the expected setting remains enabled. No remaining module finding does not prove that every page, CSS resource or dynamically loaded asset is free of mixed content.

See the PD Site Sentinel Blesta guide for related tasks, or explore PD Site Sentinel.