Find http:// scripts, styles, images, and iframes on HTTPS pages before browsers block or warn on them.
- Free
- No signup
- Fast
- Privacy-friendly
Back to Category
Mixed Content Checker
Checks HTML asset URLs for http:// on HTTPS pages. Clean sites often score 100 with zero insecure assets — that is a pass, not missing data.
What is Mixed Content Checker?
An HTTPS page that still loads http:// scripts, stylesheets, or iframes is mixed content. Browsers block or warn on active mixed content; passive images often still display with insecure warnings. Paste a URL, review active vs passive findings, fix, and re-check. Agents run this inside ship-gate and frontend-supply-chain playbooks, then verify until clean — see <a href="/developers/ship-gate">ship gate</a>.
What are common questions about Mixed Content Checker?
What problem does the Mixed Content Checker solve?
It lists http:// assets embedded on https:// pages so you upgrade scripts, styles, images, and form actions to HTTPS before browsers block them.
Who needs mixed-content audits?
Frontend developers, SEO engineers, and security-minded QA run them after HTTPS migrations and theme or CDN changes.
What is active mixed content?
Active mixed content is insecure scripts, stylesheets, or iframes on an HTTPS page. Browsers commonly block these.
What is passive mixed content?
Passive mixed content is insecure images, audio, or video on an HTTPS page. Engines often warn while still displaying many passive assets.
Do protocol-relative // URLs fix mixed content?
Protocol-relative URLs inherit the page scheme. On HTTPS they become HTTPS requests when the asset host supports TLS.
How does scoring treat active vs passive?
Scoring subtracts up to 10 points per active asset (cap 40) and up to 4 per passive (cap 20). Non-HTTPS pages lose 50 points.
Are CSS url() references inside stylesheets scanned?
HTML src/href attributes are scanned. Nested url() values inside external CSS files stay outside this HTML pass.
Where does page speed context connect?
Secure asset delivery also supports performance. Load timing continues on the Page Speed Analyzer.
What are the key features of Mixed Content Checker?
Active asset detection
Passive asset detection
Form action scheme check
Page HTTPS verdict
Severity-ranked findings
Documented score formula
How do you use Mixed Content Checker?
Enter an HTTPS page URL
Run the mixed content checker
Upgrade asset URLs to HTTPS
Why mixed content still appears after “full HTTPS”
Migrations often update the HTML document to HTTPS while leaving hard-coded http:// in older CMS fields, widget embeds, email-captured HTML, or third-party scripts. W3C Mixed Content specifications separate active types (scripts, styles, frames — alter behavior) from passive types (images, media — display only).
Active HTTP scripts on HTTPS pages break secure-context guarantees and are blocked in modern browsers — features simply never run. Passive HTTP images create “Not secure” warnings that erode trust beside checkout and lead forms. HTTP Archive Web Almanac crawls continue to track HTTPS adoption; leftover HTTP asset references are the long tail this checker targets.
Use cases: cutovers, embeds, and client QA
HTTPS cutover week — Run home, product, checkout, and top landing pages; prioritize active findings (scripts/CSS/iframes) before passive image cleanup.
Third-party embeds — Old video, chat, or ad snippets often ship http:// script hosts; evidence lists name the exact URL to replace.
Media library debt — Product images stored with absolute http:// in the database surface as passive findings.
Agency handoff — Include a clean mixed-content report beside performance checks on Page Speed Analyzer before go-live.
Scope limits of the HTML pass
This pass reads HTML-referenced src, href, and form action attributes. Nested url() inside downloaded CSS files and assets injected only after client hydration are out of scope for the first-HTML parse. Protocol-relative URLs on HTTPS pages are not mixed content when the host serves TLS.
Fix pattern: upgrade each evidence URL to HTTPS (or protocol-relative / root-relative on TLS-ready hosts). Active items first — they block functionality; passive items next for trust and console cleanliness.
Use Mixed Content Checker three ways
The free Mixed Content Checker on this page works in your browser. The same workflow is available via REST API for apps and via the remote MCP server for Cursor, Claude, and other agents — one API key, one plan, one quota. This tool is part of the seo-apis module under Digital Tools.
Agents close the full job with run_playbook ship-gate, then verify until pass — see ship gate.
- Free in browserUse Mixed Content Checker here — no account required.
- REST APICall from your server with
X-Api-Key. - Remote MCP serverSame job from Cursor or Claude via the ToolYour remote MCP server — one API key with REST.
- 1. Get an API keySign in and open Dashboard → API Keys (works for REST and MCP).
- 2. Call or connectUse the REST API from your server, or paste the MCP URL into your agent config.
- 3. Same key & creditsREST and MCP share one API key and monthly credit quota with this browser tool when the tool is API-backed.
Which technical SEO tools sit in this cluster?
- Page speed analyzer
Load and performance signals for a URL.
- Robots.txt checker
Crawl allow/deny rules and common mistakes.
- Sitemap XML validator
Sitemap coverage and crawl-load indicators.
- Canonical URL checker
Self-canonical, chains, and conflicts.
- HTTP status checker
Final status codes for publish and crawl hygiene.
Where does this job fit on ToolYour?
Which security checks pair with this SEO workflow?
Where do you browse more digital tools tools?
- Digital Tools tools
Browse the full Digital Tools category on ToolYour.
- Developer Tools tools
Format JSON, encode Base64/URL, mint UUIDs, convert timestamps, and test regex in the browser. REST and MCP sh
- Marketing Tools tools
Build UTM links, check ads copy limits, QA email subjects, and calculate ROAS/CPC/CTR — free in the browser; R
