What it means
Your home page sends neither a Content-Security-Policy with frame-ancestors nor a valid
X-Frame-Options header, or it sends X-Frame-Options with a value browsers ignore, such as
ALLOW-FROM. Any site can load your pages in an invisible frame.
Why it matters
Framing makes clickjacking possible: another site places your page under its own buttons, so a
visitor who thinks they click a game actually clicks "delete account" or "confirm payment" on your site
while signed in. Modern browsers support frame-ancestors; X-Frame-Options is the older form and still
useful as a fallback.
How to fix it
- If no one should frame your site, send
Content-Security-Policy: frame-ancestors 'none'and, for old browsers,X-Frame-Options: DENY. - If only your own pages frame it, use
frame-ancestors 'self'andX-Frame-Options: SAMEORIGIN. - To allow a partner site, list it:
frame-ancestors 'self' https://partner.example.net.ALLOW-FROMin X-Frame-Options no longer works in any current browser. - Send it as a header:
frame-ancestorsis ignored in a<meta>policy.
Check it worked
Run the HTTP and security headers check again. The Framing row should say protected, and the finding should be gone.