- Home
- Free tools
- Mixed content checker
Mixed content checker
Find the http:// resources hiding on an HTTPS page. Active ones are blocked by browsers, passive ones can break the padlock, and both are easy to fix once you can see them.
How to use it
- Enter the address of an HTTPS page.
- Read the table: Active items are blocked by browsers and can break the page, Passive items are images and media.
- Change each address to https:// in your content or theme, or use the snippet as a safety net while you clean up.
What it checks
- Scripts, stylesheets, fonts and frames loaded over http:// (active)
- Images, audio, video and posters over http:// (passive)
- Forms that submit to http://
- http:// inside inline CSS and @import
- A Content-Security-Policy with upgrade-insecure-requests
- http:// links to other pages (reported separately)
Limits
- Finds http:// resources referenced in the HTML. Resources requested later by scripts or CSS are not seen.
- Checks one page. Other pages of the site can have different problems.
- Does not show browser console messages, which can list further blocked requests.
Public pages only, one page at one point in time. See the methodology and terms.
Frequently asked questions
What is mixed content?
An HTTPS page that loads some resources over plain HTTP. Those requests can be read or changed by anyone on the network, so browsers block the dangerous kind and warn about the rest.
What is the difference between active and passive?
Active resources (scripts, styles, frames) can change the page, so browsers block them. Passive resources (images, audio, video) cannot, so many browsers upgrade them to HTTPS or load them with a warning.
Will upgrade-insecure-requests fix it?
It tells browsers to request http:// resources over HTTPS instead. It works as a safety net if the other server supports HTTPS, but fixing the addresses at the source is cleaner.
Why does a clean result not mean my page is fully secure?
Only resources in the HTML sent by the server are scanned. Anything added by JavaScript or referenced from inside CSS files is not seen here.
The tool says my page is on HTTP. What now?
Mixed content only exists on HTTPS pages. Install a certificate, redirect HTTP to HTTPS, then run the check again.
Where do I check the SSL certificate itself?
CheckDomainHealth covers certificates, expiry and chain. This tool checks the content of one page.