Mixed content checker
Find insecure HTTP resources referenced by an HTTPS webpage.
Last submissions
What this checker does
The mixed content checker scans an HTTPS webpage and finds resources referenced over insecure HTTP. Mixed content occurs when a secure page loads scripts, styles, images, or other resources over an unencrypted connection.
The tool lists the insecure resources it finds so you can update them to HTTPS or remove them.
Why mixed content is a problem
When a page is served over HTTPS, users expect the connection to be secure. An HTTP resource creates a weak point. An attacker on the network could intercept or modify that resource, potentially affecting the secure page.
Browsers respond differently depending on the resource type. Active content such as scripts and stylesheets may be blocked outright. Passive content such as images may load with a warning or be upgraded automatically. In either case, the page may break or behave inconsistently.
Mixed content also undermines trust. Browser warnings and missing resources make a site look unreliable, even if the main page itself is served securely.
Common sources of mixed content
- Hardcoded HTTP URLs: templates or content that reference
http://directly. - Third-party embeds: widgets, fonts, or tracking scripts loaded over HTTP.
- Legacy content: old images or media that were never updated.
- Protocol-relative URLs: URLs starting with
//inherit the page’s protocol and are generally safe on HTTPS, but absolute HTTP URLs are not.
Reading the results
The checker reports resources referenced with an HTTP URL. It does not test whether the resource is actually reachable over HTTPS, and it does not attempt to upgrade the URL. It reports what is present in the HTML.
Some resources may be loaded dynamically by JavaScript and may not appear in the initial HTML. The checker’s results reflect the source it receives.
Practical guidance
- Update URLs to HTTPS: most modern services support HTTPS. Change the references and test.
- Use protocol-relative or relative URLs: these avoid hardcoding the protocol and inherit the page’s security context.
- Audit third-party embeds: check provider documentation for HTTPS support and update embed codes.
- Set a Content-Security-Policy:
upgrade-insecure-requestscan help, but it is not a substitute for fixing the references.
Limitations
The checker examines the HTML for the URL you provide. Resources loaded by JavaScript after page load may not be detected. It does not verify resource availability or browser behavior.
Use the results to identify and fix insecure references, then test the page in a browser to confirm that all resources load correctly over HTTPS.
Similar tools
Find forms on HTTPS webpages that submit data to insecure HTTP URLs.
Inspect an SSL/TLS certificate: issuer, validity dates, common name and signature type.
Count the resources requested by a webpage.
Popular tools
Check which images on a page are missing alt attributes for accessibility and SEO.
Check which images on a page use lazy loading and which load immediately.
Measure the total size of a webpage, including all of its resources.
Check whether a page is blocked from search indexing by meta tags, headers or robots.txt.