Tools / Mixed content checker

Mixed content checker

Enter an HTTPS page. We read its HTML and list every sub-resource it pulls over plain http:// — split into the active resources browsers block outright and the passive ones they flag or silently upgrade.

What mixed content is

A page served over HTTPS that loads a script, stylesheet, image or iframe over http:// is “mixed content.” The lock in the address bar promises the whole page is protected, but each plaintext sub-resource can be read and rewritten in transit — which, for a script, means an attacker on the network can replace your JavaScript with theirs. Because that undermines the entire point of HTTPS, browsers treat it harshly.

Active vs passive — why the split matters

How to fix it

The right fix is to change each reference to https:// (or to a protocol-relative/root-relative path), because the markup is genuinely wrong. The common shortcut — adding upgrade-insecure-requests to your Content-Security-Policy — makes the browser rewrite http:// to https:// on the fly, which hides the symptom but leaves the source wrong and depends on every target actually supporting HTTPS. Use it as a safety net, not as the fix. This tool reads the raw markup, so it still shows you the underlying http:// references even when a CSP would paper over them in the browser.

Limits

Only resources referenced in the page’s initial HTML are visible to a passive fetch — sub-resources injected later by JavaScript, and URLs built inside already-loaded scripts or imported by a stylesheet, are not. A clean result here means the delivered HTML is clean; it is strong evidence but not a guarantee that nothing loads over http at runtime. The browser’s own developer console (Security tab) is the authority on what actually loaded insecurely for a real visit.

Related checks: the security headers analyzer (for HSTS and the upgrade-insecure-requests directive), the TLS / SSL checker for the certificate itself, and the CSP evaluator to read the policy that governs what the page may load.

Frequently asked questions

How do I fix mixed content?

Change every http:// resource URL on the page to https://, or to a relative path for files on your own site. If a third party does not serve HTTPS, host the file yourself or replace it.

Why do I have mixed content after moving my WordPress site to HTTPS?

Old http:// addresses are stored in posts, widgets and theme settings in the database. Update the site address in the settings, then run a search-and-replace on the database for the old URL.

What does upgrade-insecure-requests do?

Adding Content-Security-Policy: upgrade-insecure-requests tells browsers to fetch every http:// resource on the page over HTTPS instead. It is a useful safety net while you fix the source, but it breaks any resource that has no HTTPS version.

Does mixed content affect SEO?

Indirectly. A page whose styles or scripts are blocked can render badly and lose visitors, and the missing padlock reduces trust. Search engines prefer HTTPS pages that load completely.