Warning

Other sites can frame your pages

The short version

Send Content-Security-Policy: frame-ancestors 'self' (or X-Frame-Options: DENY).

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

  1. If no one should frame your site, send Content-Security-Policy: frame-ancestors 'none' and, for old browsers, X-Frame-Options: DENY.
  2. If only your own pages frame it, use frame-ancestors 'self' and X-Frame-Options: SAMEORIGIN.
  3. To allow a partner site, list it: frame-ancestors 'self' https://partner.example.net. ALLOW-FROM in X-Frame-Options no longer works in any current browser.
  4. Send it as a header: frame-ancestors is 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.