Mixed Content Checker
This mixed content checker reads up to 25 pages of your site, from a sitemap it finds for you or a list you paste, and lists every resource an HTTPS page asks the browser to load over plain http://.
Result for
pages checked, with an insecure reference. Capped at 25 for this free check. A full crawl checks every page.
No mixed content in the HTML or linked stylesheets of the pages checked.
Files that JavaScript adds after the page loads are not visible here. Your browser's developer console lists any it blocks or upgrades.
No problems found on the pages checked.
-
- (relative, made http:// by the page's base tag)
No mixed content
That was a sample. Check every page for mixed content.
Crawl Cove runs its mixed content check (mixed-content) on every HTTPS page it crawls and flags each page that loads an image over http://, with the addresses to change, so an old logo URL left in one template shows up on every page that uses it, not only the 25 checked here.
Download Crawl Cove freeNote
Each one is sorted by what a current browser does with it: scripts, stylesheets, iframes and fonts are blocked outright, while images, audio and video are retried over https:// and dropped if that fails. It reads srcset candidates, inline styles and the stylesheets the pages link to, flags forms that submit to an http:// address, and tries the https:// address of each insecure file once, so the fix is either "change the scheme" or "host it somewhere secure". Enter a single page to check just that page.
Use this tool often? Bookmark this page, so it is one click away next time.
Email me this result
Want a copy for your records or a client? Leave your email and we'll send you this result. It is written by a real person at Crawl Cove, not an automated blast, so it may take a little while to arrive. We'll only use your address to send it, unless you also tick the box below. Privacy policy.
Got it. We'll email your result to you. Nothing else lands in your inbox unless you ticked the tips box.
How to find mixed content on your site
-
Enter a page or a sitemap
Give it your homepage and the sitemap is found for you, or enter a sitemap URL. Or switch to Paste URLs and enter up to 25 addresses on one site, one per line. A single URL checks a single page.
-
Start with what is blocked
The insecure resources are listed with the most serious first: anything a browser refuses to load, such as a script or stylesheet, then images and media, then forms. Each shows how many of the checked pages use it.
-
Read the https:// result
Where the same file answers over https://, change http:// to https:// in the reference, or use a protocol-free path on your own domain. Where it does not, download the file and serve it from your own site, or find a secure copy.
-
Check page by page and export
Open the page list to see where each reference sits, including which stylesheet a background image comes from. Download everything as a CSV for whoever edits the templates.
What this mixed content checker looks at
For each HTTPS page it reads the HTML your server sends and collects every address the browser would fetch while building the page: script, iframe, frame, object and embed sources, stylesheet links, img src and every srcset candidate, picture sources, audio, video and video posters, url() values in style attributes and style blocks, @import rules and @font-face sources. It then reads up to ten of the stylesheets those pages link to, your own first, because a background image set in a theme file never shows in the page source. Hyperlinks to http:// sites are left out on purpose: a link is somewhere a visitor may choose to go, not something the page loads. The same goes for "http://schema.org" in JSON-LD, which is a name and not a download, and for anything inside noscript, template or an old Internet Explorer conditional comment, which a modern browser never fetches.
What is mixed content?
Mixed content is an HTTPS page that loads part of itself over plain http://. The page arrived encrypted, so the browser shows a padlock, and then a file it needs comes over a connection anyone on the same network can read or change. A tampered script can rewrite the whole page, which is why browsers treat these requests strictly. It usually appears after a move from http to https: the pages were switched, but old absolute addresses were left in templates, in content saved in the database, in a theme stylesheet, or in an embed code copied years ago.
Blocked and upgraded: active and passive mixed content
Browsers split mixed content in two. Active, or blockable, content can change the rest of the page: scripts, stylesheets, iframes, web fonts, object and embed. Every major browser refuses to load it, so the page simply breaks: a menu stops working, the layout loses its styles, a map or video frame stays blank. Passive, or upgradable, content is images, audio and video. Current Chrome, Edge and Firefox no longer load these over http://. They request the same address over https:// instead and drop the file if that fails, so what the visitor sees is a missing image. The checker labels each reference with the group it falls in and puts the blocked ones first, because those are the ones breaking pages today.
Change the scheme, or host the file yourself?
For each distinct insecure address, up to twenty per check and the most used first, the checker sends one request to the same address over https:// and reports what came back. If it answers, the fix is to change http:// to https:// where the reference is written, and the browser upgrade may already be hiding the problem in some browsers but not others. If the connection or its certificate fails, or the https:// address redirects back to http://, switching the scheme will not work: copy the file to your own site or find the provider's secure address. An error status such as 404 means the file is not at that address over https://, so check it in a browser before you switch.
How to fix mixed content
Fix it where the address is written. In a template or theme, change http:// to https:// or to a root-relative path such as /images/logo.png for files on your own domain. In content stored in a database, such as posts and pages on a content management system, run a search and replace of http://yourdomain to https://yourdomain, and take a backup first. For third-party scripts and embeds, copy a fresh embed code from the provider, which will be https:// today. For a form, change the action to the https:// address. Then run the checker again on the same pages to confirm the count is zero.
upgrade-insecure-requests and HSTS
A Content-Security-Policy header with the upgrade-insecure-requests directive tells the browser to request every http:// subresource on the page over https:// instead, including scripts and stylesheets. It is a useful safety net after a migration, but it only helps where the file exists over https://, and it hides the old addresses rather than removing them, so fix the references as well. HSTS is a different header: it makes the browser use https:// for every later request to your own domain, including its images and scripts, and does nothing for files on other hosts.
Check a page's security headers · Missing security headers: how to add each one
Insecure forms, canonicals and social images
A form on an HTTPS page that submits to an http:// address is not a load, so it is listed apart from the resources: browsers warn the visitor before the form is sent and may switch off autofill for it, which costs sign-ups. An http:// canonical tag, og:image or twitter:image is not mixed content either, because the visitor's browser never fetches it on this page. They are shown as notes, since an http:// canonical asks Google to prefer the insecure address and a social image may be fetched by platforms that refuse plain http.
Insecure canonical: what it means · Check a page's canonical
What a server-side check cannot see
This tool reads the HTML as it is served, before any JavaScript runs. A file that a script adds to the page later, and a request a script makes with fetch or XMLHttpRequest, does not appear in that HTML, so it is not reported here. To catch those, open the page in a browser with the developer tools console open: every blocked or upgraded request is logged there with its address. Pages behind a login, and pages blocked for all crawlers in robots.txt, are not fetched.
Frequently asked questions
- Is this mixed content checker free?
- Yes. It is free, needs no sign-up and no email, and the only limit is a rate limit that stops one visitor sending hundreds of checks a minute.
- What is the difference between active and passive mixed content?
- Active mixed content, such as scripts, stylesheets, iframes and fonts, can change the rest of the page, so browsers block it. Passive mixed content is images, audio and video; current Chrome, Edge and Firefox request it over https:// instead and drop it if that fails.
- How many pages can it check?
- Up to 25 pages on one site per check. From a sitemap index it follows up to 5 child sitemaps and takes the first 25 same-host URLs listed, and the result says when the sitemap listed more. Crawl Cove, the desktop crawler, checks every page it crawls and has a permanent Free plan.
- Does mixed content affect SEO?
- Not as a separate ranking factor. Google uses HTTPS as a light ranking signal and indexes the page either way, but blocked scripts and styles can break how the page renders for visitors and for Googlebot, and missing images lose their image search traffic.
- Is a link to an http:// site mixed content?
- No. A hyperlink is a page the visitor may choose to open, not something the current page loads, so browsers do not warn about it and this checker does not list it.
- Why does my browser show nothing wrong when the checker finds mixed content?
- Your browser may be upgrading the image to https:// successfully, or the reference may sit in a stylesheet or template your test page does not use. Change the address anyway: older browsers and other tools still request the http:// version.
- Does it find mixed content added by JavaScript?
- No. It reads the HTML your server sends and the stylesheets it links, before any script runs. Files added by JavaScript later appear in your browser's developer console instead.
- Does it respect robots.txt?
- Yes. Pages disallowed for all crawlers in the site's robots.txt are listed as blocked and not fetched. Redirected URLs are listed with a note rather than followed.
- Can I export or share the results?
- Yes. Download CSV gives one row per insecure reference with the page, element, type, address and https:// result. After a check the page address includes what you checked, so Copy result link gives a link that runs it again. Results are cached for fifteen minutes.
From one page to your whole site
This checks a sample of up to 25 pages. Crawl Cove runs its mixed-content check on every HTTPS page it crawls and flags each page that loads an image over http://, with the addresses to change, so an old logo URL left in one template is found on every page that uses it. See run a full site audit or compare the plans.
More free tools
More technical SEO tools →-
Website SEO Checker
Open tool → -
HTTP Header Checker
Open tool → -
Canonical Checker
Open tool →