How to fix: OpenGraph image URL is not HTTPS
The og:image meta tag uses an HTTP URL, which may cause browsers and social platforms to block the image.
Why it matters
HTTP image URLs in OG tags are blocked by major social platforms (Twitter/X, LinkedIn, Facebook) and browsers on HTTPS pages, causing missing preview images when the URL is shared. An attacker on the network can also replace the HTTP image with their own content.
All OpenGraph image URLs must use HTTPS.
How to fix it
- 1Change og:image content from http:// to https://
- 2Ensure the image server has a valid TLS certificate
Code examples
HTTPS og:image
<meta property="og:image" content="https://yoursite.com/preview.jpg" />References
Detected automatically by VulnRadar. The check id is open-graph-image-not-https, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is OpenGraph image URL is not HTTPS?
- 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 open-graph-image-not-https, 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.