Mixed-Content-Checker

So verwenden Sie dieses Tool

1. 1

   Paste the full HTTPS URL of the page you want to check (for example https://example.com/pricing) into the input field.

2. 2

   Click Analyze. The tool fetches that page server-side and parses its HTML.

3. 3

   Review the results: each flagged item shows the tag and attribute (such as script.src or img.src) and the exact http:// URL found.

4. 4

   Rewrite each listed URL to https:// in your source or CMS, then re-run the check to confirm the count drops to zero.

Was ist der Mixed-Content-Checker?

Häufige Anwendungsfälle

• Confirming a freshly migrated WordPress or static site no longer hard-codes any http:// asset URLs after switching the domain to HTTPS.

• Tracking down which third-party script, font, or analytics tag is causing the browser's 'not fully secure' shield warning on a single page.

• Spot-checking a marketing landing page before launch so embedded images and iframes do not get silently blocked under HTTPS.

• Auditing a CMS-published article whose author pasted an old http:// image URL that breaks the padlock on an otherwise secure blog.

• Verifying that a CDN or reverse-proxy change did not leave a stylesheet or favicon link pointing at the insecure HTTP origin.

• Giving a client a concrete, line-by-line list of insecure references to fix rather than a vague 'your SSL is broken' complaint.

Häufig gestellte Fragen