Warum ist das wichtig?
When an HTTPS page loads HTTP resources (images, scripts, CSS), the browser shows a security warning. Modern browsers completely block active mixed content (scripts, iframes). This damages both security and trust.
Wie beheben Sie es?
Replace all http:// URLs in your HTML, CSS and JavaScript with https:// or relative URLs (//). Check database-stored URLs. Set a Content Security Policy with upgrade-insecure-requests.
Dieser Check bewertet von 0 bis 100. Unter 50 ist ein Fail, 50 bis 89 eine Warnung, 90 oder höher ist gut. Nach jedem Crawl sehen Sie die Note pro Seite im Report, mit einer kurzen Erklärung.
Häufige Fragen
Detects insecure HTTP resources on HTTPS pages.
When an HTTPS page loads HTTP resources (images, scripts, CSS), the browser shows a security warning. Modern browsers completely block active mixed content (scripts, iframes). This damages both security and trust.
Replace all http:// URLs in your HTML, CSS and JavaScript with https:// or relative URLs (//). Check database-stored URLs. Set a Content Security Policy with upgrade-insecure-requests.
Beispiel
Kopieren Sie den Code unten und passen Sie Domain, Markenname und Inhalt an Ihre Situation an.
<!-- Use HTTPS for ALL resources --> <img src="https://cdn.yourdomain.com/images/logo.png"> <script src="https://cdn.yourdomain.com/js/app.js"></script> <!-- Or use relative URLs (safer) --> <img src="/images/logo.png"> <link rel="stylesheet" href="/build/assets/app.css"> <!-- CSP header: automatically upgrade HTTP to HTTPS --> <!-- Add to nginx.conf or .htaccess: --> add_header Content-Security-Policy "upgrade-insecure-requests" always;