Browser trust
A valid certificate can still produce warnings if page assets are loaded over HTTP.
Tool
Mixed content checker
Checks whether an HTTPS page loads images, scripts, CSS, iframes or other resources over insecure HTTP.
HTTPS resources
Mixed content checker: find HTTP resources on an HTTPS page
The DataHouse mixed content checker verifies whether an HTTPS page loads images, scripts, stylesheets, iframes or other resources over insecure HTTP. It is useful after HTTPS migrations, CMS changes and application moves to new infrastructure.
Migration cleanup
Old absolute URLs often remain in content, templates, stylesheets, widgets or integrations.
SEO and UX
HTTPS consistency, redirects, canonical URLs and secure assets all support a cleaner technical experience.
Common sources of mixed content
- Images, logos, banners and PDFs stored as http:// URLs in a CMS.
- CSS, fonts, JavaScript and libraries loaded from an old host.
- Iframes, maps, forms and external widgets without HTTPS.
- Absolute URLs hardcoded in templates, configuration or databases.
- Old CDN, reverse proxy or load balancer URLs after migration.
How to repair mixed content
Fixing mixed content usually means updating CMS content, templates, CSS, JavaScript, application configuration or database URLs so every resource is available over HTTPS.
FAQ: mixed content checker
Does mixed content mean that the SSL certificate is wrong?
Not necessarily. The certificate can be valid while the page still loads images, scripts, CSS or iframes over plain HTTP.
When should I run the mixed content checker?
Run it after moving from HTTP to HTTPS, changing a CMS, deploying a new template, adding external integrations or migrating a website.