Skip to main content

How to fix: Image URL uses protocol-relative scheme (//)

An image source uses a protocol-relative URL (//example.com/image.jpg) that inherits the page protocol.

Why it matters

If the page is served over HTTP (e.g., after a redirect failure or HSTS bypass), protocol-relative image URLs also load over HTTP, enabling mixed content and potential image replacement by a network attacker.

Use explicit https:// URLs for all external resources.

How to fix it

  1. 1Replace // with https:// in all image src attributes
  2. 2This also ensures images load correctly if the HTML is shared or stored outside a web server context

Code examples

Explicit HTTPS image

HTML
<!-- BAD: //cdn.example.com/image.jpg -->
<!-- GOOD: -->
<img src="https://cdn.example.com/image.jpg" alt="Description" />

References

Detected automatically by VulnRadar. The check id is image-protocol-relative, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Image URL uses protocol-relative scheme (//)?
VulnRadar rates this low severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id image-protocol-relative, which stays the same between runs so you can filter, diff, or gate CI on it.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for image url uses protocol-relative scheme (//)

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Image URL uses protocol-relative scheme (//) fix | VulnRadar